|
||||||||
|
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 |
||||||||
- [JIRA] (JENKINS-14550) "Checksum m... [email protected] (JIRA)
- [JIRA] (JENKINS-14550) "Check... [email protected] (JIRA)
- [JIRA] (JENKINS-14550) "Check... [email protected] (JIRA)
- [JIRA] (JENKINS-14550) "Check... [email protected] (JIRA)
- [JIRA] (JENKINS-14550) "Check... [email protected] (JIRA)
- [JIRA] (JENKINS-14550) "Check... [email protected] (JIRA)
- [JIRA] (JENKINS-14550) "Check... [email protected] (JIRA)
- [JIRA] (JENKINS-14550) "Check... [email protected] (JIRA)
- [JIRA] (JENKINS-14550) "Check... [email protected] (JIRA)

The specific case we had was when the plugin performed an svn update on trunk that involved a revision where a file was added on a branch and then that branch was merged into trunk.
Annoyingly, we had this re-occur recently, even though we're now on what purports to be 1.34.
Anyone know how we could upgrade to 1.39?