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

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|

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

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

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

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


On Wed, Sep 6, 2017, 03:05 Thomas Max <[hidden email]> wrote:
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

--
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/5d1f15a8-bf18-400e-bc8f-c888f7ac3ca2%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/CAPiUgVcAT%2BbW0_ofkYu-jVejhWwKoKqd7W38T%2BSEh8XK%3DYhA0A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

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

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

Am Mittwoch, 6. September 2017 14:17:22 UTC+2 schrieb 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


On Wed, Sep 6, 2017, 03:05 Thomas Max <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="5hlFa3VIAgAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">thoma...@...> wrote:
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 <a href="http://ci.jenkins.io" target="_blank" rel="nofollow" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fci.jenkins.io\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFOz7dbDkaa430NrqJYgXhfPnQC2Q&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fci.jenkins.io\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFOz7dbDkaa430NrqJYgXhfPnQC2Q&#39;;return true;">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

--
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="5hlFa3VIAgAJ" 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/5d1f15a8-bf18-400e-bc8f-c888f7ac3ca2%40googlegroups.com?utm_medium=email&amp;utm_source=footer" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/5d1f15a8-bf18-400e-bc8f-c888f7ac3ca2%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/5d1f15a8-bf18-400e-bc8f-c888f7ac3ca2%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;">https://groups.google.com/d/msgid/jenkinsci-dev/5d1f15a8-bf18-400e-bc8f-c888f7ac3ca2%40googlegroups.com.
For more options, visit <a href="https://groups.google.com/d/optout" target="_blank" rel="nofollow" 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/00bd175e-d0fd-4a32-a574-8cd1def65632%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

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

Daniel Beck

> On 7. Sep 2017, at 11:46, Thomas Max <[hidden email]> 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.

--
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/59F3EE49-0F7A-4EF7-9C4C-44D962DD6E07%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

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

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

Am Donnerstag, 7. September 2017 12:42:04 UTC+2 schrieb Daniel Beck:

> On 7. Sep 2017, at 11:46, Thomas Max <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="lUjswNaRAgAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">thoma...@...> 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.

--
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/7d682c64-b6fc-448e-aeaf-c40b224bfdcd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

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

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.


On Thu, Sep 7, 2017, 04:51 Thomas Max <[hidden email]> wrote:
Hello Daniel,

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

Best regards,
   Thomas

Am Donnerstag, 7. September 2017 12:42:04 UTC+2 schrieb Daniel Beck:

> On 7. Sep 2017, at 11:46, Thomas Max <[hidden email]> 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.

--
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/7d682c64-b6fc-448e-aeaf-c40b224bfdcd%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/CAPiUgVf2O9mez0Zx2RfYfd4UyG69AjsuZW0P3d_wOq8SuDicJw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

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

Thomas Max
Thanks for the information. So I'll stick to the release:prepare release:perform mechanism.

Best regards,
   Thomas

Am Donnerstag, 7. September 2017 14:08:59 UTC+2 schrieb 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.


On Thu, Sep 7, 2017, 04:51 Thomas Max <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="2MJJxJSWAgAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">thoma...@...> wrote:
Hello Daniel,

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

Best regards,
   Thomas

Am Donnerstag, 7. September 2017 12:42:04 UTC+2 schrieb Daniel Beck:

> On 7. Sep 2017, at 11:46, Thomas Max <[hidden email]> 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.

--
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="2MJJxJSWAgAJ" 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/7d682c64-b6fc-448e-aeaf-c40b224bfdcd%40googlegroups.com?utm_medium=email&amp;utm_source=footer" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/7d682c64-b6fc-448e-aeaf-c40b224bfdcd%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/7d682c64-b6fc-448e-aeaf-c40b224bfdcd%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;">https://groups.google.com/d/msgid/jenkinsci-dev/7d682c64-b6fc-448e-aeaf-c40b224bfdcd%40googlegroups.com.
For more options, visit <a href="https://groups.google.com/d/optout" target="_blank" rel="nofollow" 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/ce78f5cd-9659-4d45-bf25-67c74676194e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.