| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
This is a helper to log messages into the plugin's log file.
|
| |
|
|
| |
should be normalized.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
|
| |
compose plugin including paths still reachable through following of
symbolic links.
Keeping reachable paths through following of symbolic links in
manifest. Can lead to ENOENT error when copying the file if target
directory of a symbolic link is not yet created. The file is anyway
copied since the real path of the file is also in the manifest.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
| |
and add accept header to avoid 406 error on some http servers (e.g alioth.debian.org).
|
| |
|
|
|
|
| |
Our problem is with 4.4.2; and 4.2 lacks some features
and fails to collect all of the coverage from sub processes,
causing our reports to drop by 10%.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This fixes a regression from the canonical-pull-urls branch that was
just merged. The `OSTreeCache.__init__()` function was connecting to
the cache, which is bad because execution would randomly freeze for
several seconds when the connection was slow.
We now only initialize remote connections where needed; this was
already introduced in 5c2ef6d076921bc0121e61efaa7a719c34ea1912 but
had regressed. I renamed the keyword arg from `fetch_remote_refs`
to `use_remote_cache` because it needs to be set for any interaction
with the remote cache, doesn't matter if they are fetches or pushes.
The initialization stage is also moved later so that we print a message
telling the user what we are up to before trying the network access.
|
| | |
|
| |
|
|
|
|
|
|
| |
This is possible now that the SSH protocol can redirect to the
appropriate pull URL.
Note that this commit makes no attempt at backwards compatibility.
Everthing will break!
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Ports can and should be specified by using proper ssh:// URL forms,
e.g:
ssh://artifacts@example.com:22200/artifacts
The alternate form of artifacts@example.com:artifacts isn't a valid
URL, and doesn't let you specify a different port. People are used
to this form due to Git continuing to use it but we should encourage
people to use proper URLs.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This change is part of issue #112 ("Artifact configuration is confusing
and fragile, need canonical push/pull urls.")
It updates the bst-artifact-receive program to send a pull URL to
clients who access it over SSH.
This requires extra configuration in the artifact cache server, so that
it knows the correct pull URL. Versions of BuildStream which contain
this commit will not be able to communicate over SSH with artifact
caches that have not been updated to the same version.
Currently this is just used to double-check user configuration, but we
can now simplify the user facing configuration for artifact caches
completely.
|
| | |
|
| |
|
|
|
|
| |
This allows running tests in parallel:
./setup.py test --addopts "-n auto"
|
| |
|
|
|
|
|
|
| |
On interruption, this makes buildstream to accept the first character of all
the possible choices as if it was the full command. This behavior has been
added to the failure screen and to the interruption screen.
Fixes https://gitlab.com/BuildStream/buildstream/issues/130
|
| |
|
|
|
|
|
| |
Used the packages names we use for the docker containers we
use for CI, which are fedora based.
Fingers crossed that this is the right set of package names.
|
| |
|
|
|
|
|
| |
Seeing random crashes with 4.4.2, these are solved by
simply using version 4.2.
Need to investigate and report proper bug to upstream for this.
|
| |
|
|
|
| |
Since these changes were effected in 3b17762a4cab23c238762ca32baa348788347473,
these stringifications are now implied and no longer needed.
|
| |
|
|
| |
integration are removed
|
| |
|
|
|
|
|
|
|
|
| |
o Some things changed in master since this patch, notably the
keyword only arguments have changed
o Enhanced the user feedback to mention removed, added and modified
files resulting from running integration
o Dont silence messages while integrating the sandbox
|
| |
|
|
|
|
|
|
| |
o Use the * parameter to denote keyword-only arguments
o Remove the docs mentioning that it is specifically for the
compose element use case, while it's only used here currently,
it is not necessarily true.
|
| |
|
|
| |
Fixes issue #147
|
| |
|
|
|
|
|
|
|
| |
New-style formatting does not implicitly convert from float to int. Add
explicit conversion to fix the following error:
ValueError: Unknown format code 'd' for object of type 'float'
Fixes: 3b17762a ("Switch old-style string formattings to new...")
|
| |
|
|
|
|
|
| |
This reverts commit d05f0f433979a6ae79667bb51d4a7a5f365941d6.
Reverting this commit, seems to consistently break the cmake
integration test when running on gitlab
|
| |
|
|
|
|
|
|
| |
On interruption, this makes buildstream to accept the first character of all
the possible choices as if it was the full command. This behavior has been
added to the failure screen and to the interruption screen.
Fixes https://gitlab.com/BuildStream/buildstream/issues/130
|
| |
|
|
|
|
|
|
|
| |
Make this into a single paramaterized test case and test a few more
combinations:
o Ensure that excepting works with multiple targets in play
o Ensure that multiple exceptions succeed in excepting the commonly
depended elements which are otherwise referred to by the target
|
| |
|
|
| |
argument
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
Causes --except specified elements to be loaded separately
and the intersections of the except elements and the loaded
pipeline to be calculated.
This fixes issue #131
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
When extracting files from a base directory, we are normalizing
the TarInfo file names so we need to also normalize the link names
in the case of links and symlinks.
Fixes issue #155
|
| |
|
|
| |
This reproduces issue #155
|
| |
|
|
|
|
|
| |
Now that recurse is a mandatory keyword argument, the docs
should also reflect this; this must be done manually because
we override the signature here in the docstring, to hide some
private arguments.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
The 'result' field is optional, and currently used only by the internals
of {copy,move,link}_files. I think it makes sense to mandate that it's
called as a keyword arg in future.
|
| | |
|
| | |
|
