Re: Proposal: Jenkins Core PR reviewers team

[Baptiste Mathus]

+1 great idea, and feature indeed.
Thanks a lot Oleg

Le jeu. 19 sept. 2019 à 23:14, Oleg Nenashev  a
écrit :

> Looks like we have a consensus here. I will proceed with the change
> tomorrow if no negative feedback
>
> --
> 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/a5fe6214-7fb5-44a2-8ec2-9b53c6dd629c%40googlegroups.com
> .
>

-- 
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/CANWgJS6evN%2BH74BZiq%2BEK%3DReL8R1RVx4AX6qVGzG8syMHX5kew%40mail.gmail.com.

Amazon EC2 plugin issues with Windows agents

[alok kumar]

Hi All,
I have been trying to get windows agents spun up in Amazon EC2 via Jenkins
using the Amazon EC2 plugin.
The agents are getting launched fine, but, Jenkins is not able to connect
to them at all.
No matter whatever settings I try, like, I have this in my userdata section:












*$Script:ErrorActionPreference =
[System.Management.Automation.ActionPreference]::Stopmkdir
'C:\Jenkins'Enable-PSRemoting -Forcewinrm set winrm/config/service/Auth
'@{Basic="true"}'winrm set winrm/config/service
'@{AllowUnencrypted="true"}'winrm set winrm/config/winrs
'@{MaxMemoryPerShellMB="1024"}'Set-NetFirewallRule -Name
'WINRM-HTTP-In-TCP-PUBLIC' -RemoteAddress AnyNew-NetFirewallRule -Name
jenkins -DisplayName jenkins -Direction Inbound -Action Allow -Protocol TCP
-LocalPort Any -Profile AnyRestart-Service WinRMSet-ExecutionPolicy
-ExecutionPolicy Bypass -Scope LocalMachine*

This is based on all the suggestions that I could gather online, but, it
doesnt work.
I keep getting:

Waiting for WinRM to come up. Sleeping 10s.

Connecting to (xx.xx.xx.xx) with WinRM as Administrator


Can anyone please help me with some suggestion on how to get this working?

I see that F Manfred Furuholen, Julien Duchesne, *Matt Sicker *are the
maintainers of this plugin. Can you guys suggest something, please?

*I have tried with even the latest version 1.45 of the plugin and my master
is on version 2.176.3 *

Thanks
Alok

-- 
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/CAOqqq4SEQ1x1Y%2B5mRH0TCwzgqffJzj9FthSf55fJ3iU_357jmA%40mail.gmail.com.

Re: Proposal: Jenkins Core PR reviewers team

[Oleg Nenashev]

Looks like we have a consensus here. I will proceed with the change tomorrow if 
no negative feedback

-- 
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/a5fe6214-7fb5-44a2-8ec2-9b53c6dd629c%40googlegroups.com.

Certificate has expired for https://pkg.jenkins.io/

[Akram Ben Aissi]

Hi admins,

I am the maintainer of the openshift Jenkins plugins.
While building our image, we saw that the certificate for 
https://pkg.jenkins.io/redhat-stable has expired yesterday.

Can someone fix it ?
As I am lucky, it is urgent as our code freeze is tomorrow.
I pinged also on IRC, I have to be AFK for 1 hour; so letting the message 
here also.


-- 
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/c100a5f4-f5a5-4cbe-b4f6-b2aa3705b82d%40googlegroups.com.

Re: Proposal: Jenkins Core PR reviewers team

[Daniel Beck]

+1

> On 19. Sep 2019, at 13:26, Oleg Nenashev  wrote:
> 
> Hi all,
> 
> I would like to make a proposal w.r.t the Jenkins Core review process. 
> 
> As you may see from the pull requests, currently we have a pretty heavy 
> process which includes multiple reviews, labeling PRs for automatic changelog 
> drafts, and so on. This process helps us to maintain high quality of weekly 
> releases. Over the last year we have had many contributors who helped to 
> review core pull requests on a regular basis. These contributors do not have 
> WRITE permission in the repo, and they had no way no assign labels, request 
> reviews, re-trigger CI, and so on. Only jenkinsci/Core members have 
> permission to do that, and it is a serious overhead since we do not have many 
> active core maintainers in jenkinsci/Core looking at PRs.
> 
> Few months ago GitHub introduced a new TRIAGE permission for the repository 
> which basically gives permissions to manage issues/pull requests without 
> being actually able to merge them. IMO it gives us a great opportunity to 
> expand the core reviewers bandwidth and at the same time to offer a path for 
> onboarding new core maintainers (contributor => Triage => Write permissions).
> 
> What I suggest to do:
>   • Introduce a new jenkinsci/core-pr-reviewers team
>   • Grant the team TRIAGE permission in  
> https://github.com/jenkinsci/jenkins
>   • Maybe?: Add CODEOWNERS to GitHub to automatically request reviews 
> from the new team for new pull requests
>   • Invite contributors who regularly review Jenkins core pull requests: 
> alecharp, varyvol, MarkEWaite, res0nance, jvz, MRamonLeon, halkeye (sorry if 
> I missed anyone!)
> If the approach works well, later we can expand it to components which are a 
> part of the Jenkins core (libraries, modules, etc.).
> 
> What do you think?
> 
> Best regards,
> Oleg
> 
> 
> 
> 
> 
> 
> 
> 
> -- 
> 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/CAPfivLAypnU_vnh3GB3_DVDD5R2vZePjzvsuGtpvXEQTsyOrjQ%40mail.gmail.com.

-- 
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/DC096577-39A9-42BC-A1ED-6CBFE8885BC5%40beckweb.net.

Re: Proposal: Jenkins Core PR reviewers team

[Matt Sicker]

I like this idea, too.

On Thu, Sep 19, 2019 at 7:09 AM Mark Waite  wrote:
>
> I like the idea very much.  GitHub triage looks like a really nice addition 
> without granting more permissions than necessary.
>
> On Thu, Sep 19, 2019 at 5:58 AM Tim Jacomb  wrote:
>>
>> Sounds good to me
>>
>> On Thu, 19 Sep 2019 at 12:26, Oleg Nenashev  wrote:
>>>
>>> Hi all,
>>>
>>> I would like to make a proposal w.r.t the Jenkins Core review process.
>>>
>>> As you may see from the pull requests, currently we have a pretty heavy 
>>> process which includes multiple reviews, labeling PRs for automatic 
>>> changelog drafts, and so on. This process helps us to maintain high quality 
>>> of weekly releases. Over the last year we have had many contributors who 
>>> helped to review core pull requests on a regular basis. These contributors 
>>> do not have WRITE permission in the repo, and they had no way no assign 
>>> labels, request reviews, re-trigger CI, and so on. Only jenkinsci/Core 
>>> members have permission to do that, and it is a serious overhead since we 
>>> do not have many active core maintainers in jenkinsci/Core looking at PRs.
>>>
>>> Few months ago GitHub introduced a new TRIAGE permission for the repository 
>>> which basically gives permissions to manage issues/pull requests without 
>>> being actually able to merge them. IMO it gives us a great opportunity to 
>>> expand the core reviewers bandwidth and at the same time to offer a path 
>>> for onboarding new core maintainers (contributor => Triage => Write 
>>> permissions).
>>>
>>> What I suggest to do:
>>>
>>> Introduce a new jenkinsci/core-pr-reviewers team
>>> Grant the team TRIAGE permission in  https://github.com/jenkinsci/jenkins
>>> Maybe?: Add CODEOWNERS to GitHub to automatically request reviews from the 
>>> new team for new pull requests
>>> Invite contributors who regularly review Jenkins core pull requests: 
>>> alecharp, varyvol, MarkEWaite, res0nance, jvz, MRamonLeon, halkeye (sorry 
>>> if I missed anyone!)
>>>
>>> If the approach works well, later we can expand it to components which are 
>>> a part of the Jenkins core (libraries, modules, etc.).
>>>
>>> What do you think?
>>>
>>> Best regards,
>>> Oleg
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> --
>>> 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/CAPfivLAypnU_vnh3GB3_DVDD5R2vZePjzvsuGtpvXEQTsyOrjQ%40mail.gmail.com.
>>
>> --
>> 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/CAH-3BifMF%2B8X%3D8wG4Pbh4Q8cguSzx2j-RmtUmORmw10MsB7aLw%40mail.gmail.com.
>
>
>
> --
> Thanks!
> Mark Waite
>
> --
> 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/CAO49JtHVQq%2BdciSsHU0w5jVhrJ%3DYemzUqeERV7-6sCRYASfyuQ%40mail.gmail.com.



-- 
Matt Sicker
Senior Software Engineer, CloudBees

-- 
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/CAEot4oy%2BOUkozcYzErMpUqexxexX9OMx6aYRKaiFzCQcd5dJ9Q%40mail.gmail.com.

Re: Proposal: Jenkins Core PR reviewers team

[Mark Waite]

I like the idea very much.  GitHub triage looks like a really nice addition
without granting more permissions than necessary.

On Thu, Sep 19, 2019 at 5:58 AM Tim Jacomb  wrote:

> Sounds good to me
>
> On Thu, 19 Sep 2019 at 12:26, Oleg Nenashev 
> wrote:
>
>> Hi all,
>>
>> I would like to make a proposal w.r.t the Jenkins Core review process.
>>
>> As you may see from the pull requests
>> , currently we have a pretty
>> heavy process which includes multiple reviews, labeling PRs for automatic
>> changelog drafts, and so on. This process helps us to maintain high quality
>> of weekly releases. Over the last year we have had many contributors who
>> helped to review core pull requests on a regular basis. These contributors
>> do not have WRITE permission in the repo, and they had no way no assign
>> labels, request reviews, re-trigger CI, and so on. Only jenkinsci/Core
>> members have permission to do that, and it is a serious overhead since we
>> do not have many active core maintainers in jenkinsci/Core looking at PRs.
>>
>> Few months ago GitHub introduced a new TRIAGE
>> 
>>  permission
>> for the repository which basically gives permissions to manage issues/pull
>> requests without being actually able to merge them. IMO it gives us a great
>> opportunity to expand the core reviewers bandwidth and at the same time to
>> offer a path for onboarding new core maintainers (contributor => Triage =>
>> Write permissions).
>>
>> What I suggest to do:
>>
>>- Introduce a new jenkinsci/core-pr-reviewers team
>>- Grant the team TRIAGE permission in
>>https://github.com/jenkinsci/jenkins
>>- Maybe?: Add CODEOWNERS to GitHub to automatically request reviews
>>from the new team for new pull requests
>>- Invite contributors who regularly review Jenkins core pull
>>requests: alecharp , varyvol
>>, MarkEWaite
>>, res0nance
>>, jvz ,
>>MRamonLeon, halkeye  (sorry if I missed
>>anyone!)
>>
>> If the approach works well, later we can expand it to components which
>> are a part of the Jenkins core (libraries, modules, etc.).
>>
>> What do you think?
>>
>> Best regards,
>> Oleg
>>
>>
>>
>>
>>
>>
>>
>> --
>> 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/CAPfivLAypnU_vnh3GB3_DVDD5R2vZePjzvsuGtpvXEQTsyOrjQ%40mail.gmail.com
>> 
>> .
>>
> --
> 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/CAH-3BifMF%2B8X%3D8wG4Pbh4Q8cguSzx2j-RmtUmORmw10MsB7aLw%40mail.gmail.com
> 
> .
>


-- 
Thanks!
Mark Waite

-- 
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/CAO49JtHVQq%2BdciSsHU0w5jVhrJ%3DYemzUqeERV7-6sCRYASfyuQ%40mail.gmail.com.

Re: Proposal: Jenkins Core PR reviewers team

[Tim Jacomb]

Sounds good to me

On Thu, 19 Sep 2019 at 12:26, Oleg Nenashev  wrote:

> Hi all,
>
> I would like to make a proposal w.r.t the Jenkins Core review process.
>
> As you may see from the pull requests
> , currently we have a pretty
> heavy process which includes multiple reviews, labeling PRs for automatic
> changelog drafts, and so on. This process helps us to maintain high quality
> of weekly releases. Over the last year we have had many contributors who
> helped to review core pull requests on a regular basis. These contributors
> do not have WRITE permission in the repo, and they had no way no assign
> labels, request reviews, re-trigger CI, and so on. Only jenkinsci/Core
> members have permission to do that, and it is a serious overhead since we
> do not have many active core maintainers in jenkinsci/Core looking at PRs.
>
> Few months ago GitHub introduced a new TRIAGE
> 
>  permission
> for the repository which basically gives permissions to manage issues/pull
> requests without being actually able to merge them. IMO it gives us a great
> opportunity to expand the core reviewers bandwidth and at the same time to
> offer a path for onboarding new core maintainers (contributor => Triage =>
> Write permissions).
>
> What I suggest to do:
>
>- Introduce a new jenkinsci/core-pr-reviewers team
>- Grant the team TRIAGE permission in
>https://github.com/jenkinsci/jenkins
>- Maybe?: Add CODEOWNERS to GitHub to automatically request reviews
>from the new team for new pull requests
>- Invite contributors who regularly review Jenkins core pull requests:
>alecharp , varyvol
>, MarkEWaite
>, res0nance
>, jvz ,
>MRamonLeon, halkeye  (sorry if I missed
>anyone!)
>
> If the approach works well, later we can expand it to components which are
> a part of the Jenkins core (libraries, modules, etc.).
>
> What do you think?
>
> Best regards,
> Oleg
>
>
>
>
>
>
>
> --
> 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/CAPfivLAypnU_vnh3GB3_DVDD5R2vZePjzvsuGtpvXEQTsyOrjQ%40mail.gmail.com
> 
> .
>

-- 
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/CAH-3BifMF%2B8X%3D8wG4Pbh4Q8cguSzx2j-RmtUmORmw10MsB7aLw%40mail.gmail.com.

Re: Proposal: Jenkins Core PR reviewers team

[Marky Jackson]

+1 from me

{ 
"regards" : {
 "name" : “marky”,
 "phone" : "+1 (408) 464 2965”,
 "email" : “marky.r.jack...@gmail.com",
 "team" : “jackson5“,
 “role” : “software engineer"
 }
 }

> On Sep 19, 2019, at 4:26 AM, Oleg Nenashev  wrote:
> 
> Hi all,
> 
> I would like to make a proposal w.r.t the Jenkins Core review process. 
> 
> As you may see from the pull requests, currently we have a pretty heavy 
> process which includes multiple reviews, labeling PRs for automatic changelog 
> drafts, and so on. This process helps us to maintain high quality of weekly 
> releases. Over the last year we have had many contributors who helped to 
> review core pull requests on a regular basis. These contributors do not have 
> WRITE permission in the repo, and they had no way no assign labels, request 
> reviews, re-trigger CI, and so on. Only jenkinsci/Core members have 
> permission to do that, and it is a serious overhead since we do not have many 
> active core maintainers in jenkinsci/Core looking at PRs.
> 
> Few months ago GitHub introduced a new TRIAGE permission for the repository 
> which basically gives permissions to manage issues/pull requests without 
> being actually able to merge them. IMO it gives us a great opportunity to 
> expand the core reviewers bandwidth and at the same time to offer a path for 
> onboarding new core maintainers (contributor => Triage => Write permissions).
> 
> What I suggest to do:
> Introduce a new jenkinsci/core-pr-reviewers team
> Grant the team TRIAGE permission in  https://github.com/jenkinsci/jenkins
> Maybe?: Add CODEOWNERS to GitHub to automatically request reviews from the 
> new team for new pull requests
> Invite contributors who regularly review Jenkins core pull requests: 
> alecharp, varyvol, MarkEWaite, res0nance, jvz, MRamonLeon, halkeye (sorry if 
> I missed anyone!)
> If the approach works well, later we can expand it to components which are a 
> part of the Jenkins core (libraries, modules, etc.).
> 
> What do you think?
> 
> Best regards,
> Oleg
> 
> 
> 
> 
> 
> 
> 
> -- 
> 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/CAPfivLAypnU_vnh3GB3_DVDD5R2vZePjzvsuGtpvXEQTsyOrjQ%40mail.gmail.com.

-- 
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/681846C1-89AD-423E-BD7D-E9F171A8DFB7%40gmail.com.

Proposal: Jenkins Core PR reviewers team

[Oleg Nenashev]

Hi all,

I would like to make a proposal w.r.t the Jenkins Core review process.

As you may see from the pull requests
, currently we have a pretty
heavy process which includes multiple reviews, labeling PRs for automatic
changelog drafts, and so on. This process helps us to maintain high quality
of weekly releases. Over the last year we have had many contributors who
helped to review core pull requests on a regular basis. These contributors
do not have WRITE permission in the repo, and they had no way no assign
labels, request reviews, re-trigger CI, and so on. Only jenkinsci/Core
members have permission to do that, and it is a serious overhead since we
do not have many active core maintainers in jenkinsci/Core looking at PRs.

Few months ago GitHub introduced a new TRIAGE

permission
for the repository which basically gives permissions to manage issues/pull
requests without being actually able to merge them. IMO it gives us a great
opportunity to expand the core reviewers bandwidth and at the same time to
offer a path for onboarding new core maintainers (contributor => Triage =>
Write permissions).

What I suggest to do:

   - Introduce a new jenkinsci/core-pr-reviewers team
   - Grant the team TRIAGE permission in
   https://github.com/jenkinsci/jenkins
   - Maybe?: Add CODEOWNERS to GitHub to automatically request reviews from
   the new team for new pull requests
   - Invite contributors who regularly review Jenkins core pull requests:
   alecharp , varyvol
   , MarkEWaite 
   , res0nance , jvz 
   , MRamonLeon, halkeye  (sorry if I missed
   anyone!)

If the approach works well, later we can expand it to components which are
a part of the Jenkins core (libraries, modules, etc.).

What do you think?

Best regards,
Oleg

-- 
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/CAPfivLAypnU_vnh3GB3_DVDD5R2vZePjzvsuGtpvXEQTsyOrjQ%40mail.gmail.com.

Re: Proxy details

[Mez Pahlan]

If you get an instance of Jenkins via Jenkins.get() then you have access to 
a field that contains the proxy details jenkins.proxy. If you access this 
object you should be able to get the details you need.

On Thursday, 19 September 2019 07:13:06 UTC+1, selva vignesh wrote:
>
> Hi,
> How to get proxy details in Jenkins plugin development.where i am 
> developing plugin for my use, Which need to proxy details of Jenkins.
> Kindly share the example code snippet to get proxy details.
> Thanks in advance.
>
>
> Regards,
> Selva
>

-- 
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/57239e95-3169-4733-b088-7567e2a35b8f%40googlegroups.com.

Proxy details

[selva vignesh]

Hi,
How to get proxy details in Jenkins plugin development.where i am 
developing plugin for my use, Which need to proxy details of Jenkins.
Kindly share the example code snippet to get proxy details.
Thanks in advance.


Regards,
Selva

-- 
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/feddabb1-9597-4222-8a61-60dd37513c81%40googlegroups.com.