Welcome to Software Development on Codidact!
Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.
How to disable jobs in GitLab CI after they are successfully executed
I'm working with GitLab CI. The pipelines I'm designing contain several jobs that, once executed successfully, there shouldn't be any reason to retry/rerun them. This is an example:
default:
# Cache set up
image: docker.io/library/eclipse-temurin:21-jdk-alpine
stages:
- verification
- testing
- assembly
- deployment
# Global environment variables
assess-code-quality:
...
stage: verification
build-release:
...
stage: assembly
deploy-dev:
... # manual job
stage: deployment
deploy-test:
needs: deploy-dev
... # manual job
stage: deployment
deploy-prod:
needs: deploy-test
... # manual job
stage: deployment
test-release:
...
stage: testing
verify-source-code-formatting:
...
stage: verification
I've been searching through the CI/CD YAML syntax reference, but I haven't found anything to accomplish this across the board.
To clarify, I want to make sure that jobs like assess-code-quality, build-release, and others do not allow for reruns if they complete successfully within a given pipeline, not across the pipelines.
Any help or examples would be greatly appreciated!
1 answer
I don't think there exists a straightforward solution.
Likely you can achieve this with rules but you'll have to define and finetune them on each of the jobs. (template jobs may help a bit here.) I.e. configure some jobs to only run on merges and others only on commits etc.
The last resort would be to query the gitlab API in the job's before_script and just exit if the response indicates that the job has already run. In this case the job does run though, it would just do almost nothing.
There is an issue tracking a potential solution for branch merge duplicate pipelines: https://gitlab.com/gitlab-org/gitlab/-/issues/300146
0 comment threads
1 comment thread