summaryrefslogtreecommitdiff
path: root/.gitlab-ci.yml
Commit message (Collapse)AuthorAgeFilesLines
* .gitlab-ci.yml: Enable parallel testing with 2 CPUsJürg Billeter2019-02-201-1/+1
|
* .gitlab-ci: make wsl-test automatic, allow failureJonathan Maw2019-02-181-1/+1
|
* .gitlab-ci.yml: Some new test environments were added, but not collecting ↵Tristan Van Berkom2019-02-181-0/+2
| | | | | | | | coverage. The test jobs which create coverage reports need to be listed in the dependencies of the coverage job, as highlighted in issue #356.
* .gitlab-ci.yml: Remove "tests-python-3.7-stretch" jobJavier Jardón2019-02-121-10/+0
| | | | Fedora 29 includes python 3.7 so this is not needed anymore
* .gitlab-ci.yml: run all generic fedora test in current stable version:29Javier Jardón2019-02-121-5/+5
|
* .gitlab-ci.yml: Add job to run test in current Fedora:29Javier Jardón2019-02-121-0/+5
|
* .gitlab-ci.yml: Do not automatically run "test-wsl" until runner problems ↵jjardon/allow_fail_WSLJavier Jardón2019-02-111-0/+1
| | | | are sorted out
* .gitlab-ci.yml: Remove testing on Fedora 27Javier Jardón2019-02-091-6/+1
| | | | | | Fedora 27 is EOL since 2018-11-30 See https://fedoraproject.org/wiki/End_of_life
* Update testing images to include c++ compilerBenjamin Schubert2019-02-061-13/+13
|
* gitlab-ci: Add commands to be run by WSL runnersJonathan Maw2019-02-061-0/+14
|
* Add a Centos runnerBenjamin Schubert2019-01-211-0/+5
| | | | Centos is apparently different enough from fedora when running tests.
* .gitlab-ci.yml: Add overnight tests logs to artifacts.Valentin David2019-01-181-0/+3
|
* .gitlab-ci.yml: Add tests for python 3.7Chandan Singh2019-01-151-0/+10
| | | | | | We already have tests for python 3.5 and 3.6 but not 3.7. Fixes https://gitlab.com/BuildStream/buildstream/issues/838.
* .gitlab-ci.yml: Add job to attempt to update dependenciesChandan Singh2019-01-151-1/+16
| | | | | | | This will help us check if BuildStream is working with the latest version of dependencies, as per our constraints. This job is allowed to fail but its failure should signal that we need to add stricter constraints in some of our `.in` requirements files.
* .gitlab-ci.yml: Use latest bst-externaljjardon/bst_external_0_9Javier Jardón2019-01-141-1/+1
| | | | which include flatpak_repo plugin needed to build fdsdk
* .gitlab-ci.yml: Use newer image for overning aarch testsChandan Singh2019-01-141-1/+7
| | | | | | | | | | | | During recent reorganizing of `.gitlab-ci.yml` to work with `tox`, seems like we missed to update the image used by the overnight aarch tests, meaning that they currently fail due to `tox` being missing from them. While these tests will be skipped on MRs usually, here is an example of what the tests look like if they are actually run with this change: https://gitlab.com/BuildStream/buildstream/-/jobs/145449561. Fixes #859.
* .gitlab-ci.yml: Use latest freedesktop-sdk 18.08.25Javier Jardón2019-01-141-1/+1
|
* Support running test environments in parallel with `detox`Tristan Van Berkom2019-01-091-17/+11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This patch namespaces the test temp directory and the output coverage report file with the name of the environment under test, such that separately run tests do not access the same files. When running tests without tox, directly through setup.py, then the tmp directory will still be `./tmp`. * .gitignore: Added new .coverage-reports/ directory * .gitlab-ci.yml: Rely on tox to combine and report coverage, only tell tox about the COVERAGE_PREFIX so that results can be namespaced by CI job name. This change also publishes the sources and final combined `.coverage` file in an output gitlab artifact for inspection, and lists some missing dependencies to the `coverage` job. * tox.ini: Add comments and refactor main [testenv] section so that other environments dont inherit too much unrelated cruft. Generate the coverate reports in the respective {envtmpdir} so that all per-process coverage files are prefixed with a full path, ensuring that concurrent runs don't mix reports and addressing concerns raised in #844. Also implemented new `tox -e coverage` environment to combine any found coverage and print a report. * .coveragerc: Omit .tox/ directory from coverage stats Fixes issue #844
* .gitlab-ci.yml: Remove prepare stageChandan Singh2019-01-041-44/+5
| | | | | | | | | | As we now run tests using `tox`, we don't need to worry about manually packing and unpacking BuildStream. So, we can remove the preapre stage entirely. Update `coverage` and nightly jobs to appropriately cope with this change. Both these jobs now install all runtime dependencies from requirements files.
* Rename "tools" directory to "requirements"Chandan Singh2019-01-041-1/+1
| | | | | This seems like a better name for the directory, as it more closely describes the purpose of its contents.
* .gitlab-ci.yml: Update the CI to run the linter separately through toxTristan Van Berkom2019-01-031-0/+12
| | | | | This should save us some cycles in CI, and also allow the developer to more conveniently lint separately from testing.
* Move sphinx build functionality to toxChandan Singh2019-01-031-11/+4
| | | | | | | | | Currently the CI and the docs both have to duplicate the same inforation about how to gather dependencies etc, and have to use hacky ways to run them. Add a new `docs` environment to our tox setup so that building docs is as simple as running `tox -e docs`.
* .gitlab-ci.yml: Run tests using toxChandan Singh2019-01-031-13/+10
| | | | | Instead of invoking tests throung `setup.py`, use `tox` as a frontend in the CI pipelines.
* .gitlab-ci.yml: Use new testsuite images with pycodestyle 1.4.0Tristan Maat2019-01-021-8/+8
| | | | | | We need to bump the testsuite image versions to use the new pycodestyle update that allows excluding file paths, so that we can exclude generated python code.
* .gitlab-ci.yml: Update image versions where forgottenvalentindavid/netrcValentin David2018-11-291-2/+2
|
* .gitlab-ci.yml: Bump version of fd.o SDK and bst_external in overnight testsValentin David2018-11-221-2/+2
|
* gitlab-ci.yml: Extract test command as a variableBenjamin Schubert2018-11-201-3/+4
| | | | This removes the need of having it synchronized in multiple places
* gitlab-ci.yml: Add linux without brwap/ostree to ensure tests behaveBenjamin Schubert2018-11-201-0/+18
| | | | | This allows us to make sure that tests behave nicely while missing brwap and ostree.
* gitlab-ci.yml: use template for unix testsBenjamin Schubert2018-11-201-29/+12
| | | | | This makes all tests use the same template, which makes reasoning about them simpler
* gitlab-ci.yml: remove unused artifacts for unix testsBenjamin Schubert2018-11-201-1/+0
| | | | | The unix-logs is always empty, there is therefore no reasons of keeping it there
* gitlab-cy.yml: make linux-tests-template more composable.Benjamin Schubert2018-11-201-11/+16
| | | | This will allow for further de-duplication of work.
* Export variables globally for less repetition.Benjamin Schubert2018-11-201-5/+5
| | | | | This doesn't change the test behavior and enable for better composability of tests
* gitlab-ci.yml: Use CI_PROJECT_DIR instead of $(pwd) for cacheBenjamin Schubert2018-11-201-4/+3
|
* Test aarch64 only overnightValentin David2018-11-141-3/+11
|
* Run tests on aarch64Valentin David2018-11-141-5/+11
| | | | Fixes #755
* Use less fetchers in overnight build to work-around limitations from servers.Valentin David2018-11-051-0/+6
| | | | | | Issue happens with sourceware.org server. Fixes #742
* .gitlab-ci.yml: Change how coverage is recoveredDaniel Silverstone2018-10-251-2/+2
| | | | | | | We need to alter how coverage data is recovered in order to work with newer coverage tooling. Signed-off-by: Daniel Silverstone <daniel.silverstone@codethink.co.uk>
* Bump CI image tagsTristan Maat2018-10-251-6/+6
| | | | We need to do this so that the new linting errors pop up
* Forcing CI to install Sphinx 1.7.9docs_Search_not_workingPhillip Smyth2018-10-021-1/+2
| | | | | | | .gitlab-ci.yml: forced pip3 install Sphinx 1.7.9 The theme we use in our docs "sphinx_rtd_theme" Does not support the latest version of Sphinx (>1.8) This results in search functionality failing
* ci: correct freedestop-sdk version commenttiagogomes/ci-minor-tweaksTiago Gomes2018-10-011-1/+1
|
* ci: upper case variablesTiago Gomes2018-10-011-5/+5
| | | | For consistency.
* ci: add missing `-p` argumentTiago Gomes2018-09-261-1/+1
|
* ci: add ACME challengeTiago Gomes2018-09-261-1/+7
| | | | | | To finish the creation of the Let's Encrypt certificate, which will allows us to use https://docs.buildstream.build/ for accessing the documentation.
* ci: update freedesktop-sdk refTiago Gomes2018-09-261-1/+1
| | | | The current one doesn't build due server being down.
* CI: test building freedesktop-sdk overnightTiago Gomes2018-09-251-0/+43
| | | | Closes #514.
* Add tests for cyclic variables checkJosh Smith2018-08-291-5/+5
| | | | | Note: This modifies the docker containers used for testing to supply the pytest-timeout package.
* .gitlab-ci.yml: Moving code_quality job into tests phaseTristan Van Berkom2018-08-271-5/+5
| | | | | | 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.
* Revert ".gitlab-ci.yml: Avoid running tests in post-merge"Tristan Van Berkom2018-08-271-31/+0
| | | | This reverts commit bea01531b984522940562866e904c83e8f9aed50.
* .gitlab-ci.yml: Trying to fix code quality reportsTristan Van Berkom2018-08-261-5/+3
| | | | | | | | | 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
* .gitlab-ci.yml: Verify that source tarball installs correctlychandan/ci-sdist-testChandan Singh2018-08-241-0/+5
| | | | | | | | | | 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.
View Lorry Controller Status