Normally I just run `mvn clean test`, or `mvn clean test firebug:firebug firebug:gui`. Then if everything works, I trust the mvn release:prepare & perform will work. If you are not confident it will work, you can try cutting an experimental release [1], which might be useful too if you'd like to deploy it to a test bed server. Just use -alpha in your version.
Hope that helps B [1] https://jenkins.io/blog/2013/09/23/experimental-plugins-update-center/ ________________________________ From: JordanGS <[email protected]> To: Jenkins Developers <[email protected]> Sent: Tuesday, 14 March 2017 8:42 AM Subject: Testing a plugin before release So as to avoid burning through version numbers with bad releases, i was wondering if there is a way to test to make sure everything will compile beforehand? To publish the plugin we use: mvn release:prepare release:perform The documentation says that the jenkins credentials can be verified with:mvn deploy Is there any way to verify that the build will succeed? Maybe (for maven) mvn release:prepare -DdryRun=true and to make sure that the pull to GitHub won't have issues, just ssh -T [email protected] Or is there anything else that can be used? -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/b7ede8ea-cc0f-4ca2-80d9-427a737f38e6%40googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/391913242.6212062.1489437449756%40mail.yahoo.com. For more options, visit https://groups.google.com/d/optout.
