The Git SCM plugin for Jenkins already supports this sort of thing, via inclusion and exclusion ranges (which are paths that are matched to decide whether the project should be triggered or not).
----- Original Message ----- From: [email protected] To: [email protected] At: Dec 30 2013 03:24:55 Hi all together Am Dienstag, 17. Dezember 2013 20:25:02 UTC+1 schrieb starwarsfan: I need to setup a lot of jenkins jobs, which should be triggered if something changed on certain folders on a git repository. Let's say there ist the following structure: repo - projectA - ... - projectB - ... - ... So for this example there will be two jenkins jobs, one for projectA and one for projectB and each of these jobs should be start if something is pushed into the corresponding folder. So if I push to repo/projectA, only this job should start. Additionally the amount of these folders is undefined, so it is not an option to configure the excludes by hand because if another folder is added, lets say projectFoo, the existing jobs must work as before. No ideas so far? Kind regards, Yves -- 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 [email protected]. For more options, visit https://groups.google.com/groups/opt_out. -- 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 [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
