Hello. I have a pipeline that runs and executes a commit to the same repo within that job. The commit can be seen in the gitlab commits view, but no pipeline is triggered for this commit and also no pipeline can be seen behind the commit in the commits view. Even a simple job without any requirements doesn’t run. When I commit exactly the same commit externally with the same git commands the commit DOES seem to trigger the pipeline. Anyone an idea what could be the cause or how to debug this (I could dive into the Gitlab logs, but maybe someone has a clue?)
are you using rules in your .gitlab-ci.yml files? If so, are you able to post them here?
Sarah
nope, no rules. I will create an example gitlab project to show the use case tomorow.
1 Like
Currently a warning is logged during the commit:
$ git push origin HEAD:$CI_COMMIT_REF_NAME
Warning: Permanently added the ECDSA host key for IP address ‘172.27.2.22’ to the list of known hosts.
Could this have something to do with the fact a pipeline is not triggered?
(As a workaround I’m now triggering the pipeline with a API request to gitlab)
I wouldn’t have thought so…
@danielvanmil , Were u able to find solution to this problem? I am facing similar issue. Pipeline doesnt get triggered when I make commit from my local machine. But when I make changes to the code in the GitLab UI, make manual trigger from CI page and merge requests pipeline runs. This behavior is happening after 2 changes:
- I updated git lab ee version from 11 to 14.
- Enable sast for a particular project ( Might not be related).
Now this behavior is seen for all the projects created under this gitlab instance. Looks like some setting issue. Highly appreciate if someone could shed some light on this problem.