Re: Become a member of the jenkins core team

2019-11-13 Thread James Nord
+1 from me -- 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

Docs SIG status report and upcoming meetings

2019-11-13 Thread Mark Waite
The Jenkins documentation is improving significantly thanks to efforts from Tim Jacomb, Oleg Nenashev, Zbynek Konecny, Gavin Mogan, Sladyn Nunes, and many, many Hacktoberfest authors. Thanks to all those who are contributing and continue to contribute! Friday, November 22, 2019, we'll host a

Re: How to get TaskListener or BuildListener

2019-11-13 Thread Mark Waite
I agree with Ulli that https://jenkins.io/doc/developer/ is the first reference. In case it helps, https://jenkins.io/blog/2017/08/07/intro-to-plugin-development/ provides links to some items outside jenkins.io. On Wed, Nov 13, 2019 at 8:54 AM Ullrich Hafner wrote: >

Re: How to get TaskListener or BuildListener

2019-11-13 Thread Ullrich Hafner
https://jenkins.io/doc/developer/ > Am 13.11.2019 um 12:34 schrieb Robert Sandell : > > There is no specific one to get. A TaskListener is created for a build when > it starts, so from the job or item level there isn't one to use. > If you need an instance

Re: Become a member of the jenkins core team

2019-11-13 Thread Oleg Nenashev
+1 as a Core maintainer. Mark has been helping with the Core-related matters for years, and I see no reason not to grant him full access to the Core GitHub repo. if someone is interested, we could also tweak the Release Drafter tool to generate publicly-visible changelog drafts, e.g. in build

Re: Become a member of the jenkins core team

2019-11-13 Thread Rick
+1 from me On Wed, Nov 13, 2019 at 10:24 PM Mark Waite wrote: > I would like to become a member of the Jenkins core team with permission > to merge pull requests to Jenkins core. I'm drafting the changelog for the > weekly and LTS releases and would be helped by having access to the draft >

Become a member of the jenkins core team

2019-11-13 Thread Mark Waite
I would like to become a member of the Jenkins core team with permission to merge pull requests to Jenkins core. I'm drafting the changelog for the weekly and LTS releases and would be helped by having access to the draft GitHub release notes created by release drafter. Merge permission to the

Re: 2019 Elections: voting is delayed

2019-11-13 Thread Robert Sandell
> Have you checked in your spam folder in your corporate email address? Yes, twice and searched through the rest of my account in case it was routed to some strange folder. And then I searched again with a closer look and it turned out it had been hidden in the middle of the cert team's

Re: 2019 Elections: voting is delayed

2019-11-13 Thread Olblak
We know the vote id as it was share on that mailing list but we can't know who cast the vote on behalf of jenkins-cert. I don't know if we can invalidate a specific vote based on the vote id. --- gpg --keyserver keys.gnupg.net --recv-key 52210D3D --- On Wed, Nov 13, 2019, at 2:40 PM, Marky

Re: 2019 Elections: voting is delayed

2019-11-13 Thread Marky Jackson
Is there a way to know who cast that vote? This is concerning from a transparency perspective. My hope is that a document is being kept regarding issues faced during this entire process so it can become part of a hopeful retrospective, and that this is all done in the open. Items like the ones

Re: 2019 Elections: voting is delayed

2019-11-13 Thread Olblak
Apparently, 'jenkinsci-c...@googlegroups.com' endup in the participation list, so the first person who clicked on the email was able to cast an additional vote on behalf of 'jenkinsci-cert mailing list'. We still have some improvement to identify unique contributors --- gpg --keyserver

Re: 2019 Elections: voting is delayed

2019-11-13 Thread Olblak
> I haven't received any email to register for voting, at least not a personal > one. I've received two to various group mailing lists but not one connected > to my Jenkins account. Have you checked in your spam folder in your corporate email address? I see that your account uses your

Re: How to get TaskListener or BuildListener

2019-11-13 Thread selva vignesh
Hi Robert Thanks for the information. Is there any detailed document available for Jenkins plugin development? On Wed, Nov 13, 2019 at 5:05 PM Robert Sandell wrote: > There is no specific one to get. A TaskListener is created for a build > when it starts, so from the job or item level there

Re: How to get TaskListener or BuildListener

2019-11-13 Thread Robert Sandell
There is no specific one to get. A TaskListener is created for a build when it starts, so from the job or item level there isn't one to use. If you need an instance to send as a parameter to some api call you can for example use something like TaskListener.NULL

Re: 2019 Elections: voting is delayed

2019-11-13 Thread Robert Sandell
I haven't received any email to register for voting, at least not a personal one. I've received two to various group mailing lists but not one connected to my Jenkins account. /B Den mån 11 nov. 2019 kl 20:50 skrev Tracy Miranda : > Marky - thanks for the kind words. > > Olivier - thanks for

speed your Jenkins by an adapter of Jenkins update center

2019-11-13 Thread Rick
Hi all, An adapter of Jenkins update center. ## Why Jenkins downloads the plugins by parsing the JSON file which comes from a update center. One thing that you might already noticed is about the speed of downloading. Accessing a global storage for everyone could be slow although there're many

How to get TaskListener or BuildListener

2019-11-13 Thread selva vignesh
Hi, Can anyone please help me to get TaskListener or BuildListerner from job object or item Object Any sample snippet available. Thanks in advance -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop

Re: Jenkins Governance meeting on Nov 20

2019-11-13 Thread Oliver Gondža
Nope, lets give the mailing approach a proper shot. We can always return back if it would not seem to work. On 13/11/2019 07.33, Oleg Nenashev wrote: Last time we agreed to do LTS selection in the mailing list. I see no particular reason to return back to the original process, because there