How to perform a plugin release to Jenkins Artifact Repository through Continuous Integration?

38 views
Skip to first unread message

Shihaaz Buhary

unread,
Apr 9, 2020, 9:42:08 AM4/9/20
to Jenkins Developers
Hi All,

I know how to do a plugin release manually by executing a few commands as mentioned in the Performing a Plugin Release documentation. I can also see a page for Continuous Integration where it mentions about buildPlugin(configurations: buildPlugin.recommendedConfigurations()). What this method actually does? Does it release the plugin to repo through CI? If not, is there a way that we can achieve both (automate the release) together in the above pages? Because I can see almost all the plugins are using only the above buildPlugin(...) method in their Jenkinsfile. Or am I missing something here? I appreciate your help on this.

Thanks,
Shihaaz

Slide

unread,
Apr 9, 2020, 10:40:17 AM4/9/20
to jenkin...@googlegroups.com
buildPlugin just wraps up a bunch of the common stuff for ci.jenkins.io for building and testing plugins for master, PRs and branches. It does not release anything to the update center. You need to do releases manually.

--
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 jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/53933abf-1a36-440a-838b-6defbb733cf2%40googlegroups.com.


--
Website: http://earl-of-code.com

Shihaaz Buhary

unread,
Apr 10, 2020, 11:23:33 AM4/10/20
to Jenkins Developers
Is that how all the plugins do the release to Jenkins Artifact Repo - manually?


On Thursday, April 9, 2020 at 8:10:17 PM UTC+5:30, slide wrote:
buildPlugin just wraps up a bunch of the common stuff for ci.jenkins.io for building and testing plugins for master, PRs and branches. It does not release anything to the update center. You need to do releases manually.

On Thu, Apr 9, 2020 at 6:42 AM Shihaaz Buhary <shih...@gmail.com> wrote:
Hi All,

I know how to do a plugin release manually by executing a few commands as mentioned in the Performing a Plugin Release documentation. I can also see a page for Continuous Integration where it mentions about buildPlugin(configurations: buildPlugin.recommendedConfigurations()). What this method actually does? Does it release the plugin to repo through CI? If not, is there a way that we can achieve both (automate the release) together in the above pages? Because I can see almost all the plugins are using only the above buildPlugin(...) method in their Jenkinsfile. Or am I missing something here? I appreciate your help on this.

Thanks,
Shihaaz

--
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 jenkin...@googlegroups.com.

Slide

unread,
Apr 10, 2020, 11:46:16 AM4/10/20
to jenkin...@googlegroups.com
Yes, all releases are done manually. There are some ideas floating around to do the deployment in an automated way, but there are some things to flush out that haven't been solved yet. It's not a hard process. You run mvn release:prepare release:perform and follow the prompts.

To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/8015df3b-5a54-4796-9831-d142a892bff6%40googlegroups.com.


--
Website: http://earl-of-code.com

Tim Jacomb

unread,
Apr 10, 2020, 12:12:38 PM4/10/20
to Jenkins Developers
There's a proposal for automating plugin release here: https://jenkins.io/jep/221
Not sure what's needed to get it going though, would be great to get done

Thanks
Tim

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAPiUgVcS4VLhzE4Q95MzBDwapKqSNLivk4Y-KyCWdzK9Jwks%2Bg%40mail.gmail.com.

Matt Sicker

unread,
Apr 14, 2020, 2:55:07 PM4/14/20
to jenkin...@googlegroups.com
Typing "mvn release:{prepare,perform}" into a terminal is about as
automated as pressing the "release" button in CI. You can even press
Ctrl-R in a terminal to find the last time you used the command and
use less keystrokes than it takes to type out ci.jenkins.io.
> To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3Bify1eu%3DFs4F9VPYw_Ai_JBySYGCTvNS%2BJdcx%2BO5yWPYPg%40mail.gmail.com.



--
Matt Sicker
Senior Software Engineer, CloudBees
Reply all
Reply to author
Forward
0 new messages