SuccessfulBuildTrigger by defqault should not assume triggering project(s) belong to the same SVN repo
Reported by Jeremy Lightsmith | April 21st, 2008 @ 01:47 PM | in 1.2
The way triggered build responds to "successful build of another project" trigger is wrong, because it can only work when both projects are in the same SVN repo, and maybe not even then. The easiest way around is to make SuccessfulBuildTrigger always request the build of the latest revision (ChangeInSourceControlTrigger, on the other hand, needs to specify the revision explicitly). Another question is: what to do if one trigger asked for a specific revision, but another trigger asked for the latest (and it's not the same).
No comments found
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
Alexey Verkhovsky