Re: [Announce] Gerrit CI workflow to become a brand-new Jenkins plugin

[Stephen Connolly]

I recommend using the gitea plugin as a "clean" example of a branch source,
as it is relatively feature complete (gaps are api gaps in gitea itself)
and free of the rate limit and class migration noise in github and
Bitbucket branch source plugins

On Thu 7 Sep 2017 at 23:00, Luca Milanesio  wrote:

>
> On 7 Sep 2017, at 14:48, Vacelet, Manuel 
> wrote:
>
> Hi Luca (congrats to the new gerrit maintainer BTW),
>
> It does answer the question but raise a new one ;)
> Have you an ETA in mind for all this ?
>
>
> We are talking about weeks for sure, as I want to ship something fully
> documented and working.
>
> I was planning to share it as "showcase" with a Docker compose containing:
> - Gerrit 2.15 (or a pre-release)
> - Jenkins 2.x with BlueOcean
>
> I believe the coupling of BlueOcean + PolyGerrit will give the "business
> case" for many people to start adopting the two tools instead of heading to
> GitLab or similar.
>
> Luca.
>
>
> Manuel
>
>
>
> On Thu, Sep 7, 2017 at 12:22 PM, Luca Milanesio 
> wrote:
>
>> Hi Manuel,
>> I discussed the topic with Robert at the Jenkins World conference last
>> week, and we agreed that:
>>
>> 1. More work is needed on the branch discovery side: I need to flag the
>> ones coming from Gerrit Changes with a specific label
>> 2. The plugin is going to be focused on the branch source API feature:
>> Gerrit-branch-source similarly to GitHub-branch-source
>> 3. Gerrit Trigger plugin will stay anyway for his specific use-case:
>> triggering the build based on a Gerrit stream event
>>
>> Does that answer your questions?
>>
>> Luca.
>>
>> On 7 Sep 2017, at 08:08, Vacelet, Manuel 
>> wrote:
>>
>> Hi Luca,
>>
>> Jenkins World Conference is over, did you manage to showcase this new
>> plugin ?
>> What's the status and what are the plans for the future ?
>>
>> Manuel
>>
>> On Fri, Aug 18, 2017 at 11:04 AM, Luca Milanesio <
>> luca.milane...@gmail.com> wrote:
>>
>>> Hi Gerrit and Jenkins Community,
>>> after over two years of iterations and improvements of the Gerrit CI
>>> workflow (https://gerrit-ci.gerritforge.com), I have decided that is
>>> about time to extract the logic of our workflow and make it available as a
>>> brand-new Jenkins plugin!
>>>
>>> *Why?*
>>> I wanted to use the Gerrit CI validation workflow with potentially any
>>> project, including Gerrit plugins or anybody else wanting to adopt it.
>>> I could just "copy & paste" our Groovy workflow, however, that does not
>>> seem a sensible and long-term approach.
>>> I wanted to have "something more" than a pure triggering mechanism: I
>>> wanted to extend the power of Jenkisfile with the Gerrit review workflow
>>> verbs.
>>>
>>> *Why not?*
>>> Why should I write yet another Gerrit/Jenkins plugin? Isn't Gerrit
>>> Trigger Plugin (https://wiki.jenkins.io/display/JENKINS/Gerrit+Trigger)
>>> enough?
>>> We couldn't use it against gerrit-review.googlesource.com because
>>> stream events are just not accessible.
>>>
>>> There are unresolved issues about:
>>> - Stability: stream-events are based on SSH, which isn't scalable,
>>> reliable against downtime, etc.
>>> - Usability: at every JenkinsWorld conference people still come to me
>>> asking "how do I setup correct the Gerrit Trigger plugin"?
>>> - Integration: using it inside a JenkinsFile isn't that straightforward
>>> and multi-branch projects aren't supported either
>>>
>>> *What would it be?*
>>> I will publish a new plugin named "Gerrit Pipeline Plugin."
>>> The new name indicates:
>>> - Deep integration with Jenkins Pipeline
>>> - Out-of-the-box integration with Gerrit validation workflow in the
>>> pipeline
>>>
>>> A simple example scripted Jenkinsfile would be:
>>>
>>> node {
>>> checkout scm
>>>
>>> gerrit.withServer("http://gerrit:8080/;, "gerrit") {
>>>
>>> try {
>>> docker.image('gerritforge/play-sbt-8-jdk-alpine').inside {
>>> stage('Build') {
>>> sh 'sbt compile'
>>> }
>>> stage('Test') {
>>> sh 'sbt 'test'
>>> }
>>> }
>>>
>>> gerrit.review("Verified", 1, "It works !")
>>> } catch (e) {
>>> gerrit.review("Verified", -1, "Breaks the build ;-(")
>>> throw e
>>> }
>>> }
>>> }
>>>
>>> (Where:
>>> - https://gerrit-review.example.com would be the Gerrit URL
>>> - mycredentialsid would be the id of the credentials to access Gerrit)
>>>
>>> One key-aspect will be: stateless, configuration-less (apart from the
>>> credentials stored in Jenkins keychain)
>>> That means that multiple Jobs, multiple branches of the same Job, can
>>> have their own Gerrit integration defined and working out-of-the-box.
>>>
>>> No more people asking "how do I configure the Gerrit integration"?
>>> You'll just define a gerrit.withServer() { } and ... it will just work.
>>>
>>> *When?*

Re: [Announce] Gerrit CI workflow to become a brand-new Jenkins plugin

[Luca Milanesio]

> On 7 Sep 2017, at 14:48, Vacelet, Manuel  wrote:
> 
> Hi Luca (congrats to the new gerrit maintainer BTW),
> 
> It does answer the question but raise a new one ;)
> Have you an ETA in mind for all this ?

We are talking about weeks for sure, as I want to ship something fully 
documented and working.

I was planning to share it as "showcase" with a Docker compose containing:
- Gerrit 2.15 (or a pre-release)
- Jenkins 2.x with BlueOcean

I believe the coupling of BlueOcean + PolyGerrit will give the "business case" 
for many people to start adopting the two tools instead of heading to GitLab or 
similar.

Luca.

> 
> Manuel
>  
> 
> On Thu, Sep 7, 2017 at 12:22 PM, Luca Milanesio  > wrote:
> Hi Manuel,
> I discussed the topic with Robert at the Jenkins World conference last week, 
> and we agreed that:
> 
> 1. More work is needed on the branch discovery side: I need to flag the ones 
> coming from Gerrit Changes with a specific label
> 2. The plugin is going to be focused on the branch source API feature: 
> Gerrit-branch-source similarly to GitHub-branch-source
> 3. Gerrit Trigger plugin will stay anyway for his specific use-case: 
> triggering the build based on a Gerrit stream event
> 
> Does that answer your questions?
> 
> Luca.
> 
>> On 7 Sep 2017, at 08:08, Vacelet, Manuel > > wrote:
>> 
>> Hi Luca,
>> 
>> Jenkins World Conference is over, did you manage to showcase this new plugin 
>> ?
>> What's the status and what are the plans for the future ?
>> 
>> Manuel
>> 
>> On Fri, Aug 18, 2017 at 11:04 AM, Luca Milanesio > > wrote:
>> Hi Gerrit and Jenkins Community,
>> after over two years of iterations and improvements of the Gerrit CI 
>> workflow (https://gerrit-ci.gerritforge.com 
>> ), I have decided that is about time to 
>> extract the logic of our workflow and make it available as a brand-new 
>> Jenkins plugin!
>> 
>> Why?
>> I wanted to use the Gerrit CI validation workflow with potentially any 
>> project, including Gerrit plugins or anybody else wanting to adopt it.
>> I could just "copy & paste" our Groovy workflow, however, that does not seem 
>> a sensible and long-term approach.
>> I wanted to have "something more" than a pure triggering mechanism: I wanted 
>> to extend the power of Jenkisfile with the Gerrit review workflow verbs.
>> 
>> Why not?
>> Why should I write yet another Gerrit/Jenkins plugin? Isn't Gerrit Trigger 
>> Plugin (https://wiki.jenkins.io/display/JENKINS/Gerrit+Trigger 
>> ) enough?
>> We couldn't use it against gerrit-review.googlesource.com 
>>  because stream events are just not 
>> accessible.
>> 
>> There are unresolved issues about:
>> - Stability: stream-events are based on SSH, which isn't scalable, reliable 
>> against downtime, etc.
>> - Usability: at every JenkinsWorld conference people still come to me asking 
>> "how do I setup correct the Gerrit Trigger plugin"?
>> - Integration: using it inside a JenkinsFile isn't that straightforward and 
>> multi-branch projects aren't supported either
>> 
>> What would it be?
>> I will publish a new plugin named "Gerrit Pipeline Plugin."
>> The new name indicates:
>> - Deep integration with Jenkins Pipeline
>> - Out-of-the-box integration with Gerrit validation workflow in the pipeline
>> 
>> A simple example scripted Jenkinsfile would be:
>> 
>> node {
>> checkout scm
>> 
>> gerrit.withServer("http://gerrit:8080/ ", "gerrit") 
>> {
>> 
>> try {
>> docker.image('gerritforge/play-sbt-8-jdk-alpine').inside {
>> stage('Build') {
>> sh 'sbt compile'
>> }
>> stage('Test') {
>> sh 'sbt 'test'
>> }
>> }
>> 
>> gerrit.review("Verified", 1, "It works !")
>> } catch (e) {
>> gerrit.review("Verified", -1, "Breaks the build ;-(")
>> throw e
>> }
>> }
>> }
>> 
>> (Where:
>> - https://gerrit-review.example.com  
>> would be the Gerrit URL
>> - mycredentialsid would be the id of the credentials to access Gerrit)
>> 
>> One key-aspect will be: stateless, configuration-less (apart from the 
>> credentials stored in Jenkins keychain)
>> That means that multiple Jobs, multiple branches of the same Job, can have 
>> their own Gerrit integration defined and working out-of-the-box.
>> 
>> No more people asking "how do I configure the Gerrit integration"?
>> You'll just define a gerrit.withServer() { } and ... it will just work.
>> 
>> When?
>> I am planning to showcase the first prototype of the new plugin at the 
>> Jenkins World Conference 

Re: Asking for commiter access to amazon-ecs-plugin

[Baptiste Mathus]

Hello,
Seems like Jan is not active either these days or anymore at all.

So either you can see if you want to adopt this plugin (in that case please
follow the process described on the wiki), or this is likely to stay this
way until someone does I suspect.

Baptiste

Le 7 sept. 2017 17:22, "Surya yaramada`"  a écrit :

> Hi,
>  I am sorry for interrupting again but can I please know if there is a
> chance to merge the pull requests for AMAZON-ECS plugin.
>
>
> Thanks
> Surya
>
> On Thursday, August 24, 2017 at 4:12:47 PM UTC-4, Daniel Beck wrote:
>>
>>
>> > On 24. Aug 2017, at 22:09, Surya yaramada`  wrote:
>> >
>> >  Can I get any updates on this?
>> >
>>
>> There's no need for multiple emails per day. Give him a week or so. Jan
>> may well be on vacation.
>>
>> --
> 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-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/jenkinsci-dev/4f569b34-cfb3-427f-adc3-40406f9c6b3e%
> 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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CANWgJS5Z8F6JiEBzqj1U-Zh3dUgjfS8Fm-k5TPXF2se6rYgNHg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Pull request for Google Storage Plugin

['Alexandra Goultiaeva' via Jenkins Developers]

I've submitted a pull request 
 for Google 
Storage Plugin. Is there someone who can take a look?

I'm adding the ability to do substitutions to a field. I believe it was not 
there by omission, and there is an open bug 
 asking for 
it.

-- 
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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/5c21693d-d58e-4b6c-9421-2d66ba5ecf28%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Request to join Jenkins Security Team

[Daniel Beck]

> On 28. Aug 2017, at 19:29, Christopher Orr  wrote:
> 
> I'd like to request to join the security team.
> I've got all the prerequisites listed (2FA, CLA, nickname on IRC).

Thanks, and welcome aboard! Ping me on IRC and I'll finish setting you up.

-- 
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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/1D40F121-6A63-400B-80AC-1D05BD2C629C%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

Re: Request to join Jenkins CERT team

[Daniel Beck]

> On 3. Sep 2017, at 00:28, Steve Christou  wrote:
> 
> I would like to request access to the Jenkins CERT team.

Great to have you on board -- ping me on IRC and I'll finish setting everything 
up :-)

(For context, we talked about this last week when we met around Jenkins World.)

-- 
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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/4830F129-2754-40EA-BDF0-E7C38D223AE0%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

Re: How to edit plugin information page on https://plugins.jenkins.io

[Daniel Beck]

> On 7. Sep 2017, at 16:33, Tomasz Jurkiewicz  
> wrote:
> 
> I see that indeed there are plugin pages on wiki.jenkins.io, but - how do I 
> set connection between a wiki page and a plugin?
> (ie, how the system knows which wiki page belongs to which plugins?)
> 

This uses the  in the POM of the latest release -- that needs to point to 
a wiki page.

Known bug is that wiki.jenkins.io (new domain) isn't recognized yet, only 
wiki.jenkins-ci.org (old domain) is recognized. Should be fixed with the next 
deployment.

-- 
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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/90AEF6B9-275F-4940-B71E-26772589019D%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

Re: How to edit plugin information page on https://plugins.jenkins.io

[Daniel Beck]

> On 7. Sep 2017, at 16:37, Slide  wrote:
> 
> Each plugin wiki page has some metadata similar to below:
> 
> {jenkins-plugin-info:pluginId=token-macro|src=github}

For the plugin site, that's just being stripped out.

-- 
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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/D7A45541-4C11-4603-8257-3F4B1E9DC54B%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

Re: Asking for commiter access to amazon-ecs-plugin

[Surya yaramada`]

Hi,
 I am sorry for interrupting again but can I please know if there is a 
chance to merge the pull requests for AMAZON-ECS plugin.


Thanks 
Surya

On Thursday, August 24, 2017 at 4:12:47 PM UTC-4, Daniel Beck wrote:
>
>
> > On 24. Aug 2017, at 22:09, Surya yaramada`  > wrote: 
> > 
> >  Can I get any updates on this? 
> > 
>
> There's no need for multiple emails per day. Give him a week or so. Jan 
> may well be on vacation. 
>
>

-- 
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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/4f569b34-cfb3-427f-adc3-40406f9c6b3e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: How to stop the current pipeline step?

[Jesse Glick]

On Thu, Sep 7, 2017 at 9:02 AM, Ivo Bellin Salarin
 wrote:
> @Jesse: what's the preferred way to set the build result to unstable?

`setResult(UNSTABLE)`. But if your step “fails”, just throw
`AbortException` and let the caller decide what to do.

-- 
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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr0TS%3D4pmrhq79569mBCcEb6hTO92aL3NUH1o%3DmxZLCQmw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: How to edit plugin information page on https://plugins.jenkins.io

[Slide]

Each plugin wiki page has some metadata similar to below:

{jenkins-plugin-info:pluginId=token-macro|src=github}



On Thu, Sep 7, 2017 at 7:33 AM Tomasz Jurkiewicz 
wrote:

> Thank you!
>
> I see that indeed there are plugin pages on wiki.jenkins.io, but - how do
> I set connection between a wiki page and a plugin?
> (ie, how the system knows which wiki page belongs to which plugins?)
>
>
>
> 2017-09-07 16:27 GMT+02:00 Slide :
>
>> The plugins.jenkins.io site uses the wiki content as the basis for the
>> content for a plugin. So, to update the content on plugins.jenkins.io,
>> you need to edit the wiki page.
>>
>> On Thu, Sep 7, 2017 at 7:22 AM Tomasz Jurkiewicz <
>> jurkiewicz.to...@gmail.com> wrote:
>>
>>> Hi,
>>>
>>> I searched the mailing list, the docs,
>>> I logged to accounts.jenkins.io, but I can't see a way to edit that.
>>>
>>> I might have overlooked that. Can you guide me to the docs that describe
>>> it?
>>>
>>> --
>>> Tomasz Jurkiewicz
>>>
>>> --
>>> 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-dev+unsubscr...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/jenkinsci-dev/43464aba-324a-4e18-ad73-0e9a1853a19a%40googlegroups.com
>>> 
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> --
>> You received this message because you are subscribed to a topic in the
>> Google Groups "Jenkins Developers" group.
>> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/jenkinsci-dev/qPalGa_Wgjg/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to
>> jenkinsci-dev+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-dev/CAPiUgVc2AEbB0y6fJCwH8REiPeTUx6AB4Ej1vE13ctiReYs%3Diw%40mail.gmail.com
>> 
>> .
>
>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> --
> Pozdrawiam,
> Tomek Jurkiewicz
>
> --
> 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-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CAH6wY703DfcaZw3KJz_vkmx6957kHmu%3DP74aMHXjt8hqL53YCw%40mail.gmail.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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAPiUgVdYNb1b6qHOVmuZr6FET2bB4q3nUsX1i3fF2tP7HDZXfg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: How to edit plugin information page on https://plugins.jenkins.io

[Tomasz Jurkiewicz]

Thank you!

I see that indeed there are plugin pages on wiki.jenkins.io, but - how do I
set connection between a wiki page and a plugin?
(ie, how the system knows which wiki page belongs to which plugins?)



2017-09-07 16:27 GMT+02:00 Slide :

> The plugins.jenkins.io site uses the wiki content as the basis for the
> content for a plugin. So, to update the content on plugins.jenkins.io,
> you need to edit the wiki page.
>
> On Thu, Sep 7, 2017 at 7:22 AM Tomasz Jurkiewicz <
> jurkiewicz.to...@gmail.com> wrote:
>
>> Hi,
>>
>> I searched the mailing list, the docs,
>> I logged to accounts.jenkins.io, but I can't see a way to edit that.
>>
>> I might have overlooked that. Can you guide me to the docs that describe
>> it?
>>
>> --
>> Tomasz Jurkiewicz
>>
>> --
>> 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-dev+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit https://groups.google.com/d/
>> msgid/jenkinsci-dev/43464aba-324a-4e18-ad73-0e9a1853a19a%
>> 40googlegroups.com
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Jenkins Developers" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/jenkinsci-dev/qPalGa_Wgjg/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/jenkinsci-dev/CAPiUgVc2AEbB0y6fJCwH8REiPeTUx6AB4Ej1vE13ctiReYs%3Diw%
> 40mail.gmail.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Pozdrawiam,
Tomek Jurkiewicz

-- 
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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAH6wY703DfcaZw3KJz_vkmx6957kHmu%3DP74aMHXjt8hqL53YCw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: How to edit plugin information page on https://plugins.jenkins.io

[Slide]

The plugins.jenkins.io site uses the wiki content as the basis for the
content for a plugin. So, to update the content on plugins.jenkins.io, you
need to edit the wiki page.

On Thu, Sep 7, 2017 at 7:22 AM Tomasz Jurkiewicz 
wrote:

> Hi,
>
> I searched the mailing list, the docs,
> I logged to accounts.jenkins.io, but I can't see a way to edit that.
>
> I might have overlooked that. Can you guide me to the docs that describe
> it?
>
> --
> Tomasz Jurkiewicz
>
> --
> 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-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/43464aba-324a-4e18-ad73-0e9a1853a19a%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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAPiUgVc2AEbB0y6fJCwH8REiPeTUx6AB4Ej1vE13ctiReYs%3Diw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

How to edit plugin information page on https://plugins.jenkins.io

[Tomasz Jurkiewicz]

Hi,

I searched the mailing list, the docs, 
I logged to accounts.jenkins.io, but I can't see a way to edit that.

I might have overlooked that. Can you guide me to the docs that describe it?

--
Tomasz Jurkiewicz

-- 
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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/43464aba-324a-4e18-ad73-0e9a1853a19a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: How to stop the current pipeline step?

[Ivo Bellin Salarin]

@Jesse: what's the preferred way to set the build result to unstable?

Le mer. 6 sept. 2017 à 00:03, Jesse Glick  a écrit :

> Throw `AbortException`. Do _not_ attempt to set the build status yourself.
>
> --
> 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-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr249nUA1vquuFLXTFfdW3h0a7jWgeysUFzTu5efH%3DxnDA%40mail.gmail.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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAPc4eF9O4PUGp9QYPQPZ%2BJy%3DOzFibdfaEr%3DfGGncP22cYCtAUA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

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  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  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 jenkinsci-dev+unsubscr...@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
> 
> .
> 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 jenkinsci-dev+unsubscr...@googlegroups.com.
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.

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  > 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 jenkinsci-dev+unsubscr...@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.
For more options, visit https://groups.google.com/d/optout.

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  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 jenkinsci-dev+unsubscr...@googlegroups.com.
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.

Re: [Announce] Gerrit CI workflow to become a brand-new Jenkins plugin

[Luca Milanesio]

Hi Manuel,
I discussed the topic with Robert at the Jenkins World conference last week, 
and we agreed that:

1. More work is needed on the branch discovery side: I need to flag the ones 
coming from Gerrit Changes with a specific label
2. The plugin is going to be focused on the branch source API feature: 
Gerrit-branch-source similarly to GitHub-branch-source
3. Gerrit Trigger plugin will stay anyway for his specific use-case: triggering 
the build based on a Gerrit stream event

Does that answer your questions?

Luca.

> On 7 Sep 2017, at 08:08, Vacelet, Manuel  wrote:
> 
> Hi Luca,
> 
> Jenkins World Conference is over, did you manage to showcase this new plugin ?
> What's the status and what are the plans for the future ?
> 
> Manuel
> 
> On Fri, Aug 18, 2017 at 11:04 AM, Luca Milanesio  > wrote:
> Hi Gerrit and Jenkins Community,
> after over two years of iterations and improvements of the Gerrit CI workflow 
> (https://gerrit-ci.gerritforge.com ), I 
> have decided that is about time to extract the logic of our workflow and make 
> it available as a brand-new Jenkins plugin!
> 
> Why?
> I wanted to use the Gerrit CI validation workflow with potentially any 
> project, including Gerrit plugins or anybody else wanting to adopt it.
> I could just "copy & paste" our Groovy workflow, however, that does not seem 
> a sensible and long-term approach.
> I wanted to have "something more" than a pure triggering mechanism: I wanted 
> to extend the power of Jenkisfile with the Gerrit review workflow verbs.
> 
> Why not?
> Why should I write yet another Gerrit/Jenkins plugin? Isn't Gerrit Trigger 
> Plugin (https://wiki.jenkins.io/display/JENKINS/Gerrit+Trigger 
> ) enough?
> We couldn't use it against gerrit-review.googlesource.com 
>  because stream events are just not 
> accessible.
> 
> There are unresolved issues about:
> - Stability: stream-events are based on SSH, which isn't scalable, reliable 
> against downtime, etc.
> - Usability: at every JenkinsWorld conference people still come to me asking 
> "how do I setup correct the Gerrit Trigger plugin"?
> - Integration: using it inside a JenkinsFile isn't that straightforward and 
> multi-branch projects aren't supported either
> 
> What would it be?
> I will publish a new plugin named "Gerrit Pipeline Plugin."
> The new name indicates:
> - Deep integration with Jenkins Pipeline
> - Out-of-the-box integration with Gerrit validation workflow in the pipeline
> 
> A simple example scripted Jenkinsfile would be:
> 
> node {
> checkout scm
> 
> gerrit.withServer("http://gerrit:8080/ ", "gerrit") {
> 
> try {
> docker.image('gerritforge/play-sbt-8-jdk-alpine').inside {
> stage('Build') {
> sh 'sbt compile'
> }
> stage('Test') {
> sh 'sbt 'test'
> }
> }
> 
> gerrit.review("Verified", 1, "It works !")
> } catch (e) {
> gerrit.review("Verified", -1, "Breaks the build ;-(")
> throw e
> }
> }
> }
> 
> (Where:
> - https://gerrit-review.example.com  
> would be the Gerrit URL
> - mycredentialsid would be the id of the credentials to access Gerrit)
> 
> One key-aspect will be: stateless, configuration-less (apart from the 
> credentials stored in Jenkins keychain)
> That means that multiple Jobs, multiple branches of the same Job, can have 
> their own Gerrit integration defined and working out-of-the-box.
> 
> No more people asking "how do I configure the Gerrit integration"?
> You'll just define a gerrit.withServer() { } and ... it will just work.
> 
> When?
> I am planning to showcase the first prototype of the new plugin at the 
> Jenkins World Conference in San Francisco inside my "Data-Driven Pipeline 
> workshop."
> (https://jenkinsworld20162017.sched.com/event/APTd/data-driven-pipeline-workshop-free
>  
> )
> Shortly afterward, I will publish the plugin on the GerritForge's GitHub 
> account and will start the integration process into the Jenkins CI 
> organization.
> 
> Next steps?
> A second iteration of the plugin would have a Declarative pipeline equivalent 
> as well, which would require even less code required.
> A third iteration of the plugin would support BlueOcean as well, to have a 
> fully UX-integrated experience.
> The goal is to have Gerrit Code Review to be a 1st class citizen in the 
> Jenkins ecosystem :-)
> 
> So what happens to the Gerrit Trigger Plugin?
> The new plugin is not going to replace the current Gerrit Trigger Plugin, but 
> would rather represent an alternative to simpler 

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  > 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 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.
>>
>

-- 
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-dev+unsubscr...@googlegroups.com.
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.

Re: How to add support for InterruptedException to a plugin?

[Daniel Anechitoaie]

Thanks.

On Monday, September 4, 2017 at 4:10:39 AM UTC+3, Denys Digtiar wrote:
>
> You can refer to 
> https://wiki.jenkins.io/display/JENKINS/How+to+report+an+issue to learn 
> about the process.
>
> On Monday, August 28, 2017 at 11:53:45 PM UTC+10, Daniel Anechitoaie wrote:
>>
>> How do I create a request for enhancement for Jenkins?
>> I can try and do this and hopefully someone that has experience will 
>> implement it at some point, but not sore where and how to create this RFE.
>>
>>
>> On Monday, August 28, 2017 at 3:19:12 PM UTC+3, Jesse Glick wrote:
>>>
>>> On Mon, Aug 28, 2017 at 8:00 AM, Daniel Anechitoaie 
>>>  wrote: 
>>> > The problem is that that if I click cancel on the job it still runs 
>>> until by 
>>> > build step is finished and all files are zipped and uploaded and only 
>>> then 
>>> > it marks the build as aborted. 
>>> > Is there any way to check from my plugin if the job was aborted and 
>>> just 
>>> > stop wherever I am in the build? 
>>>
>>> I do not think so. Sounds like an RFE for Jenkins core / Remoting: 
>>> interrupting a synchronous remote call should `Thread.interrupt` the 
>>> corresponding thread on the remote side. 
>>>
>>

-- 
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-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/2a3a139c-f265-4aa0-ae9a-a1c01b95721b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.