|
||||||||
|
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 |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.
I'm sorry Dan, I still cannot reproduce the missing "release" configuration or link issue.
I performed a checkout and test on the following configurations. All of these were on my JENKINS-27722 branch, and were executed with 'mvn clean test'
Maven Version: 3.1.0, JDK Version: 1.7.0_09 x86, OS Info: Arch: x86 Family: windows Name: windows 7 Version: 6.1 - Eclipse on Windows
Maven Version: 3.1.0, JDK Version: 1.7.0_09 x64, OS Info: Arch: amd64 Family: windows Name: windows 7 Version: 6.1 - Eclipse on Windows
Maven Version: 3.1.0, JDK Version: 1.6.0_37 x64, OS Info: Arch: amd64 Family: windows Name: windows 7 Version: 6.1 - Eclipse on Windows
Maven Version: 3.0.5, JDK Version: 1.8.0_05 x64, OS Info: Arch: amd64 Family: dos Name: windows 7 Version: 6.1 - Netbeans on Windows
Maven Version: 3.3.1, JDK Version: 1.7.0_67 x64, OS Info: Arch: amd64 Family: unix Name: linux Version: 3.13.0-24-generic - Linux
Maven Version: 2.2.1, JDK Version: 1.6.0_34 x86, OS Info: Arch: i386 Family: unix Name: linux Version: 2.6.32-73-generic-pae - Linux
And they all passed the tests successfully.
I committed a couple extra tests to check various parts of the plugin are working the way they should, I hope that helps to narrow down why it's not working.