| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
Note: This modifies the docker containers used for testing to supply the
pytest-timeout package.
|
|
|
|
|
|
| |
This job always takes a long time and does not really depend
on the artifacts in the 'test' phase, moving it to the 'test'
phase will reduce overall CI time.
|
|
|
|
| |
This reverts commit bea01531b984522940562866e904c83e8f9aed50.
|
|
|
|
|
|
|
|
|
| |
This hasnt been working for a while, it might be because GitLab
doesnt quite grasp that we have multiple branches to merge MRs to,
or it might be because they have change the API and broken back compat
in some way.
See: https://docs.gitlab.com/ee/ci/examples/code_quality.html
|
|
|
|
|
|
|
|
|
|
| |
Add a check to verify that the source distribution tarball that we
generate installs corrctly. It is useful to do this check as this is the
same tarball will be used when installing BuildStream via PyPI.
This check also happens indirectly in the coverage job where we install
BuildStream but this check makes it more explicit and will also cause
the CI to fail early if the tarball is not correct.
|
| |
|
|
|
|
|
|
|
| |
These new images come with pinned versions of `pytest` and `pylint`:
- `pylint`: `== 2.1.1`
- `pytest`: `>= 3.7`
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|