Testing a plugin before release

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Testing a plugin before release

JordanGS
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 git@github.com

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 [hidden email].
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.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Testing a plugin before release

Jenkins dev mailing list
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 <[hidden email]>
To: Jenkins Developers <[hidden email]>
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 [hidden email]

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 [hidden email].
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 [hidden email].
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.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Testing a plugin before release

stephenconnolly
Always good to run `mvn hpi:run` and give it some manual sanity checks first too

On 13 March 2017 at 20:37, 'Bruno P. Kinoshita' via Jenkins Developers <[hidden email]> wrote:
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 <[hidden email]>
To: Jenkins Developers <[hidden email]>
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 [hidden email]

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 [hidden email].
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 [hidden email].
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.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CA%2BnPnMxdZGMXpx3Hn2v5xiJhjraLoEV_L--tKQHzdSVLk--nXw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Testing a plugin before release

JordanGS
Thanks for the reply, not what i meant tho. I know the project compiles and builds fine but for whatever reason the command

mvn release:prepare release:perform

maybe due to a permission issue or it did the upload to maven but failed the git push. I was hoping for a sanity test for this.

On Monday, March 13, 2017 at 4:55:35 PM UTC-4, Stephen Connolly wrote:
Always good to run `mvn hpi:run` and give it some manual sanity checks first too

On 13 March 2017 at 20:37, 'Bruno P. Kinoshita' via Jenkins Developers <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="Ar2XPxh8DwAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">jenkin...@googlegroups.com> wrote:
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] <a href="https://jenkins.io/blog/2013/09/23/experimental-plugins-update-center/" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fjenkins.io%2Fblog%2F2013%2F09%2F23%2Fexperimental-plugins-update-center%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNF4qP_P9urm46V5dYBK3fwQMF2jdw&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fjenkins.io%2Fblog%2F2013%2F09%2F23%2Fexperimental-plugins-update-center%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNF4qP_P9urm46V5dYBK3fwQMF2jdw&#39;;return true;">https://jenkins.io/blog/2013/09/23/experimental-plugins-update-center/



________________________________
From: JordanGS <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="Ar2XPxh8DwAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">develop...@...>
To: Jenkins Developers <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="Ar2XPxh8DwAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">jenkin...@googlegroups.com>
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 <a href="javascript:" target="_blank" gdf-obfuscated-mailto="Ar2XPxh8DwAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">g...@...

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 <a href="javascript:" target="_blank" gdf-obfuscated-mailto="Ar2XPxh8DwAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/jenkinsci-dev/b7ede8ea-cc0f-4ca2-80d9-427a737f38e6%40googlegroups.com" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/b7ede8ea-cc0f-4ca2-80d9-427a737f38e6%40googlegroups.com&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/b7ede8ea-cc0f-4ca2-80d9-427a737f38e6%40googlegroups.com&#39;;return true;">https://groups.google.com/d/msgid/jenkinsci-dev/b7ede8ea-cc0f-4ca2-80d9-427a737f38e6%40googlegroups.com.
For more options, visit <a href="https://groups.google.com/d/optout" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;">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 <a href="javascript:" target="_blank" gdf-obfuscated-mailto="Ar2XPxh8DwAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/jenkinsci-dev/391913242.6212062.1489437449756%40mail.yahoo.com" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/391913242.6212062.1489437449756%40mail.yahoo.com&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/391913242.6212062.1489437449756%40mail.yahoo.com&#39;;return true;">https://groups.google.com/d/msgid/jenkinsci-dev/391913242.6212062.1489437449756%40mail.yahoo.com.
For more options, visit <a href="https://groups.google.com/d/optout" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;">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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/465d2bde-ef8d-4937-94ca-e3555327c82a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Testing a plugin before release

Christopher Orr
On Mon, 13 Mar 2017, at 22:34, JordanGS wrote:
> Thanks for the reply, not what i meant tho. I know the project compiles
> and
> builds fine but for whatever reason the command
>
> mvn release:prepare release:perform
>
>
> maybe due to a permission issue or it did the upload to maven but failed
> the git push. I was hoping for a sanity test for this.

Once you're ready to release, the most common issue is permissions, but
if you didn't have upload permission then you didn't burn a version
number.  Just run perform again.

Everything is else is so rare or retryable that it's not worth worrying
about.

Regards,
Chris

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/1489530915.4027564.911461440.1709CA46%40webmail.messagingengine.com.
For more options, visit https://groups.google.com/d/optout.
Loading...