glib/.gitlab-ci
Philip Withnall 0cc745f6cb ci: Include stderr output in JUnit XML report
When running tests under valgrind, the valgrind summary is printed in
stderr, and the TAP output is printed in stdout. The valgrind summary is
useful to include in the GitLab test report, so append it to the
textual failure information for failed tests.

I can’t find a better XML element in the [JUnit
schema](https://github.com/windyroad/JUnit-Schema/blob/master/JUnit.xsd)
for representing it.

Signed-off-by: Philip Withnall <withnall@endlessm.com>

Helps: #487
2019-09-02 14:16:33 +01:00
..
2019-04-30 15:37:31 +01:00
2019-07-24 13:08:06 +01:00

CI support stuff

Docker image

GitLab CI jobs run in a Docker image, defined here. To update that image (perhaps to install some more packages):

  1. Edit .gitlab-ci/Dockerfile with the changes you want
  2. Run .gitlab-ci/run-docker.sh build --base=debian --base-version=1 to build the new image (bump the version as needed)
  3. Run .gitlab-ci/run-docker.sh push --base=debian --base-version=1 to upload the new image to the GNOME GitLab Docker registry
    • If this is the first time you're doing this, you'll need to log into the registry
    • If you use 2-factor authentication on your GNOME GitLab account, you'll need to create a personal access token and use that rather than your normal password
  4. Edit .gitlab-ci.yml (in the root of this repository) to use your new image