Same git repo with multiple jenkins job creating build problems

333 views
Skip to first unread message

Gopi Polisetti

unread,
Jun 7, 2017, 11:58:52 AM6/7/17
to Jenkins Users
Hi,

Am using Git repository,  Git Repository A it has multiple solutions b, c , d , e ... , 
Each solution has one jenkins job,
Jenkin Job B 
Jenkin Job C
Jenkin Job D
------

If I change any code (B,C,D) under Repository A -  All jenkin - B,C,D job triggers build.

If I change any code related to B then Jenkins B only has to trigger 
If I Change any code related to C then Jenkins C only has to trigger not all jobs

Any solution for this

Mark Waite

unread,
Jun 11, 2017, 7:55:31 PM6/11/17
to Jenkins Users
If you're using a freestyle job or a multi-configuration job, then you could use the "Additional Behaviours" in the plugin to ignore commits from paths with the "Polling ignores commits from certain paths".

If you're using a multi-branch pipeline or using GitHub Organization Folders, you'd need to place the "skip this build" logic inside the pipeline script itself.  That's more complicated, and may motivate you to consider separating your projects into a repository per project, rather than multiple projects in a single repository.

Mark Waite

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/ed78c51d-3d83-4822-974d-37358ee59deb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Gopi Polisetti

unread,
Jun 12, 2017, 7:26:03 AM6/12/17
to Jenkins Users
I tried ""Additional Behaviours" option this will not work for multiple project changes
My project structure is like same repo it has multiple solutions. so I have created multiple Jenkins job but if any code changes in any of the project under same repo then all jenkin jobs got triggered , this should not happened. 
Reply all
Reply to author
Forward
0 new messages