Skip to content

CI: fix .docker:tags builds, add [ci tags] commit message trigger for future testing

Karl Wette requested to merge ANU-CGA/lalsuite:ci-fix-docker-tags into master

Description

The RPM/Debian jobs (i.e. .rpmbuild and .debuild) need the .ci-lalsuite-tag-build so that they're available as prerequisites for .docker:tags.

To facilitate future testing of the lalsuite-v* tags pipeline without actually creating a tag, add [ci tags] to the commit message to run the same pipeline.

(I've now changed the jobs environment variables re. deploy actions. EXECUTE_DEPLOY_ACTIONS=yes is now set for the scheduled/tag builds on lscsoft/lalsuite which are the only 2 builds which should e.g. deploy documentation, push packages/Docker images, etc. All other pipelines possibilities will not have EXECUTE_DEPLOY_ACTIONS set and therefore should be safe to run. For example this pipeline is using [ci tags] to run the docker:tags:* jobs but shouldn't try to push the tagged containers.)

API Changes and Justification

Backwards Compatible Changes

  • This change does not modify any class/function/struct/type definitions in a public C header file or any Python class/function definitions
  • This change adds new classes/functions/structs/types to a public C header file or Python module

Backwards Incompatible Changes

  • This change modifies an existing class/function/struct/type definition in a public C header file or Python module
  • This change removes an existing class/function/struct/type from a public C header file or Python module

If any of the Backwards Incompatible check boxes are ticked please provide a justification why this change is necessary and why it needs to be done in a backwards incompatible way.

Review Status

Please provide details on any reviews related to this change and and the associated reviewers.

Merge request reports