![]() |
|
|
|
|
Issue Type:
|
![Bug]() Bug
|
|
Affects Versions:
|
current |
|
Assignee:
|
Unassigned |
|
Components:
|
tracking-svn |
|
Created:
|
14/Jun/13 3:17 AM
|
|
Description:
|
We use the Tracking SVN Plugin to configure a number of downstream jobs to run the SVN revision that last successfully passed our commit build. These jobs are triggered by the commit build.
So the sequence should be:
1. Commit build detects change in SVN, checks out and build rev 300.
2. Commit build finishes building rev 300
3. Commit build triggers analysis build
4. Analysis build starts running and finds the last successful commit build was rev 300, so runs analysis on rev 300.
Most of the time, that works but occasionally we actually get:
1. Commit build detects change in SVN, checks out and build rev 300.
2. Commit build triggers analysis build
3. Analysis build starts running and finds the last successful commit build was rev 299, so runs analysis on rev 299.
4. Commit build finishes building rev 300
It looks like the downstream builds are being triggered before the the commit build is fully recorded as complete.
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Minor]() Minor
|
|
Reporter:
|
Adrian Sutton
|
|
|
|
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.
