| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
And also refer to the user guide section instead of directly to the
tutorial, the tutorial will still be the first section of the user
guide so this is a better link target for getting started.
This is related to #528
|
|\
| |
| |
| |
| | |
.gitlab-ci.yml: Trying to fix code quality reports
See merge request BuildStream/buildstream!735
|
|/
|
|
|
|
|
|
|
| |
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
|
|\
| |
| |
| |
| | |
doc/bst2html.py: Fix deprecation warning
See merge request BuildStream/buildstream!727
|
|/
|
|
|
|
|
|
| |
This fixes the following:
"
/home/jjardon/buildstream/buildstream/doc/bst2html.py:32: DeprecationWarning: Using or importing the ABCs from 'collections' instead of from 'collections.abc' is deprecated, and in 3.8 it will stop working
from collections import Mapping
"
|
|\
| |
| |
| |
| | |
Install guide refactoring
See merge request BuildStream/buildstream!733
|
| |
| |
| |
| |
| |
| |
| |
| | |
instructions.
This obsoletes Laurence's explanation in merge request !657, and
is a part of the initiative of issue #528 to clarify which versions
users should be installing.
|
| |
| |
| |
| |
| |
| |
| |
| | |
This is not ideal as the releases are hardcoded, but I think is better
than nothing until we got a solution to automate this
This commit was originally by Javier Jardón <jjardon@gnome.org> from
merge request !661, and then later reworked into an install guide refactor.
|
| |
| |
| |
| |
| |
| |
| | |
Instead of having all of this on one page, we now have a much
simpler page for installing on distros where BuildStream is packaged
and a separate page for installing distro specific system dependencies
and installing from source code (either from PyPI or git).
|
| |
| |
| |
| |
| | |
This is referred to from the artifact install guide, and was
previously pointing directly to the source install guide.
|
|/
|
|
|
| |
This main section is just a choice of subsections, lets
make this more clear with a single level depth toctree.
|
|\
| |
| |
| |
| |
| |
| | |
Fixing some fallout in the workspace documentation additions
Closes #553
See merge request BuildStream/buildstream!732
|
| |
| |
| |
| | |
file format
|
| |
| |
| |
| |
| | |
A preventative measure against people committing the generated
html files to the wrong location.
|
| |
| |
| |
| |
| | |
Some whitespace changes to follow the style regarding empty
lines between sections.
|
| | |
|
|/ |
|
|\
| |
| |
| |
| | |
buildelement.py: remove double logging (again) as in #507
See merge request BuildStream/buildstream!730
|
|/
|
|
|
| |
This was broken again by d14d8ee29b5fcaadcfd05934de71b46221243fcd,
this commits re-applies the fix from 12fea82e12a27eccb34ef4efbaa7c6874787eb4c
|
|\
| |
| |
| |
| | |
.gitlab-ci.yml: Show timing of the 20 slowest tests
See merge request BuildStream/buildstream!716
|
|/
|
|
|
| |
This helps identifying what tests are slow or if the CI got stuck on
some of them
|
|\
| |
| |
| |
| | |
doc: Add instructions to install BuildStream via PyPI
See merge request BuildStream/buildstream!717
|
|/
|
|
|
|
|
| |
Add instructions to install and update BuildStream python package via
PyPI, and also make it the recommended method.
Part of https://gitlab.com/BuildStream/buildstream/issues/587.
|
|\
| |
| |
| |
| | |
'-k' flag not needed to run individual tests
See merge request BuildStream/buildstream!714
|
|/ |
|
|\
| |
| |
| |
| | |
Correct crash after staging tars with read-only directories
See merge request BuildStream/buildstream!713
|
| | |
|
| | |
|
|/
|
|
|
|
| |
Staging may produce directories with less than 'rwx' permissions which
will cause tempfile to throw an exception on deleting the temporary
directory if not changed.
|
|\
| |
| |
| |
| | |
tests/integration/project: Use the same alias for the alpine tarball
See merge request BuildStream/buildstream!722
|
|/
|
|
|
|
|
|
| |
This makes the integration tests use the same 'alpine' alias for the
tests as we use in the examples, this avoids a redundant download
of an extra alpine tarball in integration tests.
This is a part of #603
|
|\
| |
| |
| |
| | |
tests/integration/source-determinism.py: Use cli_integration.
See merge request BuildStream/buildstream!715
|
|/ |
|
|\
| |
| |
| |
| | |
.gitlab-ci.yml: Verify that source tarball installs correctly
See merge request BuildStream/buildstream!720
|
|/
|
|
|
|
|
|
|
|
| |
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.
|
|\
| |
| |
| |
| | |
.gitlab-ci.yml: Avoid running tests in post-merge
See merge request BuildStream/buildstream!709
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Now that we only run pre-merge CI, it makes no sense to show a badge for
the coverage and pipeline status of the last run of master.
It would make sense to show a badge for the last pipeline which
was run for the last merge request that was merged to master, but
I don't see any feature to get that information.
|
|/ |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Buildstream uses the Terminal.does_styling attribute, which was only
added in blessings 1.6.
Blessings helpfully returns an empty string when calling an nonexistent
attribute on the Terminal object, instead of failing.
Because Fedora has blessings 1.5, Buildstream thought that my terminal
couldn't handle styling, and just didn't print the status bar, silently.
Specifying the minimum version avoids this silent failure.
|
|\
| |
| |
| |
| |
| |
| | |
Remove artifact extracts when artifact expires in cache
Closes #561
See merge request BuildStream/buildstream!685
|
|/
|
|
| |
Fixes #561
|
|\
| |
| |
| |
| |
| |
| | |
Improve error message for deleted open workspaces
Closes #576
See merge request BuildStream/buildstream!703
|
|/
|
|
| |
Fixes #576.
|
|
|
|
|
|
| |
When fixing terminal notifications, I had introduced a bug
with accesses to `os.environ` which triggered KeyError, this
patch fixes it.
|
|\
| |
| |
| |
| | |
MANIFEST.in: Fix include for dev-requirements.txt
See merge request BuildStream/buildstream!704
|
|/
|
|
|
|
|
|
|
|
| |
Currently, running any setuptools commands using `setup.py` generates a
warning like so:
warning: manifest_maker: MANIFEST.in, line 21: unknown action 'dev-requirements.txt'
The syntax is invalid and got accidentally introduced in !637 but it's a
shame that this is not a warning and no obvious way to make it an error
if there are invalid things in MANIFEST.in file.
|
|\
| |
| |
| |
| | |
Don't strip pathname from debug symbol files
See merge request BuildStream/buildstream!697
|
|/
|
|
|
|
|
|
|
|
|
|
|
| |
When GDB looks for debug symbols it looks for the full path of the file
inside the configured debug-file-directory. For example, if the
debug-file-directory is set to a default of /usr/lib/debug, and you are
debugging /usr/bin/python3, GDB will look for its debug symbols at this
location: /usr/lib/debug/usr/bin/python3.
BuildStream has been putting all debug files inside /usr/lib/debug
under their $(basename), so in the above example GDB would fail to find
any debug symbols for /usr/bin/python3 because they would be in the
incorrect locatoin of /usr/lib/debug/python3.
|
|\
| |
| |
| |
| | |
Search for tags with the *.*.* patten for version
See merge request BuildStream/buildstream!601
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This has been done in a way that I hope might be able to be upstreamed
in to versioneer. This is not garanteed but it would be good if it
could be.
Please see https://github.com/warner/python-versioneer/pull/186 and
https://github.com/wsalmonct/python-versioneer/tree/feature/regexTags
for further details.
|