[JIRA] (JENKINS-15881) svn revision check failed when checking out older revision after HEAD build

[ku...@gmx.de (JIRA)]

kutzi commented on JENKINS-15881 svn revision check failed when checking out older revision after HEAD build I - or any other Jenkins developer - could fix this single error, but I wonder if Jenkins would crash (or react weirdly) at some other place then. I mean, what you're doing could be considered as an unsupported use case: usually builds only go forward in svn history, newer builds have always the same or higher revisions as the previous one. Alone the concept of a changelog for this build: what should it contains? The negation of revision N (if N is the revision of the previous build)? Who should be notified (if we have email notification or that like), if going back to the previous revision breaks the build (again)? I think this is a good question for the developers mailing list. I wonder what the real world usecase of going back to an earlier revision is. Can you explain?

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