We have a fully functional .gitlab-ci.yml configured and very happy with it, with one exception, it will not run automatically on a commit, push, merge, etc. Manually triggering the pipeline works as expected.
I have forked an exact copy of the repo and everything works automatically as expected.
I have gone through every single settings that I can compare and they all appear to be identical. The only difference is the repo with the issue is under a group and the forked one is not.
Has anyone experienced this or have any input on what to check next?
This is a self-hosted instance.
It is not using a shared runner. There is a project specific runner for this task.
Again, the main repo will run the pipline if manually created.
On the forked repo with identical settings, the pipeline is automatically triggered at each commit.
I am having completely opposite issue. I would like to have my pipline to run only when triggered manually, but each new commit triggers new pipleline.
I had the same requirement and I couldn’t find a concrete solution. But using when: manual sort of did the same thing, although you have to work around to fit that into your solution.
I am using manual but it have multiple issues. Firstly if you set allow_fail: false that you cannot merge merge requests as long as the jobs are not either cancelled or completed. If allow_fail is not being used than there is no way of chaining jobs.
