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
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.) ...
Answer
#1: Initial revision
by
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