| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Current master of all those
|
| |
|
|
|
|
|
|
|
|
| |
We do want to control what version of BuildStream are we using in the CI,
not as part as the image; an update can break the build and the same commit
that built today can break tomorrow
This reverts commit 3de7f8086cfc89e11ffdf88651ab415e661e2609.
|
|
|
|
|
|
|
|
|
|
|
|
| |
YBD scans the current working directory for definition files, which is
problematic now that we store hundreds of cached Git repos and OSTree
repos in a subdir of the definitions repo.
To avoid wasting loads of time calling stat() on tens of thousands of
directories, the cache is now in a hidden directory.
This depends on a change to YBD that causes it to efficiently ignore
hidden directories: https://gitlab.com/baserock/ybd/commit/6676c4ac0
|
| |
|
|
|
|
| |
This is hopefully what has been preventing BuildStream from pushing.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Removing since the docker image contains an installation of BuildStream
and is updated nightly (as pointed out by Sam).
|
|
|
|
|
| |
By default GitLab CI fetches and re-pushes cache, given deploy stages
won't cause the git repos to change, only fetch.
|
|
|
|
|
| |
By default, GitLab CI fetches the artifacts of all previous stages.
Be explicit about which artifacts we do and don't want.
|
| |
|
|
|
|
|
| |
Should we pick up the same runner in another job, artifacts will be
reused from this path.
|
|
|
|
| |
Allows us to only perform the tasks required for each tool.
|
| |
|
|
|
|
|
|
|
|
|
| |
With the previous attempt, storing files in the cache worked OK but
restoring from the cache did not. The symlink workaround wasn't enough
as the symlink gets created /after/ the cache is restored.
Now the whole /builds tree is on a separate Docker volume, so we should
be able to really store the cache inside the build directory.
|
|
|
|
|
|
|
|
|
|
| |
It turns out that downloaded sources have never been shared between
builds. Each container running a build has a `/cache` volume, but
a new volume is created for each container so nothing is shared.
We listed certain paths inside `/cache` to be saved by GitLab CI
between runs using the "distributed runners cache" feature, but
because the paths were outside the build directory it would just ignore
them.
|
|
|
|
|
| |
These are still needed, but are set correctly in the Docker image now so
we don't need to repeat them here.
|
|
|
|
| |
This should give a massive performance improvement.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is possible since this change: https://gitlab.com/BuildStream/buildstream/commit/00e08459c4
Older versions of BuildStream will fail to parse the project.conf file
with this change; I think it's acceptable to force everyone to update
as we are still in the development stage of the BuildStream migration.
If you want to override the configuration for whatever reason you'll
now need to put this in your ~/.config/buildstream.conf file:
projects:
baserock:
artifacts:
pull-url: ...
push-url: ...
If you set a "global" artifacts configuration by doing this...
artifacts:
pull-url: ...
... it'll be ignored because the project-specific config from this
project.conf file will take precedence.
Overriding seems to be done for the whole config block, so if you
only set push-url in your buildstream.conf file it will be interpreted
to mean "set push-url, and unset pull-url" rather than "set push-url
and use the existing value of pull-url."
|
|
|
|
|
|
|
|
|
|
|
| |
In order to bypass:
Cloning repository...
Cloning into '/builds/gitlab/omnibus-gitlab'...
error: RPC failed; curl 56 SSL read: error:00000000:lib(0):func(0):reason(0), errno 104
fatal: The remote end hung up unexpectedly
fatal: early EOF
fatal: index-pack failed
|
|
|
|
|
| |
We don't want to error out here, otherwise builds will only pass on
protected branches.
|
|
|
|
|
|
|
|
|
|
|
| |
We shouldn't download artifacts to the CI workers every time somebody
pushes just to throw them away again. This should speed up no-op builds.
The functionality is implemented in two shell scripts. Context is here:
https://gitlab.com/BuildStream/buildstream/issues/77
It would be possible to do this with a single script, but I wanted to
avoid doing any argument parsing code in shell.
|
|
|
|
|
|
| |
This is a Fedora 26 image which has BuildStream's dependencies
pre-installed, which saves us waiting to `dnf install` everything
at the start of every CI job.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
This is how a runner looks like:
$ df -h
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/docker-252:1-262208-36eaa91b86966a7afa39fbdbe717bdec58bc10efc52e09accd3e8e9ee4038658 10G 144M 9.9G 2% /
tmpfs 3.9G 0 3.9G 0% /dev
tmpfs 3.9G 0 3.9G 0% /sys/fs/cgroup
/dev/vda1 79G 1.2G 75G 2% /cache
shm 64M 0 64M 0% /dev/shm
|
|
|
|
|
| |
This way we can offer an up-to-date rootfs of a build system
that can be used in a chroot to build another systems
|
|
|
|
|
|
| |
python:2.7-slim install python in /usr/local/bin instead /usr/bin,
which is making deployment extensions to fail as they expect python
to be in /usr/bin/python
|
| |
|
|
|
|
| |
Branches that follow the pattern "staging/fromybd/$1" will `git checkout ybd -b $1`
|
|
|
|
|
| |
So we have more runners available if we have serveral users using
the ci system
|
| |
|
|
|
|
|
|
| |
And remove the build of openstack.
Change-Id: I62d028000ce4e446d1722fd486bf192dbc724265
|
|
|
|
|
|
|
| |
To avoid this error:
Could not open requirements file: [Errno 2] No such file or directory: 'requirements.txt'
Change-Id: I2edbf766ac161d34773a55b5591be03db0945409
|
|
|
|
|
|
| |
system
Change-Id: Idcbb01f93eaaafe6658baf37ecab86a817814abd
|
|
|
|
| |
Change-Id: I95008108fd9e8aa6c9d3157fc748e6edc00c3802
|
|
|
|
|
|
| |
systems/weston-qt5-system-x86_64.morph
Change-Id: I2792d794d6fb9148d256d0e4db696a27750d4644
|
|
|
|
|
|
|
| |
This is the build log failing to clone glibc:
https://gitlab.com/baserock/definitions/builds/5601838
Change-Id: I3ecdee9a77ad90488bc741c60ae49d610dbb8014
|
|
|
|
|
|
|
| |
Until we know why It is failing:
https://gitlab.com/baserock/definitions/builds/5576416
Change-Id: Ib2f00d340677899e934c32d2943f0ee22624284c
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
branches
In this way, individual developers can test specific system changing
the .gitlab-co.yml file in their own branches without the need of
building the whole set of system
Everything should be built when sending a branch for merge (in a staging/ branch)
and in when it gets actually merged (master)
Change-Id: I94a60daa05b768be72eb0bc69070694939638dab
|
|
|
|
| |
Change-Id: Ice1d5513a44667ec314ed0fcb7a583b4bbfdfd98
|
|
|
|
| |
Change-Id: Ifda0f9615b9c876d93691fb08d6715eea65e4e58
|
|
|
|
| |
Change-Id: Ibd3cfb1728423f6b7c5e96d08bf7f7073d5d56d8
|
|
|
|
|
|
| |
This reverts commit fc72e0f9ec501e986839dbb0bf10dff0675e6604.
Change-Id: I1a47c123ed26a5503bce9b60024aed796821029d
|
|
|
|
| |
Change-Id: I7229e8e4b91feff9e14927c8b508be636c657fa2
|
|
|
|
| |
Change-Id: I7acae4cdb9f56d7ef6d30e82018bfe3c16785500
|
|
|
|
| |
Change-Id: If2f3d130d713b72d67a0437450bec76a83f48e20
|