Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

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.

Post History

66%
+2 −0
Q&A How to disable jobs in GitLab CI after they are successfully executed

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.) ...

posted 27d ago by Iizuki‭

Answer
#1: Initial revision by user avatar Iizuki‭ · 2025-02-18T14:38:28Z (27 days ago)
I don't think there exists a straightforward solution.

Likely you can achieve this with [`rules`](https://docs.gitlab.com/ci/yaml/#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