Re: Terminology Updates

> I personally think without the slave context, master is pretty accurate That's a good point. I did a quick search and noticed that Apache Mesos renamed to agents a few years back but left the main controller as being a "master" so there is some precedent there. Richard. On Sat, 13 Jun 2020 at

Re: Proposal: Jenkins Code of Conduct update (Contributor Covenant 1.3 -> 1.4)

I couldn't find any good information on the differences between the versions so I cloned the repo and diffed between the versions. It works pretty well, though it's a little difficult to understand the differences at times. I find that each new version is an improvement over the previous. The

Re: Proposal: Jenkins Code of Conduct update (Contributor Covenant 1.3 -> 1.4)

+1 for proposal (1.4 version) Tracy On Fri, Jun 12, 2020 at 5:06 PM Oleg Nenashev wrote: > Dear all, > > As a follow-up to the previous Governance meeting, I would like to propose > updating the Jenkins Code of Conduct > (CoC). Currently it is based on

Re: Plugin adoption request: NUnit

+1 from me, it would be great to have a new maintainer in this plugin. Thanks a lot for stepping up! I have also pinged the code reviewers team, let's see whether we could get some reviews. BR, Oleg On Friday, June 12, 2020 at 5:07:06 PM UTC+2, Shin-ichi Morita wrote: > > Hi Team, > > I would l

Re: Proposal: Jenkins Code of Conduct update (Contributor Covenant 1.3 -> 1.4)

I am a +1 to the proposal and feel this will benefit the community greatly. > On Jun 12, 2020, at 2:05 PM, Oleg Nenashev wrote: > > Dear all, > > As a follow-up to the previous Governance meeting, I would like to propose > updating the Jenkins Code of Conduct

Proposal: Jenkins Code of Conduct update (Contributor Covenant 1.3 -> 1.4)

Dear all, As a follow-up to the previous Governance meeting, I would like to propose updating the Jenkins Code of Conduct (CoC). Currently it is based on Contributor Covenant 1.3 which wa

Re: Terminology Updates

My vote: - Master -> Controller (Host and Server are too broad, and Control Plane is to verbose) - Whitelist/Blacklist -> Allowlist/Blocklist On Thu, Jun 11, 2020 at 8:34 PM Slide wrote: > Hi Everyone, > > > > Back in the Jenkins 2.0 days, it was decided (rightfully so) to deprecate >

Re: ANN: Jenkins release artifacts uploads blockage on June 09, and a temporary downloads issue

I have two releases that I consider high-priority: github-branch-source and github-api . Users have been able to rollback to the previous release to unblock themselves, but people who cannot rollback (new installations) remain blocked. On Friday, June 12, 2020 at 10:05:33 AM UTC-7, Oleg N

Re: Terminology Updates

Jenkins Server makes sense to me as well. I'll add as a topic for the next Governance meeting. Please also make sure and weigh in on AllowList/DenyList and it's other derivatives. On Fri, Jun 12, 2020, 10:43 Marky Jackson wrote: > I like Jenkins Server too > > > On Jun 12, 2020, at 10:41 AM, Mat

Re: Terminology Updates

I like Jenkins Server too > On Jun 12, 2020, at 10:41 AM, Matt Sicker wrote: > > I also like Jenkins Server as a simple name. > > Other ideas: JenkinsD (like SystemD or any daemon), Jenkins Principal > (matches the principal/agent paradigm of agents executing code on > behalf of the principal).

Re: Terminology Updates

I also like Jenkins Server as a simple name. Other ideas: JenkinsD (like SystemD or any daemon), Jenkins Principal (matches the principal/agent paradigm of agents executing code on behalf of the principal). On Fri, Jun 12, 2020 at 12:37 PM Vlad Silverman wrote: > > I agree, “Jenkins Server” refl

Re: Terminology Updates

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". >

Blog Offensive Terminology Removal

To follow the terminology [email sent by @slide](https://groups.google.com/d/msg/jenkinsci-dev/CLR55wMZwZ8/uDjgGlnKAQAJ) the Advocacy & Outreach SIG met on 6/11/2020 and one action item was to revisit all previous Jenkins.io blog post and remove offensive terminology where possible. This action

Re: Terminology Updates

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

Re: ANN: Jenkins release artifacts uploads blockage on June 09, and a temporary downloads issue

Dear all, June 12 update: - We continue to work on the accounts migration and will share the next update on Monday - Jenkins releases are still blocked. If there are any emergency releases you need to perform, please reply in this thread. Best regards, Oleg Nenashev On Friday, Ju

Re: Terminology Updates

Control plane works but is a mouthfull. Controller works, but as others pointed out, could easily be confused in the k8s world. the other two (Host and Server) are way too generic to convey meaning if you don't know the system. You could go silly like POTUJ (President of the United Jenkins) or JO

Re: Terminology Updates

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 th

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

Azure high mem: Standard_D16_v3 vcpu 16 memory 64 AWS: m5a.xlarge vcpu 4 memory 16 GiB I've changed it to: 'm5a.4xlarge' (16CPU, 64 GB ram) It's 4 times the cost so we'll need to keep an eye on it Thanks Tim On Fri, 12 Jun 2020 at 15:20, Jesse Glick wrote: > On Tue, Jun 9, 2020 at 3:59 AM T

Re: ANN: Jenkins release artifacts uploads blockage on June 09, and a temporary downloads issue

Hi Dave, This is an email from the *Step 2. We’ll reset every user password from the LDAP database*. This one includes a temporary password, and we expect users to change it after they login into the system. For those who wonder: Yes, the temporary password is sent in plain text as mentioned a

Plugin adoption request: NUnit

Hi Team, I would like to adopt NUnit plugin and request commit access. My current interest is fixing JENKINS-50162. I submitted this pull request about 20 days ago without noticing it is marked for adoption. * Link to a plugin you want to adopt: https://github.com/jenkinsci/nunit-plugin * Lin

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

On Tue, Jun 9, 2020 at 3:59 AM Tim Jacomb wrote: > High mem could possibly do with a change, the AWS ones are much lower spec > than the Azure ones, thoughts? Not sure but I just got an unexplained EC2 (aws) - High memory ubuntu 18.04 (i-0e7f3896526c7922e) was marked offline: Connection was b

Re: Proposal: Jenkins CDF Graduation July 28th

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 m

Re: Proposal: Public community-driven roadmap for the Jenkins project

I have updated https://github.com/jenkins-infra/jenkins.io/pull/3444. Now it includes initiative labels and filtering support (pardon my JavaScript). Among major changes, Documentation, Infrastructure and Advocacy/Outreach categories have been largely merged into other groups. Any feedback will

Re: Terminology Updates

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:

Re: Adopt parameterized-trigger-plugin commit access

Hi Olivier, I am +1 for that as a former plugin maintainer, thanks a lot for standing up! I have granted you permissions in the repository. Please let me know if you want to be a default assignee in Jira. Best regards, Oleg On Friday, June 12, 2020 at 8:24:28 AM UTC+2, Olivier Lamy wrote: > >