-
Bug
-
Resolution: Not A Defect
-
Major
-
None
-
Jenkins 1.409, Parameterized Trigger Plugin 2.8, Subversion Plugin 1.25
We have a series of Jobs like this:
Job A -> Job B ----> Job C
\---> Job D
Job A and Job C / D use the same svn repo, Job B uses a subdirectory of that repo. Job A triggers Job B (and B triggers C / D) with both a set of predefined variables and with the Subversion Revision string. In the case of A -> B performing a svn checkin after A has started but before B is triggered shows that by the time Job C is triggered we do not use the same Subversion revision as Job A but rather top of tree. I don't have test data for if the change went into the subdir that Job B uses handy only A -> B -> C/D.
[JENKINS-9952] Subversion revision not passed along to all downstream jobs
Tom Rini
added a comment - Nope, just re-confirmed. Pass current build parameters and we get the current rev, not the first rev (have since moved up to 1.419).
Tom Rini
added a comment - Nope, just re-confirmed. Pass current build parameters and we get the current rev, not the first rev (have since moved up to 1.419). 
cjo9900
added a comment - You should be passing the Subversion revision parameter in both jobs A and B.
You might also want to check JENKINS-13852 which would allow the svn revisions to be passed from job A to C/D where job B uses a different svn directory.
cjo9900
added a comment - You should be passing the Subversion revision parameter in both jobs A and B.
You might also want to check JENKINS-13852 which would allow the svn revisions to be passed from job A to C/D where job B uses a different svn directory. 
ikedam
added a comment - Is this resolved?
It sounds not a bug, but a usage issue.
If not resolved, please let me know more details.
- How each job triggers downstream jobs (with what parameters).
- What revision each job checks out in cases you think wrong.
Also I want too see build.xml of all jobs where the problem happened, if it doesn't matter.
ikedam
added a comment - Is this resolved?
It sounds not a bug, but a usage issue.
If not resolved, please let me know more details.
How each job triggers downstream jobs (with what parameters).
What revision each job checks out in cases you think wrong.
Also I want too see build.xml of all jobs where the problem happened, if it doesn't matter. 
I believe if you configure the plugin to pass the current set of parameters to the downstream, it'll pass along the subversion revision parameter it got from Job A.