Skip to content
Snippets Groups Projects

.gitlab-ci.yml: Switch to rules for determining when to run a pipeline and limit dist run to tags

Open Phileas requested to merge ci-improvements into main

https://docs.gitlab.com/ee/ci/jobs/job_control.html

We're currently using only which is deprecated:

image

This:

  • moves us to rules from only
  • makes the dist pipeline only run for tags, as we don't want it to run twice (<which breaks the api repo somehow) when we create a release branch and a tag simultaneously. we also don't want to modify a release post-release without bumping the release number (v1.3.1 vs v1.3.0) as otherwise we sacrifice user (updates) and dev (people who git switch v1.3.0) friendliness.

Merge request reports

Checking pipeline status.

Loading
Loading

Activity

Filter activity
  • Approvals
  • Assignees & reviewers
  • Comments (from bots)
  • Comments (from users)
  • Commits & branches
  • Edits
  • Labels
  • Lock status
  • Mentions
  • Merge request status
  • Tracking
  • Phileas changed title from .gitlab-ci.yml: Switch to rules for determining when to run a pipeline to .gitlab-ci.yml: Switch to rules for determining when to run a pipeline and limit dist run to tags

    changed title from .gitlab-ci.yml: Switch to rules for determining when to run a pipeline to .gitlab-ci.yml: Switch to rules for determining when to run a pipeline and limit dist run to tags

    By ave on 2023-11-26T16:20:31 (imported from GitLab)

  • Phileas added 2 commits

    added 2 commits

    • 9b19c434 - 1 commit from branch main
    • aa4b98c0 - .gitlab-ci.yml: Switch to rules/if

    Compare with previous version

    By ave on 2023-11-26T16:27:07 (imported from GitLab)

Please register or sign in to reply
Loading