-
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.
