Open beikov opened 5 years ago
It looks like running Jenkinsfile from SCM overwrites trigger settings, so they are gone after you run the job once. One way to go is to define pipeline code inside the job (maybe with DSL) which then starts standard Jenkinsfile, like there: https://blog.ljdelight.com/gitlab-trigger-jenkins-builds-on-merge-request/
Hey there, I was previously very happy with a freestyle job configuration that built every MR and published the results back to Gitlab. Now I switched to using a Jenkins Pipeline script and MR changes do not trigger a Jenkins build anymore. If I go to Gitlab > Settings > Integrations > Jenkins CI and "Test and save settings", jobs for all open MRs are triggered, but no jobs are started when I do a change to any of the MRs. I see that the webhook is called, it just doesn't start the job.
I read a bit about problems with Jenkinsfiles in the SCM and other issues, but I couldn't figure out the definitive configuration that I need to get this to work.
I'm using
Here is the config I'm using
Please help me find out what is necessary to be able to build every MR and also every commit pushed to master. The same configuration worked fine for freestyle jobs but not just doesn't trigger a job when changing anything on the MR.
Here is a log entry that is produced when the webhook ist triggered due to a change on an MR