Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
D
dorie
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 31
    • Issues 31
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 9
    • Merge Requests 9
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
  • dorie
  • dorie
  • Merge Requests
  • !213

Merged
Opened Jul 20, 2020 by Lukas Riedel@lriedel🛀Owner12 of 12 tasks completed12/12 tasks

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

  • Overview 0
  • Commits 13
  • Pipelines 11
  • Changes 3

What does this MR do?

Update the .gitlab-ci.yml configuration to use rules. This allows to fine-tune job execution. In particular, setup and prep stage jobs for preparing the Docker files are now also executed when the respective Dockerfiles change.

Additionally, test:python-tests now has no dependencies and can run immediately.

Is there something that needs to be double checked?

  • setup stage triggers when changing docker/dune-env.dockerfile.
  • prep stage triggers when changing docker/dune-env-update.dockerfile.
  • Triggering works based on changes since last push to branch (not changes in latest commit).

Can this MR be accepted?

  • Implemented changes to .gitlab-ci.yml
    • Use rules
    • Run setup and prep stages for source file changes
    • Remove any dependencies of test:python-tests
  • [ ] Added/Updated tests
  • Added/Updated documentation
  • Pipeline passing
  • Squash option set
  • Delete branch option set
  • Added entry to CHANGELOG.md

Assignee: If the Squash option is set, check/update the commit message right before merging!

Related issues

Closes #203 (closed)

Edited Jul 21, 2020 by Lukas Riedel
Assignee
Assign to
Reviewer
Request review from
None
Milestone
None
Assign milestone
Time tracking
Reference: dorie/dorie!213
Source branch: 203-use-more-elaborate-rules-in-gitlab-ci-cd-configuration

Revert this merge request

This will create a new commit in order to revert the existing changes.

Switch branch
Cancel
A new branch will be created in your fork and a new merge request will be started.

Cherry-pick this merge request

Switch branch
Cancel
A new branch will be created in your fork and a new merge request will be started.