GitLab

Support coverage files in multi-output conda recipes

See merge request omegacen/ci-templates!47

Triggered by https://gitlab.astro-wise.org/omegacen/astro/-/merge_requests/594,
which is the first MR with a multi-output package. The coverage was
not picked up in that case.

Make GitLab releases for YYYY.MM.PATCH tags created by monthly merge

See merge request omegacen/ci-templates!46

Passing env vars around doesn't work for the release keyword.

Expose conda package build information to subsequent CI jobs

See merge request omegacen/ci-templates!45

Add autopep8 CI template

See merge request omegacen/ci-templates!44

Update documentation on conda an the monthly merge

See merge request omegacen/ci-templates!43

After running conda jobs on tags, the following failed:
https://gitlab.astro-wise.org/omegacen/common/-/pipelines/10844
This was due to the tags created by the MM job not being protected,
but the CONDA_UPLOAD_KEY (set globally by an admin) was.

This has been fixed for the common project: the tags `20*` are now
protected.

This MR adds a bit of documentation to other confused project owners
can understand what's going on.

Expand the black doc a bit more

See merge request omegacen/ci-templates!42

Update black documentation

See merge request omegacen/ci-templates!41

Add Black CI template

See merge request omegacen/ci-templates!40

Run conda and latex jobs on release branches

See merge request omegacen/ci-templates!38

Run conda and latex jobs on tags

See merge request omegacen/ci-templates!39

The tag information is needed in some jobs to get a proper version
string. This is only available pipelines triggered from tags, which
have $CI_COMMIT_TAG set.

This will lead to duplicate near-identical CI jobs for branches and
tags (which only differ in the $CI_COMMIT_TAG environment variable).
But there is no way to disable the branch CI jobs when there's also
a tag, because the branch CI job doesn't know anything about the tag
via the GitLab CI variables.

This is needed for the DPS, and it doesn't hurt other projects (I think).
Ideally, we'd use a regex in variable on the RHS of `=~` to give
project maintainers more control over the branch names and / or patterns.
But since this doesn't work (yet) in GitLab (13.4 at the time of writing)
we have to resort to spelling all the branches and patterns out
(so 'master', 'develop', 'release\/.*').

See the following issue on GitLab for progress on variables inside
regexes:

* https://gitlab.com/gitlab-org/gitlab/-/issues/25138
* https://gitlab.com/gitlab-org/gitlab-runner/-/issues/1809

Fix report extraction in case of test failure

See merge request omegacen/ci-templates!37

Report extraction has to be done in the `after_script` section because
GitLab CI terminates the execution of the `script` section after the
first error. This would mean that the reports wouldn't get extract if
the tests fail and the extraction would happen in the `script` section.
In contrast, `after_script` always gets executed.

Add unit test result reports to GitLab MRs and SonarQube

See merge request omegacen/ci-templates!36

Add inline coverage displayed in GitLab MRs

See merge request omegacen/ci-templates!35

See https://docs.gitlab.com/ee/user/project/merge_requests/test_coverage_visualization.html

Add env var to trigger conda jobs in scheduled pipelines

See merge request omegacen/ci-templates!34

As requested by Ewout, this environment variable can be set to
trigger the conda build and test jobs in scheduled pipelines.

Use biber in latex_pdf

See merge request omegacen/ci-templates!33