| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Instead of re-using the user-facing `buildstream/buildstream-fedora`
image for tests (that comes with BuildStream pre-installed), use
`buildstream/testsuite-fedora` image that is supposed to be used
exclusively for these tests.
Similarly, use the dedicated `buildstream/testsuite-debian` image
instead of `buildstream/buildstream-debian`.
Fixes #458.
For related discussion, see
https://gitlab.com/BuildStream/buildstream-docker-images/issues/8.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
If --force is not specified, then we'll skip session files in
the case that all of the outputs exist.
Now setting BST_FORCE_SESSION_REBUILD when building the docs
will cause the session files to be rebuilt regardless of whether
they exist or not.
The .gitlab-ci.yml was also changed to use this and force rebuilds.
|
|
|
|
|
|
|
|
|
|
| |
Before we were creating one description file for each output,
making it easier to declare a make rule for it - but the result
was that we would have to build things more and it takes a
long time.
Instead, now we have session files which describe a series of commands
to run in a session, and each command optionally produces an output file.
|
|
|
|
|
| |
Use the gitlab cache for caching sources needed for building projects
in order to collect sample output for documentation pages.
|
|
|
|
|
|
| |
This branch fixes #312 by using a hidden toctree to include
the buildstream package and reducing the amount of allowed :orphan:
pages.
|
|
|
|
|
| |
"artifacts from all previous stages are passed by default."
https://docs.gitlab.com/ee/ci/yaml/#dependencies
|
| |
|
| |
|
|
|
|
| |
See #431
|
|
|
|
| |
needed
|
| |
|
|
|
|
|
| |
This adds a new job in the prepare stage which can be viewed in
the gitlab CI, and also produces an artifacts with the json metrics.
|
|
|
|
|
| |
This extra line shows which reports will be combined, which helps us
to more quickly debug problems in the coverage job of the .gitlab-ci.yml
|
| |
|
|
|
|
| |
So they show in order nicely in the gitlab CI UI
|
| |
|
| |
|
| |
|
|
|
|
| |
This also make the job faster: from ~1min to ~30s
|
|
|
|
|
|
|
| |
The new version today 1.7.2 causes the following build error:
Warning, treated as error:
/builds/BuildStream/buildstream/dist/buildstream/doc/source/buildstream.sandbox.rst:document isn't included in any toctree
|
|
|
|
|
| |
The sphinx_rtd_theme is a sphinx theme designed to look modern and be mobile-friendly
http://sphinx-rtd-theme.readthedocs.io/en/latest/index.html
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
When specifying a location for the integration tests cache directory,
we would previously append '/integration-cache' to whatever path we
were given. This is regarded as confusing.
See: https://gitlab.com/BuildStream/buildstream/issues/267
|
|
|
|
|
|
|
| |
Do not make any assumptions about the working directory as that varies
across repositories.
Fixes #251
|
|
|
|
|
| |
The working directory of the runner is /builds/BuildStream/buildstream,
not /builds/BuildStream.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Build it in one stage before the `pages` target, and then only
make the deployment step conditional on the branch.
|
|
|
|
|
| |
Integration tests were failing as the installed version of BuildStream
didn't support the new --hardlinks option.
|
|
|
|
|
|
|
|
|
|
|
|
| |
This commit adds an initial stage to the pipeline to build a distribution
tarball and generate some helper scripts for later CI to use to unpack it
and install it.
Then, it makes sure that all pytest and integration test runs work from
the dist tarball instead of directly from the git repo, also the docs are
built from the dist tarball.
This ensures that everything continues to work with a dist tarball at all times.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The image is rebuilt nightly which means it could change under our
feet and cause confusing breakages. The reason for these nightly
rebuilds is so that the `bst-here` script offers a reasonably fresh
version of BuildStream to users. But it also means that dependencies
could change in broken ways.
You can see the list of tags here, ordered by newness:
https://hub.docker.com/r/buildstream/buildstream-fedora/tags/
The number in one of these tag names is the "version" of the image
(which is really the number of commits in the buildstream-docker-images
repo), while the hex string identifies the commit of BuildStream that
the image contains.
When changing the Docker image (to add new dependencies, or whatever)
you will need to wait until the new tag is pushed, then modify
.gitlab-ci.yml so that it pulls the new tag.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Since commit fd91491a7619964e01d1fc8 we were passing an invalid
combination of flags to `pip3 install`.
Removing `--no-index` again since it doesn't really matter about
downloading stuff during the docs build.
Also removing `-e` which is a developer convenience ("editable
mode" where a symlink to the source tree is installed rather than the
actual files) that is not needed here.
|
|
|
|
|
| |
This avoids installing random versions of python packages
from pypi when running the pytest test suite.
|
|
|
|
|
|
|
|
|
|
| |
This means we don't download anything from PyPI during the BuildStream
tests. Everything used is already in the Docker image.
This also removes an unnecessary `pip3 install coverage` call. The
Coverage library contained in the Docker image.
This fixes #100
|
|
|
|
| |
This fixes #96
|
|
|
|
|
|
|
|
|
|
| |
This allows us to remove env vars that are now set in the image,
and some packages which are already installed in the image.
I've left Sphinx (which is needed for the documentation task) out of the
image as it pulls in a bunch of Python 2 dependencies that would bloat
the image. Although note that Python 2 is already present in the image
because Bazaar depends on it.
|
| |
|
| |
|