Re: Releasing JCasC support for ghprb-plugin

:  No objections from me. On Wed, Jan 6, 2021 at 2:18 AM Oliver Gondža wrote: Hey, there is a long anticipated feature merged in in the plugin[1][2], but no maintainer appears to be active to cut a release. Are there any objections if I step in a do the release? [1] https://github.com

Introducing Jenkins Gating subsystem

Hey folks, There are 2 new plugin pending hosting request right now, and I would like to elaborate on the Gating subsystem it introduces. Partially to get the word our, but also to gain more feedback. The concept of Gating permits Jenkins to become aware of availability of individual

Data binding: Bind repeatable list of textboxes into List

Hey, I am struggling with something supposedly simple. I need to get a list of strings from user through both UI and JCasC. In UI, I use `f:repeatable > f:textbox`, that unfortunately produces a bit clumsy json structure of `"foo": [ {"name": "value 1"}, {"name": "value b"}, ... ]`. For

Releasing JCasC support for ghprb-plugin

Hey, there is a long anticipated feature merged in in the plugin[1][2], but no maintainer appears to be active to cut a release. Are there any objections if I step in a do the release? [1] https://github.com/jenkinsci/ghprb-plugin/pull/731 [2] https://issues.jenkins-ci.org/browse/JENKINS-55793

Jenkins 2.263.1 LTS RC testing started

Hello everyone, Latest LTS RC was made public and it is ready to be tested. Final release is scheduled for 2020-12-02. Please, report your findings in this thread. Download bits from http://mirrors.jenkins-ci.org/war-stable-rc/2.263.1/jenkins.war

Jenkins LTS certification process overview

Hey folks, I will be holding a brief session on the LTS maintenance and certification process tomorrow on zoom. Anyone interested is welcome to join. I will very likely not have enough material to fill the entire hour so everyone is encouraged to bring whatever questions they have. Part of

Re: LTS schedule winter break

Hey, Thank you all for the inputs. I approve the suggested timeline, so the calendar is updated. Please do not count on the exact RC date in late December. On 12/11/2020 00.43, Victor Martinez wrote: +1 Just a quick question regarding the winter break, even if the release dates are not

Jenkins 2.249.3 LTS RC testing started

Hello everyone, Latest LTS RC was made public and it is ready to be tested. Final release is scheduled for 2020-11-04. Please, report your findings in this thread. Download bits from http://mirrors.jenkins-ci.org/war-stable-rc/2.249.3/jenkins.war

Re: LTS baseline selection for the successor of 2.249

For now, we have no better candidate than 2.263. I suggest to accept it, with possibility to reevaluate in two weeks when the line is supposed to be initiated. We will keep it if nothing pressing pops up. On 23/10/2020 02.05, Mark Waite wrote: That's correct.  The windows installer can't be

LTS baseline selection for the successor of 2.249

Let's voice the baseline candidate suggestions and concerns. We seem to be in the situation where all recent weeklies are fixing recent regressions making none of them an appealing candidate to me. I do not feel like choosing the latest weekly in a hope all will be well from now on. But at

Availability of Oliver Gondža in late 2020 and onward

Hey Folks, After all those years with the project doing my best here and there (Release and LTS officer, reviewer and maintainer of a number of components), I have chosen to step back a bit. Partially as my focus is shifting away slowly, but mostly to direct my attention to my family and the

Jenkins 2.249.2 LTS RC testing started

Hello everyone, Latest LTS RC was made public and it is ready to be tested. Final release is scheduled for 2020-10-07. Please, report your findings in this thread. Download bits from http://mirrors.jenkins-ci.org/war-stable-rc/2.249.2/jenkins.war

Re: Incrementals and ATH tests (inside a plugin CI)

I am not aware that any work have been done to support this. On 27/08/2020 21.06, Ullrich Hafner wrote: My warnings plugin is using in our Jenkins CI build also UI tests (using the ATH container). Is there a way to start these UI tests (using the ATH container) so that depending plugins that

Jenkins 2.249.1 LTS RC testing started

Hello everyone, Latest LTS RC was made public and it is ready to be tested. Final release is scheduled for 2020-09-09. Please, report your findings in this thread. Download bits from http://mirrors.jenkins-ci.org/war-stable-rc/2.249.1/jenkins.war

Re: Backporting for 2.249.1?

The backporting PR is now ready: https://github.com/jenkinsci/jenkins/pull/4918 On 21/08/2020 16.22, Mark Waite wrote: Oliver, We're scheduled to have a release candidate of 2.249.1 next Wednesday, August 26.  I don't see a stable-2.249 branch on the Jenkins core repository. Will you be

Re: Jenkins 2.235.4 LTS RC testing started

wrote: Hi Oliver, Any https servers available to download the latest LTS RC? J On Sun, Aug 2, 2020 at 9:30 AM Oliver Gondža wrote: Hello everyone, Latest LTS R

Jenkins 2.235.4 LTS RC testing started

Hello everyone, Latest LTS RC was made public and it is ready to be tested. Final release is scheduled for 2020-08-12. Please, report your findings in this thread. Download bits from http://mirrors.jenkins-ci.org/war-stable-rc/2.235.4/jenkins.war Thanks! -- oliver -- You received this

LTS baseline selection for the successor of 2.235

Let's voice the baseline candidates and concerns so we have the candidate agreed on by the end of the week. To get the discussion started, how about 2.249? https://jenkins.io/changelog/ -- oliver -- You received this message because you are subscribed to the Google Groups "Jenkins

Re: LTS next week to change repo signing keys

I like the idea of dry-running the release procedure with no fixes included. Also, thanks Mark and Olivier for working around you schedules to get this implemented sooner rather than later. Do I understand correctly that you suggest to otherwise continue with 2.235 line as it was planned,

Jenkins 2.235.2 LTS RC testing started

Hello everyone, Latest LTS RC was made public and it is ready to be tested. Final release is scheduled for 2020-07-15. Please, report your findings in this thread. Download bits from http://mirrors.jenkins-ci.org/war-stable-rc/2.235.2/jenkins.war Thanks! -- oliver -- You received this

Jenkins 2.235.1 LTS RC testing started

Hello everyone, Latest LTS RC was made public and it is ready to be tested. Final release is scheduled for 2020-06-17. Please, report your findings in this thread. Download bits from http://mirrors.jenkins-ci.org/war-stable-rc/2.235.1/jenkins.war Thanks! -- oliver -- You received this

Backporting for LTS 2.235.1 under review

Hey Folks, the PR for 2.235.1 is out for review. The chances are minimal this time despite all the candidates ware backported. [1] https://github.com/jenkinsci/jenkins/pull/4768 Thanks! -- oliver -- You received this message because you are subscribed to the Google Groups "Jenkins

Re: 2.222.x LTS missing backport of JENKINS-61197

On 01/06/2020 10.03, Raihaan Shouhell wrote: Hey all, I've recently upgraded masters to the 2.222.x line and ran into an issue where a build that was using a filesystem root workspace will throw a null pointer exception. Some quick investigation revealed

Re: Branch for LTS 2.235

Hey, I went on initiating the new LTS line. I expect to get to the backporting MR creation later this week. On 25/05/2020 13.56, Beatriz Munoz wrote: Hi!! Is there an ETA for start working on 2.235 LTS? I see branch stable-2.235 is not created in Jenkins repository Thanks! Beatriz Muñoz

Backporting for LTS 2.235.1 started

Backporting has started and the RC is scheduled for 2020-06-03. Candidates: https://issues.jenkins-ci.org/issues/?filter=12146 Fixed: https://issues.jenkins-ci.org/issues/?jql=labels%20%3D%202.235.1-fixed Rejected: https://issues.jenkins-ci.org/issues/?jql=labels%20%3D%202.235.1-rejected --

Jenkins 2.222.4 LTS RC testing started

Hello everyone, Latest LTS RC was made public and it is ready to be tested. Final release is scheduled for 2020-05-20. Please, report your findings in this thread. Download bits from http://mirrors.jenkins-ci.org/war-stable-rc/2.222.4/jenkins.war Thanks! -- oliver -- You received this

Re: LTS baseline selection for the successor of 2.222

2020 at 5:47:41 PM UTC+2, Tim Jacomb wrote: 2.235 would also be my preference, I've got 2 (hopefully) last system read PRs, I would love to get in before the LTS On Wed, 29 Apr 2020 at 14:54, Daniel Beck wrote: > On 29. Apr 2020, at 12:44, O

LTS baseline selection for the successor of 2.222

In accordance we recently approved process changes, we are doing next baseline section two weeks earlier in the cycle. Let's voice the baseline candidates and concerns so we have the candidate by next Governance meeting at 2020-05-06. My preferable choices would be 2.232 as the next release

Re: ANN: Agent Docker images renaming on April 12-13

I vote for ssh-build-agent as I find it a bit more clear next to ssh-agent. The sshd-agent describes what is inside rather than what is there for the customer. On 13/04/2020 22.54, Marky Jackson wrote: I vote for jenkins/ssh-agent On Apr 13, 2020, at 1:52 PM, Oleg Nenashev

Jenkins 2.222.2 LTS RC testing started

Hello everyone, Latest LTS RC was made public and it is ready to be tested. Final release is scheduled for 2020-04-22. ``` Fixed - JENKINS-61692 Minor 2.229 "HTTP Proxy Configuration" -> "Validate Proxy" crashs immediately with NullPointerException

Backporting for LTS 2.222.2 started

Backporting has started and the RC is scheduled for 2020-04-08. This is for the first time we do backporting review in github, partially to see how practical it will be. It is expected to learn and reflect back on the process as we go. Please have look at the change proposed and rejected so

Move the LTS baseline selection to take place 2 weeks earlier in the cycle

As agreed on 2.204.* LTS line retrospective[1], I am proposing to adjust LTS schedule so that next LTS baseline will be selected in week 10 when .3 RC is published. It used to be in week 12 when .3 is released. There ware 2 reasons for this: - Lately, we slowly shifted towards choosing too

Jenkins 2.222.1 LTS RC testing started

Hello everyone, Latest LTS RC was made public and it is ready to be tested. Final release is scheduled for 2020-03-25. Please, report your findings in this thread. Note that for this release, we do know it is impacted by JENKINS-61429[1] (unable to reorder step on a job configuration page).

Re: Proposal: Emeritus maintainers

On 02/03/2020 13.55, Daniel Beck wrote: On Mon, Mar 2, 2020 at 1:50 PM Stephen Connolly > wrote: Similarly, if I come back in 2 years and see that Bob who adopted the foobar plugin from me has done nothing with it in the past year... should I need

Backporting for LTS 2.222.1 started

Backporting has started and the RC is scheduled for 2020-03-11. Candidates: https://issues.jenkins-ci.org/issues/?filter=12146 Fixed: https://issues.jenkins-ci.org/issues/?jql=labels%20%3D%202.222.1-fixed Rejected: https://issues.jenkins-ci.org/issues/?jql=labels%20%3D%202.222.1-rejected --

Re: LTS baseline selection

ue, Feb 25, 2020 at 12:33 AM Jesse Glick > wrote: On Mon, Feb 24, 2020 at 4:37 PM Oliver Gondža > wrote: > the baseline candidates Reference: https://jenkins.io/changelog/ > in advance to speed up the discussion in governance meeting. Are ba

LTS baseline selection

The last release of 2.204 LTS line is scheduled for this Wednesday, and so is the start of new LTS cycle. Let's voice the baseline candidates and our concerns in advance to speed up the discussion in governance meeting. -- oliver -- You received this message because you are subscribed to the

Re: Jenkins 2.204.3 LTS RC testing started

Propagating new file usually takes about an hour or two (never really measured), so I can only guess propagating an update takes about the same amount of time. On 17/02/2020 13.23, Mark Waite wrote: Thanks!  Any idea how long the propagation delay is through the mirrors?  I tried to download

Jenkins 2.204.3 LTS RC testing started

Hello everyone, Latest LTS RC was made public and it is ready to be tested. Final release is scheduled for 2020-02-26. Please, report your findings in this thread. Download bits from http://mirrors.jenkins-ci.org/war-stable-rc/2.204.3/jenkins.war Thanks! -- oliver -- You received this

Re: 2.204.3 RC

My apology for slipping the scheduled date. I expect to have the RC out tomorrow. On 13/02/2020 20.37, Oleg Nenashev wrote: Good question. I think we need feedback from Oliver Gondza about the planned dates. I have not heard anything about the date changes On Thursday, February 13, 2020 at

What is the process for deprecating plugin now when the wiki is read only?

I have not noticed the process was updated... Thanks! -- 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 from it, send an email to

Re: SonarCloud JenkinsCI organisation?

I am not sure what specific kind of integration are you guys looking for, but I managed to get sonar publishing to work a while ago[1][2]. - There is no requirement to have a centralized "jenkins" sonarcloud org nor having it connected to "jenkinsci" github org to have projects in that org

Jenkins 2.204.2 LTS RC testing started

Hello everyone, Latest LTS RC was made public and it is ready to be tested. Final release is scheduled for 2020-01-29. Please, report your findings in this thread. Download bits from http://mirrors.jenkins-ci.org/war-stable-rc/2.204.2/jenkins.war Thanks! -- oliver -- You received this

Re: JAMS in meetup account disappearing

+1 from me on doing the cleanup. Meetup groups come and go. Great to see a documented way to gring them back to life. On 14/01/2020 14.59, Oleg Nenashev wrote: Thanks a lot for the notice Alyssa! If my message is too long, *TL;DR: *the meetups will be restored, but it is time to clean up the

Re: S3 plugin maintainership status

Hey, this is third such message for this plugin in less than a year (if I have not missed some), so I 100% support introducing more people to maintain S3 plugin. On 13/01/2020 17.01, Evaristo Gutierrez wrote: Hi all, Nearly a month ago I raised [PR

Re: Archiving jenkinsci/groovy repo

The repo is archived now. It can always be unarchived if the need arises. On 07/01/2020 11.33, Raihaan Shouhell wrote: +1 should have been archived a long time ago. Cheers, Raihaan On Tue, Jan 7, 2020 at 4:17 PM Oliver Gondža <mailto:ogon...@gmail.com>> wrote: Thanks to

Archiving jenkinsci/groovy repo

Thanks to a github security alert, I find out we have a fork of an official groovy repo[1] in our org. It is terribly outdated and unused for over 8 years[2]. Are there any objections to archiving such repositories? The repo will remain readable but it would clearly indicate it is obsolete

Jenkins 2.204.1 LTS RC testing started

Hello everyone, Latest LTS RC was made public and it is ready to be tested. Final release is scheduled for 2019-12-18. Please, report your findings in this thread. Download bits from http://mirrors.jenkins-ci.org/war-stable-rc/2.204.1/jenkins.war Thanks! -- oliver -- You received this

Re: LTS schedule winter break

This is now reflected in the calendar. Thanks! On 02/12/2019 11.55, Daniel Beck wrote: Hi everyone, 2.204.1 is scheduled for Dec 18, .2 would be released on Jan 15, with the RC scheduled for on Jan 1. I don't expect a lot of backport candidates, or feedback on .1 in general, to come in

Re: Possible LTS regression in commons-compress

James, thanks for the updates. The way I understand that is, problem is easily fixable, affects proprietary component and is a fairly unlikely thing to do to begin with, so we do not consider this to be a blocker for LTS. Unless someone tells me I am wrong, I am targeting the RC for tomorrow.

Re: LTS schedule winter break

Alright, provided there are no objection by the meeting time tomorrow, I will go and adjust the schedule. On 02/12/2019 22.28, Mark Waite wrote: I like the postponement idea.  +1 from me On Mon, Dec 2, 2019 at 10:55 AM Daniel Beck > wrote: Hi everyone,

Re: Next LTS baseline selection

Thu, Nov 21, 2019 at 7:54 AM Daniel Beck > <mailto:db...@cloudbees.com >> wrote: > > > >     On Thu, Nov 21, 2019 at 2:17 PM Oliver Gondža >     <mailto:ogo...@gmail.com >> wrote: > > >        

Backporting for LTS 2.204.1 started

Backporting has started and the RC is scheduled for 2019-12-04. Candidates: https://issues.jenkins-ci.org/issues/?filter=12146 Fixed: https://issues.jenkins-ci.org/issues/?jql=labels%20%3D%202.204.1-fixed Rejected: https://issues.jenkins-ci.org/issues/?jql=labels%20%3D%202.204.1-rejected --

Re: Next LTS baseline selection

Alright, thanks for the inputs. Next LTS line will be 2.204. On 21/11/2019 19.44, Mark Waite wrote: On Thu, Nov 21, 2019 at 7:54 AM Daniel Beck <mailto:db...@cloudbees.com>> wrote: On Thu, Nov 21, 2019 at 2:17 PM Oliver Gondža mailto:ogon...@gmail.com>> wrote:

Re: Next LTS baseline selection

On 21/11/2019 13.20, Daniel Beck wrote: On Thu, Nov 21, 2019 at 12:40 PM Oliver Gondža <mailto:ogon...@gmail.com>> wrote: Are we ok to see how the JCasC PR is doing before committing to an LTS baseline? Are you suggesting we go with 2.198 if the JCasC PR doesn't work out?

Re: Next LTS baseline selection

I get what you say, James. My point being we ware shipping a core with this flaw for years (correct me if I wrong), there ware no documentation plugins should not save before EXTENSIONS_AUGMENTED is completed and people ware not bitten severely enough to file an issue until recently (again,

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

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

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

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

Not being a Mac OS user myself, I cannot argue how useful this is for its user-base. But provided most of the the Mac users can or do use homebrew, I say go for it! On 19/11/2019 18.26, Mark Waite wrote: This sounds like the right plan to me.  +1 On Tue, Nov 19, 2019 at 9:02 AM Oleg Nenashev

Re: speed your Jenkins by an adapter of Jenkins update center

I suspect few people would bother to report (accurate) numbers there. Setting up internal mirror is the part that needs to be done and this is the kind of bonus task that always gets outprioritized. IMO. On 15/11/2019 12.14, Rick wrote: Hi Björn, It's true that those download statistics

Re: Proposal: Jenkins Browser Support policy updates

On 15/11/2019 10.17, Oleg Nenashev wrote: Hi all, There was recently a question about Jenkins browser support policy raised in the chats. Currently the policy is hosted on Wiki (here ), and the policy looks to be REALLY

Re: Jenkins Governance meeting on Nov 20

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

Jenkins 2.190.3 LTS RC testing started

Hello everyone, Latest LTS RC was made public and it is ready to be tested. Final release is scheduled for 2019-11-20. Please, report your findings in this thread. Download bits from http://mirrors.jenkins-ci.org/war-stable-rc/2.190.3/jenkins.war Thanks! -- oliver -- You received this

Re: 2.190.2-RC availability

My apology for the delay. Published and announced. On 10/10/2019 11.23, Ildefonso Montero wrote: Hello everyone, hello Oliver, Based on https://jenkins.io/event-calendar/ 2.190.2-RC should be available from yesterday here: http://mirrors.jenkins.io/war-stable-rc/, is there any problem with

Jenkins 2.190.2 LTS RC testing started

Hello everyone, Latest LTS RC was made public and it is ready to be tested. Final release is scheduled for 2019-10-23. Please, report your findings in this thread. Download bits from http://mirrors.jenkins-ci.org/war-stable-rc/2.190.2/jenkins.war Thanks! -- oliver -- You received this

Jenkins 2.190.1 LTS RC testing started

Hello everyone, Latest LTS RC was made public and it is ready to be tested. Final release is scheduled for 2019-09-25. Please, report your findings in this thread. Download bits from http://mirrors.jenkins-ci.org/war-stable-rc/2.190.1/jenkins.war Thanks! -- oliver -- You received this

Backporting for LTS 2.190.1 started

Backporting has started and the RC is scheduled for 2019-09-11. Candidates: https://issues.jenkins-ci.org/issues/?filter=12146 Fixed: https://issues.jenkins-ci.org/issues/?jql=labels%20%3D%202.190.1-fixed Rejected: https://issues.jenkins-ci.org/issues/?jql=labels%20%3D%202.190.1-rejected --

Re: Next LTS line selection open. Due 2019-08-27

Thank you folks (and Gabriel, especially), I am taking the 2.190 as the next LTS baseline. On 29/08/2019 11.46, Oleg Nenashev wrote: Hi Oliver, Could you please let us know what is your decision about the LTS baseline? Thanks in advance, Oleg On Wednesday, August 28, 2019 at 1:59:11 PM

Re: Next LTS line selection open. Due 2019-08-27

So I guess that eliminates 2.191 as a choice for LTS. I do not feel that strong choosing between 2.190 and 2.187, and it appears Oleg and Mark leans that way. Any other inputs? On 27/08/2019 11.15, Oleg Nenashev wrote: There is a confirmed regression in Jenkins 2.191 / Remoting 3.34

Next LTS line selection open. Due 2019-08-27

For the anticipated absence of a government meeting, we will be selecting next LTS candidate here, on the mailing list. The conclusion will be wrapped up no longer than Tuesday 27th COB UTC time. Feel free to share your thoughts here. --- I believe we affectively only have 2 candidates[1],

Re: Jenkins 2.176.3 LTS RC testing started

On 08/08/2019 20.15, Daniel Beck wrote: How firm are we with this super early RC? JENKINS-58548 is a regression introduced in the recent security fixes, so affect LTS too. A fix went into this weekly and would have more than a week of testing. It seems to be a pretty minor issue, but then the

Re: Jenkins 2.176.3 LTS RC testing started

On 11/08/2019 08.12, Oleg Nenashev wrote: Are we impacted by the ci.jenkins.io status? The instance has been really unstable sine last Monday, and I am not sure we can successfully execute the common RC testing Pipelines there. Oliver, IIUC you also run it on your internal instances, right?

Re: Open call for acceptance-test-harness co-maintainers

Awesome, thanks! Right now, we are putting together first official ATH contributor guidelines[1] and it would be great if it reflects your thoughts as well. Once we have that merged, I will proceed with granting you the admin/release permissions and formally declaring you co-maintainers.

Open call for acceptance-test-harness co-maintainers

Hey Guys, I am looking for some folks interested in stepping in to ATH maintainer duties when the need arises. Reviewing, merging, releasing, adjusting, that sort of stuff. My response times there are holding things back at times so having more people to do so would certainly help with

Jenkins 2.176.3 LTS RC testing started

Hello everyone, Latest LTS RC was made public and it is ready to be tested. Final release is scheduled for 2019-08-28. Please, report your findings in this thread. Download bits from http://mirrors.jenkins-ci.org/war-stable-rc/2.176.3/jenkins.war Thanks! -- oliver -- You received this

Re: LTS schedule around DWJW

We seem to have a number of +1s with no objections. Thank you everybody, I am going to adjust the timeplan and the calendar accordingly. On 19/07/2019 14.24, Baptiste Mathus wrote: +1 Le jeu. 18 juil. 2019 à 13:44, Daniel Beck > a écrit : Hi everyone, We've

Re: Jenkins 2.176.2 LTS RC testing started

On 02/07/2019 17.37, Daniel Beck wrote: On 2. Jul 2019, at 10:31, Oliver Gondža wrote: JENKINS-57515 Major Jenkins 2.181 AIX slave start error due to can not found /com/sun/jna/aix-ppc64/libjnidispatch.so https

Jenkins 2.176.2 LTS RC testing started

Hello everyone, Latest LTS RC was made public and it is ready to be tested. Final release is scheduled for 2019-07-17. There are five issues backported and one that was postponed. Postponed: JENKINS-33843 Major 2.181 It's not possible to

Re: Jenkins Changelog: weather stats spammed?

On 28/06/2019 09.15, Daniel Beck wrote: On 28. Jun 2019, at 07:26, 'Björn Pedersen' via Jenkins Developers wrote: Has this been hit by a spam-attack? Obviously :) The worst legitimate weather we ever had was still well below 100 (because then users checking the weather stop installing

LTS release schedule slips starting 2.176.2

Hello everyone, I would like to let you know that Daniel Back and I have agreed to postpone the next LTS RC (and the whole release train that follows) as we struggle to keep up with the schedule as the summer is approaching. As indicated in the calendar, you can expect - 2.176.2 RC on

2.176.1 LTS RC regression found (Was: Jenkins 2.176.1 LTS RC testing started)

. It's a regression for us. On Thu, 23 May 2019 at 16:16, Oliver Gondža <mailto:ogon...@gmail.com>> wrote: Hello everyone, Latest LTS RC was made public and it is ready to be tested. Final release is scheduled for 2019-06-05. Postponed:         JENKINS-57528   

Jenkins 2.176.1 LTS RC testing started

Hello everyone, Latest LTS RC was made public and it is ready to be tested. Final release is scheduled for 2019-06-05. Postponed: JENKINS-57528 CriticalJenkins 2.178 Jenkins in Docker does not install detached plugins when there is no UC data

Backporting for LTS 2.176.1 started

Backporting has started and the RC is scheduled for 2019-05-22. Candidates: https://issues.jenkins-ci.org/issues/?filter=12146 Fixed: https://issues.jenkins-ci.org/issues/?jql=labels%20%3D%202.176.1-fixed Rejected: https://issues.jenkins-ci.org/issues/?jql=labels%20%3D%202.176.1-rejected --

Jenkins 2.164.3 LTS RC testing started

Hello everyone, Latest LTS RC was made public and it is ready to be tested. Final release is scheduled for 2019-05-08. Please, report your findings in this thread. Download bits from http://mirrors.jenkins-ci.org/war-stable-rc/2.164.3/jenkins.war Thanks! -- oliver -- You received this

Re: Backporting for LTS 2.164.3 started

dedicated tests added: https://github.com/jenkinsci/jenkins/pull/3925 Do you think it would be eligible to backporting in upcoming .3? Thanks Le lun. 15 avr. 2019 à 11:54, Oliver Gondža <mailto:ogon...@gmail.com>> a écrit : Backporting has started and the RC is scheduled for 2

Backporting for LTS 2.164.3 started

Backporting has started and the RC is scheduled for 2019-04-24. Candidates: https://issues.jenkins-ci.org/issues/?filter=12146 Fixed: https://issues.jenkins-ci.org/issues/?jql=labels%20%3D%202.164.3-fixed Rejected: https://issues.jenkins-ci.org/issues/?jql=labels%20%3D%202.164.3-rejected --

Re: `stalled-pr` label vs. JIRA status

On 05/04/2019 07.20, Jesse Glick wrote: On Thu, Apr 4, 2019 at 3:26 PM Daniel Beck wrote: - New status name ("Stalled" probably) STALLED - one sentence description Some work was done on this issue, but there is no clear plan for it to be completed. - category IN PROGRESS - where it

Jenkins 2.164.2 LTS RC testing started

Hello everyone, Latest LTS RC was made public and it is ready to be tested. Final release is scheduled for 2019-04-10. Please, report your findings in this thread. Download bits from http://mirrors.jenkins-ci.org/war-stable-rc/2.164.2/jenkins.war Thanks! -- oliver -- You received this

Re: acceptance-test-harness questions

On 20/03/2019 16.47, Julien HENRY wrote: Hi Olivier, Any suggestion on how to achieve this? Basically I would like to take a copy of the update center corresponding to the oldest version of Jenkins we support, and use it in our ITs. This page

Re: acceptance-test-harness questions

<https://sonarsource.com/> Le mar. 19 mars 2019 à 10:05, Oliver Gondža mailto:ogon...@gmail.com>> a écrit : Hey, let me see if I understand that. Your ATH version is new enough to correctly spoof the checksum so it works (for latest Jenki

Backporting for LTS 2.164.2 started

Backporting has started and the RC is scheduled for 2019-03-27. Candidates: https://issues.jenkins-ci.org/issues/?filter=12146 Fixed: https://issues.jenkins-ci.org/issues/?jql=labels%20%3D%202.164.2-fixed Rejected: https://issues.jenkins-ci.org/issues/?jql=labels%20%3D%202.164.2-rejected --

Re: Jenkins 2.164.1 LTS RC testing started

I 100% percent agree. Let me ask KK to do it. On 14/03/2019 07.40, Oleg Nenashev wrote: As a part of Java 11 GA prep work ran 2.164 through extensive testing on our side, including ATH and PCT for dozens of plugin. The tests have been performed on both Java 8 and Java 11, and they look good.

Re: acceptance-test-harness questions

On 07/03/2019 22.46, Julien HENRY wrote: Hi folks, Hey, I am sorry to hear you have come such a long way without discovering what is already available. (my replies inline) In the SonarQube plugin , we have developed our own WebDriver

Re: Jenkins extended choice parameter plugin: do you have write permission?

On 06/03/2019 17.46, Craig Rodrigues wrote: Hi, Do you have write privileges to the Jenkins extended-choice-parameter plugin? I notice that you merged this: jenkinsci/extended-choice-parameter-plugin#21 I have this patch jenkinsci/extended-choice-parameter-plugin#25 which gets Extended

Jenkins 2.164.1 LTS RC testing started

Hello everyone, Latest LTS RC was made public and it is ready to be tested. Final release is scheduled for 2019-03-13. Note this is the first LTS version that aims for out-of-the-box Java 11 support so you are more then welcome to give that a try as well! Please, report your findings in

Re: Setup external Jenkins processes to test via JCasC

On 14/02/2019 16.08, Jesse Glick wrote: On Thu, Feb 14, 2019 at 6:34 AM Oliver Gondža wrote: Does it sound useful to you? Yes! My main feedback is that, if possible, this should be reworked to use a Docker container to launch Jenkins, with the image configurable on a per-test basis

Re: Backporting for LTS 2.164.1 started

On 14/02/2019 16.38, Daniel Beck wrote: On 14. Feb 2019, at 11:03, Oliver Gondža wrote: Candidates: https://issues.jenkins-ci.org/issues/?filter=12146 Could you update this filter to include 'Fixed but Unreleased'? We're not consistently keeping the statuses up to date after a weekly

Setup external Jenkins processes to test via JCasC

The other day, I have spent a week on crafting a reusable JUnit rule to complement JenkinsConfiguredWithCodeRule[2] that create Jenkins SUTs as independent local processes. The use case here is starting Jenkins with realistic classloading environment, testing realistic start/stop/restart

Backporting for LTS 2.164.1 started

Backporting has started and the RC is scheduled for 2019-02-27. Candidates: https://issues.jenkins-ci.org/issues/?filter=12146 Fixed: https://issues.jenkins-ci.org/issues/?jql=labels%20%3D%202.164.1-fixed Rejected: https://issues.jenkins-ci.org/issues/?jql=labels%20%3D%202.164.1-rejected --

  1   2   3   4   5   >