release of new version of a plugin already built by ci.jenkins.io

[Thomas Max]

Hello,

I'm maintainer of a Jenkins plugin and tried to release a new version of my plugin. 

I have a Jenkinsfile in my repo so my plugin is automatically built by ci.jenkins.io.

I've alse created a new release directly in my github repo using "Draft a new release".

Is this enough or do I need to build the plugin manually on my machine and use the release procedure described in the jenkins wiki ?

Best regards,

   Thomas

[Slide]

Hi Thomas,

For the plugin to be available in the plugin manager, you need to use the release procedure described on the wiki. This uploads the plugin file to the Jenkins infrastructure so that it can be downloaded by the plugin manager.

Regards,

Aled

--
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/5d1f15a8-bf18-400e-bc8f-c888f7ac3ca2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Thomas Max]

Hello Aled,

thanks for the information. After some hustling I managed to upload a new version. Still waiting to show up in update-center.

What I'm wondering about the ci.jenkins.io integration. Why is there no way to publish a new version of a plugin since it was already built there. It makes no sense to built it on the ci if I need to build it manually on my machine once again anyway.

Best regards,

   Thomas

[Daniel Beck]

> On 7. Sep 2017, at 11:46, Thomas Max <thoma...@qf-software.com> wrote:
>
> Why is there no way to publish a new version of a plugin since it was already built there. It makes no sense to built it on the ci if I need to build it manually on my machine once again anyway.

We still need to figure out a way to implement authorization. This was actually discussed at the contributor summit last week around Jenkins World, so we may be closer to a solution now (at least in theory) than we were before.

[Thomas Max]

Hello Daniel,

this sounds promising. Is there any issue ticket I can watch to get information about changes on this topic ?

Best regards,

   Thomas

[Slide]

The versions built in the ci infra are SNAPSHOT versions and there is no tagging done for the release. The release:prepare and release:perform do several additional steps for a release that are not done in a normal build.

--
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/7d682c64-b6fc-448e-aeaf-c40b224bfdcd%40googlegroups.com.