Skip to content

GitLab

The TS-GitLab will have to shut down towards the end of the year — please think about migrating your projects to GitLab.com or GitHub.
(This is still a very early message, meant to keep you informed. There will be more urgent ones in the future.)

Closed
Created by Lukas Riedel@lriedelOwner

Use more elaborate "rules" in GitLab CI/CD configuration

Description

GitLab has recently introduced rules to the GitLab CI/CD configuration. rules is meant to replace except/only and is much more capable. In particular, we can run certain jobs based on changes to specific source files, which should come in handy with the Docker image jobs.

Proposal

  • Run setup and prep jobs when respective files change:

    setup:dune-env: &setup
  stage: setup
  rules:
    - changes:
        - docker/dune-env.dockerfile
  # ...

prep:update-dune: &update
  <<: *setup
  stage: prep
  allow_failure: true
  rules:
    # Run after pushes to master and tags
    - if: '$CI_COMMIT_BRANCH == "master"'
    - if: $CI_COMMIT_TAG
    # Run after Dockerfile changed. Do not allow failure then.
    - changes:
        - docker/dune-env-update.dockerfile
      allow_failure: false

  • Add empty needs for test:python-tests, as https://gitlab.com/gitlab-org/gitlab/-/issues/30631 is resolved.

How to test the implementation?

  • Pipeline passes regularly.
  • Changes to Dockerfiles trigger jobs.

Related issues

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information