-
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
Environment | Original: Jenkins 1.409, Parameterized Trigger Plugin 1., Subversion Plugin 1. | New: Jenkins 1.409, Parameterized Trigger Plugin 2.8, Subversion Plugin 1.25 |
Resolution | New: Not A Defect [ 7 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Workflow | Original: JNJira [ 140140 ] | New: JNJira + In-Review [ 188867 ] |