Re: Release team

[Vlad Silverman]

Good idea
 +1

> On Sep 21, 2021, at 5:53 AM, Mark Waite  wrote:
> 
> +1 from me
> 
> On Tue, Sep 21, 2021, 3:33 AM Tim Jacomb  > wrote:
> Hello
> 
> I would like to propose a release team in the Jenkins GitHub org.
> The role and permissions are documented in 
> https://github.com/jenkinsci/jenkins/blob/master/docs/MAINTAINERS.adoc#roles 
> 
>  but they don’t actually exist in the jenkinsci GitHub org.
> 
> In jenkins-infra we have a release team which current has:
> Mark Waite
> Daniel Beck
> Olivier Vernin
> Wadeck Follonier
> Oleg Nenashev
> Myself
> 
> I would like to have a release team in JenkinsCI that has write permissions 
> on jenkinsci/jenkins and jenkinsci/packaging created, with myself (release 
> officer) as the maintainer of the team.
> 
> I’ll post a list proposing people separately if people are happy with this 
> idea.
> 
> People gaining core access here should be using their permissions for release 
> activities, e.g. backporting, build fixes. 
> 
> Ideally the jenkinsci/jenkins-infra teams should be synced as well, this 
> would grant write access to the ‘jenkins-infra/release’ repository, which 
> will be helpful for:
> Any release team member will be able to update the release checklist
> Merging of PRs updating next release version / stable line
> 
> The people joining the team should also be either (thoughts?):
> Added to the LDAP group ‘release-core’
> Join the LDAP group when acting as a release lead and be removed after
> 
> Any feedback?
> 
> Thanks
> Tim
> 
> -- 
> 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-3Bic1AHThGLJoR%2Bb3bP1pKZHDZTDePOE1p3CAx%2B7aa_qCew%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/CAO49JtFXo6iB%3Dg-DN2m0PS47BJeRsMrMtOp29E4raDHE%3D_YG7Q%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/50118D18-D67D-4351-AB7F-079B383B3AF4%40gmail.com.

Re: LTS schedule winter break

[Vlad Silverman]

+1

> On Nov 11, 2020, at 1:54 AM, fque...@cloudbees.com  
> wrote:
> 
> +1
> 
> On Wednesday, November 11, 2020 at 10:42:01 AM UTC+1 bmu...@cloudbees.com 
> wrote:
> +1
> 
> On Wednesday, November 11, 2020 at 10:15:24 AM UTC+1 Raul Arabaolaza wrote:
> +1
> 
> On Wednesday, November 11, 2020 at 10:08:45 AM UTC+1 Ildefonso Montero wrote:
> +1
> 
> On Wednesday, November 11, 2020 at 10:01:20 AM UTC+1 Antonio Muñiz wrote:
> +1
> 
> On Wed, 11 Nov 2020 at 09:48, Daniel Beck > wrote:
> Hi everyone,
> 
> We have an LTS release scheduled for December 30, which probably isn't 
> useful: The RC testing period is from Dec 16 to Dec 30. Plus who wants to 
> release things the day before NYE?
> 
> I propose we add a two-week break between 2.263.1 release and 2.263.2 RC, 
> postponing all future RCs and releases by two weeks accordingly.
> 
> Before:
> Dec 2 - 2.263.1 Release
> Dec 16 - 2.263.2 RC
> Dec 30 - 2.263.2 Release
> etc.
> 
> After:
> Dec 2 - 2.263.1 Release
> Dec 30 - 2.263.2 RC
> Jan 13 - 2.263.2 Release
> etc.
> 
> This should give us a useful RC testing period in early January. Since this 
> is the .2 release, a slightly longer backporting period in December could 
> help getting more fixes in for issues discovered in .1 as well.
> 
> While the RC would be scheduled for Dec 30, it could always be prepared 
> earlier if nobody would be around in late December to do it. If that doesn't 
> work out and it is published in early Jan, that wouldn't be too much of a 
> delay either.
> 
> WDYT?
> 
> Daniel
> 
> -- 
> 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/821EFEC7-55BA-475B-B977-1DCC1F559B82%40beckweb.net
>  
> .
> 
> 
> -- 
> Antonio Muñiz
> Human, 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/46de2d26-f36e-422a-820c-03cf70343416n%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/A5E724A4-C700-430E-9F59-89500F146762%40gmail.com.

Re: Proposal - Expanding the DockerHub admins team

[Vlad Silverman]

+1

> On Jul 29, 2020, at 9:24 AM, 'Gavin Mogan' via Jenkins Developers 
>  wrote:
> 
> +1
> 
> On Wed, Jul 29, 2020 at 9:20 AM Tim Jacomb  > wrote:
> +1
> 
> On Wed, 29 Jul 2020 at 17:14, Matt Sicker  > wrote:
> Sounds great!
> 
> On Wed, Jul 29, 2020 at 11:06 AM Oleg Nenashev  > wrote:
> >
> > Hi all,
> >
> > I am planning to be on vacation in the beginning of September, likely off 
> > the grid for some time. I would like to ensure that we have a good bus 
> > factor. Taking our experience with the Docker images in the recent months, 
> > it would be great to add more admins there.
> >
> > I propose to add Alex Earl and Mark Waite to the team. It would mean the 
> > administrative access to all DockerHub organizations: jenkins, jenkinsci, 
> > jenkins4eval. Both Mark and Alex have CLA signed. They also have 
> > administrative access to many areas of the Jenkins infrastructure, 
> > including critical components like the new release infrastructure and 
> > Trusted CI.
> >
> > Any objections?
> >
> > Thanks in advance,
> > 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/CAPfivLBiDZxaB3txQjmABX8t1_L4W2YY%3Dvg5G7C%2BX0vcPqfzsg%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/CAEot4ozj%3DFAjDU4fjQni9U3XsNQ2p%2Bi3Jbhwc-ncMZZ8ZYmDSw%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-3BicwCsJfLA1xhWAb4m_S4HJUaJkho1y70vmac3UVK%2BKvOw%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/CAG%3D_Duti-rP2UEvVohek_1BRpjLBqGBLV6jO48cypyUG7yR4hg%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/1DAD5C85-E611-4D6F-A3FA-706DC3A356B8%40gmail.com.

Re: LTS next week to change repo signing keys

[Vlad Silverman]

Thank you Mark for issuing this proposal and clarifying the steps.
+1 from me as well.

Please don’t hesitate to ask if any help is needed.

Thx, Vlad

> On Jul 22, 2020, at 12:58 PM, Tim Jacomb  wrote:
> 
> +1 would be great to do one release while Olivier is around.
> 
> Would be good to have at least one user facing change in it, but I guess not 
> required.
> 
> Thanks
> Tim
> 
> On Wed, 22 Jul 2020 at 20:29, Mark Waite  > wrote:
> The core release automation process has been used to deliver weekly releases 
> since mid-April.  It was used to deliver the weekly security release 
> recently.  We are ready to deliver the Long Term Support (LTS) releases with 
> core release automation.
> 
> Olivier Vernin has been the lead implementer of core release automation work. 
>  He'll be unavailable in August.  We'd like to deliver an LTS next week, 
> while he is still available.  We'll use that delivery to train others and 
> verify the release process documentation.  We'll then run future core 
> releases entirely from the core release automation.
> 
> Proposal:
> 
> Create Jenkins 2.235.3 LTS release the week of July 27 using core release 
> automation.  We'll use the current tip of the stable-2.235 branch.  build the 
> same code as was used for Jenkins 2.235.2 with a single .  The changes 
> between 2.235.2 and 2.235.3 would be:
> Increment the version number from 2.235.2 to 2.235.3
> Use the new repository signing key for the Debian/Ubuntu, Red Hat/CentOS, and 
> OpenSUSE repositories
> Use acceptance test harness version as committed on the stable-2.235 branch
> We've been using the new repository signing keys with weekly builds for the 
> last several months.  It is now time to switch to the new repository signing 
> keys for the long term support releases.
> 
> Proposed steps:
> Oliver Gondza approve the plan (as release officer)
> Mark Waite prepare a blog post announcing the change of repository signing 
> keys and the steps administrators must take to install the new repository keys
> Mark Waite prepare the changelog and upgrade guide for Jenkins 2.235.3 with 
> instructions for administrators to install the new repository keys
> Olivier Vernin and Mark Waite generate the 2.235.3 LTS build July 27, 28, or 
> 29 using the core release automation based on the current contents of the 
> stable-2.235 branch
> Comments, concerns, questions?
> 
> 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/53818c9b-b9b6-462a-9dcf-9a320fed192en%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/CAH-3BictR95ZGdaFh%2BmXjXq_P9Ofx6e08A-icPmO4hXdz6pnkw%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/E83C9321-9761-431C-8847-4E4715A9F32D%40gmail.com.

Re: Bug Triage "Team"

[Vlad Silverman]

I would be interested

> On Jun 16, 2020, at 2:07 PM, Mark Waite  wrote:
> 
> I'm interested.
> 
> On Tue, Jun 16, 2020 at 2:22 PM Oleg Nenashev  > wrote:
> Hi all,
> 
> I would like to recover this thread. As a part of the CDF graduation 
> criteria, we are expected to pass the Core Infrastructure Initiative 
> checklist. There is a thread about it here 
> .
> According to the CII criteria for issue reporting 
> , 
> The project MUST acknowledge a majority of bug reports submitted in the last 
> 2-12 months (inclusive); the response need not include a fix
> The project SHOULD respond to a majority (>50%) of enhancement requests in 
> the last 2-12 months (inclusive).
> Under this criteria the "project" means the Jenkins core and its components, 
> our current certification process 
>  does not 
> include plugins. I did some queries in Jira. We are somewhat compliant with 
> the first criteria (thanks to Daniel Beck and other contributors who 
> occasionally scrub issues), but not with the second one.
> 
> In order to hit the goal, I think we need to discuss starting the triage team 
> as it was proposed by Alex Earl, and maybe introducing a formal process for 
> acknowledging defects (e.g. "confirmed" label). Would anyone be interested to 
> participate?
> 
> Best regards,
> Oleg
> 
> 
> 
> On Sunday, December 16, 2018 at 1:05:08 PM UTC+1, Oleg Nenashev wrote:
> Hi all,
> 
> Over last years I have been triaging incoming JIRA issues in the JENKINS 
> project together with several other contributors. I was also a default 
> assignee in the “_unsorted 
> ”
>  JIRA component which was suggested by default in the issue creation screen. 
> Currently there are around 500 issues in the component, and I suspect I 
> processed hundreds of JIRA issues and assigned them to proper components 
> since the _unsorted was introduced.
> 
> As some of the Jenkins contributors already know, I will have a very limited 
> availability in the community over the next several months (personal 
> matters). I will be unable to provide a timely response in the tickets. I 
> would like to ensure that I do not become a bottleneck in the issue triage 
> process.
> Several days ago I removed the default assignee in _unsorted and unassigned 
> the rest of open tickets
> There are only 40 open tickets 
> 
>  now, many of them can be actually closed
> This component has explicit disclaimer that there is NO response ETA, and I 
> was not able to process all requests there. I welcome anybody to become a 
> default assignee there, e.g. on a rotation basis.
> Next week I will stop triaging incoming issues in the Jenkins core
> I used to take a look at new issues every few days after I started 
> maintaining the Jenkins core (regressions, misreported high-severity issues), 
> but it is not sustainable going forward
> I will also stop triaging issues in plugins I used to maintain and then 
> marked for adoption, but which have not been adopted yet
> Examples: EnvInject , Mask Passwords 
> , Release 
> , Periodic Backup 
> , etc.
> Thanks a lot to everybody who contributes to the issue triage in Jenkins JIRA!
> 
> Best regards,
> Oleg
> 
> 
> 
> On Tuesday, April 11, 2017 at 6:49:42 PM UTC+2, slide wrote:
> Any time that people can give is great. Even a spare 10 minutes here and 
> there would be helpful if you spread it across a large number of people.
> 
> On Tue, Apr 11, 2017 at 4:01 AM Mark Waite > wrote:
> My situation is similar to Oleg's.  My first priority is to review bugs 
> submitted against the plugins I maintain, and to reproduce bugs for those 
> plugins, and to create automated environments to reproduce those bugs.  
> Helping with other projects will come as a second priority.
> 
> Mark Waite
> 
> On Tue, Apr 11, 2017 at 3:13 AM Oleg Nenashev > wrote:
> Hi all,
> 
> I am in. 
> 
> Right now I dedicate time for reviewing incoming issues in the core, 
> Remoting, "_unsorted", a couple of other modules and a bunch of plugins I am 
> supposed to maintain. I can unlikely dedicate more time to review other 
> components (would prefer to do bugfixing in core/remoting), but at least I am 
> ready to keep working on the current stuff.
> 
> BR, Oleg
> 
> 2017-04-11 10:07 GMT+02:00 Daniel Beck >:
> 
> > On 10.04.2017, at 22:44, Slide > wrote:
> >
> > if you are interested!
> 
> I am.
> 
> --
> You received this 

Re: Proposal: Jenkins CDF Graduation July 28th

[Vlad Silverman]

+1 from me on achieving CDF Graduation by July 28 based on listed Criteria 
Checklist

Thx, Vlad

> On Jun 12, 2020, at 6:43 AM, Oleg Nenashev  wrote:
> 
> I have started a Google Doc with a checklist: 
> https://docs.google.com/document/d/1Ldmtny6OfEtQlCqdFWqq9Z25cxkZFX6yNiRqOOxo77c/edit?usp=sharing
> Please feel free to contribute and suggest changes!
> 
> Best regards,
> Oleg
> 
> On Friday, June 12, 2020 at 12:16:35 AM UTC+2, Marky Jackson wrote:
> +1 from me
> 
>> On Jun 11, 2020, at 2:39 PM, Tracy Miranda > wrote:
>> 
>> All,
>> Last year Jenkins became a CD.Foundation  project. 
>> The Technical Oversight Committee (TOC) of CDF set out a project lifecycle 
>> 
>>  for projects as part of the governance model. CDF is proposing Jenkins be 
>> the first project to go through the process and "graduate" i.e. demonstrate 
>> it has met the acceptance criteria 
>> .
>> Dan Lorenc, the current TOC Chair, joined the Jenkins Governance meeting 
>>  this month for an overview of the process and 
>> we had a discussion around the criteria. In short, there are a few 
>> housekeeping things to do for Jenkins to graduate, and the process has 
>> already been beneficial to the project health (e.g. helping identify that we 
>> need to strengthen the triage team, update Code-of-Conduct, etc). Project 
>> graduation will also be an opportunity to promote the Jenkins project via 
>> CDF channels and highlight how the project goes from strength to strength. 
>> I would like to propose that the Jenkins Community commit to graduating by 
>> the end of July, i.e. on July 28th 2020 at the CDF TOC meeting, we show how 
>> we've met the criteria and ask for a vote. 
>> (Note: this schedule allows CDF to graduate Jenkins as the first project but 
>> also in a timely way so other CDF projects may also graduate in 2020.)
>> Please go ahead and vote/comment on this proposal.
>> Regards,
>> Tracy
>> 
>> 
>> -- 
>> 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 jenkin...@googlegroups.com <>.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-dev/CACTaz6q74FSexfzGqa1BVRXVP-R%2BD161LXALOxL-bd2BrrO7Dg%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/e483e68c-08de-4843-af21-0c00b0a5d574o%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/B76A4C6D-32CA-43A6-91BD-70C6B2CA548C%40gmail.com.

Re: Terminology Updates

[Vlad Silverman]

I agree, “Jenkins Server” reflects primary functionality and definitely makes 
sense.

Thx, Vlad

> On Jun 12, 2020, at 10:21 AM, Mark Waite  wrote:
> 
> My favorite is Jenkins server.  I'll use whatever term is ultimately 
> selected, but "Jenkins server" is easier for me than "Control Plane".
> 
> On Fri, Jun 12, 2020 at 10:13 AM Jeff Thompson  > wrote:
> My favorite is "Jenkins server" or something like that. There are already 
> existing usages and it's reasonably explanatory. Something with "manager" 
> could also work, but I don't find the term as clean and clear.
> 
> Outside of bias issues, one of the problems with whitelist and blacklist is 
> that the terms don't really say what they do. Sometimes the interpretation 
> depends on which way you're looking at it. Somewhat similar to whether a 
> class hierarchy goes up or down.
> 
> "AllowList" and "DenyList" are good matching pairs that convey more semantics 
> about what they do.
> 
> In other discussions we have noted that not all usages of whitelist/blacklist 
> fall into the same behavioral meaning. Sometimes we will need to use 
> different terminology to better convey the meaning.
> 
> Jeff
> 
> On 6/12/20 3:20 AM, Oleg Nenashev wrote:
>> I am +1 for changing the terminology, and I encourage Jenkins contributors 
>> to participate in this effort. It is not something we could change in a 
>> minute, but we could do a gradual cleanup and improve the overall 
>> documentation while doing so.
>> 
>> I am -1 w.r.t "host" due to the following reasons:
>> Host term is very generic, it has thousands of usages in Jenkins 
>> https://github.com/search?q=org%3Ajenkinsci+host=Code 
>> . Choosing this 
>> term will require a careful cleanup to avoid confusion in user documentation 
>> and the codebase
>> "agent host" is often used to describe target hosts for outbound agents
>> My suggestion would be to consider a "Jenkins server" term. You can see that 
>> such a term is already used in our codebase 
>> ,
>>  website  
>> and
>>  on 3rd party resources 
>> .
>> 
>> Best regards,
>> Oleg
>> 
>> On Friday, June 12, 2020 at 6:42:34 AM UTC+2, Marky Jackson wrote:
>> It is a suggestion for consideration if you would like.
>> 
>>> On Jun 11, 2020, at 9:35 PM, Richard Bywater > wrote:
>>> 
>>> 
>>> Good point. I actually wonder if Manager is a reasonable replacement?
>>> 
>>> On Fri, 12 Jun 2020 at 16:04, Marky Jackson > wrote:
>>> The concern with controller may be a conflict with Kubernetes on Jenkins 
>>> given the same name. This was originally my suggestion but than I 
>>> remembered I was also part of renaming in that community.
>>> 
>>> > On Jun 11, 2020, at 9:02 PM, Richard Bywater > wrote:
>>> > 
>>> -- 
>>> 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 jenkin...@googlegroups.com <>.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/jenkinsci-dev/CAAy0hwcrbnGua2b3sHamE2AG1r3z8cXBxA02%2B4NrQHMWqQjzyg%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/4ffdf650-4bb4-4878-a629-4e49c3ac06b5o%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/e024d4a9-09e1-ff95-3bbc-a35d486e21ed%40cloudbees.com
>  
> .
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Jenkins Developers" group.
> To 

Re: RCA of memory conditions on Ubuntu EC2 agents on ci.jenkins.io causing test instability

[Vlad Silverman]

> I don't know what the cost difference is between the t2 and m5a instances.

I guess it depends on the region.
More details are at https://aws.amazon.com/ec2/pricing/on-demand/ 


> On Jun 5, 2020, at 2:02 PM, Slide  wrote:
> 
> We are currently using t2.small instances on EC2 for the non-high memory 
> instances
> 
> 
> 
> Going from t2.small to t2.medium would double the CPU Credits / hour, though 
> it also doubles vCPU count and Mem. 
> 
> The high mem instances are using m5.adxlarge:
> 
> 
> 
> I don't know what the cost difference is between the t2 and m5a instances.
> 
> On Fri, Jun 5, 2020 at 1:40 PM Basil Crow  > wrote:
> On Fri, Jun 5, 2020 at 1:24 PM Jesse Glick  > wrote:
> > The next step would be PRs to infrastructure repositories.
> 
> I agree. Unfortunately I have spent too much time on this issue already and
> cannot volunteer to become an infrastructure developer at present.
> 
> > 256Mb seems low for a Surefire JVM—this needs to run Jenkins and all
> > plugins plus whatever your test code is doing.
> 
> I agree, which is why I said "I worked around the problem" rather than "I
> solved the problem." Changing the JVM settings for Surefire and the agent
> launched by my tests was easy because both those JVMs were completely within
> my control. I agree that a long-term solution would involve setting -Xmx and
> -Xms on all agent and Maven JVMs as well as possibly increasing the EC2
> instance size for these nodes.
> 
> -- 
> 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/CAFwNDjrjW2aA74pqoFMhca%2BD0YqL%3DWvNe46g7G1aM3Bmx5LrWQ%40mail.gmail.com
>  
> .
> 
> 
> -- 
> Website: http://earl-of-code.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/CAPiUgVfTTqU65LN7iDo%2BMw5xPnCKFJfiTqq7kgcCtfXVMsN42w%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/FCEB4838-4FF8-410F-AEB3-6FACBDF98D80%40gmail.com.

Re: Hosting the Jenkins UI/UX Hackfest repository in jenkinsci

[Vlad Silverman]

+1

> On May 20, 2020, at 8:52 AM, Ullrich Hafner  wrote:
> 
> +1
> 
>> Am 20.05.2020 um 17:12 schrieb Marky Jackson > >:
>> 
>> +1
>> 
>>> On May 20, 2020, at 6:38 AM, Oleg Nenashev >> > wrote:
>>> 
>>> Hi all,
>>> 
>>> I am working on a repository for the UI/UX online hackfest 
>>>  next week. This 
>>> repository would be used for tracking and visualizing contributions during 
>>> the Hackfest, with help from the All Contributors 
>>>  GitHub App and additional tooling. 
>>> Work-in-progress repository draft: 
>>> https://github.com/oleg-nenashev/jenkins-uiux-hackfest-2020 
>>> 
>>> 
>>> I would like to have this repository hosted within the jenkinsci 
>>>  GitHub organization so that it is a part of 
>>> the Jenkins project. All Contributors app is already installed for the 
>>> organization. Would everyone be fine with moving the repo to our GitHub org?
>>> 
>>> Thanks in advance,
>>> Oleg
>>> 
>>> P.S: I have added this subject to the today's Governance meeting agenda
>>> 
>>> 
>>> -- 
>>> 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/CAPfivLBEnyjwQj9%2BFZkfq3m2tNy_SV4Ww%2Bc5j6i6hvR6C9R54g%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/9C0466DE-324D-489B-A706-551A14890809%40gmail.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/224FAA03-EF6B-44C8-840F-BB0DB3C4C6A1%40gmail.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/E45675AA-247F-47DC-A848-C7335C8B36D9%40gmail.com.

Re: Time to revive the Cloud Native SIG?

[Vlad Silverman]

I would be glad contributing to this as well

> On May 14, 2020, at 3:06 PM, Marky Jackson  wrote:
> 
> I whole heartily support this and please count me in to do whatever is needed.
> 
>> On May 14, 2020, at 2:39 PM, Oleg Nenashev  wrote:
>> 
>> 
>> Hi all,
>> 
>> The Jenkins Cloud Native special interest group 
>>  has been dormant for about a year 
>> since the offline meeting at Kubecon 2019 in Barcelona. There is a lot of 
>> interest from the users about running Jenkins in cloud environments and, 
>> specifically, in Kubernetes. We have recently started a series of "Jenkins 
>> in Kubernetes" online meetups 
>> , and we got positive 
>> feedback and many follow-ups there. It would be great if we could recover 
>> the SIG.
>> 
>> Previously the SIG was mostly focused on the deep Jenkins architecture 
>> changes, including pluggable storage and architecture changes towards 
>> stateless Jenkins. This is definitely a valiant goal which should be worked 
>> on, but for the SIG it was a challenge to consolidate a critical mass of 
>> contributors to push such deep surgery changes forward. I hope that we will 
>> eventually get there, but the SIG format did not work well.
>> 
>> I would suggest to change the scope of the SIG and to refocus it on 
>> use-cases for Jenkins end users and administrators:
>> Integrations with Kubernetes and other projects from the CNCF landscape
>> Managing Jenkins in Kubernetes: Helm charts, Jenkins operator, monitoring 
>> with Prometheus, etc.
>> Jenkins on Cloud providers (AWS, Google Cloud, Azure, etc): Provisioning of 
>> agents, cloud storage, and other common use-cases
>> Jenkins FaaS Capabilities: Jenkinsfile Runner and similar engines
>> Integrations with cloud native CI/CD engines like Tekton and Jenkins X
>> 
>> Immediate projects the SIG would focus on: Kubernetes plugin ecosystem, 
>> Jenkins Kubernetes Operator (JEP-219), Jenkinsfile Runner, External 
>> Fingerprint Storage (GSoC 2020 project), "Jenkins on Kubernetes" meetup 
>> follow-up discussions with speakers. We could add more projects if there are 
>> active initiatives there and put them on the Jenkins roadmap 
>> .
>> 
>> What do you think? I would appreciate any feedback and comments. If there 
>> are multiple contributors interested, I am ready to go ahead and get the SIG 
>> running again.
>> 
>> Thanks for your feedback,
>> 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/168EC3AC-204F-4486-A776-8F999C058FDD%40gmail.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/6FF427E7-C776-41DF-BB8B-58639066F7B9%40gmail.com.

Re: Governance and Jenkins is the Way on Jumbotron

[Vlad Silverman]

+1 - that's another wonderful idea to promote the Jenkins project

On Monday, May 4, 2020 at 6:06:55 PM UTC-7, Mark Waite wrote:
>
> The "Jenkins is the Way 
> " blog post 
> invites users to share their Jenkins stories.  I would like to see us 
> highlight the collection and highlighting of Jenkins experiences even more.
>
> One way to highlight further is to add the "Jenkins is the Way" blog post 
> to the Jumbotron on the front page of the jenkins.io site.  I've added it 
> to the governance meeting agenda for this Wednesday.
>
> As one way of reducing time spent in the governance meeting on the topic, 
> I'd like to gather comments from the mailing list prior to the meeting.
>
> Would you support including "Jenkins is the Way" in the Jumbotron rotation 
> for a period of 30 - 45 days?
>
> 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/b5663b1c-6a61-4bc2-8e26-4a3eeca60bd8%40googlegroups.com.

Re: Proposal: Making the Hosting team official (and onboarding new members)

[Vlad Silverman]

Great idea! I am +1 for both

> On Apr 29, 2020, at 5:02 AM, Marky Jackson  wrote:
> 
> For me it is both. +1 for the proposal and +1 to join
> 
>> On Apr 29, 2020, at 5:01 AM, Oleg Nenashev > > wrote:
>> 
>> Hi all. Just to make sure, +1 for the proposal or +1 for joining the teams? 
>> :)
>> 
>> On Wed, Apr 29, 2020, 13:58 Marky Jackson > > wrote:
>> This is a great idea and I am a +1
>> 
>> On Wednesday, April 29, 2020 at 2:09:27 AM UTC-7, Oleg Nenashev wrote:
>> Hi all,
>> 
>> 
>> In the Jenkins community we have an unofficial Hosting team which handles 
>> various requests related to plugin hosting (forking/transferring plugins, 
>> managing permissions and update center blacklists, etc.) There are multiple 
>> contributors involved in this activity on a regular basis, and it would be 
>> great to document these processes so that we could use these docs as a 
>> reference and as guidelines for onboarding new contributors to help with the 
>> hosting process. I would propose to create an official team and to introduce 
>> an onboarding process:
>> 
>> Proposal
>> Make the "Hosting Team" official, document its roles somewhere on jenkins.io 
>> . Scope: plugin and component hosting on Jenkins 
>> resources (GitHub, Update Centers, etc.)
>> Grant permissions to active contributors who are interested and who already 
>> have experience with the hosting process (e.g. Tim Jacomb, Wadeck Follonier)
>> Create new HOSTING/Mailing list triage guidelines
>> Invite interested contributors to help with triage of hosting requests as a 
>> first onboarding step to get permissions needed for GitHub / Update Site and 
>> Repository Permission Updater management
>> Team Responsibilities. Below there are some current responsibilities related 
>> to the hosting process. This list is likely incomplete, please feel free to 
>> add more items.
>> Triage and processing of new plugin HOSTING requests in Jenkins Jira. 
>> Currently Alex Earl champions it, and there are only a few contributors who 
>> help with the requests triage. Such triage is instrumental to...
>> Ensuring hosted plugins have proper artifactIds. We cannot easily change 
>> them later...
>> Do sanity check of plugins for security issues. Thanks to Alex Earl and the 
>> security team for handling it
>> Checking for duplication with existing plugins 
>> 
>>  and offering to contribute there instead of hosting a new plugin (but not 
>> blocking hosting)
>> Plugin licenses (see this thread 
>> )
>> Processing plugin release permissions in Repository Permission Updater 
>> . There is 
>> a @jenkins-infra/hosting 
>>  team handling it (Alex 
>> Earl, Baptiste Mathus and me)
>> Processing GitHub permission and Plugin adoption 
>>  
>> requests in the developer mailing list. There is a number of contributors 
>> replying to these requests, most of operations can be done via Jenkins IRC 
>> bot 
>> Manual changes in GitHub repositories for some requests, e.g. plugin 
>> renaming. There is a @jenkinsci/github-admins 
>>  team which manages 
>> such requests
>> Processing repo transfer requests (when maintainers want to transfer plugins 
>> instead of forking), via jenkinsci-transfer org or directly. There is a 
>> @jenkinsci/github-admins 
>>  team which manages 
>> it 
>> Processing blacklisting and plugin tagging/doc URL requests in 
>> /update-center2  for 
>> non-security reasons. It is currently handled by Daniel Beck and a number of 
>> other contributors
>> Maintaining the Plugin hosting, publishing and governance documentation in 
>> https://www.jenkins.io/doc/developer . 
>> Docs SIG is doing some cleanup
>> If we agree that we want to have a more official team, I will create a new 
>> page on jenkins.io  for it, similar to the Core 
>> Maintainers Guide 
>> .
>> 
>> Also, looking for new contributors who would like to join the Hosting and 
>> the triage sub-team!
>> 
>> Thanks for your feedback,
>> Oleg
>> 
>> 
>> -- 
>> 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/ljwhniI-T3U/unsubscribe 
>> 

Re: best ide

[Vlad Silverman]

Had anybody tried using Visual Code?  Although some say it’s not complete IDE - 
it would be interesting to know if Visual Code has any advantages over Eclipse 
or IntelliJ for Jenkins developers.

Thx, Vlad

> On Apr 28, 2020, at 11:56 AM, James Nord  wrote:
> 
> eclipse is generally ok - but sometimes it doesn't run the annotation 
> processor so Extensions don't get the correct information generated and then 
> they don't show up when debugging...
> 
> dropping to the command line to run mvn clean package -DskipTests  works for 
> me.
> 
> I've had issues with IntelliJ - there is no great IDE only ones that suck 
> less than others in some areas..  sometimes I just use the cli and vim 
> because it sucks less.  pick your poison
> 
> /James
> 
> On Tuesday, April 28, 2020 at 9:23:59 AM UTC+1, Miguelangel Fernandez wrote:
> Hi, I've been using this to relative success:
> IntelliJ Community 2017.3.5
> IntelliJ Stapler plugin 1.8 
> Maven 3.3.9
> JDK 1.8.0_112 
> There's no option in IntelliJ to create a new Jenkins plugin project. And I 
> can't navigate from the Jelly resources to the linked Java code. So it's 
> limited.
> I just looked at the Netbeans plugin and thought it looked nice, but found 
> it's meant for 8.2, which is no longer supported. It would be good to know if 
> this plugin is still fit for purpose.
> I only get into Jenkins plugin development every now and then. It would be 
> great to get an updated recommendation of dev environment config from people 
> who do Jenkins development more frequently.
> 
> 
> On Friday, 20 November 2015 08:44:47 UTC+1, tahoma tahrir wrote:
> What is the best IDE for developing and debuging jenkins 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/5cb31279-b0e2-4687-a404-3576b99210be%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/BF08A169-82CE-42B9-A359-E3EE60252387%40gmail.com.

Addition to copy editors team

[Vlad Silverman]

Hello,

I would like to be added to the copy editors team.
Please see below several of my recent pull requests:

https://github.com/jenkinsci/infra-cla/pull/87 


https://github.com/jenkins-infra/jenkins.io/pull/3069 


https://github.com/jenkins-infra/jenkins.io/pull/3061 


https://github.com/vsilverman/jenkins-ci/pull/3 


https://github.com/vsilverman/jenkins-ci/pull/4 


https://github.com/vsilverman/jenkins-ci/pull/5 


Thx, Vlad
https://vsilverman.github.io/jenkins-ci/ 


-- 
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/F1857606-EDF8-4A97-8515-B804D6832846%40gmail.com.

Re: Discussion: Jenkins Core Maintainer/Developer discussion channels

[Vlad Silverman]

I also think that mattermost is a reasonable chat solution for devops teams 
- https://github.com/mattermost.  Besides results of comparing mattermost 
and slack are pretty obvious - https://mattermost.com/mattermost-vs-slack/
 :-)
Just my 2c

Thx, Vlad

On Wednesday, April 8, 2020 at 5:17:38 AM UTC-7, Oleg Nenashev wrote:
>
> Hi all,
>
> In the Proposal: Expanding the Jenkins Core maintainers team 
> 
>  thread 
> we briefly discussed creation of chats and other communication channels for 
> Jenkins core maintainers which could help in the case of runtime 
> communications: merge/changelog discussions, sync-ups between maintainers, 
> etc. Right now we mostly use pull requests and mailing lists for such kind 
> of discussions, but a number of private messages between maintainers makes 
> me tink that we might be lacking a chat for runtime discussions. Also, we 
> could setup a regular call to discuss maintenance topics, do reviews in the 
> screenshare mode and to do knowledge transfers about the codebase.
>
> I would appreciate feedback from Jenkins core maintainers and active 
> contributors:
>
>- Would a dedicated chat help us? E.g. jenkinsci/core-developers in 
>Gitter
>- Would it make sense to have a regular or an on-demand call for core 
>maintainers? 
>
> Thanks for your time,
> 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/9d3db873-77b7-4a0c-97e8-82cbd3a413b0%40googlegroups.com.