|
||||||||
|
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 [email protected].
For more options, visit https://groups.google.com/d/optout.
This is an issue for me as well. We have 200+ active branches. Every time I set up a new job, it has to process all the branches which takes days. I really only want it to run for go-forward commits.
Note that the git polling log shows:
Started on Jan 30, 2015 12:02:07 PM
Polling SCM changes on master
Using strategy: Default
[poll] Last Built Revision: Revision cd2a0430283cdbbd378900fd849caca4b2674bc1 (origin/bugfix/XYBACKLOG-12369)
What I would like is an option to be able to set the "Last Built Revision" to the latest revision in the repository when I first create a new job. In the hope that git polling would only detect future commits, not run the job for all existing branches.