Re: Next LTS baseline selection

I like that idea, Jesse. Can we agree on picking 2.204 with JENKINS-58993 patched to only fail when assertions are on? -- oliver -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails fro

Re: Proposal: new initialization milestone for configuration-as-code-plugin

> > > The whole point of the initial code was to stop non deterministic random > race conditions to occur and it is doing its job perfectly well. > > Yes, deterministic is very important. I think this fix is necessary until the new milestone is introduced. I also agree with the workaround

Re: cps-groovy => translate.txt

I really appreciate your answer Jesse, I am not planning on touching anything but I discovered this.. CPS stuff and is quite interesting, never heard of it and it is fascinating the applications it may have, that is the main reason I am deeply trying to understand the library. Also, may I ask yo

Re: Jenkins test harness not loading JS files in dependencies of plugin under test

On Wed, Nov 20, 2019 at 5:37 PM Ullrich Hafner wrote: > Is this a known limitation of the test harness? Or is this a bug I can try to > fix in the test harness Since you are probably the first to encounter the issue, I would guess it is a bug. Whether it is fixable, I have no idea offhand. --

Re: Proposal: Deprecating/Removing OS X packaging for Jenkins

Hi all, Documentation updates are ready for review: - Documentation patch: https://github.com/jenkins-infra/jenkins.io/pull/2666 - Deprecation announcement blogpost: https://github.com/jenkins-infra/jenkins.io/pull/2667 Thanks a lot to everyone for feedback and reviews. On Wednes

Jenkins test harness not loading JS files in dependencies of plugin under test

I’m trying to write UI tests with Jenkins test harness (based on HTMLUnit). When one of my jelly files under test uses a JS library that is part of another plugin (i.e. in a maven dependency) then the JS file seems to be not exposed and Jenkins reports a 404. The same jelly file works fine when

Re: Adopting Google Metadata plugin

+1 From GCP On Wednesday, November 20, 2019 at 6:38:32 AM UTC-8, Adrien Lecharpentier wrote: > > Hello, > > I came across the Google Metadata plugin [1] and saw that this plugin > hasn't been touched in 5years. So I'd like to become maintainer of the > plugin. > > Matt, would you agree for me

Re: Cannot release openshift-login plugin

Looks like you released pretty recently. Update center only updates a couple times a day, I think it usually updates within 6 hours. On Wed., Nov. 20, 2019, 1:05 p.m. Akram Ben Aissi, wrote: > Hi here, we have release a 2 versions of openshift-login-plugin (1.0.21 > and .22) and they are still n

Cannot release openshift-login plugin

Hi here, we have release a 2 versions of openshift-login-plugin (1.0.21 and .22) and they are still not on https://updates.jenkins.io/download/plugins/openshift-login/ . however they are present here: https://repo.jenkins-ci.org/releases/org/openshift/jenkins/openshift-login/ . Any idea ?

Re: Proposal: Deprecating/Removing OS X packaging for Jenkins

Package deprecation was approved at the Governance meeting. I will go ahead and submit a PR with changes On Wednesday, November 20, 2019 at 9:09:13 AM UTC+1, Olblak wrote: > > I am happy to see that we all agree on this. \o/ > > --- > gpg --keyserver keys.gnupg.net --recv-key 52210D3D > --- > > >

Re: Proposal: Jenkins Browser Support policy updates

The policy change has been approved by the Governance meeting. Taking the consensus here, I went ahead and merged https://github.com/jenkins-infra/jenkins.io/pulls Thanks all! On Tuesday, November 19, 2019 at 11:42:46 PM UTC+1, Oleg Nenashev wrote: > > Since we have a Governance meeting tomorrow

Re: Next LTS baseline selection

On Wed, Nov 20, 2019 at 2:33 PM Oliver Gondža wrote: > Even when we would be be able to compensate now in the plugin, > because that would leave several JCasC versions available that are known > to be broken on newer cores. So just mention in the upgrade guide that you need to update the `configu

Re: Next LTS baseline selection

I can not speak to Config As Code, but the issue I found that lead me to write the code in Jenkins in the first place was reported reliably by one of CloudBees' customers (they could hit it every single time). I also saw this on my internal issue sometimes (we randomly lost the cloud configurati

Re: Next LTS baseline selection

While I agree with James' reasoning in theory, I see breaking JCasC as a big deal. Even when we would be be able to compensate now in the plugin, because that would leave several JCasC versions available that are known to be broken on newer cores. How about asserting JENKINS-58993 violation on

Re: Next LTS baseline selection

Do we have an idea of how often this manifests? On 20/11/2019 19.00, Oleg Nenashev wrote: https://groups.google.com/forum/#!topic/jenkinsci-dev/O_g1kk39TBQ is quite related to this thread. We might want to consider 2.198 as a baseline, just for discussion. On Wednesday, November 20, 2019 at 3:

Re: Next LTS baseline selection

I will bite :) I would be -1 on that version. not having the fix in core is allowing silent corruption of configuration. knowing allowing silent corruption and doing nothing about it has no place to exist in code. It is not Jenkins that is blowing up but a plugin manipulating Jenkins state be

Re: Hacktoberfest 2019 highlights + swag budget request

Is there an SVG? I think there's too many colors to 3d print but I kinda want to see it I can simplify it On Wed., Nov. 20, 2019, 4:32 a.m. Oleg Nenashev, wrote: > especially if we can get a Jenkins Hacktoberfest logo for this :) >> > > We have one! > https://jenkins.io/images/logos/oktoberfest/

Re: Proposal: new initialization milestone for configuration-as-code-plugin

https://github.com/jenkinsci/configuration-as-code-plugin/pull/1204 manipluating Jenkins internal state whilst it is being loaded is equally hacky. > Our problem is that it is going to land in LTS in one month unless we take a baseline before 2.198 you actually DO want this code to be in. th

Re: Next LTS baseline selection

https://groups.google.com/forum/#!topic/jenkinsci-dev/O_g1kk39TBQ is quite related to this thread. We might want to consider 2.198 as a baseline, just for discussion. On Wednesday, November 20, 2019 at 3:49:31 PM UTC+1, Oleg Nenashev wrote: > > 2.205 exploded due to https://issues.jenkins-ci.org

Re: Proposal: new initialization milestone for configuration-as-code-plugin

That fix is indeed dirty, but it might be acceptable. Our problem is that it is going to land in LTS in one month unless we take a baseline before 2.198 On Wednesday, November 20, 2019 at 6:24:38 PM UTC+1, James Nord wrote: > > If you (or someone) wants to try a quick and dirty quick fix (until t

Re: Adopting Google Metadata plugin

I see batmat pinged people on your PR, so +1 from me after the 2 week timeout On Wed., Nov. 20, 2019, 6:43 a.m. Adrien Lecharpentier, < adrien.lecharpent...@gmail.com> wrote: > I'm sorry Matt, it seems that you are not the current maintainer of the > plugin based on > repository-permissions-updat

Re: Proposal: new initialization milestone for configuration-as-code-plugin

If you (or someone) wants to try a quick and dirty quick fix (until the required milestones are available) then sleeping an amount of time if a system property is set would be a temporary hackish workaround. https://github.com/jenkinsci/configuration-as-code-plugin/blob/c7864838afa0c96b346974800

Re: Jenkins Governance meeting on Nov 20

Current agenda: - LTS status check - Event updates: FOSDEM, Jenkins World, etc. - Trademark usage request: Jenkins Master Class (Parker Ennis) - https://groups.google.com/forum/#!topic/jenkinsci-dev/Cq_NQwyLD5s - Budget request: Hacktoberfest swag (Oleg Nenashev

Re: There were errors checking the update sites: None of the tool installer metadata passed the signature check when updating UC data

Yeah, seems the root cause On Wednesday, November 20, 2019 at 4:03:12 PM UTC+1, Björn Pedersen wrote: > > HI, > > as the problems stems from the fact that at least the tool bundles are > signed with an expired key, this affects all jenkins versions. > > Am Mittwoch, 20. November 2019 15:56:34 U

Re: There were errors checking the update sites: None of the tool installer metadata passed the signature check when updating UC data

HI, as the problems stems from the fact that at least the tool bundles are signed with an expired key, this affects all jenkins versions. Am Mittwoch, 20. November 2019 15:56:34 UTC+1 schrieb Raul Arabaolaza: > > Hi all, > > You may have noticed https://issues.jenkins-ci.org/browse/JENKINS-602

There were errors checking the update sites: None of the tool installer metadata passed the signature check when updating UC data

Hi all, You may have noticed https://issues.jenkins-ci.org/browse/JENKINS-60229, just to expand a little we have found this is not only affecting 2.205 version but also 2.190.2 and 2.190.1 and some proprietary versions based on the current `stable-2.190` branch. Full error in the aforemention

Re: Next LTS baseline selection

2.205 exploded due to https://issues.jenkins-ci.org/browse/JENKINS-60199, but IIUC it could be mitigated by upgrade guidelines. It discourages selecting 2.205 s the new LTS baseline anyway, IMHO needs more soak testing for other possible regressions +1 for 2.204. It has some negative community r

Re: Adopting Google Metadata plugin

I'm sorry Matt, it seems that you are not the current maintainer of the plugin based on repository-permissions-updater#plugin-google-metadata-plugin.yml. Nghia Tran, would yo

Adopting Google Metadata plugin

Hello, I came across the Google Metadata plugin [1] and saw that this plugin hasn't been touched in 5years. So I'd like to become maintainer of the plugin. Matt, would you agree for me to help you with this plugin? -- Adrien [1]: https://github.com/jenkinsci/google-metadata-plugin -- You rece

Re: Next LTS baseline selection

2.204 sounds reasonable. -- 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 vis

Re: cps-groovy => translate.txt

On Tue, Nov 19, 2019 at 10:27 AM medianopepeter wrote: > I am not fully understanding how the resource translate.txt actually works I suppose you are referring to translatable.txt and https://github.com/cloudbees/groovy-cps/blob/4916a1f80c5c8b1a1a23c2bf366d98be7e87ab56/dgm-builder/src/main/java/c

Next LTS baseline selection

It is the time of the cycle again for us to choose next LTS baseline as a successor to 2.190. Please, voice your preference or concerns here so we can wrap up the discussion on governance meeting today (sorry for not letting folks more time for the discussion). My personal suggestion is 2.204,

Re: Proposal: Implementing sensible fine grained permissions to allow an administer to securely delegate some aspects of jenkins configuration

On Mon, Nov 18, 2019 at 9:57 PM Michael Cirioli wrote: > WIP implementation prototype can be found at > https://github.com/mikecirioli/jenkins/tree/FGP Would you mind filing this as a draft PR against jenkinsci/jenkins? While https://github.com/jenkinsci/jenkins/compare/master...mikecirioli:FGP

Re: Hacktoberfest 2019 highlights + swag budget request

> > especially if we can get a Jenkins Hacktoberfest logo for this :) > We have one! https://jenkins.io/images/logos/oktoberfest/oktoberfest.png On Wednesday, November 20, 2019 at 9:12:35 AM UTC+1, Olblak wrote: > > Strong +1 from me, sending a letter with few stickers is nice, especially > i

Re: Hacktoberfest 2019 highlights + swag budget request

Strong +1 from me, sending a letter with few stickers is nice, especially if we can get a Jenkins Hacktoberfest logo for this :) --- gpg --keyserver keys.gnupg.net --recv-key 52210D3D --- On Wed, Nov 20, 2019, at 2:59 AM, YanJun Shi wrote: > +1 from me. It's a virtuous cycle. > > On Wed, Nov

Re: Proposal: Deprecating/Removing OS X packaging for Jenkins

I am happy to see that we all agree on this. \o/ --- gpg --keyserver keys.gnupg.net --recv-key 52210D3D --- On Wed, Nov 20, 2019, at 3:09 AM, Richard Bywater wrote: > > I'm confused that this advertises *building and running Jenkins from master > > sources*, which probably should never be done