Thanks for looking into this, Mark.

My use case seems simple on the surface. These are the basic requirements:

  • One single repo with all projects in different folders (ProjectA, ProjectB, etc.)
  • Jenkins has a universal jobs called 'ProjectA', 'ProjectB' and so on, that monitor all branches. This way I can have devs validate their changes and validate anything going into a release branch using one job.
  • At the same time, when polling Git, check for changes only under 'ProjectA' folder, so I don't trigger 'ProjectA' job for changes under 'ProjectB' folder.

Let me know if you have an idea on how to deal with this setup.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to