date:20180417

On Tue, Apr 17, 2018 at 4:45 PM, nicolas de loof
 wrote:
> Job class hierarchy is full of hand written JSON parsing

I suspect such cases are fixable, which would take some work, but on
the other hand we would get a clearer code base as a result anyway.

-- 
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/CANfRfr03rVj6r1tWfwYeO1QKeDMtDYjuc8fF0Se%2B4Rh9qbZFvg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Request for comments: Special Interest Groups (SIGs) for the Jenkins project

2018-04-17 Thread R. Tyler Croy

(replies inline)

On Tue, 17 Apr 2018, Oleg Nenashev wrote:

> Hi,
> 
> We are starting GSoC meetings next week. If you need somebody to dry-run 
> the SIG infrastructure, sign us up :)
> 
> Reasoning: Having recorded GSoC sessions would be definitely helpful so 
> that we can share meetings with students/mentors who miss meetings. OTOH I 
> am not sure whether this content is useful for other community members.
> 
> Actually I would propose to have 2 SIGs:
> 
>- GSoC - special for GSoC. All infrastructure is ready
>- Newcomer onboarding - Another SIG for newcomers in Jenkins community + 
>Q + discussions about contributor experience
>   - We could split generic GSoC meetings to there (e.g. plugin 
>   development intros & Co)

I'll add you as a manager to the Brand Account so you can use Hangouts on Air
for the GSoC discussions. I agreed that a GSoC Special Interest Group makes
sense, I don't think a "Newcomer" one does because I don't understand what the
"regular business" of the SIG would be. For example, it's very clear to me
what the purpose and mission of a GSoC SIG would be, and why they would meet
regularly.

I don't think we need to carve up everything we do into SIGs for the record, I
think there's a need for SIGs on specified "business" which requires a group's
regular attention, but that doesn't mean everything fits into the model IMHO.

If I'm misunderstanding or missing something about the mission for a
prospective Newcomer SIG, let me know.

Cheers

-- 
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/20180417215803.GP1836%40grape.lasagna.io.
For more options, visit https://groups.google.com/d/optout.

signature.asc
Description: PGP signature

Re: State of Xcode plugin??

Ah yes, it was Arnaud. Sorry

On Tuesday, April 17, 2018 at 10:48:54 PM UTC+2, Mark Waite wrote:
>
> Maybe someone else did that?  I don't have permission to grant access.
>
> Mark Waite
>
> On Tue, Apr 17, 2018, 2:45 PM Oleg Nenashev  > wrote:
>
>> IIUC Mark Waite has granted you the access. Welcome onboard!
>>
>> BR, Oleg
>>
>> On Monday, April 16, 2018 at 3:40:40 PM UTC+2, Kazuhide Takahashi wrote:
>>>
>>> Maintainers of 'Jenkins Xcode Plugin' are currently inactive, and 
>>> reflections of pull requests are delayed, so I am willing to take over 
>>> their duties.
>>> To do this, you need write access to WiKi pages and git repositories, so 
>>> please approve this.
>>>
>>> 2016年9月7日水曜日 2時37分33秒 UTC+9 Brantone:

 Curious as to the current state of Xcode plugin. Although there was a 
 recent merge last month, there hasn't been a release in almost a year and 
 a 
 list of PRs piling up.
 I've attempted to contact current maintainer about helping out, but 
 have not heard word back.
 Is there a process for such a situation??
 With changes in Jenkins 2.x and Xcode 8, would be a shame for the 
 plugin to get further behind.

 Cheers

>>> -- 
>> 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/27449f2a-86a2-43fb-8a9a-7466eefc049f%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/903a76e7-61c3-41ef-b14f-5dc73100e068%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: State of Xcode plugin??

2018-04-17 Thread Mark Waite

Maybe someone else did that?  I don't have permission to grant access.

Mark Waite

On Tue, Apr 17, 2018, 2:45 PM Oleg Nenashev  wrote:

> IIUC Mark Waite has granted you the access. Welcome onboard!
>
> BR, Oleg
>
> On Monday, April 16, 2018 at 3:40:40 PM UTC+2, Kazuhide Takahashi wrote:
>>
>> Maintainers of 'Jenkins Xcode Plugin' are currently inactive, and
>> reflections of pull requests are delayed, so I am willing to take over
>> their duties.
>> To do this, you need write access to WiKi pages and git repositories, so
>> please approve this.
>>
>> 2016年9月7日水曜日 2時37分33秒 UTC+9 Brantone:
>>>
>>> Curious as to the current state of Xcode plugin. Although there was a
>>> recent merge last month, there hasn't been a release in almost a year and a
>>> list of PRs piling up.
>>> I've attempted to contact current maintainer about helping out, but have
>>> not heard word back.
>>> Is there a process for such a situation??
>>> With changes in Jenkins 2.x and Xcode 8, would be a shame for the plugin
>>> to get further behind.
>>>
>>> Cheers
>>>
>> --
> 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/27449f2a-86a2-43fb-8a9a-7466eefc049f%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/CAO49JtGUJy7qgNOQ7t5HXE1OCE0KGg%3DOcNYQTfK9hoVm1K3kWg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: State of Xcode plugin??

IIUC Mark Waite has granted you the access. Welcome onboard!

BR, Oleg

On Monday, April 16, 2018 at 3:40:40 PM UTC+2, Kazuhide Takahashi wrote:
>
> Maintainers of 'Jenkins Xcode Plugin' are currently inactive, and 
> reflections of pull requests are delayed, so I am willing to take over 
> their duties.
> To do this, you need write access to WiKi pages and git repositories, so 
> please approve this.
>
> 2016年9月7日水曜日 2時37分33秒 UTC+9 Brantone:
>>
>> Curious as to the current state of Xcode plugin. Although there was a 
>> recent merge last month, there hasn't been a release in almost a year and a 
>> list of PRs piling up.
>> I've attempted to contact current maintainer about helping out, but have 
>> not heard word back.
>> Is there a process for such a situation??
>> With changes in Jenkins 2.x and Xcode 8, would be a shame for the plugin 
>> to get further behind.
>>
>> Cheers
>>
>

-- 
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/27449f2a-86a2-43fb-8a9a-7466eefc049f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [JEP-201] [configuration-as-code] Feedback from Meetup

2018-04-17 Thread nicolas de loof

2018-04-17 22:05 GMT+02:00 Jesse Glick :

> On Tue, Apr 17, 2018 at 2:03 PM, nicolas de loof
>  wrote:
> > the yaml schema is for a specific version of jenkins-core + plugin.
> > Any change to a plugin will change this model, this will happen any time
> a
> > DataBoundConstructor is modified
>
> Well, typically we would expect parameters to be compatible after a
> plugin update, so that if for example a `@DataBoundSetter` method
> needs to be `@Deprecated`, it is removed from databinding but still
> accessible as a Java setter. The compatibility policy for such
> refactorings does need to be defined. Currently we only expect plugins
> to be compatible in their XStream settings form, plus Pipeline `Step`s
> and any `Describable`s used by them need to continue to accept
> parameters that worked before.
>

we exclude Deprecated setters as potential CasC attributes, so this
wouldn't help
As you said there's no expectation for compatibility at this level we could
rely on.
That being said I don't consider this to be an issue : with CasC we can
produce a schema and tooling to discover such compatibility issue and let
end-user know before they apply to production.


>
> > I would anyway expect Credentials plugin to own this code, so such
> decision
> > is made from maintainer
>
> JEP-201 is introducing a new overall Jenkins feature, and the
> Credentials plugin is a longstanding piece of plumbing, so I would
> expect JEP-201 developers to address this particular integration.
>

CasC plugin demonstrate we can support it with current implementation, even
if this one relies on some uncommon yaml syntax.
I consider credentials-plugin maintainer to have a better vision of what
should be exposed to end-user than me.



>
> > I don't understand why this plugin adopted this
> > odd design - most probably for compatibility reasons
>
> I do not think compatibility had anything to do with it. The
> configuration model of Credentials is that you have various providers,
> inside of each of which you can create various domains, each of which
> then contains a set of credentials. The Java-level structure is more
> or less arbitrary and was not intended to map directly to Jenkins
> databinding, because its UI manifestation is not a single
> configuration screen.
>
> > sounds to me job-dsl could support a yaml syntax (just by switching
> > parser)
>
> Why would you need `job-dsl` at all? You already have a general system
> for binding YAML to `Describable`s. You would need a bit of extra code
> to bind some syntax to `TopLevelItem` and
> `DirectlyModifiableTopLevelItemGroup`, and a call to JENKINS-50173 if
> and when written.
>

1. Job class hierarchy is full of hand written JSON parsing so we can't use
same discovery approach
2. job-dsl is very popular for this purpose, I don't want to spend time
re-inventing the wheel for a successful solution.

I'd like job-dsl support to be option in JCasC, so we do support this
approach but some alternate way is also possible in a future release.


> --
> 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/CANfRfr00%2BpNy%2BSfbY%2BLeye-GYd0v7Q%
> 2BxttRZCJddyv_Y8fgOyA%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/CANMVJzn%3Dx0bUXrqPECiFLo-5Fpd3PkVxwVcm%2BvnDBPbNDg%3DDYg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Request for comments: Special Interest Groups (SIGs) for the Jenkins project

Hi,

We are starting GSoC meetings next week. If you need somebody to dry-run 
the SIG infrastructure, sign us up :)

Reasoning: Having recorded GSoC sessions would be definitely helpful so 
that we can share meetings with students/mentors who miss meetings. OTOH I 
am not sure whether this content is useful for other community members.

Actually I would propose to have 2 SIGs:

   - GSoC - special for GSoC. All infrastructure is ready
   - Newcomer onboarding - Another SIG for newcomers in Jenkins community + 
   Q + discussions about contributor experience
  - We could split generic GSoC meetings to there (e.g. plugin 
  development intros & Co)
  
Best regards,
Oleg


On Monday, April 16, 2018 at 4:17:22 PM UTC+2, R Tyler Croy wrote:
>
> (replies inline) 
>
> On Wed, 11 Apr 2018, Ewelina Wilkosz wrote: 
>
> > I must say I only briefly scanned the part with all the jenkinsci-foo 
> and 
> > sig-foo :( it seemed like a lot indeed. I like the rest of the document 
> > though! but this part was almost verwhelming... 
> > that's why I asked about SIG Lead responsibility. If we want to do a 
> good 
> > job we should make it as easy as possible - not that I'm lazy, but let's 
> be 
> > realistic 
> > 
> > We can see people being confused about Jenkins Developers and Jenkins 
> Users 
> > mailing list - if we have too many groups to choose from I would 
> probably 
> > spend so much time trying to figure out which one is the one I should 
> post 
> > in 
>
>
> Thanks Ewelina and Ba(p)tiste, I've made some changes and removed the 
> manymany 
> recommended mailing lists as I don't think we're at the point of needing 
> them 
> yet. 
>
>
> Filed as a proper Draft now: https://github.com/jenkinsci/jep/pull/81 
>
>

-- 
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/51f508f7-a12b-4c00-8467-f307f70b82b5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: HockeyApp plugin maintainers

Hi Mez,

We have a process for abandoned plugins ownership handover (2 weeks after 
the explicit request and ping of maintainers). More info 


If you are interested to take ownership of the plugin, the next step would 
be to sent them a direct email (see their JIRA profiles). After that we 
could start countdown and transfer ownership if there is no response. 
Brantone  seems to be active in GitHub though, 
so hopefully you will get a response earlier.

Hopefully it helps,
Oleg


On Tuesday, April 17, 2018 at 9:53:35 PM UTC+2, Mez Pahlan wrote:
>
> Hello Jenkins Devs!
>
> I'm interested in contributing to the HockeyApp 
> 
>  
> plugin and want to reach out to the plugin maintainers to see if they can 
> help resolve some PRs. My immediate interest is in the PR#48 
> 
>  
> that I have raised but I also notice that there are a number of outstanding 
> PRs that have not progressed - some for over a year.
>
> Oleg Nenashev has been kind enough to help me with my PR and ping the 
> current maintainers but I want to try on here as well.
>
> ping [brantone - Brenton Barte, dkochetkov - Denis Kochetkov, ohoeltke - 
> Oliver Hoeltke]
>
> In the future, I would like to raise more PRs so want to be sure they can 
> be progressed. I'd be happy to become a maintainer too but would probably 
> need some help and guidance on that as I have not done that before.
>
> Cheers!
>
> Mez
>

-- 
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/ab71cede-d56a-499e-b498-30d3123a31bc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [JEP-201] [configuration-as-code] Feedback from Meetup

On Tue, Apr 17, 2018 at 2:03 PM, nicolas de loof
 wrote:
> the yaml schema is for a specific version of jenkins-core + plugin.
> Any change to a plugin will change this model, this will happen any time a
> DataBoundConstructor is modified

Well, typically we would expect parameters to be compatible after a
plugin update, so that if for example a `@DataBoundSetter` method
needs to be `@Deprecated`, it is removed from databinding but still
accessible as a Java setter. The compatibility policy for such
refactorings does need to be defined. Currently we only expect plugins
to be compatible in their XStream settings form, plus Pipeline `Step`s
and any `Describable`s used by them need to continue to accept
parameters that worked before.

> I would anyway expect Credentials plugin to own this code, so such decision
> is made from maintainer

JEP-201 is introducing a new overall Jenkins feature, and the
Credentials plugin is a longstanding piece of plumbing, so I would
expect JEP-201 developers to address this particular integration.

> I don't understand why this plugin adopted this
> odd design - most probably for compatibility reasons

I do not think compatibility had anything to do with it. The
configuration model of Credentials is that you have various providers,
inside of each of which you can create various domains, each of which
then contains a set of credentials. The Java-level structure is more
or less arbitrary and was not intended to map directly to Jenkins
databinding, because its UI manifestation is not a single
configuration screen.

> sounds to me job-dsl could support a yaml syntax (just by switching
> parser)

Why would you need `job-dsl` at all? You already have a general system
for binding YAML to `Describable`s. You would need a bit of extra code
to bind some syntax to `TopLevelItem` and
`DirectlyModifiableTopLevelItemGroup`, and a call to JENKINS-50173 if
and when written.

-- 
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/CANfRfr00%2BpNy%2BSfbY%2BLeye-GYd0v7Q%2BxttRZCJddyv_Y8fgOyA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

HockeyApp plugin maintainers

2018-04-17 Thread Mez Pahlan

Hello Jenkins Devs!

I'm interested in contributing to the HockeyApp 
 plugin and want to reach out to the 
plugin maintainers to see if they can help resolve some PRs. My immediate 
interest is in the PR#48 
 that I have raised 
but I also notice that there are a number of outstanding PRs that have not 
progressed - some for over a year.

Oleg Nenashev has been kind enough to help me with my PR and ping the 
current maintainers but I want to try on here as well.

ping [brantone - Brenton Barte, dkochetkov - Denis Kochetkov, ohoeltke - 
Oliver Hoeltke]

In the future, I would like to raise more PRs so want to be sure they can 
be progressed. I'd be happy to become a maintainer too but would probably 
need some help and guidance on that as I have not done that before.

Cheers!

Mez

-- 
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/41f0970f-3e99-40c9-85c8-d1d4c2989d75%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [JEP-201] [configuration-as-code] Feedback from Meetup

2018-04-17 Thread nicolas de loof

2018-04-17 17:58 GMT+02:00 Jesse Glick :

> Some things that might otherwise have gotten lost in IRC.
>
>
> About the automatic inference of symbols like `ldap` from
> `hudson.security.LDAPSecurityRealm`: this seems like a nice trick to
> use when prototyping the JEP, so you can see realistic stuff working
> before plugins are updated to use `@Symbol`. But I do not think this
> should be retained in a 1.0 version—all supported plugins should be
> given the annotation. Reasoning:
>
> · Adding an annotation poses no risk to plugin stability, so there is
> no reason for a maintainer to object to it.
> · Symbols must be unique within their extension point (for example
> there may be only one `SecurityRealm` named `ldap`), so they must be
> chosen carefully and deliberately.
> · People might begin relying on the inferred names and then it would
> be a compatibility issue to fix this later.
>
>
the yaml schema is for a specific version of jenkins-core + plugin.
Any change to a plugin will change this model, this will happen any time a
DataBoundConstructor is modified, this is the price to pay for allignment
with UI databinding.
As a result, I don't think we should expect any compatibility on version
upgrades. If you want to run with new version of plugins, run a test master
or any JCasC validation tool before.


>
> The credentials domain syntax, IIRC something like
>
> system:
>   ? # global
>   : -credentials
> # …
>
> baffles everyone who sees it. Just because internally `credentials`
> uses a `Map` from (I guess) domains to lists of credentials does not
> mean you must reflect that in YAML syntax. You should rather model a
> list of credentials, each of which may have an optional attribute for
> the domain (ID?).
>

The idea here was to estimate the minimal required code base to offer glue
code for credentials. This is definitively not for 1.0
I would anyway expect Credentials plugin to own this code, so such decision
is made from maintainer - I don't understand why this plugin adopted this
odd design - most probably for compatibility reasons - the web UI offering
a hierarchical representation of registered credentials.


>
> It is no excuse that you are trying to keep things mapped tightly to
> the databinding model in the plugin, because Jenkins databinding does
> not have any standard support for `Map`s at all—this is all bound to
> custom UI screens in `credentials`. Therefore it is reasonable for
> JCasC to also have a custom converter. Plugins which use simple
> databinding, which would consist of `List`s of `Describable`s only,
> would not need any custom code.
>

As I said, I expect such things to take place within plugins themsleves,
either with custom JCasC _or_ by changing the databound model


>
>
> Using Job DSL Groovy to create jobs is fine as a short-term workaround
> but should not be how `TopLevelItem`s are defined in 1.0 I think.
> There should be native YAML syntax for this, based on the same
> databinding model as any other settings. As `@Symbol` is adopted,
> these should look structurally similar anyway.
>

Agree, sounds to me job-dsl could support a yaml syntax (just by switching
parser). Need to investigate how to generate the adequate schema and
documentation



>
> --
> 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/CANfRfr3e56PQf4vrDLPjPU11MxzKX
> 3L%3DR%2BQVROgyAyuKRYB97A%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/CANMVJznHMAPGtfava_DgxpNKgLGsEsWfAGgUiuPbNMRA3wbxfA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: FYI: On naming SCM implementation and extension plugins

On Tue, Apr 17, 2018 at 11:10 AM, Carles Capdevila Tejada
 wrote:
> should I change it before into gitblit-scm?

According to the doc, since

https://plugins.jenkins.io/gitblit

does not exist, you should use that.

> I hope it doesn't
> prevent users from finding it as its naming deviates

Users will not typically find plugins by `shortName`; rather by
display name and tags.

-- 
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/CANfRfr0PQm_Gx9kahT_CSxf5BrAKkg36-JhE7%2BiayAgQ5J4S-A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[JEP-201] [configuration-as-code] Feedback from Meetup

Some things that might otherwise have gotten lost in IRC.

About the automatic inference of symbols like `ldap` from
`hudson.security.LDAPSecurityRealm`: this seems like a nice trick to
use when prototyping the JEP, so you can see realistic stuff working
before plugins are updated to use `@Symbol`. But I do not think this
should be retained in a 1.0 version—all supported plugins should be
given the annotation. Reasoning:

· Adding an annotation poses no risk to plugin stability, so there is
no reason for a maintainer to object to it.
· Symbols must be unique within their extension point (for example
there may be only one `SecurityRealm` named `ldap`), so they must be
chosen carefully and deliberately.
· People might begin relying on the inferred names and then it would
be a compatibility issue to fix this later.

The credentials domain syntax, IIRC something like

system:
? # global
: -credentials
# …

baffles everyone who sees it. Just because internally `credentials`
uses a `Map` from (I guess) domains to lists of credentials does not
mean you must reflect that in YAML syntax. You should rather model a
list of credentials, each of which may have an optional attribute for
the domain (ID?).

It is no excuse that you are trying to keep things mapped tightly to
the databinding model in the plugin, because Jenkins databinding does
not have any standard support for `Map`s at all—this is all bound to
custom UI screens in `credentials`. Therefore it is reasonable for
JCasC to also have a custom converter. Plugins which use simple
databinding, which would consist of `List`s of `Describable`s only,
would not need any custom code.

Using Job DSL Groovy to create jobs is fine as a short-term workaround
but should not be how `TopLevelItem`s are defined in 1.0 I think.
There should be native YAML syntax for this, based on the same
databinding model as any other settings. As `@Symbol` is adopted,
these should look structurally similar anyway.

--
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/CANfRfr3e56PQf4vrDLPjPU11MxzKX3L%3DR%2BQVROgyAyuKRYB97A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: FYI: On naming SCM implementation and extension plugins

2018-04-17 Thread Carles Capdevila Tejada

Hi Stephen,

I have a (not yet hosted) plugin 
which 
does the same as Github Organization, but for Gitblit. Right now it's 
called *gitblit-branch-source*, following the naming of the respective 
Github and BitBucket plugins.

I'm thinking on requesting it to be hosted in the Jenkins community 
repositories; should I change it before into *gitblit-scm*? I hope it 
doesn't prevent users from finding it as its naming deviates from such big 
plugins as Github and BitBucket :'D

Thank you for your attention.

-- 
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/687e9d0f-e17d-4299-9b6d-a35e90c7ff35%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Where does the code for pipeline's 'agent' live?

2018-04-17 Thread Robert Sandell

If it is the `agent` in declarative syntax you're after here are some
starting points maybe, depending on what it is you want to learn:

https://github.com/jenkinsci/pipeline-model-definition-plugin/blob/master/pipeline-model-api/src/main/java/org/jenkinsci/plugins/pipeline/modeldefinition/ast/ModelASTAgent.java
https://github.com/jenkinsci/pipeline-model-definition-plugin/blob/master/pipeline-model-api/src/main/java/org/jenkinsci/plugins/pipeline/modeldefinition/ast/ModelASTStage.java
https://github.com/jenkinsci/pipeline-model-definition-plugin/blob/master/pipeline-model-definition/src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/model/Agent.groovy
https://github.com/jenkinsci/pipeline-model-definition-plugin/blob/master/pipeline-model-extensions/src/main/java/org/jenkinsci/plugins/pipeline/modeldefinition/agent/DeclarativeAgent.java
https://github.com/jenkinsci/pipeline-model-definition-plugin/blob/master/pipeline-model-definition/src/main/resources/org/jenkinsci/plugins/pipeline/modeldefinition/ModelInterpreter.groovy#L486

/B


2018-04-17 15:30 GMT+02:00 Joe Fair :

> I'm looking at how jobs in pipelines work, but I'm having trouble
> searching for the code for the 'agent' tag in a pipeline.  I haven't found
> any "Symbol" for agent, but I may not have looked in the right package
> yet.  I understand there may be something about 'Stapler', but I'm not
> clear.
>
> Where can I learn about 'agent'?
> Thanks,
> Joe
>
> --
> 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/CAHhz2bcHZCbFdAvMYci4d70SUZBB3
> NDyDaoGKCTHdRC%2ByL%3DtUA%40mail.gmail.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
*Robert Sandell*
Software Engineer
CloudBees, Inc.
[image: CloudBees-Logo.png] 
E: rsand...@cloudbees.com
Twitter: robert_sandell

-- 
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/CALzHZS36fU2r5cx8gf0B_1N-eG8SGmQWCXZzgmQAaJFCcd7dOw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Request to become maintainer of the statistics-gatherer-plugin

2018-04-17 Thread lucamilanesio

I have create the 
PR https://github.com/jenkins-infra/repository-permissions-updater/pull/670 
to request permissions to upload new versions of the artifacts.
Is there a form or a similar process to add permissions to the GitHub 
repository?

It has been 14 days (2 weeks) that I tried to get in touch with the 
maintainer and got no answers from any e-mails, mentions or anything else 
:-(

Even the 2nd top contributor is not sure if the maintainer is looking at it 
or not.

Thank you for your help.

Luca.

On Monday, April 16, 2018 at 11:41:19 AM UTC+1, lucamilanesio wrote:
>
> Hi all,
> the PR has been waiting for 13 days now (see 
> https://github.com/jenkinsci/statistics-gatherer-plugin/pull/4) and still 
> no news from the current maintainer :-(
>
> Can we process my request this week? As discussed, I would rather avoid 
> forking the plugin and create confusion. However, we need to get this done 
> and get the SCM Info fixed.
>
> Thank you in advance.
> Luca.
>
> On 13 Apr 2018, at 10:37, Luca Milanesio  wrote:
>
> PIng ... any news from the current Maintainers?
> Are we set for end of next week to make a decision on this?
>
> Luca.
>
> On 10 Apr 2018, at 08:07, Luca Milanesio  wrote:
>
> 2 weeks sound good to me, and yes, I always avoid forks :-)
>
> Luca.
>
> On 10 Apr 2018, at 08:02, Joseph P  wrote:
>
> Usually the wait period is 2 weeks :) I would not recommend creating 
> another plugin.
>
> -- 
> 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/8b9ce146-6cf1-4b5a-a702-108ffe540d29%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/18159fb9-d016-4a14-98d0-1694381e1966%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: trilead-ssh2 maintainer

Hi Ivan,

Actually I have reached out to the current maintainer (Michael Clarke) in
the private message.
And he said he is still planning to maintain this particular lib. So we
cannot grant ownership right now.

I will ping him

BR, Oleg



On Tue, Apr 17, 2018 at 3:52 PM, Ivan Fernandez Calvo <
kuisathave...@gmail.com> wrote:

> Hi,
>
> There is no new from current maintainers either in the pull requests nor
> here, Can we move forward?
>
> --
> 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/z-uIydVxqMM/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/8a8389a8-d43f-412c-ad63-e211e6bae509%
> 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/CAPfivLDC%3DmpUuU72fdN8955eu20DH-Rwg9d8U35zGD6UPvBEAA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: trilead-ssh2 maintainer

2018-04-17 Thread Ivan Fernandez Calvo

Hi,

There is no new from current maintainers either in the pull requests nor 
here, Can we move forward?

-- 
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/8a8389a8-d43f-412c-ad63-e211e6bae509%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Where does the code for pipeline's 'agent' live?

2018-04-17 Thread Joe Fair

I'm looking at how jobs in pipelines work, but I'm having trouble searching
for the code for the 'agent' tag in a pipeline.  I haven't found any
"Symbol" for agent, but I may not have looked in the right package yet.  I
understand there may be something about 'Stapler', but I'm not clear.

Where can I learn about 'agent'?
Thanks,
Joe

-- 
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/CAHhz2bcHZCbFdAvMYci4d70SUZBB3NDyDaoGKCTHdRC%2ByL%3DtUA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: AtomicFileWriterTest fails

2018-04-17 Thread Jonathan Bergh

@Baptiste - yes, sorry about that - i need to be properly configured on 
JIRA as well. Just busy with a release coming up next week and trying to 
get up and running with the project in between. 

best
jonathan

On Tuesday, 17 April 2018 11:19:40 UTC+2, Baptiste Mathus wrote:
>
> Filed as https://github.com/jenkinsci/jenkins/pull/3397
>
> @Jonathan, I would have requested your review there too, but didn't have 
> your GitHub handle.
>
> thanks
>
> 2018-04-17 10:57 GMT+02:00 Baptiste Mathus 
> :
>
>> Fine by me. 
>>
>> But then my only question left is: should we request INFRA to change our 
>> Windows agents on ci.jenkins.io so that they are configured 
>> differently/more like a target environment and less like a dev machine? 
>> Since, again, those tests did run correctly there and I guess we would 
>> like them to have failed to catch mistakes (?).
>>
>> 2018-04-16 22:31 GMT+02:00 Jesse Glick > >:
>>
>>> On Mon, Apr 16, 2018 at 4:14 PM, Devin Nusbaum >> > wrote:
>>> > I would just
>>> > ignore it on Windows unconditionally.
>>>
>>> Yes, especially given JENKINS-37862.
>>>
>>> -- 
>>> 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/CANfRfr2f58KoC10HUYMB_ZfZauaUQOJNW2y34brzvDzr3vS1PA%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/ac7a8379-5977-4149-b856-adfbcf3c0be7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Jenkins World 2018] - Graders wanted

2018-04-17 Thread Girish Kg

Hi Alyssa,
I am good and please let me know what is the next step towards joining the
review board.

Warm Regards
Girish KG

On 16 April 2018 at 19:52, Alyssa Tong  wrote:

> Hi Girish,
>
> Basically you will be reviewing the submissions received and giving it a
> score, and or add comments (your opinion). That's it!
>
> Thanks,
> alyssa
>
> On Sun, Apr 15, 2018 at 10:07 PM, Girish Kg  wrote:
>
>> I am interested. Please provide more details on the roles and
>> responsibilities. Thanks.
>>
>> Warm Regards
>> Girish KG
>>
>> On 16 April 2018 at 00:49, Joe Fair  wrote:
>>
>>> I'd be glad to help, too.
>>> Joe
>>>
>>> On Friday, April 13, 2018 at 12:09:08 PM UTC-4, alytong13 wrote:

 Hello,

 I am looking for additional graders to join the Jenkins World (JW)
 review committee to help grade Jenkins World 2018 SF & EU proposals.

 Time commitment expected:

- JW SF: 137 Jenkins submissions.
- JW EU: 76 Jenkins submissions at the moment but most likely will
increase after close of CFP this Sunday.

 What you get:

- Pix, bio on the Committee webpage (part of JW website)
- JW swag
- Free conference ticket to JW

 Criteria:

- You love to read and has a keen mind for the latest and greatest,
trendy technical topics

 Pls respond to this thread if you're interested.

 BR,
 alyssa

 --
>>> 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/ms
>>> gid/jenkinsci-dev/de7f7cd8-e48e-4a48-a8f6-6f5f989d7642%40goo
>>> glegroups.com
>>> 
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>>
>> --
>> Warm Regards
>> .//Girish KG
>>
>> --
>> 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/ms
>> gid/jenkinsci-dev/CADtmhQOysSGz_S4-GnoQ5Bdu7LjjCZagyJea87ziD
>> R46v4CVAA%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/CAMBsfbtkpSTmbA-nfO6DSxXm4EK9%
> 3DmMQeiFnBgpsfvixJmJ%2B3Q%40mail.gmail.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Warm Regards
.//Girish KG

-- 
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/CADtmhQN4kZJCUkJd2d5oppvf3%2B%3DBduNpS9U2%3DtV4n8q5vu7trg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: AtomicFileWriterTest fails

Filed as https://github.com/jenkinsci/jenkins/pull/3397

@Jonathan, I would have requested your review there too, but didn't have
your GitHub handle.

thanks

2018-04-17 10:57 GMT+02:00 Baptiste Mathus :

> Fine by me.
>
> But then my only question left is: should we request INFRA to change our
> Windows agents on ci.jenkins.io so that they are configured
> differently/more like a target environment and less like a dev machine?
> Since, again, those tests did run correctly there and I guess we would
> like them to have failed to catch mistakes (?).
>
> 2018-04-16 22:31 GMT+02:00 Jesse Glick :
>
>> On Mon, Apr 16, 2018 at 4:14 PM, Devin Nusbaum 
>> wrote:
>> > I would just
>> > ignore it on Windows unconditionally.
>>
>> Yes, especially given JENKINS-37862.
>>
>> --
>> 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/ms
>> gid/jenkinsci-dev/CANfRfr2f58KoC10HUYMB_ZfZauaUQOJNW2y34brzv
>> Dzr3vS1PA%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/CANWgJS7yiGOLXZ6PRyxT9dvwOKrozGKe22HNPspr-D3%3DwS9HQQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: AtomicFileWriterTest fails

Fine by me.

But then my only question left is: should we request INFRA to change our
Windows agents on ci.jenkins.io so that they are configured
differently/more like a target environment and less like a dev machine?
Since, again, those tests did run correctly there and I guess we would like
them to have failed to catch mistakes (?).

2018-04-16 22:31 GMT+02:00 Jesse Glick :

> On Mon, Apr 16, 2018 at 4:14 PM, Devin Nusbaum 
> wrote:
> > I would just
> > ignore it on Windows unconditionally.
>
> Yes, especially given JENKINS-37862.
>
> --
> 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/CANfRfr2f58KoC10HUYMB_ZfZauaUQOJNW2y34brzvDzr3vS1PA%
> 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/CANWgJS7mAoAPkwhUKd8fk%3DJ8fDftLFMpLXxU-DiBJzb1vsOK6w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: External Artifact Storage

Posted a small comment/request for clarification on the merged PR, but
otherwise LGTM.

2018-04-13 17:38 GMT+02:00 Carlos Sanchez :

> PR submitted at https://github.com/jenkinsci/jep/pull/83
>
> On Fri, Apr 13, 2018 at 5:24 PM, Oleg Nenashev 
> wrote:
>
>> Looks good to me **as a DRAFT**.
>> Please propose a pull request so that JEP editors can review it.
>>
>> We also need somebody to be selected as BDFL Delegate if KK is not
>> available to review it.
>>
>> BR, Oleg
>>
>>
>> On Friday, April 13, 2018 at 4:25:38 AM UTC+2, Jesse Glick wrote:
>>>
>>> +1
>>>
>> --
>> 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/ms
>> gid/jenkinsci-dev/0851cc7d-d3cc-4da9-8a76-b841817e38da%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/CALHFn6P6vQxzVXmLLQnff7CFeOTYbC6aF7OmM-KVBM%2BXwGPbjg%
> 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/CANWgJS7BWNgaYiwAD8_UQEQUbFrEoBwu0XusET6x8Ebv3r0PvQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Request to be made a maintainer of audit-trail-plugin

Hello,

As Oleg said, this repo is maintained by Oliver, an active member of the
community. So we would strongly prefer to get an answer from him here
before moving forward.

Also, in any case, the usual request timeout for taking over maintainership
is two full weeks, so please be patient.

Cheers

2018-04-13 8:14 GMT+02:00 :

> Hi
>
> Any updates?
>
> Cheers,
> Tomasz
>
> --
> 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/1263e546-1aad-409a-bc10-75330b8fa609%
> 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/CANWgJS6LaZetkdOq80MbnWF95K6y2uyGP9OrHUrmnYbb%3DEQu4w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Request to be made maintainer of platformlabeler plugin?