Re: Releasing JCasC support for ghprb-plugin

[Oliver Gondža]

CCing the latest appointed maintainer.

On 25/01/2021 18.55, Matt Sicker wrote:

I'd argue that without a maintainer, a plugin would be better off
archived until someone with sufficient interest to maintain it
volunteers.


We have plenty of plugins that are crucial to thousands of users with no 
active maintainer. It is far from ideal, but yet the way it is.


I am concerned that if we insist of someone adopting plugins in order to 
move some issue forward, we will only encourage people to make reckless 
commitments and as a result have more plugins with _inactive_ 
maintainers appointed (since they would become maintainers to fix an 
issue or two, but will not provide long term mainenance) and higher 
maintainer fluctuation.



On Fri, Jan 22, 2021 at 3:05 AM ogondza  wrote:


I understand it feels strange, though it is the second best thing we can do in 
case we lack a maintainer.
On Wednesday, January 6, 2021 at 5:53:37 PM UTC+1 msi...@cloudbees.com wrote:


I'd prefer if this plugin has an actual maintainer. Otherwise, this
also seems like false advertising that the plugin is still supported
by anyone.

On Wed, Jan 6, 2021 at 10:45 AM 'Gavin Mogan' via Jenkins Developers
 wrote:


If you do a release and there are new bugs are you going to handle them?

Without a maintainer it seems like deploying to prod and not monitoring 
afterwards.

Gavin

On Wed., Jan. 6, 2021, 6:03 a.m. Marky Jackson,  wrote:


Same, no objections

On Jan 6, 2021, at 6:01 AM, Mark Waite  wrote:


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/jenkinsci/ghprb-plugin/pull/731
[2] https://issues.jenkins-ci.org/browse/JENKINS-55793
--
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 jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/f3e65b25-477d-a780-ceae-eb8dec945f40%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-de...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtETdyEZtHzG2%2BLGBHyBmKHZPTjLQffozt16GWYb%3DP_htg%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-de...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CE90DAE5-AF7D-452E-BAAB-6DD82A6B0B5A%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-de...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAG%3D_Dut0W%3DJyR48uxTvPpUgZg2vS1nRsAtHREKW%2BGsbjfXRX%3Dw%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/8c9149bf-b71b-4184-a280-2280ad1eeb66n%40googlegroups.com.







--
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/a7c72c09-c9c7-2354-9434-03fb49e317fe%40gmail.com.

Introducing Jenkins Gating subsystem

[Oliver Gondža]

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 infrastructure components that builds interact with (think 
SCM hosting, release servers, support infrastructure, etc.), and make a 
decision of not to run builds or pipeline stages there when they are 
down and when failure is iminnent.


To obtain the needed data, gating-core plugin depends on other plugins 
(specific to individual monitoring tools) that will obtain and report 
infrastructure availability. The other plugin is one such backend for 
Atlassian StatusPage.


Gating core plugin provides:

- The way to visualize the availability of reported resources from all 
available sources (i.e., backend plugins)
- The generic job property to declare dependency on resources, so when 
some of them is down, the build will wait in Jenkins queue until they 
are all up.
- Pipeline block-step that will block execution of its nested steps 
until all resources are up.
- Exposes those data for other plugins that interact with external 
systems can learn out outages in a civilized way.


Note that in the past, Red Hat have also authored `cachet-gating` plugin 
that *do not* implement this general gating approach, and since we are 
abandoning cachet monitoring/reporting system internally, it might as 
well never support it.


Please let me know if there are any questions or comments that you have. 
The broader the perspective before the first release, the better.


[1] https://github.com/olivergondza/gating-core-plugin
[2] https://github.com/olivergondza/statuspage-gating-plugin

Thank you!
--
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/39f8197f-c62a-376c-5d6f-7ed3f1eae30e%40gmail.com.

Data binding: Bind repeatable list of textboxes into List

[Oliver Gondža]

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 databinding only, this is hidden and 
can be read through a dummy data-bound class with field `String name` so 
I can consume `List` and unwrap the strings manually. However, 
this breaks the desired JCasC semantics of:


```
foo:
  - one
  - two
```

I ended up overriding `GlobalConfiguration#configure` to massage the 
Json during form submission only to make it match the straightforward 
type of `List` that also works for JCasC. That, of course, is ugly.


Is there a more elegant way to read list of string inputs and have it 
bound to `List`?


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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/bde36da3-0ed4-d02a-7760-1e54d42dcbf8%40gmail.com.

Releasing JCasC support for ghprb-plugin

[Oliver Gondža]

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
--
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/f3e65b25-477d-a780-ceae-eb8dec945f40%40gmail.com.

Jenkins 2.263.1 LTS RC testing started

[Oliver Gondža]

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 
(sha256:679d2436eb1b537fe378905306cdbf904e2a540dc39f0718aa6cfc68c9bff107)


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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/d93aa1e1-a2c8-743d-80e5-e81a112d6942%40gmail.com.

Jenkins LTS certification process overview

[Oliver Gondža]

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 the reason this is happening (now) is that I will no longer be a 
Release Officer after the election, so it is a first step on handing 
that process over to the community.


https://calendar.google.com/event?action=TEMPLATE=N2FiMnYxcTNzb3FiM3YxdmdqcDJldWdoMjMgNHNzMTJmMG1xcjN0YnAxdDJmZTM2OXNsZjRAZw=4ss12f0mqr3tbp1t2fe369slf4%40group.calendar.google.com

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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/5ba8a174-b031-256f-ec68-2c86a0b2944e%40gmail.com.

Re: LTS schedule winter break

[Oliver Gondža]

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 known yet I wonder whether the calendar could be 
potentially changed to reflect a potentially release freeze for the last 
two weeks of the year and the new week of next year by default? This is 
something that have been happening for the last years as de facto standard,.


Cheers

On Wednesday, 11 November 2020 at 20:41:37 UTC Oleg Nenashev wrote:

I am pretty sure that our Release Automation infra would not mind to
cut a release on Dec 30, but there is still a lot of manual work
involved in cutting an LTS release.
I am +1 for postponing, especially if there are no major issues to
be addressed.

Postponing the release would also give more time for ramp-up to a
new release officer whose term starts on Dec 03.

Best regards,
Oleg


On Wednesday, November 11, 2020 at 7:32:53 PM UTC+1
vsilv...@gmail.com wrote:

+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-de...@googlegroups.com.
To view this discussion on the web visit

Jenkins 2.249.3 LTS RC testing started

[Oliver Gondža]

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 
(sha256:9b6a00807f2539571c5a838ec9494d091089e756fe8eeae3bd2c22d94babecee)


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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/58373d87-4170-cf1a-f004-fc9de92ecc95%40gmail.com.

Re: LTS baseline selection for the successor of 2.249

[Oliver Gondža]

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 built (yet) due to an 
issue with password expiration and the Windows Docker container.


Windows users can install prior weekly releases and use the "Upgrade 
now" button inside Jenkins to install 2.263 on their Windows computer.


On Thu, Oct 22, 2020 at 6:03 PM vsilv...@gmail.com 
 > wrote:


It looks Windows release is not available -
https://github.com/jenkins-infra/jenkins.io/issues/3892

On Thursday, October 22, 2020 at 2:48:45 PM UTC-7 Jesse Glick wrote:

For what it is worth, 2.263 seems reasonable.
https://www.jenkins.io/changelog/ shows no user complaints so far.

-- 
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/30b38bff-19bc-4897-8d1a-d416b6664ef5n%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/CAO49JtGyGEfOQ_0t15-LnqRVHWa31kVZ1QZ8dftkbeea8ohKQg%40mail.gmail.com 
.



--
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/e59ae697-1d6d-055d-6cb7-0fe75f014897%40gmail.com.

LTS baseline selection for the successor of 2.249

[Oliver Gondža]

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 the same time 2.258 (2020-09-22), the latest release 
its changelog is filling me with confidence, feels too old by now.


Thoughts?

https://jenkins.io/changelog/
--
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/ade43a0c-24f6-e065-fb51-4d1fae279cdb%40gmail.com.

Availability of Oliver Gondža in late 2020 and onward

[Oliver Gondža]

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 twins expected to be born in a couple of weeks.


Because of that:

- I will not be a candidate for a Release officer nor a Board member 
this year.

- I will no longer maintain jenkinsci/acceptance-test-harness.
- The responsibility for leading LTS will be gradually transferred to 
some community member interested.


I have truly enjoyed those 8 years in a company of so many talented and 
engaged engineers. It is not that I am leaving never to show up again, 
but this housekeeping is long overdue, and I owe doing this to the 
project and to myself.


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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/0a98fdb2-6f21-d55d-c197-0b32745628ed%40gmail.com.

Jenkins 2.249.2 LTS RC testing started

[Oliver Gondža]

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 
(sha256:da03fb4edb732f8a9b8034944257ba1deccc8790ce79c486369f4b10f87ace2a)


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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/8df6d0ae-2a8b-8825-4893-286474d04d2a%40gmail.com.

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

[Oliver Gondža]

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 have an incremental 
version are also resolved? Incrementals are resolved fine in integration 
tests but in UI tests the official update center is used which does not 
contain the incremental versions.


See: 
https://ci.jenkins.io/job/Plugins/job/warnings-ng-plugin/job/PR-595/5/testReport/io.jenkins.plugins.analysis.warnings/SmokeTests/shouldRecordIssuesInPipelineAndExpandTokens/


java.io.IOException: Failed to load: Warnings Next Generation Plugin 
(8.5.0-SNAPSHOT (private-2e85864e-ubuntu))
master49529| - Plugin is missing: forensics-api (0.8.0-rc587.65fc61fe9be2)


--
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/10362FBD-68D4-4ADD-BEA9-267CB38E6EED%40gmail.com 
.



--
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/aca6a70f-861b-9723-bdf2-d034b4dfc452%40gmail.com.

Jenkins 2.249.1 LTS RC testing started

[Oliver Gondža]

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 
(sha256:b87ac2d3296149d5b28a40016f6394fb1246c6ae8ba18b50ce7b9458a9853992)


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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/964dcec6-7200-9d58-ee7f-3926852824ba%40gmail.com.

Re: Backporting for 2.249.1?

[Oliver Gondža]

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 starting that backport branch soon?

Any issues that might risk the release date of Jenkins 2.249.1?

I've started a draft proposal for a Jenkins Online Meetup to describe 
the new features in 2.249.1.  I'd prefer to host that meetup a few days 
after the release date, so would like to be sure that I am assuming the 
correct release date (September 9).


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/2f6ef0a3-b00d-477c-8556-5d319168dca4n%40googlegroups.com 
.



--
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/2b06a015-cfa0-895d-1c38-f6bee9722119%40gmail.com.

Re: Jenkins 2.235.4 LTS RC testing started

[Oliver Gondža]

Hey, good idea, Baptiste.

The hash of the uploaded file is 
sha256:d83ad972ec4a645e0ce580dd82668af3b0ea4d775f15910fe90a44687c926841.


I will make it part of the future announcements: 
https://github.com/jenkins-infra/backend-commit-history-parser/commit/1eb7c84ab4a397960f72020ff276e5efe551fdd0


On 12/08/2020 08.48, Baptiste Mathus wrote:
IIUC the most important, and quite easy, thing they could be done here 
before we can also have the right thing on server side is for Oliver to 
publish the hash for the local file he uploaded?


This way even if someone was able to midm the http:// server folks could 
check they're testing the expected binaries?


WDYT ?

Oliver, are you able to add the computed hash in this thread?

Thanks

-- Baptiste

Le mar. 11 août 2020 à 17:24, Mark Waite <mailto:mark.earl.wa...@gmail.com>> a écrit :



On Tue, Aug 11, 2020 at 8:55 AM 'Björn Pedersen' via Jenkins
Developers mailto:jenkinsci-dev@googlegroups.com>> wrote:

It looks like the certificate does not  cover all domains that 
are currently server:


This server could not prove that it is mirrors.jenkins-ci.org
<http://mirrors.jenkins-ci.org>; its security certificate is
from pkg.origin.jenkins.io <http://pkg.origin.jenkins.io>. This
may be caused by a misconfiguration or an attacker intercepting
your connection
As it is a letsencyrpt certifacte, maybe just adding the domain

(https://certbot.eff.org/docs/using.html#changing-a-certificate-s-domains
if using certbot)  could help?


   Unfortunately, there's significantly more involved in the
transition than adding an SSL certificate to the domain.

That location is the root of the Jenkins mirrors.  The mirroring
software we use does not support HTTPS.  We're in the process of
switching to new mirroring software that supports HTTPS.

Björn
johno.c...@gmail.com <mailto:johno.c...@gmail.com> schrieb am
Montag, 10. August 2020 um 19:33:23 UTC+2:

Would be great if in the future you could provide a https
link and hashes of the binary. Sadly I did a little bit of
digging and found this ticket..
https://issues.jenkins.io/browse/INFRA-266

J

On Mon, Aug 10, 2020 at 7:25 PM Johno Crawford
 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 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 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/84782d44-dd40-619f-9f6f-2585455bc89d%40gmail.com.



-- 
Johno Crawford




-- 
Johno Crawford


-- 
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
<mailto:jenkinsci-dev+unsubscr...@googlegroups.com>.
To view this discussion on the web visit

https://groups.google.com/d/msgid/jenkinsci-dev/c632c50b-fe72-4f4e-84fb-1f2e47c26901n%40googlegroups.com

<https://groups.google.com/d/msgid/jenkinsci-dev/c632c50b-fe72-4f4e-84fb-1f2e47c26901n%40googlegroups.com?utm_medium=email_source=footer>.

-- 
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
<mailto:jenkinsci-dev+unsubscr...@googlegroups.com>.
To view this discussion on the web visit

https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtGs4EO1gAk_P%3DVXkytxrmzzq7AkqSewrKr4yTd22k_rRw%40mail.gmail.com

<https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtGs4EO1gAk_P%3DVXkytxrmzzq7AkqSewrKr4yTd22k

Jenkins 2.235.4 LTS RC testing started

[Oliver Gondža]

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 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/84782d44-dd40-619f-9f6f-2585455bc89d%40gmail.com.

LTS baseline selection for the successor of 2.235

[Oliver Gondža]

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 
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/3292bcc0-2fb5-08ab-51b6-fb88f53c0eb4%40gmail.com.

Re: LTS next week to change repo signing keys

[Oliver Gondža]

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, 2.235.4 RC on 29th of July and 2.235.4 
Release on 12th of August?


Are there any objections to Mark's proposal?

On 22/07/2020 22.16, Vlad Silverman wrote:

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 
.



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

Jenkins 2.235.2 LTS RC testing started

[Oliver Gondža]

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 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/72b7a25b-2415-d916-33bd-afee9f721f3b%40gmail.com.

Jenkins 2.235.1 LTS RC testing started

[Oliver Gondža]

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 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/c1c58956-ab12-4bfa-56a7-1ee47c6bf8b6%40gmail.com.

Backporting for LTS 2.235.1 under review

[Oliver Gondža]

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 
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/d53ccaf1-fe2f-eea0-2b67-1f9f49e5feca%40gmail.com.

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

[Oliver Gondža]

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 
https://issues.jenkins-ci.org/browse/JENKINS-61197 which states 
2.222.1-fixed but the bug exists in my instance running 2.222.3,


Inspecting the 2.222.1 tag reveals that the bug still exists and was not 
backported 
https://github.com/jenkinsci/jenkins/blob/d66bd8595e531749e842274a806eabab5cc16a32/core/src/main/java/hudson/model/AbstractBuild.java#L866-L869


Hello, thanks for bringing this up. I probably mislabeled the issue. The 
set of backported patches, changelog and upgrade guidelines seems to be 
in sync - that this is not fixed in 2.222.1.


Fixing the issue labels.
--
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/1fd2038a-7be5-02b7-f8de-e38a0989870a%40gmail.com.

Re: Branch for LTS 2.235

[Oliver Gondža]

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 Manso
Sr Software 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/13FFEF99-2492-42EA-A7E5-7DF5E91B134B%40cloudbees.com 
.



--
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/c22ae2e4-2100-dbca-0514-5efe4d730be1%40gmail.com.

Backporting for LTS 2.235.1 started

[Oliver Gondža]

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

--
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/56132bc6-0d40-b81c-b433-9d80acc5041b%40gmail.com.

Jenkins 2.222.4 LTS RC testing started

[Oliver Gondža]

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 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/33daf095-0141-8712-2e9d-7c965211b8d8%40gmail.com.

Re: LTS baseline selection for the successor of 2.222

[Oliver Gondža]

After the discussion on the Governance Meeting, we agreed to go for 
2.235 as a next LTS baseline. 2.235.1 is expected to be out six weeks 
from now.


On 29/04/2020 18.36, Mark Waite wrote:
+1 from me for 2.235, particularly with the additional UI improvements 
in recent releases.


Also assuming that there will be *lots of help testing the release 
candidate* once it is delivered . ☺ ☺ ☺


On Wed, Apr 29, 2020 at 9:59 AM Oleg Nenashev <mailto:o.v.nenas...@gmail.com>> wrote:


+1 for 2.235, assuming that we are conservative about merges this week.

On Wednesday, April 29, 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, Oliver Gondža
 wrote:
 >
 > In accordance we recently approved process changes, we
are doing next baseline section two weeks earlier in the cycle.

Assuming nobody merges something crazy into core this week,
I'm for 2.235.

We've moved the baseline decision earlier to give us the
freedom to choose a very recent release without a lot of
risk and overlapping work schedules, since we'll have 4
weeks to identify and fix problems and back port those
fixes. So I propose we try this and see how it goes.

(FWIW we probably want to figure out what to do about
JENKINS-61937 before the new LTS lands…)

-- 
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/900CA800-A7CB-486B-B49A-93DF05F30CB8%40beckweb.net.

-- 
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
<mailto:jenkinsci-dev+unsubscr...@googlegroups.com>.
To view this discussion on the web visit

https://groups.google.com/d/msgid/jenkinsci-dev/c34d0118-503e-42e3-b6e3-e57384621cf0%40googlegroups.com

<https://groups.google.com/d/msgid/jenkinsci-dev/c34d0118-503e-42e3-b6e3-e57384621cf0%40googlegroups.com?utm_medium=email_source=footer>.

--
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 
<mailto:jenkinsci-dev+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtHCpxgwu3qjVa1RVhn_x44jYhBniu3dOzOPsZZ3SUQJ0A%40mail.gmail.com 
<https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtHCpxgwu3qjVa1RVhn_x44jYhBniu3dOzOPsZZ3SUQJ0A%40mail.gmail.com?utm_medium=email_source=footer>.



--
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/7f972e87-d22b-f5b0-36e9-3c364e56ab49%40gmail.com.

LTS baseline selection for the successor of 2.222

[Oliver Gondža]

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 have introduced 
2 known regressions. They are resolved in 2.234 so that would work as a 
second option, too.


https://jenkins.io/changelog/
--
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/ef5d8ebf-1812-a451-1c75-d9b7344b430d%40gmail.com.

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

[Oliver Gondža]

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 > wrote:


Just to summarize the vote for SSH images:

  * "ssh-agent" - (Tim, Jesse - in PR, Alex, Mark - in Gitter)
  * "ssh-build-agent" - (Daniel, Mark, Tim - in PR, Alex - in PR)
  * "sshd-agent" - (Ivan, Mark, Gavin)

After some consideration, I decided to abstain since I neither use nor 
plan to use this image.
My pull request is already built for "ssh-agent", so I will go ahead 
and setup DockerHub builds for this image.
If there are strong opinions, we have 1-2 extra days to revisit naming 
before the blogpost is shipped.


Best regards,
Oleg


On Monday, April 13, 2020 at 2:04:58 PM UTC+2, Mark Waite wrote:

ssh-build-agents sounds great to me.  +1

On Mon, Apr 13, 2020 at 5:40 AM Tim Jacomb > wrote:

+1

On Mon, 13 Apr 2020 at 11:47, Oleg Nenashev
> wrote:

We did not receive any negative feedback about "SSH Build
Agents" AFAICT. This is also my preference at the moment:
https://github.com/jenkinsci/docker-ssh-slave/pull/50


On Mon, Apr 13, 2020, 12:16 Daniel Beck > wrote:



> On 12. Apr 2020, at 15:59, Oleg Nenashev
> wrote:
>
> Regarding the SSH agent image, will wait till
tomorrow to get more feedback.

The plugin is now called "SSH Build Agents", so it
makes sense to me to call the corresponding image
ssh-build-agent.

In fact, all the labels on
https://hub.docker.com/r/jenkins/ssh-slave
 are
already consistent with that. Any negative feedback on
that since you introduced that?

-- 
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/oxD-Hd_7l9k/unsubscribe

.
To unsubscribe from this group and all its topics,
send an email to jenkin...@googlegroups.com .
To view this discussion on the web visit

https://groups.google.com/d/msgid/jenkinsci-dev/42F47D14-A921-40E8-8F49-8660C9ABDCE5%40beckweb.net

.


-- 
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/CAPfivLB%3DjiicZbY4GbdiKetK0H1rBMPEo%2Bonk_YoXAnm14eQjw%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 jenkin...@googlegroups.com .
To view this discussion on the web visit

https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3BieyVf79FdwrAtwdQfDYLkMV3YSBvX9BP5j_iKRJUiAszw%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/bb22bf86-b71b-4627-9d66-d20ecf9bcf33%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 

Jenkins 2.222.2 LTS RC testing started

[Oliver Gondža]

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

regression
https://issues.jenkins-ci.org/browse/JENKINS-61692

JENKINS-61688   Critical2.229
Global build discarders configuration isn't loaded from disk
https://issues.jenkins-ci.org/browse/JENKINS-61688

JENKINS-61465   Major   2.226
	Make Functions#checkAnyPermission work on objects that aren't 
AccessControlled

https://issues.jenkins-ci.org/browse/JENKINS-61465

JENKINS-61279   Minor   2.224
Update version number dependency to 1.7
https://issues.jenkins-ci.org/browse/JENKINS-61279

JENKINS-60788   Minor   2.224
NullPointerException when hitting Check Now against a custom update 
center
https://issues.jenkins-ci.org/browse/JENKINS-60788

JENKINS-60454   Major   2.223
Jenkins.instance is missing after restart
https://issues.jenkins-ci.org/browse/JENKINS-60454
```

Please, report your findings in this thread.

Download bits from 
http://mirrors.jenkins-ci.org/war-stable-rc/2.222.2/jenkins.war


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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/a4b44451-9b24-7c14-c7b4-a2af84540638%40gmail.com.

Backporting for LTS 2.222.2 started

[Oliver Gondža]

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 we have a 
consensus of what goes in by 2020-04-08.


Backporting PR: https://github.com/jenkinsci/jenkins/pull/4618

Candidates: https://issues.jenkins-ci.org/issues/?filter=12146
Fixed: 
https://issues.jenkins-ci.org/issues/?jql=labels%20%3D%202.222.2-fixed
Rejected: 
https://issues.jenkins-ci.org/issues/?jql=labels%20%3D%202.222.2-rejected


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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/0bf36d17-2b3b-9427-b071-2ed5b6a6aba5%40gmail.com.

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

[Oliver Gondža]

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 new baselines 
effectively shortening the core soak time. Making the call 2 weeks 
sooner (no matter how new the core) will create the time buffer for more 
issues to be discovered and fixed before the LTS is published.


- Core developers/reviewers tend to be busy testing during RC testing 
periods and preparing weeklies that are likely to be chosen an LTS 
baseline (LTS week 10-12). Making the call 2 weeks sooner will prevent 
the two to overlap.


Please let us know your thoughts and concerns by the end of the week.

[1] 
https://docs.google.com/document/d/1NzR1XtkCfk6MDSD1jRq5H-iPSjqKvP-pfUO0b9lVZ9k/edit?disco=JRfN_wA

[2] https://github.com/jenkins-infra/jenkins.io/pull/3017

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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/b428a179-b218-7913-6142-a6d086e09169%40gmail.com.

Jenkins 2.222.1 LTS RC testing started

[Oliver Gondža]

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). 
We have also decided to include the train of winstone/jetty fixes[2, 3, 
4, 5], wiling to revert that (from 5.9 to 5.3) in case it will case 
further problems.


Download bits from 
http://mirrors.jenkins-ci.org/war-stable-rc/2.222.1/jenkins.war


[1] https://issues.jenkins-ci.org/browse/JENKINS-61429
[2] https://issues.jenkins-ci.org/browse/JENKINS-60857
[3] https://issues.jenkins-ci.org/browse/JENKINS-60409
[4] https://issues.jenkins-ci.org/browse/JENKINS-60199
[5] https://issues.jenkins-ci.org/browse/JENKINS-57888

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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/43c1c7d8-7da7-6671-85ff-94d7b2359685%40gmail.com.

Re: Proposal: Emeritus maintainers

[Oliver Gondža]

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 to wait for bob's timeout of two weeks to pick
up the plugin?

For sure if Bob is maintaining the plugin actively and has commits
etc then Bob should be respected... but if Bob is don;t nothing and
hasn't moved himself to Emeritus, should he be entitled to block me
from picking the plugin back up?\


This all makes sense in a way, but then we get to choose between a 
really complex decision tree (what even counts as actively maintained?), 
or just improvising every time (i.e. have a vaguely defined judgment 
call in there somewhere).


I tend to agree this is getting way to complex given the limited value I 
can see in this.


What is an effective difference for such a one-year-restricted 
fast-track-reintroduced emeritus maintainer and a "real" maintainer that 
just not commit in a while? I mean, it appears simpleer to just keep 
being a maintainer...


--
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/63f29269-0a84-41a5-0863-156920d070c3%40gmail.com.

Backporting for LTS 2.222.1 started

[Oliver Gondža]

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

--
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/45338843-8203-1137-0918-0dfe9fcfa248%40gmail.com.

Re: LTS baseline selection

[Oliver Gondža]

The have almost unanimous support for 2.222. Since users can opt-out 
from the potentially breaking changes, I do not see a reason why not to 
use it.


On 25/02/2020 13.04, Oleg Nenashev wrote:
Regarding 2.222... I believe there is a lot for interest to get 2.222 in 
the LTS so that plugins could start adapting to the new Systemread and 
Manage permissions earlier. There is a lot of experimental features and 
new APIs included there, and I believe it would be valuable for the 
Jenkins community if this release was selected as an LTS baseline. At 
the same time, I admit that the release has not been battle tested for long.


Some notes:

  * 2.222 was released this Sunday, and the release metrics are yet to
be seen.
  o The community rating is 19 positives and 2 "I had to rollback"
  o There is no issues reported to this release in Jira or in social
media
  o There is one negative feedback in the UX SIG Gitter
<https://gitter.im/jenkinsci/ux-sig> about the header size in
the default UI. The header went from 68px to 96px (thanks
Wadeck) and caused some feedback about mispositioned controls
and impact on muscle memory by Rocky Breslow. I consider it as
an important feedback, but AFAICT we can optimize the header
size and backport the change if needed
  * 2.221 has a flawless community rating (31 positive), there is no
regressions reported
  o JENKINS-61121
<https://issues.jenkins-ci.org/browse/JENKINS-61121> will need
to be backported if we chose this release
  * Issues in both releases
  o There is a JENKINS-61197
<https://issues.jenkins-ci.org/browse/JENKINS-61197> regression
which impacts custom workspaces in the root directory (or
Windows drive label). I am working on a fix, it should be
backportable

My personal preference would be to go with 2.222 unless there are major 
issues discovered there by the RC date. In order to make it happen, we 
should at least process the UX report with the header. I deployed 2.222 
on my local setup, and it looks good with the default setting and with 
Manage and SystemRead permissions enabled. Experimental Web UI works as 
well, but I reverted to the classic one.


BR, Oleg


On Tuesday, February 25, 2020 at 11:39:35 AM UTC+1, Baptiste Mathus wrote:



On Tue, 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 baselines still selected during governance meetings? I thought
that had switched to the list.


I /think/ the discussion happens here a lot, but the final /stamp/
after the trend/discussion/decision here is still done during gov
meeting (still makes sense IMO).



-- 
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/CANfRfr1C4wg1EiT18OuyG3Mi3WeZspgwtUuqpME2L_7P-O%2B_CQ%40mail.gmail.com

<https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr1C4wg1EiT18OuyG3Mi3WeZspgwtUuqpME2L_7P-O%2B_CQ%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 
<mailto:jenkinsci-dev+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/a98cbee5-e2b9-4164-be01-7f7c5c2ddbfe%40googlegroups.com 
<https://groups.google.com/d/msgid/jenkinsci-dev/a98cbee5-e2b9-4164-be01-7f7c5c2ddbfe%40googlegroups.com?utm_medium=email_source=footer>.



--
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/3b262486-7cdf-d6ef-cc04-12b68df74230%40gmail.com.

LTS baseline selection

[Oliver Gondža]

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 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/9e08b697-7d0d-01b0-f165-6b063df7c83b%40gmail.com.

Re: Jenkins 2.204.3 LTS RC testing started

[Oliver Gondža]

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 the URL you provided 
http://mirrors.jenkins-ci.org/war-stable-rc/2.204.3/jenkins.war and the 
sha245sum that I see is still the original, not the new one that you 
provided.


On Mon, Feb 17, 2020 at 5:09 AM ogondza > wrote:


Mark, thanks for reporting this. I have published an RC respin[1]
with Java 8, until we identify the reason why is this causing problems.

Please make sure the ongoing testing is done with
ca01d0bf523d6752f54277ca4c91feef0d60acc75c42d65f65bbefe09f9e8e69
(sha256). Thanks!

[1] http://mirrors.jenkins-ci.org/war-stable-rc/2.204.3/jenkins.war

--
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 jenkinsci-dev+unsubscr...@googlegroups.com
.
To view this discussion on the web visit

https://groups.google.com/d/msgid/jenkinsci-dev/005cb301-b149-44b4-bf3a-25dbd5ca35dd%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/CAO49JtGY783zJoVQXbz3xpa7j-bmh3nnrY20ThQYU660STX9zg%40mail.gmail.com 
.



--
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/86c961e2-c861-c4a6-80e0-fd60b70e15b5%40gmail.com.

Jenkins 2.204.3 LTS RC testing started

[Oliver Gondža]

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 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/c39ac777-ee73-66ad-1b62-9fc473aae342%40gmail.com.

Re: 2.204.3 RC

[Oliver Gondža]

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 7:16:34 PM UTC+1, Raul Arabaolaza wrote:

Hello all,

According to the calendar the 2.204.3 RC should be out yesterday
Wednesday 12th, but it seems is not yet and there are no new commits
in the stable-2.204 branch since 16 days ago. Has it been delayed
for some reason?

Regards

-- 


Raul Arabaolaza Barquin
Staff Software Engineer

CloudBees, Inc.



P: +34-637340429
E: rarab...@cloudbees.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/aefb4360-0a58-42e5-8f91-086df2da49d1%40googlegroups.com 
.



--
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/6bc8920f-b5e6-f101-0d44-5000cecaae0f%40gmail.com.

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

[Oliver Gondža]

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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/60817275-605c-420b-a1a2-83c4f1a95668%40gmail.com.

Re: SonarCloud JenkinsCI organisation?

[Oliver Gondža]

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


- It does work for master and branches, but cannot work for pull 
requests AFAIK. The problem there is travis is injecting the credentials 
(so results can be published), but it does not inject that in case the 
code comes from out of given repo for security reasons.


[1] 
https://github.com/jenkinsci/ws-cleanup-plugin/commit/c7553f470723c4ec0749b49f944ba97cb4a3e230#diff-354f30a63fb0907d4ad57269548329e3

[2] https://sonarcloud.io/dashboard?id=jenkins_ws-cleanup-plugin

On 02/02/2020 13.00, Oleg Nenashev wrote:
Thanks for raising this in their community forum! I often meet with 
SonarSource engineers and PMs at meetups in Switzerland, and I will make 
sure to bring up this topic with them


On Sun, Feb 2, 2020, 12:26 Radosław Antoniuk > wrote:


Hi Oleg,

Thanks for picking this up. Yes, I totally agree that the
requirement for the organisation admin to link to specific
repository won't work in the Jenkins OSS forking approach.
I already asked the same question in the help forum and let's see
where it goes from there:

https://community.sonarsource.com/t/unable-to-create-organisation-account-with-github/19322/3
The problem with personal forks is that I wanted to have this in the
Pull Request process which won't work unless every "forker" will
configure it for them.
I'll give it a try to configure this manually via maven plugin and
variable token though, but not sure if I can get the PR comments
automatically in this way.

Cheers,
Radek


On Sat, Feb 1, 2020 at 11:56 PM Oleg Nenashev
mailto:o.v.nenas...@gmail.com>> wrote:

Hi all,

UPD: it looks like we cannot really add projects to SonarCloud
without linking the entire organization there.
Not going to happen without explicit approval by the security
team and the governance meeting.

I suggest other alternate options:

  * Use personal forks for analysis. It nukes all benefits from
pull requests integration
  * Contact SonarCloud support to allow adding new projects
without linking the entire organization
  * Use alternate services which have a less greedy requirements

BR, Oleg


On Saturday, February 1, 2020 at 11:46:59 PM UTC+1, Oleg
Nenashev wrote:

Looks like the project IDs are already used for jenkins:
https://sonarcloud.io/dashboard?id=jenkins
"jenkinsci" is a registered organization, I believe. We have
3 repos with enabled SonarCloud app:

sonarcloud.PNG

Additionally, apparently I need organisation admin
permissions on github.com/jenkinsci
 organisation to be able to
link it automatically.


I am not sure it is something we want. If we add
organization, all 2000+ Jenkins GitHub org members will be
added to SonarCloud/
Not sure we would ever want to do so, and definitely it will
require a long discussion.

If someone is interested, I manually created an org manually
for now: https://sonarcloud.io/organizations/jenkinsci/
I can add anyone who is interested in evaluation. Mark and
Stefan were definitely talking about it at the contributor
summit yesterday...



On Saturday, February 1, 2020 at 3:10:37 PM UTC+1, Radek
Antoniuk wrote:

Hey,

I'm trying to hook jira-plugin into SonarCloud, but when
I'm trying to create jenkins or jenkinsci organisation,
it shows me that the organisation already exists.
Additionally, apparently I need organisation admin
permissions on github.com/jenkinsci
 organisation to be able to
link it automatically.

Anyone knows if we have already the organisation on
SonarCloud?

-- 
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/aBdbOyKU2B8/unsubscribe.
To unsubscribe from this group and all its topics, send an email
to jenkinsci-dev+unsubscr...@googlegroups.com
.
To view this discussion on the web visit

Jenkins 2.204.2 LTS RC testing started

[Oliver Gondža]

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 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/88d47b08-44b6-47cb-bc6d-fd059e5ec7cf%40gmail.com.

Re: JAMS in meetup account disappearing

[Oliver Gondža]

+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 inactive meetups. There is a proposal below


Some updates there:

  * As communicated by Tracy, the root cause is that meetup.com support
removed more meetups than it was requested by CDF.
  * Last week we had a meeting with CDF where we discussed the issue.
Participants: Alyssa Tong (Jenkins Event Officer), Jacqueline
Salinas (Director of Ecosystem, CDF), Tracy Miranda and me
  * At this meeting we agreed that:
  o Removed meetups meetups will be restored. It will take a while
since it is a lengthy manual process by meetup.com support
  o CDF will grant us an additional grace 3-month grace period to
try restoring inactive meetups in the Jenkins community (and/or
to convert them to CI/CD meetups). Heads-up about cleaning up
inactive meetups was sent out on *Oct 26* to meetup organizers,
so we will need to reimplement the process and do additional
communications
  o If meetups are not restored, CDF will use the "step down"
process


instead of deleting the meetups. It will give the local
communities an additional chance to restore the meetups

Just to explain the reasons of the Jenkins Area Meetups cleanup:

  * Running CI/CD Pro Meetup.com account
 costs *12k USD per quarter*.
The majority of these costs used to go to *106 *Jenkins Area Meetups
  * CDF has a limited budget for Outreach programs and meetups. They are
happy to sponsor active meetups, but in the case of Jenkins we
accumulated a number of inactive ones
  * Meanwhile, more than 60% of the meetups are dormant. Inactive
meetups cost the same amount of money as active ones
  o *27* JAMs groups have NEVER had a meetup on meetup.com
  o *40* other JAMs did not have any events organized in 2019
  * Dormant JAMs prevent CDF from...
  o Sponsoring swag/food/venue for meetups and other events
  o Onboarding new CI/CD and Jenkins meetups in active local communities
  o Organizing other events and running outreach programs

So you may see there is a good reason to cleanup meetups which are 
really inactive. Some of us might be mentally attached to these meetups 
(e.g. I was a co-org in several removed meetups), but IMO we need to 
face the reality and adjust our meetup program. I would suggest the 
following process:


 1. Wait till meetups are restored
 2. Do a best effort attempt to revive the meetups
  * Communicate the incoming deprecation/cleanup of meetups AGAIN to
meetup organizers and all meetup members
  * For meetups that never happened
  o CDF steps down


as an organizer immediately after the meetup recovery.
Current meetup leaders can take it over. If it does not
happen, all meetup members will have 2 weeks to react and
take over the meetups
  o If reactivated, meetups can rejoin again by following the
process defined by CDF 
  * For meetups with at least one event in the past
  o 3-month grace period is applied
  o During this period we will try to contact meetup organizers
and members through community channels and get the meetups
scheduled
  o If there are no meetups happen/get announced, CDF steps down
as an organizer. Current meetup leaders can take it over or
step down as leaders
  o If reactivated, meetups can rejoin again by following the
process defined by CDF 
 3. Simplify the meetup process
  * CDF takes over the most of the operations responsibilities (see
the JAM pull request from Alyssa
)
  * We could simplify the meetup process and bound it to the
Advocacy SIG to keep things simple
  o Advocacy SIG is open to help meetup organizers to
get their meetup started (mostly by advice since operations
are managed by CDF)
  o jenkinsci-jam and events mailing lists are archived. The
latter one is just inactive, the first one is plagued by
spam and no longer used for meetup operations purposes
  o Advocacy channels are used instead
  * Jenkins project might still use some of its own money to
facilitate the meetups in addition to 

Re: S3 plugin maintainership status

[Oliver Gondža]

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 
#124|https://github.com/jenkinsci/s3-plugin/pull/124] on the S3 plugin. 
It has not been reviewed or merged yet. I also noticed that there are 
quite a lot of open PRs and that the plugin hasn’t been released for 
more than a year and half.


Possibly it is bad timing because of the holiday season. However if this 
is not the case, CloudBees would be more than happy to provide help and 
support with keeping the plugin up to date and secure. We would like to 
request co-maintainership for the plugin, unless there are active plans 
to make a new release of the plugin.
CloudBees see the S3 Plugin as being a critical plugin for Jenkins users 
that want to run their builds on AWS.


Best regards.

--
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/232122fa-a6a7-4488-b168-2e4cb25f671c%40googlegroups.com 
.



--
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/6a0ed53c-2391-e10b-5cb7-a3348760a95d%40gmail.com.

Re: Archiving jenkinsci/groovy repo

[Oliver Gondža]

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 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 and it
will
not be searched for vulnerabilities, noone is interested in.

[1] https://github.com/jenkinsci/groovy
[2]

https://github.com/jenkinsci/jenkins/commit/b8673633da9aa4f0632a4a9e1fc26729cfca0f9e

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 jenkinsci-dev+unsubscr...@googlegroups.com
<mailto:jenkinsci-dev%2bunsubscr...@googlegroups.com>.
To view this discussion on the web visit

https://groups.google.com/d/msgid/jenkinsci-dev/3ce4514d-3464-6003-2f96-7125155c18eb%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 
<mailto:jenkinsci-dev+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAFoxvgwcj-gBCuxUyfm_w-VogutwXbtNmohigmm_9NSaw-oweg%40mail.gmail.com 
<https://groups.google.com/d/msgid/jenkinsci-dev/CAFoxvgwcj-gBCuxUyfm_w-VogutwXbtNmohigmm_9NSaw-oweg%40mail.gmail.com?utm_medium=email_source=footer>.



--
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/56421f16-b20b-361b-5dde-f402ff856429%40gmail.com.

Archiving jenkinsci/groovy repo

[Oliver Gondža]

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 and it will 
not be searched for vulnerabilities, noone is interested in.


[1] https://github.com/jenkinsci/groovy
[2] 
https://github.com/jenkinsci/jenkins/commit/b8673633da9aa4f0632a4a9e1fc26729cfca0f9e


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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/3ce4514d-3464-6003-2f96-7125155c18eb%40gmail.com.

Jenkins 2.204.1 LTS RC testing started

[Oliver Gondža]

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 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/4b2807a0-01dc-1fc1-5a2f-9ffca19a86d9%40gmail.com.

Re: LTS schedule winter break

[Oliver Gondža]

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 between Dec 18 and Jan 1.

Hence I propose we take a two week break as in past years, postponing the RC 
and release of .2 (and all subsequent releases) by two weeks, so that the new 
dates are:

- Dec 18: .1 release (unchanged)
- Jan 15: .2 RC
- Jan 29: .2 release
- Feb 12: .3 RC
etc.

Thoughts?

Daniel
--

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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/5f866dfc-3e34-266b-4468-383319c3012b%40gmail.com.

Re: Possible LTS regression in commons-compress

[Oliver Gondža]

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.

On 27/11/2019 12.50, James Nord wrote:
I have tracked the cause of the issue to an optimisation we had for the 
old Hudson code to not flush all the time to prevent lots of small 
chunks being flushed (as the old implementation flushed for each block 
(512 bytes))


If I disable that then the code works with 1.15 and above.  I have not 
looked into the code to see if commons compress also has issues with 
flushing, but I doubt any other plugins will be doing any similar 
optimisation.


/James




On Wednesday, November 27, 2019 at 8:23:47 AM UTC, Baptiste Mathus wrote:

Sounds to me we should git bisect commons-compress between 1.14 and
1.15 usage, to nail and possibly confirm Björn's hypothesis?

On Wed, Nov 27, 2019 at 8:36 AM 'Björn Pedersen' via Jenkins
Developers > wrote:

Hi,

I have 2 changes that seem candiates:
1) 1.15 enforces blocklen=512 which is different from the old
default and raises an error if anything else is specified
  
(https://commons.apache.org/proper/commons-compress/javadocs/api-1.19/index.html 
)
2) 1.16 renamed the preserveAbsolutePath to |TarArchiveEntry

(String


 name,
boolean preserveAbsolutePath)|
|(less likely that is the cause).
|

Björn

Am Mittwoch, 27. November 2019 01:03:40 UTC+1 schrieb James Nord:

Hi all,

just a quick note, I /think /I have discovered a regression
in 2.204 upcoming LTS due to commons-compress library bump.

One of our plugins was using TarInputStream

for
2.190 but this is now restricted.
so without bumping core we moved the code over to use the
commons-compress version (and all is happy).

However when bumping the Jenkins version to 2.204 which
picks up the newer compress we have lots of unit test
failures due to what seems like (at very first glance as I
just narrowed it down and its late!) empty tar files (when
they should not be empty)

as a (quick and dirty) test I made the commons-compress
version configurable and it does seem like this is the issue

mvn test -Dtest=TheTest -Djenkins.version=2.204
-DcompressVersion=1.19 -Denforcer.skip *fails*
mvn test -Dtest=TheTest -Djenkins.version=2.204
-DcompressVersion=1.10 -Denforcer.skip passes
mvn test -Dtest=TheTest -Djenkins.version=2.190.3
-DcompressVersion=1.10 -Denforcer.skip passes
mvn test -Dtest=TheTest -Djenkins.version=2.190.3
-DcompressVersion=1.19 -Denforcer.skip *fails
*
doing some more bisection

mvn test -Dtest=TheTest -Djenkins.version=2.190.3
-DcompressVersion=1.15 -Denforcer.skip *fails
*mvn test -Dtest=TheTest -Djenkins.version=2.190.3
-DcompressVersion=1.13 -Denforcer.skip passes
mvn test -Dtest=TheTest -Djenkins.version=2.190.3
-DcompressVersion=1.14 -Denforcer.skip passes


I don't yet know what is causing this (but it does appear to
be something in commons-compress 1.15 and I will investigate
that.  (changelog

)

But this seems very scary to me (and I am surprised there
has not been some reports in the weeklies of archives etc
not working correctly).  Also very weired as 1.15 has been
released for a good amount of time.

Will continue the investigation tomorrow but if this rings a
bell with anyone in any reported Jiras it would be good to
correlate.

/James

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

Re: LTS schedule winter break

[Oliver Gondža]

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,

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 between Dec 18 and Jan 1.

Hence I propose we take a two week break as in past years,
postponing the RC and release of .2 (and all subsequent releases) by
two weeks, so that the new dates are:

- Dec 18: .1 release (unchanged)
- Jan 15: .2 RC
- Jan 29: .2 release
- Feb 12: .3 RC
etc.

Thoughts?

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-dev+unsubscr...@googlegroups.com
.
To view this discussion on the web visit

https://groups.google.com/d/msgid/jenkinsci-dev/7D652E56-59DA-4C41-A48A-D05CBA6CCFA0%40beckweb.net.



--
Thanks!
Mark Waite



--
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/5499a505-1ead-4c3a-c0c2-c46c27be5e0b%40gmail.com.

Re: Next LTS baseline selection

[Oliver Gondža]

I am glad to hear that. I have started backporting things today but I am 
leaving this thing untouched and waiting for feedback. And that is 
positive for now.


On 26/11/2019 12.47, James Nord wrote:
just following up the workaound for Config as Code plugin was tested by 
夏润泽and shown to work. it has also been merged.


http://github.com/jenkinsci/configuration-as-code-plugin/pull/1204

On Thursday, November 21, 2019 at 6:54:20 PM UTC, ogondza wrote:

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:ogo...@gmail.com >> wrote:
 >
 >
 >         Are there any objections to choosing 2.204 as the next
baseline
 >         and iron
 >         out what to do about JENKINS-58993 in next two weeks?
 >
 >
 >     I agree this is the most pragmatic approach.
 >
 >
 > That is my preference as well.
 >
 >     --
 >     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 
 >     <mailto:jenkinsci-dev+unsubscr...@googlegroups.com
>.
 >     To view this discussion on the web visit
 >

https://groups.google.com/d/msgid/jenkinsci-dev/CAMo7PtKh0z7hqv5LFF03HQkkj%3DTV57%2BAJviDZ%2B0QrmZC1RtgUA%40mail.gmail.com

<https://groups.google.com/d/msgid/jenkinsci-dev/CAMo7PtKh0z7hqv5LFF03HQkkj%3DTV57%2BAJviDZ%2B0QrmZC1RtgUA%40mail.gmail.com>

 >
<https://groups.google.com/d/msgid/jenkinsci-dev/CAMo7PtKh0z7hqv5LFF03HQkkj%3DTV57%2BAJviDZ%2B0QrmZC1RtgUA%40mail.gmail.com?utm_medium=email_source=footer


<https://groups.google.com/d/msgid/jenkinsci-dev/CAMo7PtKh0z7hqv5LFF03HQkkj%3DTV57%2BAJviDZ%2B0QrmZC1RtgUA%40mail.gmail.com?utm_medium=email_source=footer>>.

 >
 >
 >
 > --
 > 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 jenkin...@googlegroups.com 
 > <mailto:jenkinsci-dev+unsubscr...@googlegroups.com >.
 > To view this discussion on the web visit
 >

https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtH5_oSB2s48VjViRYbXUcXfqigWyWD0idynfhbfXy%2Bfew%40mail.gmail.com

<https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtH5_oSB2s48VjViRYbXUcXfqigWyWD0idynfhbfXy%2Bfew%40mail.gmail.com>

 >

<https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtH5_oSB2s48VjViRYbXUcXfqigWyWD0idynfhbfXy%2Bfew%40mail.gmail.com?utm_medium=email_source=footer

<https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtH5_oSB2s48VjViRYbXUcXfqigWyWD0idynfhbfXy%2Bfew%40mail.gmail.com?utm_medium=email_source=footer>>.



-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com 
<mailto:jenkinsci-dev+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/e7a0ee81-e2c4-411b-97bd-c01256a8ef10%40googlegroups.com 
<https://groups.google.com/d/msgid/jenkinsci-dev/e7a0ee81-e2c4-411b-97bd-c01256a8ef10%40googlegroups.com?utm_medium=email_source=footer>.



--
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/70f9835b-4970-6bdf-6bca-99a5474db8d2%40gmail.com.

Backporting for LTS 2.204.1 started

[Oliver Gondža]

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

--
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/a475bbad-ae62-9b87-f932-1a31105413cb%40gmail.com.

Re: Next LTS baseline selection

[Oliver Gondža]

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:


Are there any objections to choosing 2.204 as the next baseline
and iron
out what to do about JENKINS-58993 in next two weeks?


I agree this is the most pragmatic approach.


That is my preference as well.

-- 
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
<mailto:jenkinsci-dev+unsubscr...@googlegroups.com>.
To view this discussion on the web visit

https://groups.google.com/d/msgid/jenkinsci-dev/CAMo7PtKh0z7hqv5LFF03HQkkj%3DTV57%2BAJviDZ%2B0QrmZC1RtgUA%40mail.gmail.com

<https://groups.google.com/d/msgid/jenkinsci-dev/CAMo7PtKh0z7hqv5LFF03HQkkj%3DTV57%2BAJviDZ%2B0QrmZC1RtgUA%40mail.gmail.com?utm_medium=email_source=footer>.



--
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 
<mailto:jenkinsci-dev+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtH5_oSB2s48VjViRYbXUcXfqigWyWD0idynfhbfXy%2Bfew%40mail.gmail.com 
<https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtH5_oSB2s48VjViRYbXUcXfqigWyWD0idynfhbfXy%2Bfew%40mail.gmail.com?utm_medium=email_source=footer>.



--
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/075bc6f8-726b-0aea-01b1-935023a2a939%40gmail.com.

Re: Next LTS baseline selection

[Oliver Gondža]

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? Or 
does 'baseline' include a distinction between '2.204' and '2.204 with 
LTS only revert of 58993'?


Good point. I do not suggest to go with 2.198 so this really is about 
2.204 with or without JENKINS-58993 enforcement.


Are there any objections to choosing 2.204 as the next baseline and iron 
out what to do about JENKINS-58993 in next two weeks?

--
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/11be6366-215c-a86f-83a3-faa80835f42a%40gmail.com.

Re: Next LTS baseline selection

[Oliver Gondža]

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, correct me if I a wrong). So from this standpoint, I see the 
claim that "no level of dataloss is acceptable" (while breaking JCasC 
users) a bit, for the lack of better word, fundamentalistic. All I am 
after here is to find the reasonable balance between the added safety of 
your fix and the impact on the JCasC customers.


So for now, it seems to me the most of the folks lean towards shipping 
the fix the way it is and documenting eventual consequences.


Are we ok to see how the JCasC PR is doing before committing to an LTS 
baseline?


On 21/11/2019 11.38, James Nord wrote:
I will state this again -*no level of dataloss is acceptable* - we 
should not back this change out or make it disabled by default.


There is a drive by untested PR to Configuration As Code plugin if 
someone wants to look at it.


https://github.com/jenkinsci/configuration-as-code-plugin/pull/1204

/James

On Thursday, November 21, 2019 at 7:51:39 AM UTC, ogondza wrote:

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 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/3588ff14-54bc-4d6e-99c8-1144bc502683%40googlegroups.com 
.



--
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/285c28ec-53ef-4dfe-3b3a-8526c63b3920%40gmail.com.

Re: Next LTS baseline selection

[Oliver Gondža]

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 only during unit tests, so 
we cause plugin maintainers to fix things before they hit people's 
production (not in 100% of cases, I know)?


Also, I know I risk this was already discussed, but can we wrap the 
whole milestone execution into Jenkins BulkChange so whatever saves will 
be acted upon once the milestone is over?


On 20/11/2019 19.52, James Nord wrote:

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 before it has been loaded causing race conditions and potential 
dataloss (infact I have observed data-loss which is why I wrote that 
defensive code to begin with)


there have not been that many (as far as I can tell) reports of this, so 
I would say you can work around that in a plugin that at least means you 
are not susceptible to dataloss (at the expense of Jenkins startup time).




On Wednesday, November 20, 2019 at 6:00:43 PM UTC, 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:49:31 PM UTC+1, Oleg Nenashev
wrote:

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 ratings, but I do
not see particular issues in JIRA which would block it.
All changes are relatively minor, and 2.203 ratings were fine.

In 2.204 we would really want to have
https://issues.jenkins-ci.org/browse/JENKINS-59679
 from Zbynek
so that we can proceed with plugin documentation
migration.without impacting UX for LTS users.

Best regards,
Oleg

On Wednesday, November 20, 2019 at 3:05:23 PM UTC+1, Jesse Glick
wrote:

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 visit 
https://groups.google.com/d/msgid/jenkinsci-dev/a5f74add-9e84-4882-aad5-916b24064459%40googlegroups.com 
.



--
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/cd592d69-9273-7ccc-d2bd-6f1f9218e684%40gmail.com.

Re: Next LTS baseline selection

[Oliver Gondža]

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:49:31 PM UTC+1, Oleg Nenashev wrote:

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 ratings, but I do not
see particular issues in JIRA which would block it.
All changes are relatively minor, and 2.203 ratings were fine.

In 2.204 we would really want to have
https://issues.jenkins-ci.org/browse/JENKINS-59679
 from Zbynek so
that we can proceed with plugin documentation migration.without
impacting UX for LTS users.

Best regards,
Oleg

On Wednesday, November 20, 2019 at 3:05:23 PM UTC+1, Jesse Glick wrote:

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 visit 
https://groups.google.com/d/msgid/jenkinsci-dev/a3026a36-8f17-4804-98d3-cc70c24a7d75%40googlegroups.com 
.



--
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/9fca53ac-8b62-56e2-69f7-e38ec6cb205f%40gmail.com.

Next LTS baseline selection

[Oliver Gondža]

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, smallish with no radical changes while 
reasonable recent.


https://jenkins.io/changelog/
--
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/9f8b066c-7a29-fef9-2904-3a77b89ff5a1%40gmail.com.

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

[Oliver Gondža]

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 > wrote:


Hi all,

As you probably know, there is ongoing work on automating Jenkins
Core releases within the Jenkins infrastructure. Apart from Linux
and Windows distributions, there is also a OS X installer which is
being produced for each Weekly and LTS release in the current
release environment (download link
).
There are also a homebrew formula
 being maintained by the
HomeBrew community, these packages are even listed in our
installation guide .

In the new environment we use MS Azure, and there is no good way to
produce OS X builds there, because they require MacOS. We could use
an external service for that, but it would add additional point of
failure and implementation/maintenance overhead. Since the HomeBrew
is a defacto standard in MacOS, I do not think it worth the effort.
What f we just stop shipping them?

Implementation plan:

  * Deprecate in the next weekly releases
  o It requires a changelog entry in one of the next weekly
releases + LTS upgrade guideline entry + likely a
deprecation blogpost
  * Use HomeBrew as a recommended source of MacOS installers, mark
it as a 3rd-party installer like we do for other downloads
  *
  * Remove MacOS native packaging from Jenkins release Pipelines
once we fully switch to automated releases

WDYT?

Best regards,
Oleg



-- 
You received this message because you are subscribed to the Google

Groups "Jenkins Platform SIG" group.
To unsubscribe from this group and stop receiving emails from it,
send an email to jenkins-platform-sig+unsubscr...@googlegroups.com
.
To view this discussion on the web visit

https://groups.google.com/d/msgid/jenkins-platform-sig/CAPfivLC_G-MGPH_GOiZkjba%2BcA4SbUpxpLFVj%3D0vC81Y48%2BufQ%40mail.gmail.com

.



--
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/CAO49JtFZt%3DOq3NCSD%2BwQGeKH6QkBBGaVBHZCwbFxvDTV751P_A%40mail.gmail.com 
.



--
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/a0a0059a-aa99-efb5-a8f4-71e2891a0332%40gmail.com.

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

[Oliver Gondža]

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 cannot be count. What about 
building a third party statistic site. And we can publish this data 
besides the official one as a reference. What do you think about this?


Best,
Rick

On Fri, Nov 15, 2019 at 6:52 PM 'Björn Pedersen' via Jenkins Developers 
mailto:jenkinsci-dev@googlegroups.com>> 
wrote:


Hi,

So the idea is to omit the round-trip to the main update center on
each download. Community-wise this has one downside: all those
downloads then do not show up in the download statistics.
But the same is true for all fully private mirrors behind firewalls
that serve updatecenter.json  with internal urls.


Björn

Am Donnerstag, 14. November 2019 13:45:11 UTC+1 schrieb Rick:

Hi Baptiste,

Thanks for your response. Jenkins download the plugin by the URL
which comes from update-center.json. For example this plugin

http://updates.jenkins-ci.org/download/plugins/AnchorChain/1.0/AnchorChain.hpi.

The problem is that it’s too slow for me. I hope jenkins can
download it from

https://mirrors.tuna.tsinghua.edu.cn/jenkins/plugins/AnchorChain/1.0/AnchorChain.hpi.


-- 
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/4e01b094-d310-448c-9706-6ed526a36e52%40googlegroups.com

.



--
Zhao Xiaojie (Rick)
Blog: https://github.com/LinuxSuRen
Twitter: https://twitter.com/suren69811254

--
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/CAMM7nTF%3Ddk69exkvWN0Tv6rsdDa0cbcCLDSHaf8KxTsqKdgdRg%40mail.gmail.com 
.



--
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/2e072c53-8421-a371-f9d5-4e53e5c88cd3%40gmail.com.

Re: Proposal: Jenkins Browser Support policy updates

[Oliver Gondža]

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 old. E.g. we say that Safari 6+ are 
fully supported, ouch. It does not look like we had any major changes 
since the inception of the policy in 2014. I have created a pull reques 
t to move the 
policy to jenkins.io, and I would like to make some changes to actualize it.


What do I propose?

  * Chrome, Firefox, IE, Safari
  o Level 1:
  + "Latest regular release, latest minor release / patch level"
  o Level 2:
  + Previous patches of the latest regular release
  + Latest minor release / patch level  for the "Version -1" 
  o Level 3:

  + All other versions
  * Other browsers, including mobile versions, Chromium, Microsoft EDGE,
etc.:
  o Level 2: Latest regular release, latest minor release / patch level
  o Level 3: All other versions


This policy should be somewhat aligned with the current ATH state. IIUC 
we test only Firefox now, and there is a PR by Oliver Gondza to run 
tests on Chrome instead (here 
)


WDYT?


It makes sense to me up date it this way - especially getting rid of the 
explicit versions so this does not get outdated so easily.


Speaking of ATH, there is not enough hands to mirror the support matrix 
and test the UI on all supported browsers - not even those from level 1. 
We have started tentatively looking into replacing FF with chrome as the 
only browser we test with to (hopefully) improve the stability and 
(certainly) improve the test relevance.


--
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/6438b52c-9ac7-49d4-5056-ae1c6c921ac6%40gmail.com.

Re: Jenkins Governance meeting on Nov 20

[Oliver Gondža]

Nope, lets give the mailing approach a proper shot. We can always return 
back if it would not seem to work.


On 13/11/2019 07.33, Oleg Nenashev wrote:
Last time we agreed to do LTS selection in the mailing list. I see no 
particular reason to return back to the original process, because there 
are only few people who show up at governance meetings at the moment. 
But we can add this topic if Oliver votes for it.


I can also run a meeting on Nov 27 if we need it

On Tue, Nov 12, 2019, 23:47 James Nord > wrote:


is it also too early for LTS.next selection?

-- 
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/jnw3pG892yo/unsubscribe.
To unsubscribe from this group and all its topics, 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/ab46071f-29cb-4d90-8640-b9159b05d702%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/CAPfivLAdXf%3DgAi0AcQqMEa8f_SggupR5fP9%2Bop3sSj-L11RBjw%40mail.gmail.com 
.



--
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/22f0b764-732b-93f6-e4bc-7a98f7a94b3c%40gmail.com.

Jenkins 2.190.3 LTS RC testing started

[Oliver Gondža]

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 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/ad4968de-b017-7f7f-56bb-c8ba69879684%40gmail.com.

Re: 2.190.2-RC availability

[Oliver Gondža]

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 this? any ETA to having there available?


Thanks in advance!

--
*Ildefonso Montero Pérez
*
Software Engineer
CloudBees, Inc.


E: imont...@cloudbees.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/CA%2BUGhi93DSVqSRM6KJ70NYQJ4gSrVG_JPhkVu0CgN-6f%3DJJvpg%40mail.gmail.com 
.



--
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/b132fe65-d6df-dabc-a235-a7aa285a1e79%40gmail.com.

Jenkins 2.190.2 LTS RC testing started

[Oliver Gondža]

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 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/11677e0d-5609-0813-0020-2ba23db3a566%40gmail.com.

Jenkins 2.190.1 LTS RC testing started

[Oliver Gondža]

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 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/b03da97c-1075-a58b-d57d-7e1c51c69f6d%40gmail.com.

Backporting for LTS 2.190.1 started

[Oliver Gondža]

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

--
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/dc475718-9f3b-6c5d-c467-f6812b154cb1%40gmail.com.

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

[Oliver Gondža]

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 UTC+2, Mark Waite wrote:

+1 from me to choose 2.190 as the baseline.

On Wednesday, August 28, 2019 at 7:39:31 AM UTC-4, Oleg Nenashev wrote:

Great to see the fix!
https://github.com/jenkinsci/jenkins/pull/4176
 can be
trivially backported, so I think we can go ahead with 2.190 as a
baseline.

BR, Oleg


On Wed, Aug 28, 2019 at 12:54 PM Mark Waite wrote:



On Tuesday, August 27, 2019 at 6:00:13 AM UTC-4, Oleg
Nenashev wrote:

For me 2.187 is a default pick. If somebody investigates
JENKINS-58912


 /
JENKINS-58938
 and
clarifies impact/possibility of a fix for .1, then I am
fine with 190. Cannot commit to investigate it unfortunately

There are some reasons to want 2.190. Apart from emoji
support for job names (yey!) there are some more
meaningful changes like plugin installation
parallelization for Setup Wizard (Jenkins Startup
Experience), security hardening, install-plugin fixes,
and other changes which could help LTS users.


Gabriel Lavoie has submitted a pull request to fix those two
issues.  The pull request is at
https://github.com/jenkinsci/jenkins/pull/4176
 and is
related to the slow trigger monitor that was first released
in 2.189.

I haven't yet been able to interactively verify the problem
myself, but am thrilled that Gabriel was able to do so and
that a pull request has been submitted.

That change leads me towards favoring 2.187, before that
admin monitor was added.  I could be persuaded otherwise
(especially considering the security fix that was announced
for today), assuming we also have a fix for the remoting
issue that was reported as
https://issues.jenkins-ci.org/browse/JENKINS-59094


Mark Waite

On Tuesday, August 27, 2019 at 11:50:34 AM UTC+2,
ogondza wrote:

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
 >
https://issues.jenkins-ci.org/browse/JENKINS-59094

 >
 > I think it a serious obstacle for this version or
for the tomorrow's
 > security fix as a baseline.
 >
 > BR, Oleg
 >
 > On Monday, August 26, 2019 at 1:37:18 PM UTC+2,
Mark Waite wrote:
 >
 >     I've started testing 2.190 late Friday.  I
did not find any
 >     immediate reasons to reject it as the LTS. 
The security release

 >     scheduled for Wednesday seems to me like a
good reason to prefer
 >     choosing 2.190 as a baseline, then update to
the security release as
 >     the baseline after it is delivered.
 >
 >     I haven't investigated the startup failures
reported in
 >     JENKINS-58912 and JENKINS-58938.
 >
 >     I'm also concerned about JENKINS-58692 from
the KDE project
 >     beginning in 2.186.  Jesse Glick investigated
it and was unable to
 >     duplicate it.  The KDE project found a
workaround (install the
 >     symlinks plugin) 

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

[Oliver Gondža]

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
https://issues.jenkins-ci.org/browse/JENKINS-59094

I think it a serious obstacle for this version or for the tomorrow's 
security fix as a baseline.


BR, Oleg

On Monday, August 26, 2019 at 1:37:18 PM UTC+2, Mark Waite wrote:

I've started testing 2.190 late Friday.  I did not find any
immediate reasons to reject it as the LTS.  The security release
scheduled for Wednesday seems to me like a good reason to prefer
choosing 2.190 as a baseline, then update to the security release as
the baseline after it is delivered.

I haven't investigated the startup failures reported in
JENKINS-58912 and JENKINS-58938.

I'm also concerned about JENKINS-58692 from the KDE project
beginning in 2.186.  Jesse Glick investigated it and was unable to
duplicate it.  The KDE project found a workaround (install the
symlinks plugin) and can't really explore other options because it
is their production system.  JENKINS-58692 will affect 2.186 and
later, so it seems relevant to investigate further as a risk to any
LTS version we select.

I prefer the upcoming security release as the baseline, but
JENKINS-58912 and JENKINS-58938  need investigation before the LTS
is released.

Mark Waite

On Mon, Aug 26, 2019 at 6:28 AM Oleg Nenashev > wrote:

I would vote for 2.187 as a baseline. FTR
https://groups.google.com/forum/#!topic/jenkinsci-dev/oQ8PD1hgYBE 
 for
the mailing list selection process proposal.

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 UT


We have a security release on Wednesday. Assuming it is stable,
we could use it as a baseline.

If we discuss only released versions
https://jenkins.io/changelog/#v2.189
 has a pretty bad
community rating. JENKINS-58912
 /
JENKINS-58938
 looks to be
a pretty bad regression somewhere, but nobody has investigated
the issue so far. It is not clear when and why it happens. I am
not sure we are safe to go into LTS with it. So 2.187 is my
preference (2.188 was burned)

BR, Oleg


On Monday, August 26, 2019 at 11:00:47 AM UTC+2, ogondza wrote:

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], 2.189
and 2.190.
Since 2.190 has relatively few changes in it, all minor, got
2 weeks of
soaking with nothing but positive community feedback, I vote
to choose
that despite being the latest weekly published.

[1] https://jenkins.io/changelog/

-- 
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 jenkin...@googlegroups.com .
To view this discussion on the web visit

https://groups.google.com/d/msgid/jenkinsci-dev/2577f42d-5a15-4995-b5f8-a97de6a60fe7%40googlegroups.com

.



-- 
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/8346a1c4-ca52-4f6f-b89a-f00bb0eb48e2%40googlegroups.com 
.



--
oliver

--
You received this message because you are subscribed to the Google Groups "Jenkins 
Developers" group.
To unsubscribe from this group and stop 

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

[Oliver Gondža]

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], 2.189 and 2.190. 
Since 2.190 has relatively few changes in it, all minor, got 2 weeks of 
soaking with nothing but positive community feedback, I vote to choose 
that despite being the latest weekly published.


[1] https://jenkins.io/changelog/

--
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/2694c06c-0108-6276-8adf-f8797a392655%40gmail.com.

Re: Jenkins 2.176.3 LTS RC testing started

[Oliver Gondža]

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 fix is also 
straightforward.


I agree this is trivial enough to backport this late.

--
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/93bc4347-34f9-ec1c-75db-5819817748b1%40gmail.com.

Re: Jenkins 2.176.3 LTS RC testing started

[Oliver Gondža]

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?


Yes, we do cross run this in multiple environments not be surprised this 
way.


--
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/54b9ac7a-7073-9af1-2e40-22a67ce24574%40gmail.com.

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

[Oliver Gondža]

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. 
Then, except for carrying away the daily routine, I would be more than 
happy to discuss and set some long term vision of the project.


[1] https://github.com/jenkinsci/acceptance-test-harness/pull/520

Thanks again for your interest!

On 02/08/2019 14.29, Antonio Muñiz wrote:

I can help with this too!

On Fri, 2 Aug 2019 at 14:27, m.vilacides > wrote:


Hi Oliver,

first of all, thanks for the fantastic job you've been doing during
these years, really appreciated. I would love to step up and help,
let me know what the next steps are.

Cheers

On Friday, August 2, 2019 at 1:10:26 PM UTC+2, ogondza wrote:

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 keeping ATH in good
shape.

--
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/8e97162e-cbaf-6242-f526-2b7e8fb3d8b3%40gmail.com.

Open call for acceptance-test-harness co-maintainers

[Oliver Gondža]

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 keeping ATH in good shape.


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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/22b6bee8-ee5b-aeb8-14ca-a8b0cf006d23%40gmail.com.

Jenkins 2.176.3 LTS RC testing started

[Oliver Gondža]

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 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/9f60e1e0-2dc0-1bee-7396-d33d480651e0%40gmail.com.

Re: LTS schedule around DWJW

[Oliver Gondža]

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 previously moved the LTS schedule back by two weeks for the
release yesterday. Unfortunately, that means that the next LTS
release would be done during DWJW on August 14.

I don't know yet whether there will be security fixes ready to be
included in that release, but if they are, I'd rather not want to
publish such an update during a huge conference, with many of the
people present there expected to apply the update. While we could
reschedule once we've determined whether there are going to be
security fixes, I think it makes sense for us to decide on this
earlier, to allow time to prepare.

As we'd have the same problem 4 releases later in early December due
to DWJW Lisbon, I propose to move the LTS schedule back 2 weeks
starting with 2.176.3, which would then release August 28 instead of
August 14. 2.NEXT.1 would then release September 25, and so on.

Anyone opposed to this plan?

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-dev+unsubscr...@googlegroups.com
.
To view this discussion on the web visit

https://groups.google.com/d/msgid/jenkinsci-dev/956E3B69-90A4-4897-8023-8811DE8FBD90%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

--
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/CANWgJS6dMwgRNnp44MbUXvSA4M_N26yMwyh62mPn7YTEm64MSQ%40mail.gmail.com 
.



--
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/65346b22-5279-118a-f7c0-0b3ec092e1a0%40gmail.com.

Re: Jenkins 2.176.2 LTS RC testing started

[Oliver Gondža]

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://issues.jenkins-ci.org/browse/JENKINS-57515


Do we really want this change backported? It seems to have caused JENKINS-58207.



Good catch, linking those two in JIRA. I agree to revert this backport.

--
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/2383fd4f-defa-f67c-a4dc-3f5bf815a321%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Jenkins 2.176.2 LTS RC testing started

[Oliver Gondža]

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 disable/uninstall optional dependencies
https://issues.jenkins-ci.org/browse/JENKINS-33843

Fixed:
JENKINS-57993   Minor   2.181
Noisy ClosedChannelException from 
DefaultJnlpSlaveReceiver.channelClosed
https://issues.jenkins-ci.org/browse/JENKINS-57993

JENKINS-57725   Minor   Jenkins 2.181
Proc.executor inherits ContextClassLoader dynamically
https://issues.jenkins-ci.org/browse/JENKINS-57725

JENKINS-57528   CriticalJenkins 2.178
		Jenkins in Docker does not install detached plugins when there is no 
UC data

https://issues.jenkins-ci.org/browse/JENKINS-57528

JENKINS-57515   Major   Jenkins 2.181
		AIX slave start error due to can not found 
/com/sun/jna/aix-ppc64/libjnidispatch.so

https://issues.jenkins-ci.org/browse/JENKINS-57515

JENKINS-57477   CriticalJenkins 2.178
Cancelling a job results in "sendctrlc.x64...exe" stops working
https://issues.jenkins-ci.org/browse/JENKINS-57477


Please, report your findings in this thread.

Download bits from 
http://mirrors.jenkins-ci.org/war-stable-rc/2.176.2/jenkins.war


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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/fe13cf6e-f137-4b62-5090-3be24e1a335c%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins Changelog: weather stats spammed?

[Oliver Gondža]

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 that release).

The changelog weather has no spam protection, and if it's obvious garbage we 
(well, me at least) simply ignore it. It's only a useful tool as long as no 
users mess with it.

If anyone's interested in improving things, the repo is at 
https://github.com/jenkins-infra/rating



I am wondering whether this would not be better delegated to one of the 
free online voting services - they surely have the spam-protection 
figured out. In fact, my brief search was a bit disappointing as many of 
the services ware too powerful for the yes/no answers we are after.


Do we happen to know whether we need PHP and PostgreSQL for other things 
in our infra? It can also be and interesting simplification...


--
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/c007bb5b-001a-8f94-aa5f-3f3757c54485%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

LTS release schedule slips starting 2.176.2

[Oliver Gondža]

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 2019-07-03
- 2.176.2 on 2019-07-17
- 2.176.3 RC on 2019-07-31

... and so on.

Thanks for understanding.
--
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/7057487e-8494-fa79-e770-e9897b6e76f5%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

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

[Oliver Gondža]

That is spot-on Antonio. I can imagine it will break any plugin using 
JNLP launcher where the VM can happen to be ready sooner than the 
computer is created.


For me, reverting https://github.com/jenkinsci/jenkins/pull/4005 is 
preferable over changing the baseline this late in the cycle.


Do you guys intent to revert it in weekly, provide a fix or do something 
else? I am asking so we can coordinate actions...


On 28/05/2019 14.44, Antonio Muñiz wrote:
JENKINS-57713 <https://issues.jenkins-ci.org/browse/JENKINS-57713> - 
This is breaking a proprietary cloud implementation. 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           Critical                Jenkins 2.178
                 Jenkins in Docker does not install detached plugins
when there is no
UC data
https://issues.jenkins-ci.org/browse/JENKINS-57528

         JENKINS-25369           Minor                   Jenkins 2.178
                 DNS multicast error messages
https://issues.jenkins-ci.org/browse/JENKINS-25369

         JENKINS-57477           Critical                Jenkins 2.178
                 Cancelling a job results in "sendctrlc.x64...exe"
stops working
https://issues.jenkins-ci.org/browse/JENKINS-57477

Fixed:
         JENKINS-57412           Major                   Jenkins 2.177
                 Incorrect deletion for setup wizard of Chinese
localization files on
Jenkins LTS 2.176
https://issues.jenkins-ci.org/browse/JENKINS-57412

         JENKINS-57111           Major                   Jenkins 2.177
                 Base class setChannel does not handle exceptions
from onOnline call
https://issues.jenkins-ci.org/browse/JENKINS-57111


Please, report your findings in this thread.

Download bits from
http://mirrors.jenkins-ci.org/war-stable-rc/2.176.1/jenkins.war

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 jenkinsci-dev+unsubscr...@googlegroups.com
<mailto:jenkinsci-dev%2bunsubscr...@googlegroups.com>.
To view this discussion on the web visit

https://groups.google.com/d/msgid/jenkinsci-dev/02142c5b-b89e-fbed-5243-a16b7b956c8c%40gmail.com.
For more options, visit https://groups.google.com/d/optout.



--
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 
<mailto:jenkinsci-dev+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAJc7kzRNyGPHV7Q%2B2z22T%2BD5QM6P3HXgowYW6NnS1rScB5SFUQ%40mail.gmail.com 
<https://groups.google.com/d/msgid/jenkinsci-dev/CAJc7kzRNyGPHV7Q%2B2z22T%2BD5QM6P3HXgowYW6NnS1rScB5SFUQ%40mail.gmail.com?utm_medium=email_source=footer>.

For more options, visit https://groups.google.com/d/optout.



--
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/307b963c-3bf6-4a71-a563-b41967063f9e%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Jenkins 2.176.1 LTS RC testing started

[Oliver Gondža]

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

https://issues.jenkins-ci.org/browse/JENKINS-57528

JENKINS-25369   Minor   Jenkins 2.178
DNS multicast error messages
https://issues.jenkins-ci.org/browse/JENKINS-25369

JENKINS-57477   CriticalJenkins 2.178
Cancelling a job results in "sendctrlc.x64...exe" stops working
https://issues.jenkins-ci.org/browse/JENKINS-57477

Fixed:
JENKINS-57412   Major   Jenkins 2.177
		Incorrect deletion for setup wizard of Chinese localization files on 
Jenkins LTS 2.176

https://issues.jenkins-ci.org/browse/JENKINS-57412

JENKINS-57111   Major   Jenkins 2.177
Base class setChannel does not handle exceptions from onOnline 
call
https://issues.jenkins-ci.org/browse/JENKINS-57111


Please, report your findings in this thread.

Download bits from 
http://mirrors.jenkins-ci.org/war-stable-rc/2.176.1/jenkins.war


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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/02142c5b-b89e-fbed-5243-a16b7b956c8c%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Backporting for LTS 2.176.1 started

[Oliver Gondža]

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

--
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/9654cbbe-3654-f66b-67c7-ab58d85df2e4%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Jenkins 2.164.3 LTS RC testing started

[Oliver Gondža]

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 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/c316c8de-60b6-5f42-cb5d-267d4566c15b%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Backporting for LTS 2.164.3 started

[Oliver Gondža]

Baptiste, thanks for the suggestion but I lean towards skipping this for 
2.164.3.


To the best of my understanding, this issues was present for 6 entire 
LTS lines (possibly without being reported). Given the consequences are 
duplication of a renamed agent after restart, I dare to dispute this is 
a blocker issue to begin with.


Or do I miss something?

On 19/04/2019 09.53, Baptiste Mathus wrote:
Just added lts-candidate on 
https://issues.jenkins-ci.org/browse/JENKINS-56403 merged yesterday.
I think it could be considered given the regression fix PR is fairly 
small and has had 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 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
-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com
<mailto:jenkinsci-dev%2bunsubscr...@googlegroups.com>.
To view this discussion on the web visit

https://groups.google.com/d/msgid/jenkinsci-dev/845a8da6-c20e-1f50-e69e-319fe283b1f7%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

--
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 
<mailto:jenkinsci-dev+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CANWgJS5kQG7s-Ex1PQhO%3DUYxC_Hb3fNXtKGjhgrC6k%3Df8afOVA%40mail.gmail.com 
<https://groups.google.com/d/msgid/jenkinsci-dev/CANWgJS5kQG7s-Ex1PQhO%3DUYxC_Hb3fNXtKGjhgrC6k%3Df8afOVA%40mail.gmail.com?utm_medium=email_source=footer>.

For more options, visit https://groups.google.com/d/optout.



--
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/2deacef6-a160-936a-3b41-d523f97f2fa2%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Backporting for LTS 2.164.3 started

[Oliver Gondža]

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

--
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/845a8da6-c20e-1f50-e69e-319fe283b1f7%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

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

[Oliver Gondža]

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 sorts into the list of existing statuses


Perhaps between REOPENED and IN REVIEW.


Additionally, a complete list of transitions to add, which each consist of:
   - from status
   - to status
   - button label (For example "Stop Progress" is the label for In Progress -> 
Open)


I guess these should suffice:

IN PROGRESS → STALLED “Stalled”
IN REVIEW → STALLED “Stalled”
STALLED → IN PROGRESS “Back in progress”
STALLED → OPEN “No longer in progress”


   - optionally a screen to show, and what fields it should contain


Do not think anything like that would be needed.



I am wondering, do we really want to invest so much energy to clearly 
label clutter (stalled PRs) in both github and JIRA? The way I look at 
it is the PR failed to deliver the fix for the issue in question but 
there might be others created in the future - I is not clear to me what 
value is there in forwarding this info to JIRA.


Not that I have any numbers at hand on how often such stalled PRs dies, 
revives, or keep being stalled - I presume they just sit there until 
closed more of then then not, but I am wondering if an efficient way to 
close such PRs would not be a better time investment. We would get rid 
of what I see as clutter rather then precisely label it for someone else 
to do something about it later.


--
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/c2d4a678-fe87-c93b-5029-e16c6e2c7d07%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Jenkins 2.164.2 LTS RC testing started

[Oliver Gondža]

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 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/5064debe-93e9-f1e3-ab24-eba6de1790ba%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: acceptance-test-harness questions

[Oliver Gondža]

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 
 
give several ways to control plugin versions, but I haven't found a way 
to point the update center to a local json file for example.


You would have to assemble update center for that Jenkins version is 
some way. By assemble I mean identify plugin versions that does not 
require newer Jenkins core while still having dependencies satisfied.


The idea with modified json file is clever, but I am not sure if someone 
has ever tried that. I have just tested that it can be injected in via 
`-Dupdate_center_url=file:update-center.json` java property property, 
but it misbehaves in case the url got cached earlier. To fix that, [1] 
needs to be updated not to cache custom `update_center_url`.


[1] 
https://github.com/jenkinsci/acceptance-test-harness/blob/master/src/main/java/org/jenkinsci/test/acceptance/update_center/CachedUpdateCenterMetadataLoader.java#L38


--
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/a546dd6c-c420-b427-c89f-71e1e1188534%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: acceptance-test-harness questions

[Oliver Gondža]

On 19/03/2019 17.26, Julien HENRY wrote:
My tests are green when executed with Jenkins 2.164.1! That's already 
great news, thanks for your help.


But with the oldest Jenkins version we are supporting (2.89.4), all 
pipeline related tests are failing. I wonder if this could be an issue 
with the update center.


Quite likely, see[1] to check for which LTS lines we still distribute 
update centers. 2.89 is the latest we have dropped the UC for to this 
day. The infra falls back to UC for latest weekly and it is not able to 
satisfy plugin dependencies given the ancient core.


You might want to setup and maintain you own UC for releases you support 
to prevent this from happening (as upstream UCs are rotated 
(a)periodically) if you have not already.


[1] https://updates.jenkins-ci.org/


@WithPlugins("workflow-aggregator")

In logs, I can see:

*16:27:41* INFO: workflow-aggregator is not installed

[...]

*16:27:41* Mar 19, 2019 4:27:41 PM 
org.jenkinsci.test.acceptance.junit.WithPlugins$RuleImpl$1 installPlugins
*16:27:41* INFO: Installing plugins for test: [workflow-aggregator, sonar, 
filesystem_scm, plain-credentials]

[...]

*16:28:27* master57755|INFO: Adding dependent install of 
pipeline-model-definition for plugin workflow-aggregator

[...]

*16:28:27* master57755|INFO: Adding dependent install of 
workflow-cps-global-lib for plugin pipeline-model-definition

[...]

*16:28:35* master57755|INFO: Starting the installation of Pipeline: Shared 
Groovy Libraries on behalf of anonymous
*16:28:35* Mar 19, 2019 4:28:35 PM 
org.jenkinsci.test.acceptance.update_center.MockUpdateCenter 
lambda$ensureRunning$3
*16:28:35* INFO: serving 
/home/ssjenka/.m2/repository/org/jenkins-ci/plugins/workflow/workflow-cps-global-lib/2.13/workflow-cps-global-lib-2.13.hpi
*16:28:36* master57755|Mar 19, 2019 4:28:35 PM 
hudson.model.UpdateCenter$UpdateCenterConfiguration download
*16:28:36* master57755|INFO: Downloading Pipeline: Shared Groovy Libraries
*16:28:36* master57755|Mar 19, 2019 4:28:35 PM hudson.PluginManager dynamicLoad
*16:28:36* master57755|INFO: Attempting to dynamic load 
/home/ssjenka/cix/workspace/sonar-scanner-jenkins-qa/4adbdb2c/its/target/jenkins1486774028372987495home/plugins/workflow-cps-global-lib.jpi
*16:28:36* master57755|Mar 19, 2019 4:28:36 PM 
hudson.model.UpdateCenter$DownloadJob run
*16:28:36* master57755|SEVERE: Failed to install Pipeline: Shared Groovy 
Libraries
*16:28:36* master57755|java.io.IOException: Failed to dynamically deploy this 
plugin
*16:28:36* master57755| at 
hudson.model.UpdateCenter$InstallationJob._run(UpdateCenter.java:1893)
*16:28:36* master57755| at 
hudson.model.UpdateCenter$DownloadJob.run(UpdateCenter.java:1651)
*16:28:36* master57755| at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
*16:28:36* master57755| at 
java.util.concurrent.FutureTask.run(FutureTask.java:266)
*16:28:36* master57755| at 
hudson.remoting.AtmostOneThreadExecutor$Worker.run(AtmostOneThreadExecutor.java:110)
*16:28:36* master57755| at java.lang.Thread.run(Thread.java:748)
*16:28:36* master57755|Caused by: java.io.IOException: Failed to install 
workflow-cps-global-lib plugin
*16:28:36* master57755| at 
hudson.PluginManager.dynamicLoad(PluginManager.java:882)
*16:28:36* master57755| at 
hudson.PluginManager.dynamicLoad(PluginManager.java:821)
*16:28:36* master57755| at 
hudson.model.UpdateCenter$InstallationJob._run(UpdateCenter.java:1889)
*16:28:36* master57755| ... 5 more
*16:28:36* master57755|Caused by: java.io.IOException: Pipeline: Shared Groovy 
Libraries v2.13 failed to load.
*16:28:36* master57755| - You must update Jenkins from v2.89.4 to v2.107.3 or 
later to run this plugin.
*16:28:36* master57755| at 
hudson.PluginWrapper.resolvePluginDependencies(PluginWrapper.java:626)
*16:28:36* master57755| at 
hudson.PluginManager.dynamicLoad(PluginManager.java:872)
*16:28:36* master57755| ... 7 more


Do you know why is workflow-cps-global-lib plugin 2.13 selected to be 
installed if it is not compatible with Jenkins 2.89.4? Shouldn't it 
always select the latest compatible version?




Julien Henry | SonarSource

Developer

https://sonarsource.com <https://sonarsource.com/>


Le mar. 19 mars 2019 à 14:01, Julien HENRY <mailto:julien.he...@sonarsource.com>> a écrit :


You got it right :)

I have tested removing the sha1 only and it works fine, I will open
a PR.

Julien Henry | SonarSource

Developer

https://sonarsource.com <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 Jenkins versions, at least). Where it does not
work is
older versions of Jenkins, from before the sha512 was
introduced, since
the other checksums are not modified.

Provided 

Backporting for LTS 2.164.2 started

[Oliver Gondža]

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

--
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/a023a10b-8f8f-5586-3178-26b42b3f863f%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins 2.164.1 LTS RC testing started

[Oliver Gondža]

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.


I am +1 for shipping 2.164.1

BR, Oleg

On Thursday, March 14, 2019 at 3:11:13 AM UTC+1, Mark Waite wrote:

I've been running 2.164.1 release candidate for over a week in my
environment without detecting any surprises.

Mark Waite

On Wed, Mar 13, 2019 at 7:54 PM Oleg Nenashev > wrote:

Since there was no governance meeting yesterday, what is the
plan w.r.t the new LTS release (2.164.1).
Will it get postponed till the next Governance meeting? Or will
it be shipped today/tomorrow as it was planned?

On Thursday, February 28, 2019 at 1:41:55 PM UTC+1, ogondza wrote:

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 this thread.

Download bits from
http://mirrors.jenkins-ci.org/war-stable-rc/2.164.1/jenkins.war



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 jenkinsci-de...@googlegroups.com .
To view this discussion on the web visit

https://groups.google.com/d/msgid/jenkinsci-dev/9618cc9e-588c-4840-8aac-c99d09d5b6aa%40googlegroups.com

.
For more options, visit https://groups.google.com/d/optout
.



-- 
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/87492c01-300b-4b33-b1ce-399b1fea43a9%40googlegroups.com 
.

For more options, visit https://groups.google.com/d/optout.



--
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/faeb15db-e3fb-7e6f-93da-5366c9f8046d%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: acceptance-test-harness questions

[Oliver Gondža]

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 based framework 
 
to test our plugin, including many Jenkins UI utility methods (create 
job, configure tools, ...). I discovered only "recently" the official 
acceptance-test-harness 
 project that 
seems to aim at the same goal. Maybe it was not existing when we started 
writing ITs but that's not important.


Today I would like to drop our own code, and use the common 
acceptance-test-harness, in order to save us some efforts, but I'm also 
ready to contribute. I have started migrating our test suites but so far 
I faced two issues:


1) location of the gecko driver

On my box, this code 
 
looks wrong, since it ends up configuring gecko driver property to:

which: no geckodriver in ()

Also I tried to force manually the path using the property 
-Dwebdriver.gecko.driver=xxx but it doesn't work, since the same code 
always override the property, without checking first if it was already 
defined. To me it seems the code only work when geckodriver *is* in the 
PATH.


Yeah, it appears to be an expectation in the code, but keeping the 
property if configured makes sense to me. Please, file that PR.



2) SonarQube Scanner tool automatic installer returns outdated entries

My test was failing because it was not able to configure a SonarQube 
Scanner tool. After debugging, I was surprised to discover that the 
installer metadata are already cached 
 
when the JUT starts (and uses a very old copy). So the real update 
center 
 
is never called.


Is there any reason to have 
this hudson.plugins.sonar.SonarRunnerInstaller file in the 
acceptance-test-harness distribution? Can I simply open a PR to remove 
it, or is there a good reason to keep it?


They ware checked in in order to speed things up and IIRC prevent a race 
condition of attempting to configure those tools in test before the 
updates are fetched. It is hackish as hell but I suspect it will be 
quite elaborate to get rid of that. Feel free to just check in a newer 
version to keep you going.


--
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/5d7cc7ff-1049-54d0-3026-ca58fd1a85e1%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

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

[Oliver Gondža]

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 Choice Parameter plugin working inside a declarative pipeline.


If you have write privs, can you please merge that and release a new 
version of the plugin?


Hey,

jenkinsci/extended-choice-parameter-plugin#21 was a one time thing[1] as 
the plugin had no CI configured at all. I am adding Vimil into the loop 
to react.


For the record, there is a pending maintainership request from last year[2].

[1] https://groups.google.com/d/topic/jenkinsci-dev/6f_wKvfpESk/discussion
[2] https://groups.google.com/d/topic/jenkinsci-dev/rBi3dhQFfL4/discussion

--
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/c446db8d-4e31-94ba-4949-2b756fb2ef16%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Jenkins 2.164.1 LTS RC testing started

[Oliver Gondža]

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 this thread.

Download bits from 
http://mirrors.jenkins-ci.org/war-stable-rc/2.164.1/jenkins.war


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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/d41e62b6-eee8-2d19-3e9a-4a59b895aa7a%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Setup external Jenkins processes to test via JCasC

[Oliver Gondža]

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. (That does not preclude mounting Maven-specific files
like `jenkins.war` and dependency `*.jpi` from the local repository or
`target` directory.) This would allow for much better control over
tests. I have sorely missed this in `mercurial-plugin`, for example.
There probably also needs to be some work done to allow agents to also
run in containers, like `docker-fixtures` does, with ports bound.
(Docker Compose? Minikube / microk8s? Something based on
testcontainers.org?)



Can you be more specific on the use-case here? As I understand, you 
suggest to use container as a per-test fixture (ala docker-fixtures) and 
running Jenkins _inside_ of the container.


--
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/bba3350a-2ea9-c97d-c423-2a2bc1e2e148%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Backporting for LTS 2.164.1 started

[Oliver Gondža]

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 release, and while 
we should fix that, we should make the back porting process more robust.

JENKINS-55197 is an example of such an invisible (former) 'lts-candidate' issue.



Good point, changed the relevant predicate to `statusCategory = Done`.

--
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/29c8e3d9-5c2d-e756-f2a1-c52cd7c8d5a7%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Setup external Jenkins processes to test via JCasC

[Oliver Gondža]

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 
scenarios (otherwise affected by JUT) or setting up multiple Jenkinses 
for test. I am distributing this to see if folks are interested in 
having something like this available so we can extract it from the 
plugin this was initially developed for.


---

The simplest way to consume it is:

```
public @Rule TemporaryFolder tmp = new TemporaryFolder();
public @Rule ExternalJenkinsRule ejr = new ExternalJenkinsRule(tmp);

@Test
@ExternalFixture(name = "my-jenkins", resource = "my-jenkins.yaml", 
injectPlugins = "matrix-auth")

public void myJenkins() throws Exception {
ExternalJenkinsRule.Fixture myJenkins = ejr.fixture("my-jenkins");
com.offbytwo.jenkins.JenkinsServer jenkinsServer = 
myJenkins.getClient();

...
}
```

- The Jenkinses are launched in parallel in case there are multiple of them.
- Injected plugins are inject with their dependencies resolved by 
maven-hpi-plugin:resolve-test-dependencies (IOW, they have to be 
declared as maven dependencies but their injections is safe and fast).
- Primary means of controlling such Jenkins is through 
jenkinsci/java-client-api.

- Dedicated temporary folder is allocated for every Jenkins.
- Jenkins log can be accessed for investigation.

For advanced usage one can subclass the ExternalJenkinsRule (as 
demonstrated by [1]) in order to:


- Rearrange or modify the declared fixture annotations per test (DRY).
- Alter plugins to inject (DRY).
- Specify particular environment variables, JVM or Jenkins arguments.
- All of the above can be tailored based on declared fixture role. 
Meaning the customizations deployed to individual fixtures do not have 
to be the same - common for heterogeneous grids.


There are certainly many areas to improve this, though for now my 
question is: Does it sound useful to you?


[1] https://github.com/jenkinsci/node-sharing-plugin/pull/106
[2] 
https://github.com/jenkinsci/configuration-as-code-plugin/blob/master/plugin/src/test/java/io/jenkins/plugins/casc/misc/JenkinsConfiguredWithCodeRule.java


Cheers
--
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/1be57933-62d2-7588-3e9e-83a4c7269b5d%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Backporting for LTS 2.164.1 started

[Oliver Gondža]

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

--
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/fed3de0b-17db-4983-f3c8-d1b3556f1ed7%40gmail.com.
For more options, visit https://groups.google.com/d/optout.