Re: Pipeline predefined steps question

[flavius . cater]

Thank you for answering to my question, was really helpful, saved me a lot 
of time.

On Wednesday, 5 September 2018 15:52:05 UTC+3, Jesse Glick wrote:
>
> On Wed, Sep 5, 2018 at 7:27 AM > wrote: 
> > I would like to see where the predefined steps in the pipeline syntax 
> are declared. 
>
> In the plugin defining each step. 
>
> > I am interested in the "stage" step as I would like to rename it to my 
> "newstage" 
>
> Not sure why, but do not do that. 
>
> > and to work in declarative pipeline 
>
> It will not. This keyword is hard-coded in Declarative Pipeline. 
>

-- 
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/86b0dd8a-38ef-474e-b3db-278fc4cff7ef%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Confluence Maintenance on Saterday 1er of August at 4PM (UTC)

[Kazuhide Takahashi]

Is maintenance still ongoing?
I answered the WiKi question of the plug-in I maintain and it disappeared.

2018年9月2日日曜日 9時25分38秒 UTC+9 Olblak:
>
> Hey, 
> A small update on wiki.jenkins.io 
> It took way longer than expected, I had to restore the database on a new 
> mysql server, in order to upgrade confluence to the latest version. 
> The previous server (mysql 5.5) wasn't supported by Confluence anymore. 
>
> It appears after the upgrade that confluence is slower than ever even if 
> the server doesn't seem to be stressed. 
> There is something weird with the database, sometimes confluence complains 
> about not being able to acquire JDBC connections, and the new mysql server 
> doesn't seems to be stressed neither. 
> I don't have the energy to investigate and I won't be able to find a 
> solution until tomorrow evening. 
>
> --- 
> -> gpg --keyserver keys.gnupg.net --recv-key 52210D3D 
> --- 
>
> On Thu, Aug 30, 2018, at 2:43 PM, Olblak wrote: 
> > Hi Everybody, 
> > 
> > It's time for another major service update. 
> > I'll update Confluence this Saturday first of September from 4PM UTC, 
> > unfortunately I can't really tell how long it will be. 
> > It appears in my test that it could take more than a hour. 
> > 
> > Feel free to tell if there is any reason to delay this maintenance 
> window. 
> > Again I'll send a message on this thread once it's done 
> > 
> > Cheers 
> > 
> > 
> > --- 
> > -> gpg --keyserver keys.gnupg.net --recv-key 52210D3D 
> > --- 
> > 
> > -- 
> > 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/1535633018.961566.1491271256.5AA7D412%40webmail.messagingengine.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/ef5ef468-105a-4dc1-a65a-b7f1e1017877%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins: Shifting Gears

[Kohsuke Kawaguchi]

On Wed, Sep 5, 2018 at 2:45 PM Baptiste Mathus  wrote:

> Side tracking a bit, sorry, beat with me. Not sure for others, but
>
> >  suggest we don't turn this into a mega thread of everything that no one
> can keep track of
>
> Might also have not had the expected effect.
>
> I think mega-threads, though sometimes hard indeed to follow, also show
> the level of interest from people. So maybe like a brainstorming session,
> we shouldn't try and organize it beforehand but actually encourage answers,
> even those that might sound off topic. Then we see what still 'sticks to
> the wall'.
>

I see, yeah, I did write that. Point taken.


Le mer. 5 sept. 2018 à 20:39, Kohsuke Kawaguchi  a écrit :
>
>> Hi, I just wanted to see what people thought of this? It created quite a
>> reaction in places like Hacker News, but I'm not seeing any reaction in
>> here, which is where I care the most.
>>
>> Have people had a chance to read/see it? I'm sure you will have opinions.
>> Please let me know.
>>
>>
>> On Fri, Aug 31, 2018 at 1:33 PM Kohsuke Kawaguchi  wrote:
>>
>>> I've just posted a message to the fellow Jenkins contributors on
>>> jenkins.io: https://jenkins.io/blog/2018/08/31/shifting-gears/
>>>
>>> Any thoughts, feedbacks, etc are appreciated.
>>>
>>> Note that the pitch is at a pretty high level, and much of the things
>>> need to be designed, discussed, implemented, and so on. Those discussions
>>> will happen over coming days and months in here, SIGs, and JEPs, so I
>>> suggest we don't turn this into a mega thread of everything that no one can
>>> keep track of, like what happened with the email thread at the time of
>>> Jenkins 2.
>>> --
>>> Kohsuke Kawaguchi
>>>
>> --
>> Kohsuke Kawaguchi
>>
> --
Kohsuke Kawaguchi

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

Re: Jenkins: Shifting Gears

[Kohsuke Kawaguchi]

On Wed, Sep 5, 2018 at 12:03 PM Keith Zantow  wrote:

> Hi Kohsuke,
>
> To be honest, theres's a lot to digest. *I encourage everyone to read the
> details rather than skim the headlines* as the entirety of what you're
> talking about is meat rather than fluff.
>
> I think there are a couple bits that are somewhat vague or misunderstood.
> The relationship between Jenkins, Jenkins X, Cloud Native Jenkins, Jenkins
> Jolt, etc. is probably one of the most confusing or misunderstood parts of
> the ecosystem to people who are not particularly familiar with the
> projects. On the surface, it could appear that some of these are
> contradictory or completely different things. Perhaps there could be some
> name mangling of the projects that make things a bit more clear where they
> fall in the ecosystem, along with a plan to align the parts that make sense
> would be welcomed.
>

OK, I hear a similar sentiment from a few more people, I think I can
provide some pictures to help.


>
> Cheers,
> -Keith
>
> On Wed, Sep 5, 2018 at 2:39 PM Kohsuke Kawaguchi  wrote:
>
>> Hi, I just wanted to see what people thought of this? It created quite a
>> reaction in places like Hacker News, but I'm not seeing any reaction in
>> here, which is where I care the most.
>>
>> Have people had a chance to read/see it? I'm sure you will have opinions.
>> Please let me know.
>>
>>
>> On Fri, Aug 31, 2018 at 1:33 PM Kohsuke Kawaguchi  wrote:
>>
>>> I've just posted a message to the fellow Jenkins contributors on
>>> jenkins.io: https://jenkins.io/blog/2018/08/31/shifting-gears/
>>>
>>> Any thoughts, feedbacks, etc are appreciated.
>>>
>>> Note that the pitch is at a pretty high level, and much of the things
>>> need to be designed, discussed, implemented, and so on. Those discussions
>>> will happen over coming days and months in here, SIGs, and JEPs, so I
>>> suggest we don't turn this into a mega thread of everything that no one can
>>> keep track of, like what happened with the email thread at the time of
>>> Jenkins 2.
>>> --
>>> Kohsuke Kawaguchi
>>>
>> --
>> Kohsuke Kawaguchi
>>
>> --
>> 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/CAN4CQ4zX%3DDZAS8BD-b40mFruVUPH7zE7cUF-6pWOZQRKr8BGsw%40mail.gmail.com
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
> --
>
> Keith Zantow
> Senior Software Engineer
> CloudBees, Inc.
>
> [image: CloudBees-Logo.png]
>
>
> E: kzan...@cloudbees.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/CAJTHQaFGyPCLzSxrpzOj5qVcVMteNDb8cU_8Ymc%3DiLwVTdvdhg%40mail.gmail.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>
-- 
Kohsuke Kawaguchi

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

Re: Jenkins: Shifting Gears

[Baptiste Mathus]

Side tracking a bit, sorry, beat with me. Not sure for others, but

>  suggest we don't turn this into a mega thread of everything that no one
can keep track of

Might also have not had the expected effect.

I think mega-threads, though sometimes hard indeed to follow, also show the
level of interest from people. So maybe like a brainstorming session, we
shouldn't try and organize it beforehand but actually encourage answers,
even those that might sound off topic. Then we see what still 'sticks to
the wall'.



Le mer. 5 sept. 2018 à 20:39, Kohsuke Kawaguchi  a écrit :

> Hi, I just wanted to see what people thought of this? It created quite a
> reaction in places like Hacker News, but I'm not seeing any reaction in
> here, which is where I care the most.
>
> Have people had a chance to read/see it? I'm sure you will have opinions.
> Please let me know.
>
>
> On Fri, Aug 31, 2018 at 1:33 PM Kohsuke Kawaguchi  wrote:
>
>> I've just posted a message to the fellow Jenkins contributors on
>> jenkins.io: https://jenkins.io/blog/2018/08/31/shifting-gears/
>>
>> Any thoughts, feedbacks, etc are appreciated.
>>
>> Note that the pitch is at a pretty high level, and much of the things
>> need to be designed, discussed, implemented, and so on. Those discussions
>> will happen over coming days and months in here, SIGs, and JEPs, so I
>> suggest we don't turn this into a mega thread of everything that no one can
>> keep track of, like what happened with the email thread at the time of
>> Jenkins 2.
>> --
>> Kohsuke Kawaguchi
>>
> --
> Kohsuke Kawaguchi
>
> --
> 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/CAN4CQ4zX%3DDZAS8BD-b40mFruVUPH7zE7cUF-6pWOZQRKr8BGsw%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/CANWgJS5%3D9nhRiodONQ85ebmvYup%2BnQ_Zmc0mAReXPhHBbxydiw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins: Shifting Gears

[Keith Zantow]

Hi Kohsuke,

To be honest, theres's a lot to digest. *I encourage everyone to read the
details rather than skim the headlines* as the entirety of what you're
talking about is meat rather than fluff.

I think there are a couple bits that are somewhat vague or misunderstood.
The relationship between Jenkins, Jenkins X, Cloud Native Jenkins, Jenkins
Jolt, etc. is probably one of the most confusing or misunderstood parts of
the ecosystem to people who are not particularly familiar with the
projects. On the surface, it could appear that some of these are
contradictory or completely different things. Perhaps there could be some
name mangling of the projects that make things a bit more clear where they
fall in the ecosystem, along with a plan to align the parts that make sense
would be welcomed.

Cheers,
-Keith

On Wed, Sep 5, 2018 at 2:39 PM Kohsuke Kawaguchi  wrote:

> Hi, I just wanted to see what people thought of this? It created quite a
> reaction in places like Hacker News, but I'm not seeing any reaction in
> here, which is where I care the most.
>
> Have people had a chance to read/see it? I'm sure you will have opinions.
> Please let me know.
>
>
> On Fri, Aug 31, 2018 at 1:33 PM Kohsuke Kawaguchi  wrote:
>
>> I've just posted a message to the fellow Jenkins contributors on
>> jenkins.io: https://jenkins.io/blog/2018/08/31/shifting-gears/
>>
>> Any thoughts, feedbacks, etc are appreciated.
>>
>> Note that the pitch is at a pretty high level, and much of the things
>> need to be designed, discussed, implemented, and so on. Those discussions
>> will happen over coming days and months in here, SIGs, and JEPs, so I
>> suggest we don't turn this into a mega thread of everything that no one can
>> keep track of, like what happened with the email thread at the time of
>> Jenkins 2.
>> --
>> Kohsuke Kawaguchi
>>
> --
> Kohsuke Kawaguchi
>
> --
> 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/CAN4CQ4zX%3DDZAS8BD-b40mFruVUPH7zE7cUF-6pWOZQRKr8BGsw%40mail.gmail.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 

Keith Zantow
Senior Software Engineer
CloudBees, Inc.

[image: CloudBees-Logo.png]


E: kzan...@cloudbees.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/CAJTHQaFGyPCLzSxrpzOj5qVcVMteNDb8cU_8Ymc%3DiLwVTdvdhg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins: Shifting Gears

[Kohsuke Kawaguchi]

Hi, I just wanted to see what people thought of this? It created quite a
reaction in places like Hacker News, but I'm not seeing any reaction in
here, which is where I care the most.

Have people had a chance to read/see it? I'm sure you will have opinions.
Please let me know.


On Fri, Aug 31, 2018 at 1:33 PM Kohsuke Kawaguchi  wrote:

> I've just posted a message to the fellow Jenkins contributors on
> jenkins.io: https://jenkins.io/blog/2018/08/31/shifting-gears/
>
> Any thoughts, feedbacks, etc are appreciated.
>
> Note that the pitch is at a pretty high level, and much of the things need
> to be designed, discussed, implemented, and so on. Those discussions will
> happen over coming days and months in here, SIGs, and JEPs, so I suggest we
> don't turn this into a mega thread of everything that no one can keep track
> of, like what happened with the email thread at the time of Jenkins 2.
> --
> Kohsuke Kawaguchi
>
-- 
Kohsuke Kawaguchi

-- 
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/CAN4CQ4zX%3DDZAS8BD-b40mFruVUPH7zE7cUF-6pWOZQRKr8BGsw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [GCI-mentors] GCI 2018 org applications open September 6-17 - contest begins October 23rd for students

[Kristin Whetstone]

>From my perspective, I'd love to get help with some of the documentation
tasks.  I'd like to participate, and would be willing to help out wherever
needed.

Thanks!
Kristin

On Sun, Sep 2, 2018 at 6:59 AM, Aldrin Leal  wrote:

> I'd love to - I've got a couple of small tasks in my plugins, and I've
> happy to help mentor a Student into doing it. Not only for fun, but also to
> give back. What should be our next steps?
>
> --
> -- Aldrin Leal,  / https://ingenieux.io/about/
>
> On Sun, Sep 2, 2018 at 5:47 AM, Oleg Nenashev 
> wrote:
>
>> Hi Supun,
>>
>> // Added Jenkins Developers group to CC
>>
>> FYI, Google Code-in (GCI) is a contest to introduce pre-university
>>> students (ages 13-17) to open source software development. IMHO
>>> participating GCI is a great advantage to the community and hope its bit
>>> different experience for all of us. Last year GCI was very successful and
>>> 25 opensource mentoring organizations participated [1]. I think this year
>>> we also can apply as a mentoring organization. Your suggestions would be
>>> greatly appreciated.
>>>
>>> [1] https://opensource.googleblog.com/2018/01/google-code-in-201
>>> 7-winners.html
>>>
>>
>> I think it may be interesting to the Jenkins community. Our main
>> challenge would be to create enough small tasks
>> 
>> which should be doable by a newbie contributor. It should be possible for
>> "Design" and "Documentation" sections, QA and research are also possible.
>> Regarding Coding, it will require processing of newbie-friendly
>> 
>> tasks and describing them properly. It is certainly doable, but we need a
>> number of contributors, especially in the following timeframes:
>>
>>- Sep 06 - Sep 17 - Applications
>>- Oct 23 - Dec 27 - Contest
>>
>> In my case, I am not available to drive the applications period, my
>> schedule is fully packed due to the DevOps World | Jenkins World prep work.
>> November-December will be also quite busy for me, I prefer to not commit on
>> being an active mentor during this period. If somebody is interested to be
>> an organization admin (e.g. Supun), I will be happy to provide as much
>> assistance as I can.
>>
>> Would anybody from Jenkins Developers be interested in participating?
>> Generally it requires creating/describing small tasks in the area of your
>> interest (plugins you maintain, etc.)
>>
>> Best regards,
>> Oleg
>>
>>
>>
>> On Thu, Aug 30, 2018 at 7:59 AM Supun Wanniarachchi <
>> supunpram...@gmail.com> wrote:
>>
>>> Hi All,
>>>
>>> FYI, Google Code-in (GCI) is a contest to introduce pre-university
>>> students (ages 13-17) to open source software development. IMHO
>>> participating GCI is a great advantage to the community and hope its bit
>>> different experience for all of us. Last year GCI was very successful and
>>> 25 opensource mentoring organizations participated [1]. I think this year
>>> we also can apply as a mentoring organization. Your suggestions would be
>>> greatly appreciated.
>>>
>>> [1] https://opensource.googleblog.com/2018/01/google-code-in-201
>>> 7-winners.html
>>>
>>> Best Regards,
>>> Supun.
>>>
>>> -- Forwarded message -
>>> From: Google Code-in Mentors 
>>> Date: Thu, Aug 30, 2018 at 1:04 AM
>>> Subject: [GCI-mentors] GCI 2018 org applications open September 6-17 -
>>> contest begins October 23rd for students
>>> To: Google Code-in Mentors 
>>>
>>>
>>> Hello GCI mentors,
>>>
>>> We are pleased to announce Google Code-in (GCI) 2018 ,
>>> the 9th consecutive year of our contest for pre-university students ages
>>> 13-17. Please be aware GCI will start about a month earlier this year
>>> than in previous years - the contest starts for students October 23rd!
>>>
>>> The GCI timeline, FAQs, Rules and flyers have been updated on the contest
>>> site .
>>>
>>> Organizations -- If you would like to apply for the 2018 program please
>>> start thinking about the tasks you would like students to work on and reach
>>> out to your community members to ask if they would like to be mentors for
>>> the program. *Organization applications open for GCI orgs *next week on
>>> Thursday, September 6th, and close less than 2 weeks later on Monday,
>>> September 17th. We will announce organizations on Tuesday, September 18th
>>> giving orgs 5 weeks to create their tasks before the contest begins on
>>> October 23rd.
>>>
>>> The major changes for GCI 2018 are:
>>>
>>>-
>>>
>>>Orgs will evaluate the 20 students completing the most tasks with
>>>their org when deciding on finalists and winners
>>>-
>>>
>>>Orgs will choose 6 finalists (instead of 5)
>>>-
>>>
>>>We have renamed the User Interface category to Design
>>>-
>>>
>>>Students will have to wait until Goog

Re: Pipeline predefined steps question

[Jesse Glick]

On Wed, Sep 5, 2018 at 7:27 AM  wrote:
> I would like to see where the predefined steps in the pipeline syntax are 
> declared.

In the plugin defining each step.

> I am interested in the "stage" step as I would like to rename it to my 
> "newstage"

Not sure why, but do not do that.

> and to work in declarative pipeline

It will not. This keyword is hard-coded in Declarative Pipeline.

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

Pipeline predefined steps question

[flavius . cater]

Hello, I would like to see where the predefined steps in the pipeline 
syntax are declared. I am interested in the "stage" step as I would like to 
rename it to my "newstage" (if I rename the pipeline-stage-plugin StageStep 
name) and to work in declarative pipeline. (Because by changing the name in 
the plugin and use it like that works only in scripted pipeline).
Thanks !

-- 
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/9e17f805-9767-4748-86ef-48a7551d0946%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Bitbucket Branch Source Plugin Maintainer

[Antonio Muñiz]

Thanks Baptiste!

On Tue, 4 Sep 2018 at 23:20, Baptiste Mathus  wrote:

> Commit access is still only granted by the bot. As Michael said.
>
> As Antonio approved it, I just granted casz commit access to the plugin.
> As usual, the invitation must be accepted first so it takes effect.
>
> [23:16] <+ batmat> | jenkins-admin: hello old friend
> [23:16] <@jenkins-adm> | Hello batmat!
> [23:17] <+ batmat> | jenkins-admin: make casz committer on
> bitbucket-branch-source-plugin
> [23:17] <@jenkins-adm> | Added casz as a GitHub committer for repository
> bitbucket-branch-source-plugin
> [23:17] <+ batmat> | jenkins-admin
>
>
> Filing a PR as described by Antonio is going to be needed to if Joseph
> wants to be able to also release.
>
> Le lun. 3 sept. 2018 à 12:05, Antonio Muñiz  a
> écrit :
>
>> Sure! You are "casz" on GitHub, right? Thanks for all your contributions!
>>
>> Send a PR to
>> https://github.com/jenkins-infra/repository-permissions-updater/blob/master/permissions/plugin-cloudbees-bitbucket-branch-source.yml
>> to include yourself in the committers list. It needs approvals by 2
>> maintainers (I think). You have mine already :)
>>
>> On Mon, 3 Sep 2018 at 02:10, Michael Neale  wrote:
>>
>>> I think we can still grant committer access via the irc bot (but will
>>> need to be added to permissions repo) - Antonio that makes sense? Interest
>>> is increasing in this plugin.
>>>
>>> On Saturday, September 1, 2018 at 6:43:21 AM UTC+10, Joseph P wrote:

 I am pretty familiar with the code base, contributed and reviewed a lot
 of the PRs, so if your up for it wouldn't mind being the second maintainer.
 Also maintainer on the bitbucket webhook plugin for non native webhook
 bitbucket.

 💪

 torsdag den 30. august 2018 kl. 09.47.21 UTC+2 skrev Antonio Muñiz:
>
> BTW, I'm one of the maintainers, but I'd like to get at least one more
> review from another maintainer.
>
> On Thu, 30 Aug 2018 at 09:18, Antonio Muñiz 
> wrote:
>
>> Review done.
>>
>> On Wed, 29 Aug 2018 at 04:05, Richard Bywater 
>> wrote:
>>
>>> Hi
>>>
>>> Just wanted to put out a call to see who identifies with being the
>>> maintainer for the Bitbucket Branch Source Plugin at the moment.
>>>
>>> Reason I ask is that there's a few PRs building up at the moment and
>>> one of them (
>>> https://github.com/jenkinsci/bitbucket-branch-source-plugin/pull/115 )
>>> would be of great use for those of us who use a different URL for HTTP &
>>> SSH.
>>>
>>> Thanks in advance :)
>>> Richard.
>>>
>>> --
>>> 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/CAMui946PmsQ-M%2B%3DV2vOcAvwdqz5D%2BP0AVv4_CuVKxuvPH5Hr-g%40mail.gmail.com
>>> 
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>> --
>> Antonio Muñiz
>> Software Engineer
>> CloudBees, Inc.
>>
>
>
> --
> Antonio Muñiz
> Software Engineer
> CloudBees, Inc.
>
 --
>>> 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/325c63bb-9db0-4c20-9563-9966649513e3%40googlegroups.com
>>> 
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>> --
>> Antonio Muñiz
>> Software Engineer
>> CloudBees, Inc.
>>
>> --
>> 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/CAJc7kzQiM-2T-5KbnP%2BGqX9NuO1FTO%2Bd-fEg5gYM_vLM6Aa6TA%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 unsubscr

Re: Adopt a plugin

[Oleg Nenashev]

Hi,

The maintainer seems to be active.
The last release was released 6 days ago, 1 day before this request was 
submitted.

Even if the plugin is up for adoption, it would be great to get his 
explicit confirmation in this thread or in 
https://github.com/jenkinsci/prometheus-plugin/pull/61

BR, Oleg

On Tuesday, September 4, 2018 at 11:11:55 PM UTC+2, Baptiste Mathus wrote:
>
> > have reached out to Lars Sjostrom 
>
> Any evidence for this somewhere? This element can obviously reduce the 
> timeout period 
> (which BTW out of this context as it stands would not have *really* 
> started yet as the current maintainer(s) is not in CC).
>
> Le sam. 1 sept. 2018 à 02:46, Marky Jackson  > a écrit :
>
>> The following plugin is up for adoption. I would like to maintain this 
>> plugin and have reached out to Lars Sjostrom 
>> https://plugins.jenkins.io/prometheus
>>
>>
>> GitHub user: markyjackson-taulia
>> Jenkins Infra username: jequals5
>>
>>
>> Should I file a pull request in repository-permissions-updater right away 
>> or wait for the two weeks grace period to end?
>>
>> -- 
>> 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/945F7363-722F-4709-AD75-BBCFF00506AF%40gmail.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/ab02bb85-aa89-4320-84e4-2ecd8b24fbfc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Looking to be added as a maintainer for pam-auth-plugin

[Oleg Nenashev]

Hi Matt,

Access granted, thanks for the patience.

I thought we handled this on IRC already?
>
It does not mean that we should remember user IDs.
Some users also chose to have different GitHub and User IDs for different 
plugins, so I expect them to be provided explicitly in each request.

Best regards,
Oleg
 

On Tuesday, September 4, 2018 at 8:01:44 PM UTC+2, Matt Sicker wrote:
>
> I thought we handled this on IRC already? GitHub is jvz. JIRA is also jvz 
> from what I remember (JIRA looks like it's down at the moment).
>
> On Mon, Sep 3, 2018 at 6:52 AM Oleg Nenashev  > wrote:
>
>> Hi Stephen, thanks for the response.
>> I am ready to transfer the permissions. @Matt, I need you JIRA and Github 
>> ID to do the transfer.
>>
>> BR, Oleg
>>
>> On Monday, September 3, 2018 at 11:35:24 AM UTC+2, Stephen Connolly wrote:
>>>
>>> I have no recollection of ever being a maintainer of that plugin
>>>
>>> On Fri, 17 Aug 2018 at 15:51, Matt Sicker  wrote:
>>>
 CCing Jesse and Stephen who seem to be the two most active maintainers 
 historically for this plugin.

 On Fri, Aug 17, 2018 at 6:45 AM Oleg Nenashev  
 wrote:

> Please reach out to the maintainer and get his explicit confirmation 
> in this thread.
> If you want to request ownership transfer, the process is described 
> here: 
> https://wiki.jenkins.io/display/JENKINS/Adopt+a+Plugin#AdoptaPlugin-Requestcommitaccess
>
> BR, Oleg
>
> On Thursday, August 16, 2018 at 9:22:39 PM UTC+2, Matt Sicker wrote:
>>
>> I've got an open PR there, and I'd like to be added as a maintainer.
>>
>> -- 
>> Matt Sicker
>> 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-de...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/66d8deb8-1661-44c9-8efe-c2fdcfbe8cc0%40googlegroups.com
>  
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>


 -- 
 Matt Sicker
 Software Engineer, CloudBees

>>>
>>>
>>> -- 
>>> *Stephen Connolly*
>>> Software Developer & Architect
>>> CloudBees, Inc.
>>>
>>> [image: CloudBees-Logo.png] 
>>> E: scon...@cloudbees.com
>>> Twitter: @connolly_s 
>>>
>>> -- 
>> 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/dd9d6af3-cb0a-4a19-aa8b-d48323ba83cb%40googlegroups.com
>>  
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
> -- 
> Matt Sicker
> 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/e25d8cbc-81b5-4078-9e9d-5045916d34cc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.