What if multiple Jenkins jobs reference the same repo? about jenkins-gitlab-hook-plugin HOT 5 CLOSED

Hi! Yes you are right, it will trigger all the Jenkins projects that are referencing the given repository.

There are a few way you can force specific projects to build:

• Specify branches
  • e.g. on one Jenkins project you can specify only the master branch to be built, and on the other you can specify other branches
  • downside is that you need to exactly know which branch is to be built, so new branches will not be built at all (until you add a new Jenkins project for that specific branch)
  • if I am not mistaking, you can event specify multiple branches e.g. origin/interesting-branches*
  • you can even use Inverse strategy for branch definition, plugin takes that into account as well
• Ignore repository during notify commit
  • this will prevent a project build from being triggered at all
  • you might also disable a Jenkins project, but this seems cleaner
• Wait for "Automatic branch project creation" feature
  • then the plugin would automatically create Jenkins projects for each new branch, based on "master" template
  • but I wouldn't expect this any time soon :-)

These are just some of the options.
I guess everything depends on why you actually need multiple Jenkins projects per one Git repository.

from jenkins-gitlab-hook-plugin.

Closing the issue due to inactivity...

from jenkins-gitlab-hook-plugin.

Hi, @elvanja! I've enjoyed fast builds with gitlab hook, thanks for the plugin. However, I have 2 jobs per branch: one for tests, one for deploys. First one triggers the latter. But since they are both pointing to the same repo they both are triggered on git push into gitlab. This leads to deploy job running before tests, which is highly undesirable behavior :)

Is there any workaround so that I can disable hook for specific job without disabling it completely? This is similar to this request in jira tracker

from jenkins-gitlab-hook-plugin.

I've managed to work around using /gitlab/notify/ hook instead of /gitlab/build_now. Deploy job without SCM polling is not triggered, but test job is triggered, if SCM polling is enabled (I've setup it to poll once a year, and that works fine). This solution is derived from #17

from jenkins-gitlab-hook-plugin.

Hi @coagulant, yes there is a workaround.
For the second Jenkins project/job, you can enable "Don't trigger a build on commit notifications".
When this plugin searches for all projects to build upon a commit from Gitlab, it skips projects with this switch turned on.

from jenkins-gitlab-hook-plugin.