![]() |
|
|
|
|
Issue Type:
|
![New Feature]() New Feature
|
|
Assignee:
|
Nicolas De Loof
|
|
Components:
|
build-flow |
|
Created:
|
31/Jan/13 6:30 PM
|
|
Description:
|
For build-flow to trigger builds based on SCM changes, it seems that it must do checkout of the SCM defined as if it were going to do a build itself. It would be desirable for build-flow to simply record the latest revision number (or hash, or whathaveyou) for the SCM in question and just check that value when deciding to trigger a build based on SCM changes.
There's really no need (in my case at least) for the build-flow project itself to do a checkout. In fact, it's highly undesirable. The projects it triggers are the only ones that need to do the checkouts.
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Major]() Major
|
|
Reporter:
|
Quentin Hartman
|
|
|
|
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/groups/opt_out.
