Re: Two week break in LTS schedule at end of 2024

[Tim Jacomb]

Sounds good to me thanks

On Mon, 15 Jul 2024 at 20:12, Basil Crow  wrote:

> +1
>
> --
> 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/CAFwNDjqwQ0dsAdZ3bqoaZxvtC3yzk6QEMpwFvgn3MWJGQn2%3DfQ%40mail.gmail.com
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3BicB5K%2BDHH4VM4k9%2BLGCoBpFq8e5ULPYT6KZhHFaktLebQ%40mail.gmail.com.

Re: 2.462 as 7 Aug 2024 LTS baseline?

[Tim Jacomb]

Confirmed

On Mon, 8 Jul 2024 at 00:40, Mark Waite  wrote:

> Based on the responses, I am assuming that 2.462 is selected as the
> baseline for the LTS releases that will start with 2.462.1 on 7 Aug 2024.
> I've made entries in the Jenkins calendar for the LTS releases and the LTS
> release candidates.
>
> Tim Jacomb, can you confirm that you are OK with that plan?
>
> Mark Waite
>
> On Tuesday, June 25, 2024 at 6:13:34 PM UTC-6 m...@basilcrow.com wrote:
>
>> On Tue, Jun 25, 2024 at 3:21 PM Mark Waite  wrote:
>> >
>> > I'm not aware of any other bug reports related to Apache File Upload 2.
>>
>> There is also JENKINS-73235, but just like JENKINS-73320 we are also
>> blocked on upstream and the number of affected users is small (0.55%
>> and 0.79% and of controllers, respectively). I don't think these
>> numbers are significant enough to affect LTS baseline selection. Those
>> users can always stick to the previous LTS until upstream takes action
>> to release the already merged fix (in the case of JENKINS-73320) or to
>> make the plugin compilable so I can help with a fix (in the case of
>> JENKINS-73235).
>>
> --
> 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/769973dd-485a-42ac-adaf-8bdf51406737n%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/769973dd-485a-42ac-adaf-8bdf51406737n%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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3BifUm9hDGC_nQ8j6awn%3DEQRdr_4WF3Cz0%3DjE6RHk_86WcA%40mail.gmail.com.

Re: Enable Renovate app on `gravatar-plugin`

[Tim Jacomb]

I've approved the installation request you sent

On Thu, 6 Jun 2024 at 11:06, 'Michael Kriese' via Jenkins Developers <
jenkinsci-dev@googlegroups.com> wrote:

> Hi,
>
> i like to use renovate on my two adopted repos.
> Can someone with organization admin permissions enable it for me?
>
> - https://github.com/jenkinsci/gravatar-plugin
>
> Regards
> Michael
>
> --
> 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/915d67fd-0a2d-434d-9f2e-19ab44ad8aa6n%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-3Bid7EADP-KP9r8Zx95-o-s2QhEBgAH6AA%3DLZRhNhODcUAw%40mail.gmail.com.

Re: Spring Security upgrade from 5.x to 6.x

[Tim Jacomb]

Sounds good to me

On Sat, 11 May 2024 at 04:08, Mark Waite  wrote:

>
>
> On Friday, May 10, 2024 at 12:51:46 PM UTC-6 Basil wrote:
>
> Based on my prototyping in JENKINS-73120, there is quite a bit of work
> to support Jetty 12 (even just EE 8 with javax imports), blocked on
> the requirement of Java 17. From my perspective the sooner we require
> Java 17, the better. Perhaps we can require Java 17 in weeklies two
> weeks earlier than planned, acknowledging that this creates two fewer
> choices for LTS selection. Thoughts?
>
>
> I like the idea.  It would mean that the LTS baseline selected for the
> last Jenkins LTS to support Java 11 would need to be two weeks earlier,
> but we've chosen LTS baselines that were not the most recent weekly
> before.
>
> 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/450e7eff-2c7b-4aba-a10a-979aa7dba9a2n%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-3BidRaVECsQ1p-snXTcQEsMmAdekQwLxHhe6YJRTuzGb6TA%40mail.gmail.com.

Re: SCM plugin with Multi-Branch Pipeline throwing InaccessibleObjectException

[Tim Jacomb]

I find in my IDE (IntelliJ) sometimes I need to add the `--add-opens` to
command line arguments for hpi:run

On Mon, 22 Apr 2024 at 13:15, 'Jesse Glick' via Jenkins Developers <
jenkinsci-dev@googlegroups.com> wrote:

> How are you running Jenkins when you see this? Should not occur when
> either using `mvn hpi:run` nor `mvn test` on a `JenkinsRule`-based test so
> far as I know.
> https://github.com/jenkinsci/plugin-pom/blob/692c7757f468ea6b1ecf52a39edb8379020816c3/pom.xml#L65-L70
> and associated setup should be passing the right JVM argument to allow this
> reflection.
>
> --
> 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/CANfRfr3fMOePYaXEa6q4uFc-%2BJMB8dN%2B80-aLN7V4GtnMV_muQ%40mail.gmail.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3Bifz2JnhaBnUVYUa8vzCzZKVZz%2BeSXw2NiwYG81Et5Y9tQ%40mail.gmail.com.

Re: Windows-arm64 native support

[Tim Jacomb]

>From my point of view GitHub actions is fine.
I don’t think we want to add something that takes so long to install to our
image builds.

This isn’t something we really want to maintain but it needed updating for
something and it has no one actively maintaining it.

I’m not sure if any of our maintainers would be able to build this on ARM
and what happens on the next release of the person who built the current
one isn’t available.

On Fri, 5 Apr 2024 at 09:02, Pierrick Bouvier 
wrote:

> On Friday 5 April 2024 at 02:23:47 UTC+4 m...@basilcrow.com wrote:
>
> While we do encourage first-time contributors, I think it would be
> tricky for a first-time contributor to submit a rewrite like this,
> because potential problems might not be discovered for several weeks,
> at which point the motivation (or funding) to work on the project
> might have decreased. While not insurmountable, I think these
> challenges have caused me to have a preference for incremental
> improvement rather than a rewrite, especially given that the interest
> is coming from a first-time contributor. As annoying as it is to delve
> into an unfamiliar codebase and write a CI/CD script for an abandoned
> codebase, at least the problem is well-defined, and we can be assured
> that the result won't break existing use cases. With a rewrite, that
> risk increases and I think we would have to be very careful about
> review, testing, and (potential) regression management. If a long-time
> contributor like yourself proposed to do such a rewrite, I would feel
> more comfortable with it, especially if that long-time contributor
> promised to be around to deal with any regressions.
>
>
> I agree with this.
> On Linaro side, I have a green light to work on existing wimp component,
> if you still find interest in it.
> If you prefer a full rewrite, just make it clear, so I can let you work on
> this.
>
> I understand the implications of technical debt you mention, and the
> existing issues.
>
> However, this thread was just to add arm64 support.
> Is there anyone here that see interest in this?
> I reiterate politely my demand: Could we merge the changes required, let
> someone trusted (you, or any Jenkins core dev, not me) build the binaries,
> commit them, make a new release, and call it a day?
>
> I can remove all the CI part of this. My goal was simply to prove
> objectively that it compiles, and not to open another pandora's box.
> I don't care about the tool I use, as long as it provides me what I need
> in a finite amount of time (took me only two hours to get a clean GitHub
> Actions pipeline).
>
> Finally, I would just note that on all this thread, and the PR associated,
> we never discussed any detail of current arm64 support proposal, but simply
> a useless debate about CI A vs B. Maybe it would be more constructive.
>
> --
> 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/e4274c93-124f-49d5-a0c9-fcf50788b46cn%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-3BidcS6NQ5Q%3D_fc2pOACO8zgBibxYCbEB-aBGx_JMB1%3DOaw%40mail.gmail.com.

Re: Remove Suggestimate from issues.jenkins.io?

[Tim Jacomb]

According to their website it's free for open source projects:
https://enhancera.com/jira/suggestimate/buy.html

I think it's just in a bit of a state of confusion due to Atlassian's
retirement of server and our moving to data center.

Is it worth trying to get the plugin relicensed, e.g. does it provide
benefit by preventing some duplicate tickets being filed?

On Mon, 11 Mar 2024 at 15:42, Basil Crow  wrote:

> +1
>
> On Mon, Mar 11, 2024 at 6:48 AM Mark Waite 
> wrote:
> >
> > The Jenkins Jira instance uses a Jira datacenter license that is donated
> to the Jenkins project by Atlassian.
> >
> > The Suggestimate plugin is installed on the Jenkins Jira instance and is
> reporting that its license has expired.  The Suggestimate pricing page says
> that the plugin would cost $4500 per year based on the number of users of
> our Jira instance.  The question and answer section indicates that our
> donated Jira Datacenter license does not include the license for the plugin.
> >
> > I propose that we should remove that plugin from issues.jenkins.io
> rather than pay a licensing fee for the plugin.
> >
> > Any objections to the removal of that plugin from issues.jenkins.io?
> >
> > 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/a96f9c00-ff28-47fb-a3eb-210826ae5d7dn%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/CAFwNDjpaspVJWUAHtyYjNSMxrvkhZmws5GwNbqZjCshgND0vbQ%40mail.gmail.com
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3BieVqU35PAL-gHZY8k_RNBzr9fWb-5TrE72wUHeyAMNTkg%40mail.gmail.com.

Re: 2.440 as Feb 21, 2024 LTS baseline?

[Tim Jacomb]

+1

On Sat, 13 Jan 2024 at 08:51, 'Alexander Brandes' via Jenkins Developers <
jenkinsci-dev@googlegroups.com> wrote:

> I’m +1 for 2.440 :)
>
>
> On 13. Jan 2024, at 02:32, Mark Waite  wrote:
>
> Wednesday Jan 10, 2024 is the day that we should select the baseline for
> the long term support release that will be delivered February 21, 2024.
>
> I propose Jenkins 2.440  as the
> next LTS baseline.  It was released Tuesday Jan 9, 2024.  It includes user
> interface improvements, configuration as code improvements, and
> improvements to the remoting library that communicates with agents.
>
> Feedback is positive on the release.  It is running on weekly.jenkins.io
> and I'm using on my weekly installation.
>
> 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/bea3f5b4-bea7-41b4-8344-6bdcb56bc33en%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/A48D3272-E4E5-4203-86BD-BE106F0A1CAB%40notmyfault.dev
> 
> .
>

-- 
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-3Bidx1khZUc_-mey-W3A%2BzcasCi%3DzKRu8p05z9DD%3D5wdL3A%40mail.gmail.com.

Re: Github webhook push events delays in SCM API plugin

[Tim Jacomb]

You aren’t getting rate limited by GitHub are you?

We use the open telemetry plugin to show a dashboard with the remaining
rate limit of all the credentials.

If you give a bit more info  about your setup or thread dumps it may be
possible to see where the delays are coming from

On Tue, 19 Dec 2023 at 15:01, DuMaM  wrote:

> Hi,
>
> Thanks for this replay.
> i found your blog post about it, and we also tweaked a bit this property,
> what helped greatly.
> Sadly i still see some issues connected to "
> I was asking about it mostly because if there is a possibility to tweak
> this in run time, we can make this to adjust in a dynamic way to the
> current Jenkins load.
>
> czwartek, 14 grudnia 2023 o 21:51:06 UTC+1 timja...@gmail.com napisał(a):
>
>> The thread pool is initialised when the first event is received.
>> There's not much point making it editable at runtime I think.
>>
>> If you are hitting delays run "jenkins.scm.api.SCMEvent.executorService"
>> In the script console and see if you have any queued.
>>
>> We run with 40 threads using that system property.
>>
>> If you are using GitHub org folders keep in mind it's not really designed
>> for multiple folders pointing to the same GitHub org, it doesn't scale very
>> well in its current setup.
>>
>> Depending on the issue I may be able to advise more as I debugged a
>> similar issue last year and I made a few changes to github-branch-source
>> and scm-api to help.
>>
>> Cheers
>> Tim
>>
>> On Thu, 14 Dec 2023 at 18:59, DuMaM  wrote:
>>
>>> Hi,
>>>
>>> I would like to discuss some idea.
>>> I recently came across some delays connected with GitHub webhooks
>>> processing.
>>> Furthermore, I found out that there is a property in the SCM API plugin
>>> which can drive SCM event queue behavior.
>>>
>>> https://github.com/jenkinsci/scm-api-plugin/blob/bab9621cdacf4276ed5f0c93e41f794290bfc67b/src/main/java/jenkins/scm/api/SCMEvent.java#L111C5-L111C5
>>>
>>> Is there any chance of making this property not the final one, to enable
>>> edits on run time?
>>>
>>> According to the code, we can kill this service and a new service
>>> singleton should be spawned, and this way we can fine tune this behavior.
>>>
>>> Thanks,
>>> Bartosz Nowak
>>>
>>> --
>>> 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/1ca1086d-e9c7-4987-8e7f-227a58fe834an%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/1f4432bd-44d7-407c-9e10-060562fe33a2n%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-3Bifsgfy5VggTQq_64FrU%3D9B_sh8uZTbW4Wn7EpvKNJyL3w%40mail.gmail.com.

Re: Github webhook push events delays in SCM API plugin

[Tim Jacomb]

The thread pool is initialised when the first event is received.
There's not much point making it editable at runtime I think.

If you are hitting delays run "jenkins.scm.api.SCMEvent.executorService"
In the script console and see if you have any queued.

We run with 40 threads using that system property.

If you are using GitHub org folders keep in mind it's not really designed
for multiple folders pointing to the same GitHub org, it doesn't scale very
well in its current setup.

Depending on the issue I may be able to advise more as I debugged a similar
issue last year and I made a few changes to github-branch-source and
scm-api to help.

Cheers
Tim

On Thu, 14 Dec 2023 at 18:59, DuMaM  wrote:

> Hi,
>
> I would like to discuss some idea.
> I recently came across some delays connected with GitHub webhooks
> processing.
> Furthermore, I found out that there is a property in the SCM API plugin
> which can drive SCM event queue behavior.
>
> https://github.com/jenkinsci/scm-api-plugin/blob/bab9621cdacf4276ed5f0c93e41f794290bfc67b/src/main/java/jenkins/scm/api/SCMEvent.java#L111C5-L111C5
>
> Is there any chance of making this property not the final one, to enable
> edits on run time?
>
> According to the code, we can kill this service and a new service
> singleton should be spawned, and this way we can fine tune this behavior.
>
> Thanks,
> Bartosz Nowak
>
> --
> 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/1ca1086d-e9c7-4987-8e7f-227a58fe834an%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-3BicjZjjgsH_eWRKbX%3DbNKNnbunM9x530TBcb6u%3DxfUwXDw%40mail.gmail.com.

Re: 2.426 as Nov 15, 2023 LTS baseline?

[Tim Jacomb]

Confirmed

On Fri, 13 Oct 2023 at 23:23, Mark Waite  wrote:

> Tim Jacomb, can you confirm that 2.426 is approved as the next LTS
> baseline?
>
> 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/78b4cbe6-824e-4d9f-b561-37323b0a1b24n%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/78b4cbe6-824e-4d9f-b561-37323b0a1b24n%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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3Bies-t1KBE4SOzsRYWpr-UAFgVPJUrvD%3DjqeKvruUGPOHw%40mail.gmail.com.

Re: Proposal: Kris Stern to join the release team

[Tim Jacomb]

Approved

On Mon, 9 Oct 2023 at 10:21, Oleg Nenashev  wrote:

> +1
>
> On Wednesday, October 4, 2023 at 1:30:04 PM UTC+2 stephan...@gmail.com
> wrote:
>
>> +1 from me, good work Kris
>>
>> Le lun. 2 oct. 2023 à 19:57, 'Kevin Martens' via Jenkins Developers <
>> jenkin...@googlegroups.com> a écrit :
>>
>>> +1 from me too!
>>>
>>> On Mon, Oct 2, 2023 at 1:40 PM Basil Crow  wrote:
>>>
 +1

 On Mon, Oct 2, 2023 at 5:06 AM Hervé  wrote:

> FWIW, +1 from me too!
>
> --
> 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/CAE1M8%2B9yQf3YzbEPkv%3DnAEQyPFoihRJL5cWGi6myVzwqM9EzZQ%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/CAFwNDjr3h1gnWGTSP0hfwVHd0-VWWA%3DYW_fnvQLr5VAume03Nw%40mail.gmail.com
 
 .

>>>
>>>
>>> --
>>> Kevin Martens
>>> Technical Content Developer
>>> CloudBees, Inc.
>>>
>>>
>>> E: kmar...@cloudbees.com
>>>
>>> Pronouns: He/Him/His
>>>
>>> --
>>> 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/CAP92yNdo8EE7KMWRrXMiTbZO3QMEHhcMc_v%3DD3%2BdQ_Ss2VU70g%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/8a9b4429-8517-4ddf-befd-e1c94698c73fn%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-3BicY%2B7OrHJ%2BL-zMjTytp17hgT8REN4OO-%2BNvPYaRm_%2Bh%2Bw%40mail.gmail.com.

Re: [Information] Release block "Beta" program

[Tim Jacomb]

On Wed, 6 Sept 2023 at 12:42, 'wfoll...@cloudbees.com' via Jenkins
Developers  wrote:

> Last time we tested, the branch locking has the problem to be visible for
> anyone. This means that you can guess which plugin will receive an advisory
> soon.


It could be locked for any reason, and personally I would say the trade-off
of the _very_ limited information is worth it here.


> The feature usage is up to the maintainers, like it's too limited for
> them, they can just communicate with their co-maintainers to ensure the
> master/main branch will not updated and no other releases are done.
>

I have multiple times merged pull requests on plugins that are staged, with
or without co-maintainers, it's really not something that's easy to keep
track of when you maintain more than one plugin, especially when it happens
a week or two after staging, and even more especially when you weren't
involved in the actual security fix.


> For the bots, that's pretty interesting, I haven't thought about the fully
> automatic flow there.
>
> On Tuesday, September 5, 2023 at 11:51:58 PM UTC+2 timja...@gmail.com
> wrote:
>
>> Also this won’t work with any bots that can auto merge when CI checks
>> pass, e.g. renovate and dependabot, whereas a locked branch will work.
>>
>> On Tue, 5 Sep 2023 at 17:48, Tim Jacomb  wrote:
>>
>>> Why not lock the branch instead?
>>> That means it won’t break review approvals in the meantime and things
>>> like enabling auto merge for when the release block is over
>>>
>>> On Tue, 5 Sep 2023 at 17:13, 'wfoll...@cloudbees.com' via Jenkins
>>> Developers  wrote:
>>>
>>>> Dear plugin maintainers,
>>>>
>>>> *Context*
>>>> In situations where the security team is collaborating with plugin
>>>> maintainers on a coordinated release, the artifacts are staged and
>>>> commits/tags are pushed to a designated private repository.
>>>>
>>>> However, challenges arise when multiple maintainers are simultaneously
>>>> working on the same plugin. Coordinating these efforts becomes crucial. If
>>>> another maintainer merges pull requests or releases a new version of the
>>>> plugin while a coordinated security release is pending, it necessitates
>>>> re-staging the artifacts. Depending on the timing of such occurrences in
>>>> relation to the release schedule, it can create unnecessary urgency and
>>>> often result in time wasted.
>>>>
>>>> *Objectives*
>>>> We want to have a way to inform the plugin maintainers while not
>>>> revealing specific details about the advisory in advance.
>>>>
>>>> *Current solution*
>>>> We've implemented an automation solution for your convenience. You can
>>>> now trigger this automation by simply commenting "/block-release" in the
>>>> SECURITY ticket assigned to you. This action will reduce GitHub permissions
>>>> for contributors to "Triage”. At the same time, a GitHub advisory will be
>>>> created, with contributors included as "Collaborators," allowing them to
>>>> view the advisory and receive a notification.
>>>>
>>>>
>>>> Once the release is completed, the security team will promptly remove
>>>> the block. You can also initiate the removal by commenting
>>>> "/unblock-release" in the same SECURITY ticket.
>>>>
>>>> *Known limitations*
>>>>
>>>>- Our automation cannot prevent all incidents but aims to cover
>>>>most cases.
>>>>- For vulnerabilities affecting multiple plugins, the security team
>>>>has to be involved to widen the scope of the block.
>>>>- Some corner cases like users with "org owner" permissions in
>>>>GitHub or Administer permission on ci.jenkins.io are still able to
>>>>perform actions that could make the staged artifacts no longer valid.
>>>>
>>>>
>>>> *Browser extension option*
>>>> If you’re a GitHub “org owner” and want to easily see if there is a
>>>> pending advisory in the current repository you are browsing, you may find
>>>> this browser extension valuable:
>>>> https://github.com/Wadeck/extension-jenkins-security.
>>>>
>>>> This automation was tested already multiple times in a closed beta way,
>>>> and now we are opening the beta to anyone interested. After some iterations
>>>> we will call it GA but still welcome any feedback.

Re: [Information] Release block "Beta" program

[Tim Jacomb]

Also this won’t work with any bots that can auto merge when CI checks pass,
e.g. renovate and dependabot, whereas a locked branch will work.

On Tue, 5 Sep 2023 at 17:48, Tim Jacomb  wrote:

> Why not lock the branch instead?
> That means it won’t break review approvals in the meantime and things like
> enabling auto merge for when the release block is over
>
> On Tue, 5 Sep 2023 at 17:13, 'wfoll...@cloudbees.com' via Jenkins
> Developers  wrote:
>
>> Dear plugin maintainers,
>>
>> *Context*
>> In situations where the security team is collaborating with plugin
>> maintainers on a coordinated release, the artifacts are staged and
>> commits/tags are pushed to a designated private repository.
>>
>> However, challenges arise when multiple maintainers are simultaneously
>> working on the same plugin. Coordinating these efforts becomes crucial. If
>> another maintainer merges pull requests or releases a new version of the
>> plugin while a coordinated security release is pending, it necessitates
>> re-staging the artifacts. Depending on the timing of such occurrences in
>> relation to the release schedule, it can create unnecessary urgency and
>> often result in time wasted.
>>
>> *Objectives*
>> We want to have a way to inform the plugin maintainers while not
>> revealing specific details about the advisory in advance.
>>
>> *Current solution*
>> We've implemented an automation solution for your convenience. You can
>> now trigger this automation by simply commenting "/block-release" in the
>> SECURITY ticket assigned to you. This action will reduce GitHub permissions
>> for contributors to "Triage”. At the same time, a GitHub advisory will be
>> created, with contributors included as "Collaborators," allowing them to
>> view the advisory and receive a notification.
>>
>>
>> Once the release is completed, the security team will promptly remove the
>> block. You can also initiate the removal by commenting "/unblock-release"
>> in the same SECURITY ticket.
>>
>> *Known limitations*
>>
>>- Our automation cannot prevent all incidents but aims to cover most
>>cases.
>>- For vulnerabilities affecting multiple plugins, the security team
>>has to be involved to widen the scope of the block.
>>- Some corner cases like users with "org owner" permissions in GitHub
>>or Administer permission on ci.jenkins.io are still able to perform
>>actions that could make the staged artifacts no longer valid.
>>
>>
>> *Browser extension option*
>> If you’re a GitHub “org owner” and want to easily see if there is a
>> pending advisory in the current repository you are browsing, you may find
>> this browser extension valuable:
>> https://github.com/Wadeck/extension-jenkins-security.
>>
>> This automation was tested already multiple times in a closed beta way,
>> and now we are opening the beta to anyone interested. After some iterations
>> we will call it GA but still welcome any feedback.
>>
>> Wadeck Follonier
>>
>> Jenkins Security officer
>>
>> --
>> 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/2ffd0261-6682-4c67-b5ca-0f29c97ecbadn%40googlegroups.com
>> <https://groups.google.com/d/msgid/jenkinsci-dev/2ffd0261-6682-4c67-b5ca-0f29c97ecbadn%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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3BieTRxdjibCfVJfCaAbf5Scw%2BuNx_VsZ-T8HVL5nnmfDJA%40mail.gmail.com.

Re: [Information] Release block "Beta" program

[Tim Jacomb]

Why not lock the branch instead?
That means it won’t break review approvals in the meantime and things like
enabling auto merge for when the release block is over

On Tue, 5 Sep 2023 at 17:13, 'wfoll...@cloudbees.com' via Jenkins
Developers  wrote:

> Dear plugin maintainers,
>
> *Context*
> In situations where the security team is collaborating with plugin
> maintainers on a coordinated release, the artifacts are staged and
> commits/tags are pushed to a designated private repository.
>
> However, challenges arise when multiple maintainers are simultaneously
> working on the same plugin. Coordinating these efforts becomes crucial. If
> another maintainer merges pull requests or releases a new version of the
> plugin while a coordinated security release is pending, it necessitates
> re-staging the artifacts. Depending on the timing of such occurrences in
> relation to the release schedule, it can create unnecessary urgency and
> often result in time wasted.
>
> *Objectives*
> We want to have a way to inform the plugin maintainers while not revealing
> specific details about the advisory in advance.
>
> *Current solution*
> We've implemented an automation solution for your convenience. You can now
> trigger this automation by simply commenting "/block-release" in the
> SECURITY ticket assigned to you. This action will reduce GitHub permissions
> for contributors to "Triage”. At the same time, a GitHub advisory will be
> created, with contributors included as "Collaborators," allowing them to
> view the advisory and receive a notification.
>
>
> Once the release is completed, the security team will promptly remove the
> block. You can also initiate the removal by commenting "/unblock-release"
> in the same SECURITY ticket.
>
> *Known limitations*
>
>- Our automation cannot prevent all incidents but aims to cover most
>cases.
>- For vulnerabilities affecting multiple plugins, the security team
>has to be involved to widen the scope of the block.
>- Some corner cases like users with "org owner" permissions in GitHub
>or Administer permission on ci.jenkins.io are still able to perform
>actions that could make the staged artifacts no longer valid.
>
>
> *Browser extension option*
> If you’re a GitHub “org owner” and want to easily see if there is a
> pending advisory in the current repository you are browsing, you may find
> this browser extension valuable:
> https://github.com/Wadeck/extension-jenkins-security.
>
> This automation was tested already multiple times in a closed beta way,
> and now we are opening the beta to anyone interested. After some iterations
> we will call it GA but still welcome any feedback.
>
> Wadeck Follonier
>
> Jenkins Security officer
>
> --
> 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/2ffd0261-6682-4c67-b5ca-0f29c97ecbadn%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-3Bievg057Ht73iA7rynNdg0cLQjFupMaEcJriwwcWynwDtA%40mail.gmail.com.

Re: Jenkins 2.413 as next LTS baseline?

[Tim Jacomb]

Ah I see I missed that 2.415 was out.

Let’s continue with 2.414 and backport security fixes

On Mon, 24 Jul 2023 at 15:41, 'jn...@cloudbees.com' via Jenkins Developers <
jenkinsci-dev@googlegroups.com> wrote:

> >  2.415 appears to have a regression in the dialog handling that I just
> found with a minimal amount of testing, so possibly too new to have had
> exposure  :-(
> https://issues.jenkins.io/browse/JENKINS-71699
>
> On Monday, July 24, 2023 at 3:31:21 PM UTC+1 jn...@cloudbees.com wrote:
>
>> Thanks Tim & Basil for continuing this.
>>
>> I filed https://issues.jenkins.io/browse/JENKINS-71698 for LTS tracking
>> and tagged the jenkins PR
>> 
>>
>> >  Shall we go with 2.415 instead as it will have security fixes
>>
>> not sure I follow 2.415 is not a security release?  are you meaning 2.416
>> which will be the security release which will naturally contain the 2.415
>> bits?
>>
>> 2.415 *appears* to have a regression in the dialog handling that I just
>> found with a minimal amount of testing, so possibly too new to have had
>> exposure  :-(
>> On Monday, July 24, 2023 at 2:29:46 PM UTC+1 timja...@gmail.com wrote:
>>
>>> Shall we go with 2.415 instead as it will have security fixes (given
>>> they would be backported anyway, it's less confusing if we start with the
>>> version they were introduced in I think)?
>>>
>>> The plugin manager bug in 2.414 has been fixed.
>>>
>>> On Sat, 22 Jul 2023 at 00:21, Basil Crow  wrote:
>>>
 On Fri, Jul 21, 2023 at 10:42 AM 'jn...@cloudbees.com' via Jenkins
 Developers  wrote:
 > 2.414 has a regression in the plugin manager.
 > I would be -1 on this unless that is fixed (currently missing a
 Jenkins bug but has been the cause of a lot of ATH failures)
 > https://github.com/jenkinsci/acceptance-test-harness/issues/1284 for
 the current status/investigation, I will file a Jenkins bug on Monday to
 track.

 Thanks for starting to investigate this. As I wrote in the discussion
 at jenkinsci/acceptance-test-harness#1284, I was able to definitively
 implicate jenkinsci/jenkins#8025 as the cause of the ATH test failure
 by widening the race window with some sleeps, and I may have been able
 to chase away the ATH test failure and/or fix the bug by removing the
 asynchrony from the original change.

 Since jenkinsci/jenkins#8025 was the last commit in 2.414 and since
 2.414 contains some other changes that we want, I would like to
 propose that we keep 2.414 as the next LTS baseline but simply revert
 jenkinsci/jenkins#8025 from the stable branch before shipping. (An
 equally plausible alternative would be to choose 2.413 and backport
 the other changes that we want.)

 As far as the main branch is concerned, now that I have come up with a
 way to reproduce the original problem, I would like to propose that we
 give folks a limited amount of time (say, a week) to come up with a
 solution and otherwise revert jenkinsci/jenkins#8025 on the main
 branch as well to restore stability to the ATH test suite.

 --
 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/CAFwNDjpCWAkp6nfB07z3wc9bMqaFs091tbGWyW3CVMQZm8dFmw%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/7d39f095-36c4-4164-a4b9-34f920b5d3dcn%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-3Bich6me_uc6AiaCN%3D2ut74D2L3AmxOb-V50nKaMNvyUGaQ%40mail.gmail.com.

Re: Jenkins 2.413 as next LTS baseline?

[Tim Jacomb]

Shall we go with 2.415 instead as it will have security fixes (given they
would be backported anyway, it's less confusing if we start with the
version they were introduced in I think)?

The plugin manager bug in 2.414 has been fixed.

On Sat, 22 Jul 2023 at 00:21, Basil Crow  wrote:

> On Fri, Jul 21, 2023 at 10:42 AM 'jn...@cloudbees.com' via Jenkins
> Developers  wrote:
> > 2.414 has a regression in the plugin manager.
> > I would be -1 on this unless that is fixed (currently missing a Jenkins
> bug but has been the cause of a lot of ATH failures)
> > https://github.com/jenkinsci/acceptance-test-harness/issues/1284 for
> the current status/investigation, I will file a Jenkins bug on Monday to
> track.
>
> Thanks for starting to investigate this. As I wrote in the discussion
> at jenkinsci/acceptance-test-harness#1284, I was able to definitively
> implicate jenkinsci/jenkins#8025 as the cause of the ATH test failure
> by widening the race window with some sleeps, and I may have been able
> to chase away the ATH test failure and/or fix the bug by removing the
> asynchrony from the original change.
>
> Since jenkinsci/jenkins#8025 was the last commit in 2.414 and since
> 2.414 contains some other changes that we want, I would like to
> propose that we keep 2.414 as the next LTS baseline but simply revert
> jenkinsci/jenkins#8025 from the stable branch before shipping. (An
> equally plausible alternative would be to choose 2.413 and backport
> the other changes that we want.)
>
> As far as the main branch is concerned, now that I have come up with a
> way to reproduce the original problem, I would like to propose that we
> give folks a limited amount of time (say, a week) to come up with a
> solution and otherwise revert jenkinsci/jenkins#8025 on the main
> branch as well to restore stability to the ATH test suite.
>
> --
> 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/CAFwNDjpCWAkp6nfB07z3wc9bMqaFs091tbGWyW3CVMQZm8dFmw%40mail.gmail.com
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3Bic73ZV1YKp%2BA4u8Cu4v2tAWkfxym9OgirexhvOfSBrQWQ%40mail.gmail.com.

Re: Jenkins 2.413 as next LTS baseline?

[Tim Jacomb]

Yes

On Mon, 17 Jul 2023 at 19:47, Mark Waite  wrote:

>
>
> On Monday, July 17, 2023 at 9:41:51 AM UTC-6 Basil Crow wrote:
>
> There do not appear to be any known user-visible regressions in production
> code in 2.414, but jenkinsci/jenkins#7872
> <https://github.com/jenkinsci/jenkins/pull/7872> implies a change in
> Login Theme (3,757 installations) which has not yet been completed (tracked
> in JENKINS-71238 <https://issues.jenkins.io/browse/JENKINS-71238>) and
> jenkinsci/jenkins#7942 <https://github.com/jenkinsci/jenkins/pull/7942>
> implies a change in Calendar View (1,866 installations) which has not yet
> been completed (tracked in JENKINS-71663
> <https://issues.jenkins.io/browse/JENKINS-71663>). If these tasks are not
> completed by the time 2.414 LTS ships, they should be documented as known
> defects in the release notes.
>
>
> Thanks for noting those needed additions to the upgrade guide.  Since
> those changes are in Jenkins 2.413 and in Jenkins 2.414, it makes sense to
> me that we choose Jenkins 2.414.
>
> Tim Jacomb, do you agree that Jenkins 2.414 should be the baseline for the
> LTS release scheduled for August 23, 2023?
>
> 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/2fad8aa3-2774-413d-b41b-1f2e1ee1a94dn%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/2fad8aa3-2774-413d-b41b-1f2e1ee1a94dn%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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3BidBb0eaiecRCwTJvSfSJrddA9bsLa70fzsM1Bj7z0zCew%40mail.gmail.com.

Re: Drop 2.375.x support from plugin bom

[Tim Jacomb]

+1 from me.

On Mon, 26 Jun 2023 at 23:44, Basil Crow  wrote:

> No strong feeling one way or another from me. When we began requiring
> 2.361.x or newer, there was a strong technical reason; namely, it was
> prohibitively difficult to support Java 11 as a first-class citizen in
> the toolchain alongside Java 8. There is no similar technical
> justification in this case, since the relevant changes to bring the
> 2.375.x BOM line up to feature parity with the 2.387.x BOM line with
> regard to the plugin parent POM and test harness (i.e., the HtmlUnit
> migration) could be backported if desired. So the question comes down
> to whether we feel the benefit justifies the cost. If I were doing
> this work myself, I would try to retain support for 2.375.x since
> there is some minor inconvenience in dropping support for 2.375.x and
> since I think the cost of backporting is relatively low. But since I
> believe the people doing the work should make the decisions, it is not
> up to me.
>
> --
> 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/CAFwNDjoCH9orjtO1NaA94gFzF5gz7AuEKa-Kn4RNP50yBqyJYw%40mail.gmail.com
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3Bica_fXhjnqiSO1LhK5O%3DximXfmPhUSt7DJEKdQ2mOUTdQ%40mail.gmail.com.

Re: Requesting admin access to the jenkinsci GitHub organization

[Tim Jacomb]

I've added Basil as an organisation owner

On Tue, 13 Jun 2023 at 07:50, 'wfoll...@cloudbees.com' via Jenkins
Developers  wrote:

> +1
>
> On Tuesday, June 6, 2023 at 10:36:39 AM UTC+2 Adrien Lecharpentier wrote:
>
>> +1 as well from me.
>>
>> Le mar. 6 juin 2023, 10:15, Baptiste Mathus  a écrit :
>>
>>> +1.
>>>
>>> Le lun. 5 juin 2023 à 19:33, Srikanth Jana  a
>>> écrit :
>>>
 +1 from me

 On Mon, Jun 5, 2023 at 11:01 PM Alexander Brandes 
 wrote:

> +1 for Basil
>
> On Mon 5. Jun 2023 at 19:30, Mark Waite  wrote:
>
>>
>>
>> On Monday, June 5, 2023 at 11:29:18 AM UTC-6 m Basil Crow wrote:
>>
>> I would like to become an organization administrator of the jenkinsci
>> GitHub organization. This would facilitate various efforts I am
>> involved with, such as repository transfers.
>>
>>
>> +1 from me.
>>
>> --
>> 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/78809aba-d9ca-4d43-98bf-858811577121n%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-de...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CAP9joaGh28MKR0jSRptwGGhnAKNn_7C8W2aTQVgzpqmsyjtgeQ%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/CAJxAiNDnHRF5BRtESwKfdsmH9pi698V24TjXTMPXCTfOEUmK4Q%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/CANWgJS7QcnLsR4ZRR5tU9y6fWsQ2dKP2xdGCpx84V44ga3xhAg%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/84f3cd9d-81c0-420f-b7c6-663d6145d271n%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-3Bif4urS%2BODx_HAod5xV4DwEZnofC8ug4Mr9R3CbN7m3PtQ%40mail.gmail.com.

Re: Backporting for LTS 2.401.2 has started

[Tim Jacomb]

+1 for EOL Monitor

On Fri, 9 Jun 2023 at 18:01, Basil Crow  wrote:

> That makes sense to me, and I think an exception is justified for
> time-sensitive areas, such as EOL notifications. The feature has been
> in weeklies without any reports of regression.
>
> On Fri, Jun 9, 2023 at 8:34 AM Mark Waite 
> wrote:
> > I would like to inform users earlier about end of life operating
> systems, if that difference from the standard LTS backporting rules would
> be allowed.
> >
> > Specifically, we would backport:
> >
> > Warn when operating system end of life is approaching -
> https://github.com/jenkinsci/jenkins/pull/7913 (Jenkins 2.407)
> > Fix Fedora 38 date in operating system end of life warning -
> https://github.com/jenkinsci/jenkins/pull/8082 (Jenkins 2.409)
> >
> > That would make the operating system end of life warning visible to LTS
> users 8 weeks before it would naturally become visible.
> >
> > This is backporting a feature, so I am also just fine if this is
> rejected, since it is not according to the standard backporting rules where
> we rarely backport features to an LTS line.
> >
> > I would revise the blog post that announces the end of life operating
> system warning to state that the warning is available to LTS users in
> 2.401.2
> >
> > 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/CAFwNDjoEguYDuOAuw2yxJ82HnT1WOvtvDaN8-0O5XdTvwyUKuw%40mail.gmail.com
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3BicNBhkfeD6pq0OeR4fZQQEYUkvCYbbbtA7MMGTgWCUnng%40mail.gmail.com.

Re: Requesting Admin access to the jenkinsci organization

[Tim Jacomb]

+1

On Mon, 5 Jun 2023 at 10:05, Ullrich Hafner 
wrote:

> +1 from me
>
> Am 05.06.2023 um 09:50 schrieb Alexander Brandes :
>
> Hey everyone,
>
> I would like to increase my involvement within the Jenkins project beyond
> a maintainer scope, and would like to request admin access to the jenkinsci
> GitHub organization.
>
> Besides my seat on the Jenkins governance board, I am one of the core
> maintainers within the jenkinsci GitHub organization.
> The recent sponsorship of the project coming from GitHub and the adoption
> of enterprise features, like autolink references you can find in core
> repositories already, are one of the examples of my work, which wouldn't be
> possible without me bothering Tim Jacomb constantly to click the right
> buttons for me.
> I have admin access to various core component and plugin repositories
> within the jenkinsci organization, plus the jenkins-infra organization,
> including jenkins.io or the plugin site. Having admin permissions in the
> jenkinsci organization would allow me to help to facilitate contributions
> of these kinds to the Jenkins project.
>
> My GitHub account is configured securely, and I have an ICLA signed.
>
> Would the project be fine with such a request?
> Thanks in advance,
> Alexander Brandes
>
> --
> 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/CAP9joaHYsQEvPKLQpxdWPW_OR92O98F8Xt1AWMyDsO-03tYiQg%40mail.gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/CAP9joaHYsQEvPKLQpxdWPW_OR92O98F8Xt1AWMyDsO-03tYiQg%40mail.gmail.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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/E1D85BB2-8BC6-4346-B134-5035E20B4B32%40gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/E1D85BB2-8BC6-4346-B134-5035E20B4B32%40gmail.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3Bie3AH7VGA1MT6D5qXcO1FraMa-kGPEb6809onObpio6mw%40mail.gmail.com.

2.401.2 release lead

[Tim Jacomb]

Hello

Is anyone interested in being the release lead for 2.401.2?

Planned dates can be seen on the event calendar:
https://www.jenkins.io/events/#event-calendar
Release candidate by 14th June
Release on 28th June

The documentation is at:
https://github.com/jenkins-infra/release/blob/master/.github/ISSUE_TEMPLATE/1-lts-release-checklist.md

Past release leads will be available to answer any questions and provide
guidance.

We chat in #jenkins-release on libera IRC,
https://www.jenkins.io/chat/#jenkins-release or on the bridged matrix
channel.

Anyone interested?

Thanks
Tim

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3BiddAfOz0SWzcNfUHOUvZog%3DpCQxvn29Z9sf532TxcUv0g%40mail.gmail.com.

Release lead for 2.401.1

[Tim Jacomb]

Hello

Is anyone interested in being the release lead for 2.401.1?

Planned dates can be seen on the event calendar:
https://www.jenkins.io/events/#event-calendar
Release candidate by 17th May (apologies for short notice can be a little
late if needed)
Release on 31st May

The documentation is at:
https://github.com/jenkins-infra/release/blob/master/.github/ISSUE_TEMPLATE/1-lts-release-checklist.md

I'll be available to answer any questions and provide guidance (along with
hopefully other past release leads)

We chat in #jenkins-release on libera IRC,
https://www.jenkins.io/chat/#jenkins-release or on the bridged matrix
channel.

Anyone interested?

Thanks
Tim

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3BicC9C7yGdZu3n_AyP52by7THAirHj-bTffc1S_si0Ys-g%40mail.gmail.com.

Re: Prototype.js replacing JSON.stringify

[Tim Jacomb]

I think pull requests are now open for all of the core usage of prototype.

and a PR for bom and ATH which removes prototype in
https://github.com/jenkinsci/jenkins/pull/7781

Basil has opened a PR with a feature flag that you can use to disable
prototype and do some more testing / developing of prototype removal fixes:
https://github.com/jenkinsci/jenkins/pull/7948

On Sat, 6 May 2023 at 00:43, Basil Crow  wrote:

> On Mon, Mar 13, 2023 at 3:27 PM 'Gavin Mogan' via Jenkins Developers
>  wrote:
> >
> > I think the first steps would be to remove as many of those references
> from core before detaching the plugin and making it optional
>
> Detaching Prototype to a plugin might work, but it is also likely to
> create problems in practice — plugins that update their core baseline
> to one after the detach point won't necessarily get test failures once
> Prototype is missing unless they have HtmlUnit tests for all portions
> of their UI (unlikely) and so their maintainers are unlikely to notice
> that they need to do anything until after the plugin is released and
> users start complaining. There are about 50 plugins that use
> Prototype, so I think the better solution is to proactively remove
> Prototype usages from all of them and then remove Prototype from core.
> This is a large amount of work, but it could be feasible if everyone
> in this thread participated in the effort.
>
> --
> 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/CAFwNDjrxgJ589zG9k%2BbXSgt_OJrHWq%2B3nrAPWUtt%2BtwHs2RQYA%40mail.gmail.com
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3BidSye9zAqne%2BriavCJLL%2BtUT4f9M8cLV-EmsmKr5%3DhFHQ%40mail.gmail.com.

Re: Jenkins 2.401 as next LTS baseline?

[Tim Jacomb]

Yes

On Thu, 27 Apr 2023 at 17:34, Mark Waite  wrote:

> Based on the feedback, Tim Jacomb are you OK with the selection of 2.401
> as the next LTS baseline?
>
> 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/6b627b70-5992-4507-8abb-bd6abdea8cc9n%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/6b627b70-5992-4507-8abb-bd6abdea8cc9n%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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3BiejPqgos6%3DJZpZ9hTcsnNt6-y8f--Yg2vjZxUrwo4fkJA%40mail.gmail.com.

Re: Reimbursement for code signing certificate

[Tim Jacomb]

+1

On Tue, 18 Apr 2023 at 19:32, Basil Crow  wrote:

> On Tue, Apr 18, 2023 at 11:23 AM 'Gavin Mogan' via Jenkins Developers
>  wrote:
> > Shouldn't this be submitted via expensify and approved in the board
> > mailing list?
>
> From JEP-15 (at revision b8bfe17), § 3.3.2 ("Use of donations"), lines
> 177-178:
>
> > Budget requests should be submitted to the developer mailing list and
> > discussed there, the Governance meeting will be doing a formal
> > approval/rejection based on the community feedback.
>
> --
> 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/CAFwNDjpHawAfD7141y-_TxgOThzrMH_g7Z9x8To2p9vQHPM5Bw%40mail.gmail.com
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3Bif%2Bm%2BaUJYNW1F5xQTz6DCm1jj5qWj%2B%3D_go1vq4Z0hVOyA%40mail.gmail.com.

Release lead for 2.387.3

[Tim Jacomb]

Hello

Is anyone interested in being the release lead for 2.387.3?

Planned dates can be seen on the event calendar:
https://www.jenkins.io/events/#event-calendar
Release candidate by 19th April (apologies for short notice can be a little
late if needed)
Release on 3rd May

The documentation is at:
https://github.com/jenkins-infra/release
/blob/master/.github/ISSUE_TEMPLATE/1-lts-release-checklist.md

I'll be available to answer any questions and provide guidance (along with
hopefully other past release leads)

We chat in #jenkins-release on libera IRC,
https://www.jenkins.io/chat/#jenkins-release or on the bridged matrix
channel.

Anyone interested?

Thanks
Tim

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3BidbN3HD8EiYCm18pyPBK8zGstWpMV%3DepdbTPa0X%3DRQvLw%40mail.gmail.com.

Re: script to configure repository labels

[Tim Jacomb]

It can be setup at the org level as a repository default, Gavin also had an
app where you could click a button and it would set it all up for your
repository

On Fri, 31 Mar 2023 at 13:23, Ullrich Hafner 
wrote:

> I am using the action
>
>
> https://github.com/jenkinsci/warnings-ng-plugin/blob/master/.github/workflows/sync-labels.yml
>
> With the configuration in
>
>
> https://github.com/jenkinsci/warnings-ng-plugin/blob/master/.github/labels.yml
>
> In all my repositories.
>
> It uses https://github.com/micnncim/action-label-syncer internally.
>
>
> Am 31.03.2023 um 14:13 schrieb 'Herve Le Meur' via Jenkins Developers <
> jenkinsci-dev@googlegroups.com>:
>
> > I was wondering if the infra team or anyone else had already written a
> script to set the labels to the
> https://github.com/jenkinsci/.github/blob/master/.github/release-drafter.yml
> ones
>
> Not that I know but I think it's a good idea! I encountered the same need
> on jenkins-infra repositories.
>
> > Additionally if the standard colours for the labels had been defined
> somewhere to avoid having conflicting label colours.
>
> Same.
>
> Do you mind opening a help desk issue with this request?
>
> On Fri, Mar 31, 2023 at 1:46 PM 'jn...@cloudbees.com' via Jenkins
> Developers  wrote:
>
>> Hi all,
>>
>> When modernising a plugin I find the tedious part is to create all the
>> labels for both CD releases and the release notes.
>>
>> it's time consuming to find a reference repo and then duplicate the
>> labels (and their colours) to the repo I am updating.
>>
>> As this is not an uncommon task I was wondering if the infra team or
>> anyone else had already written a script to set the labels to the
>> https://github.com/jenkinsci/.github/blob/master/.github/release-drafter.yml
>> ones that I was unaware?
>> Additionally if the standard colours for the labels had been defined
>> somewhere to avoid having conflicting label colours.
>>
>> /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 jenkinsci-dev+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-dev/2e3f2933-00be-4bf7-b340-6be50484e0a9n%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/CAL-Lwjwm7gOXg9%3DE2e1du2F%2BpRVypWH1zK%3DZE2Zib9CvQop6ew%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/6BEDA057-4C9C-4E9B-BDFD-E6899314F1E9%40gmail.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3Bie2HXebm52EkbBEcBw3%2BL35YkSr6Rw1fxazvm8cdTZwEA%40mail.gmail.com.

Re: Prototype.js replacing JSON.stringify

[Tim Jacomb]

There's a draft PR open at https://github.com/jenkinsci/jenkins/pull/7781
It does almost all of core.

There were one or two more complicated ones I left for later.

This search shows the rest of the jenkinsci hosted plugins as well:
https://github.com/search?q=org%3Ajenkinsci+Ajax.Request++NOT+repo%3Ajenkinsci%2Fjenkins+=code=1

If anyone wants to help they could either test the above pull request or
submit some pull requests to other plugins.

Thanks
Tim

On Tue, 14 Mar 2023 at 08:06, Tim Jacomb  wrote:

> I've made a start:
> https://github.com/jenkinsci/jenkins/pull/7727
>
> This PR is also removing some prototype as well:
> https://github.com/jenkinsci/jenkins/pull/7718
>
> On Mon, 13 Mar 2023 at 22:27, 'Gavin Mogan' via Jenkins Developers <
> jenkinsci-dev@googlegroups.com> wrote:
>
>> My knowledge of core is pretty out dated, but as far as I know, a lot of
>> the behaviors are defined using YUI and Prototypejs
>> I think the first steps would be to remove as many of those references
>> from core before detaching the plugin and making it optional
>>
>> For example, the Ajax.Request would need to be re-written
>>
>> https://github.com/jenkinsci/jenkins/blob/a4447db3d88fd883b99ff3925a5ea90864794367/core/src/main/resources/lib/form/link/link.js#L15
>>
>> https://github.com/jenkinsci/jenkins/blob/a4447db3d88fd883b99ff3925a5ea90864794367/core/src/main/resources/lib/layout/breadcrumbs.js#L168
>>
>> I'm sure there's lots of other legacy items left behind.
>>
>> Talking about it is good, but unless people actually make PRs, it'll
>> never actually get replaced.
>>
>> On Sat, Mar 11, 2023, 8:01 PM 'Rahul Somasunderam' via Jenkins Developers
>>  wrote:
>>
>>> Is it possible to turn it into its own plugin and treat it as an
>>> implicit dependency for plugins relying on older versions of Jenkins, but
>>> remove it later?
>>>
>>>
>>> On Mar 11, 2023, at 15:37, Ullrich Hafner 
>>> wrote:
>>>
>>> I think I also have some problems with this ugly dependency. Seems that
>>> other JS libraries that rely on JSON stringify (datatables, echarts) break
>>> in some places as well :-(
>>>
>>> But this JS code is so deeply nested in Jenkins UI code that I have no
>>> clue on how to fix that...
>>>
>>>
>>> Am 02.03.2023 um 23:15 schrieb 'Gavin Mogan' via Jenkins Developers <
>>> jenkinsci-dev@googlegroups.com>:
>>>
>>> I vaguely remember some javascript code somewhere deleting
>>> Object.prototype.toJSON() or something
>>>
>>> A quick search found
>>> https://github.com/jenkinsci/jenkins/blob/e41aeaacf434b9ff93c8848f8eddbfcbb27ed462/war/src/main/js/util/jenkins.js#L20-L54
>>> In theory that makes JSON.stringify work again, but would make the other
>>> prototype js fail, so would have to be done temporarily.
>>>
>>>
>>> On Thu, Mar 2, 2023 at 1:59 PM Ullrich Hafner 
>>> wrote:
>>>
>>>>
>>>> Hi!
>>>> I was looking at some javascript that was behaving differently on
>>>> Jenkins than it does on other apps. I boiled it down to the simplest
>>>> reproducible test case.
>>>> It turned out that serialization was behaving differently when calling
>>>> JSON.stringify.
>>>>
>>>> This is the sample code you can run on the Chrome DevTools
>>>>
>>>> JSON.stringify({ a: [1, 2, 3] });
>>>>
>>>> On Jenkins, this is the behavior
>>>>
>>>> '{"a":"[1, 2, 3]"}'
>>>>
>>>> On other apps, this is the behavior
>>>>
>>>> '{"a":[1, 2, 3]}'
>>>>
>>>> When I attempt to debug the code, stepping into `JSON.stringify` on
>>>> Jenkins takes me to prototype.js.
>>>>
>>>> I've seen some threads here attempting not to rely on prototype.js for
>>>> functionality, but how far are we from removing it?
>>>>
>>>>
>>>> Very far. A couple of years ago I even tried to upgrade prototype.js to
>>>> the latest version but failed, since some plugins are depending on
>>>> prototype.js as well. All UI stuff is tightly coupled to prototype.js, this
>>>> will be very hard to remove.
>>>>
>>>>
>>>> - Rahul
>>>>
>>>> --
>>>> You received this message because you are subscribed to the Google
>>>> Groups "Jenkins Developers" group.
>>>> To unsub

Re: New maintainer for Jenkins Operator

[Tim Jacomb]

+ jenkinsci-dev

On Fri, 24 Mar 2023 at 15:12, 'Piotr Ryba' via Jenkins Cloud Native SIG <
jenkins-cloud-native-...@googlegroups.com> wrote:

> Hello,
>
> My name is Peter, I work at VirtusLab and am part of the team maintaining
> the Jenkins Operator 
> project.
>
> A few days ago we’ve published an announcement
>  regarding the
> further involvement of the VirtusLab team in the operator. Long story
> short, we’ll be limiting our contribution to the project as the company is
> pursuing other goals.
>
> Nonetheless, there are members of the Jenkins Community willing to take
> over. Luigi (brokenp...@gmail.com) has already begun his work to get the
> project back in shape by going through the open issues, publishing a
> roadmap ,
> and working on the pull requests. If anybody is interested in helping to
> keep the project alive, Luigi is the person to go to.
>
> It’s good to see the project live on.
>
> Best regards,
>
> Peter
>
> Email correspondence is considered personal data processing. Check out our 
> Privacy
> Policy  for details about the controller of
> your data and your rights according to GDPR/RODO.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Cloud Native SIG" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkins-cloud-native-sig+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkins-cloud-native-sig/CA%2Byt-6VPCjPVx0Brv9kiCR-dfPQWEUahb7vUd3uF%3DryWEKOdtw%40mail.gmail.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3Bifb9rdPOa9z4H7magQKDHi4aEJtrC5M0jrEspPJVH1UzQ%40mail.gmail.com.

Re: 2.387.2 RC?

[Tim Jacomb]

Nope I just forgot to send the release lead email.

Is there anyone able to do it?

Thanks
Tim

On Mon, 20 Mar 2023 at 16:42, Baptiste Mathus  wrote:

> Hi all,
>
> @Tim in the calendar, the 2.387.2 RC is supposed to go out this Wednesday
> the 22nd .
> Is the calendar outdated, or are we going to start the backporting process
> soon?
>
> Thanks!
>
> -- Baptiste
>
> --
> 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/CANWgJS6F0jn4OiLXHNNt4Dg07xpdZGo%2B5RMuKkz9WbwrOt21%3DQ%40mail.gmail.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3BiefJm1cqm8JojmKFiebc--s8jY%3DVqXL4e0ao799u768hQ%40mail.gmail.com.

Re: Prototype.js replacing JSON.stringify

[Tim Jacomb]

I've made a start:
https://github.com/jenkinsci/jenkins/pull/7727

This PR is also removing some prototype as well:
https://github.com/jenkinsci/jenkins/pull/7718

On Mon, 13 Mar 2023 at 22:27, 'Gavin Mogan' via Jenkins Developers <
jenkinsci-dev@googlegroups.com> wrote:

> My knowledge of core is pretty out dated, but as far as I know, a lot of
> the behaviors are defined using YUI and Prototypejs
> I think the first steps would be to remove as many of those references
> from core before detaching the plugin and making it optional
>
> For example, the Ajax.Request would need to be re-written
>
> https://github.com/jenkinsci/jenkins/blob/a4447db3d88fd883b99ff3925a5ea90864794367/core/src/main/resources/lib/form/link/link.js#L15
>
> https://github.com/jenkinsci/jenkins/blob/a4447db3d88fd883b99ff3925a5ea90864794367/core/src/main/resources/lib/layout/breadcrumbs.js#L168
>
> I'm sure there's lots of other legacy items left behind.
>
> Talking about it is good, but unless people actually make PRs, it'll never
> actually get replaced.
>
> On Sat, Mar 11, 2023, 8:01 PM 'Rahul Somasunderam' via Jenkins Developers <
> jenkinsci-dev@googlegroups.com> wrote:
>
>> Is it possible to turn it into its own plugin and treat it as an implicit
>> dependency for plugins relying on older versions of Jenkins, but remove it
>> later?
>>
>>
>> On Mar 11, 2023, at 15:37, Ullrich Hafner 
>> wrote:
>>
>> I think I also have some problems with this ugly dependency. Seems that
>> other JS libraries that rely on JSON stringify (datatables, echarts) break
>> in some places as well :-(
>>
>> But this JS code is so deeply nested in Jenkins UI code that I have no
>> clue on how to fix that...
>>
>>
>> Am 02.03.2023 um 23:15 schrieb 'Gavin Mogan' via Jenkins Developers <
>> jenkinsci-dev@googlegroups.com>:
>>
>> I vaguely remember some javascript code somewhere deleting
>> Object.prototype.toJSON() or something
>>
>> A quick search found
>> https://github.com/jenkinsci/jenkins/blob/e41aeaacf434b9ff93c8848f8eddbfcbb27ed462/war/src/main/js/util/jenkins.js#L20-L54
>> In theory that makes JSON.stringify work again, but would make the other
>> prototype js fail, so would have to be done temporarily.
>>
>>
>> On Thu, Mar 2, 2023 at 1:59 PM Ullrich Hafner 
>> wrote:
>>
>>>
>>> Hi!
>>> I was looking at some javascript that was behaving differently on
>>> Jenkins than it does on other apps. I boiled it down to the simplest
>>> reproducible test case.
>>> It turned out that serialization was behaving differently when calling
>>> JSON.stringify.
>>>
>>> This is the sample code you can run on the Chrome DevTools
>>>
>>> JSON.stringify({ a: [1, 2, 3] });
>>>
>>> On Jenkins, this is the behavior
>>>
>>> '{"a":"[1, 2, 3]"}'
>>>
>>> On other apps, this is the behavior
>>>
>>> '{"a":[1, 2, 3]}'
>>>
>>> When I attempt to debug the code, stepping into `JSON.stringify` on
>>> Jenkins takes me to prototype.js.
>>>
>>> I've seen some threads here attempting not to rely on prototype.js for
>>> functionality, but how far are we from removing it?
>>>
>>>
>>> Very far. A couple of years ago I even tried to upgrade prototype.js to
>>> the latest version but failed, since some plugins are depending on
>>> prototype.js as well. All UI stuff is tightly coupled to prototype.js, this
>>> will be very hard to remove.
>>>
>>>
>>> - Rahul
>>>
>>> --
>>> 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/708c6498-e0d4-481e-9ad7-e0a8e5af65ffn%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/76FFAC15-B00C-4528-8AB1-68ED0E6D7055%40gmail.com
>>> 
>>> .
>>>
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Jenkins Developers" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to jenkinsci-dev+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-dev/CAG%3D_Duv8NOUT%2BzGfEoww2bf11kdNAkkT8HCwG%3DUoRuCB6J5ktQ%40mail.gmail.com
>> 

Re: Jenkinsci Cloudevents plugin

[Tim Jacomb]

Given the plugins implement different specifications without being too
close to the details I would suggest a new plugin even if it’s based on the
existing one.
There’s no need to confuse users with having a different spec in the
artefact id

On Tue, 7 Mar 2023 at 19:47, Mark Waite  wrote:

>
>
> On Monday, March 6, 2023 at 10:54:37 AM UTC-7 Jamie Plower wrote:
>
> HI all,
>
>
>
> I work for Ger McMahon at Fidelity and we working on restarting the above
> initiative around building a CDEvents Plugin for Jenkins. Reviewing the
> advise above it am keen to commence the process where we can look at
> forking and renaming the plugin. Oleg would be possible to follow up with
> some help around getting the appropriate permission to kick off the process
> and appreciate any assistance in helping me & team navigate through this
> process initially in hosting/adopting this CD Events plugin
>
>
>
>
> Thanks for your willingness to work on CDEvents.  That's great news.
>
> I think that you should adopt the CloudEvents plugin
>  and use it as the basis for
> your efforts.  The "Adopt a plugin"
> 
> instructions guide you through the necessary steps.  Vibhav is one of the
> maintainers and can approve the adoption request.
>
> While waiting for approval of the adoption request, you could use the
> steps in the "Improve a plugin"
>  tutorial to
> submit preparatory pull requests to that plugin.  The plugin needs to be
> updated with most of the steps that are included in that tutorial.
>
> Changing the display name of the plugin is quite easy.  See the mailing
> list thread
> 
> for details.
>
> I think that the new plugin you're envisioning will be close enough to the
> existing plugin that you'll want to start with the existing plugin rather
> than create a new plugin.
>
> 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/a91e46f2-0217-4024-ba13-5c584d079acfn%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-3Bidjg70YqnwABUkFrOsbzBWzF5onQvWrds%3D0NnSyQ7v%2BXg%40mail.gmail.com.

Re: Managing clouds UI in Jenkins

[Tim Jacomb]

Vincent provided a PR for this:
https://github.com/jenkinsci/jenkins/pull/7658

I've done some work on it and it's now ready for review.

Thanks
Tim

On Thu, 19 Jan 2023 at 17:34, John Patrick  wrote:

> I was needing to fix configure within those pages only a few hour ago.
> Some way of knowing config is valid/active/working would be useful
> Also grouping or highlighting nodes which are in the same cloud config
> would be useful.
> I had two cloud configurations, and several cloud agents showing, but it
> was hard to see which are via which cloud provider. But one cloud config
> when i click test connection was failing, but that required page navigation
> and the to expand the options. So all the nodes where via one cloud
> provider.
> John
>
>
> On Thu, 19 Jan 2023 at 11:32, Tim Jacomb  wrote:
>
>> Seems reasonable to me although a prototype would allow giving better
>> feedback :)
>>
>> On Thu, 19 Jan 2023 at 09:55, Vincent Latombe 
>> wrote:
>>
>>> Hello,
>>>
>>> I've been looking at cloud configuration recently, and these are my
>>> naive thoughts about it. Let me know what you think of it.
>>>
>>> Clouds configuration was moved from Configure System to Manage Nodes and
>>> Clouds through #4339 <https://github.com/jenkinsci/jenkins/pull/4339> 
>>> (already
>>> 3 years ago)
>>>
>>> [image: Capture d’écran 2023-01-19 à 10.38.54.png]
>>>
>>> Looking at the "Manage nodes and clouds" page, beyond the "Configure
>>> Clouds" in the sidebar, it is still very focused on nodes, not so much on
>>> clouds (even though there is an optional computerSet view for each cloud).
>>>
>>> The "Configure Clouds" screen lists all configured clouds. As mentioned
>>> in #4339 <https://github.com/jenkinsci/jenkins/pull/4339>, in practice
>>> these take a lot of vertical space due to the model complexity that comes
>>> with some cloud implementations.
>>>
>>> Clouds have an 'index' view, accessible through
>>> /manage/cloud//. I don't think any implementation implements
>>> this page so this is currently just a title, and it doesn't have any
>>> sidebar.
>>>
>>> I think it would be more consistent to have :
>>> - at the top, a button to add a new cloud, next to the button "new node"
>>> - this needs a new screen to add a new cloud, similar to how we declare
>>> a new node
>>> - have a list of clouds directly in the "Manage nodes and clouds"
>>> screen, with clickable name and configure link
>>> - a more complete index screen for individual clouds. Sidebar would
>>> include a link to configure, and the main page would include the current
>>> 'computerSet' view. Sidebar could include additional actions contributed
>>> from plugins going forward.
>>> - a configure screen for an individual cloud
>>> - remove the "Configure clouds" link, since now clouds would be
>>> configurable individually.
>>>
>>> Cheers,
>>>
>>> Vincent
>>>
>>> --
>>> 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-zGCi7efXHgj59TMQbCamN7x03yzysL45tj4Z%3DZ5tC1%3DgAew%40mail.gmail.com
>>> <https://groups.google.com/d/msgid/jenkinsci-dev/CAH-zGCi7efXHgj59TMQbCamN7x03yzysL45tj4Z%3DZ5tC1%3DgAew%40mail.gmail.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.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3Biek-sjMX_1dD7cuX_6rd3zwbpsswP-Ycw6bu-riPbwdNg%40mail.gmail.com
>> <https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3Biek-sjMX_1dD7cuX_6rd3zwbpsswP-Ycw6bu-riPbwdNg%40mail.gmail.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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CAH9u10mNB71idxmC0845eonYwi_kQHRaoS8wHttnuUn0sGJfCQ%40mail.gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/CAH9u10mNB71idxmC0845eonYwi_kQHRaoS8wHttnuUn0sGJfCQ%40mail.gmail.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3BieEHVfSs_JWBN5izN_5Aq%2BZsSRBgDKPgZK0aXj2SnpU4g%40mail.gmail.com.

Re: Next LTS baseline

[Tim Jacomb]

I've added the RC dates and the start of the line after next to take us out
to May

On Mon, 6 Feb 2023 at 18:29, Mark Waite  wrote:

> On Monday, February 6, 2023 at 11:07:12 AM UTC-7 Alex Brandes wrote:
> Does someone mind adding new release dates to the calendar with the new
> baseline, please? It's running out of dates.
>
>
> Done .  Updated the 2.xxx.1 item to 2.387.1 and added 2.387.2  2.387.3
>
> --
> 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/4fd3253c-070d-498e-9cd4-b297afd6e781n%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-3Bic_63x1V%2Bab3KDyPfgv5XWehErAcO5%3DjZS%3DpsiZLZ1asg%40mail.gmail.com.

2.387. 1 release lead

[Tim Jacomb]

Hello

Is anyone interested in being the release lead for 2.387.1?

Planned dates can be seen on the event calendar:
https://www.jenkins.io/events/#event-calendar
Release candidate by 22nd February
Release on 8th March

The documentation is at:
https://github.com/jenkins-infra/release/blob/master/.github/ISSUE_TEMPLATE/1-lts-release-checklist.md

I'll be available to answer any questions and provide guidance (along with
hopefully other past release leads)

We chat in #jenkins-release on libera IRC,
https://www.jenkins.io/chat/#jenkins-release or on the bridged matrix
channel.

Anyone interested?

Thanks
Tim

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3Bicp%3DUD_AoMji8Huko9o2MubuAp-Qth8emyE6kdirADk_A%40mail.gmail.com.

Re: Next LTS baseline

[Tim Jacomb]

2.387 has been selected as the next baseline

Cheers
Tim

On Sun, 29 Jan 2023 at 15:21, Oleg Nenashev  wrote:

> Belated +1
>
> On Wednesday, January 25, 2023 at 3:36:25 AM UTC+1 Mark Waite wrote:
>
>> +1 from me for 2.387.
>>
>> On Tuesday, January 24, 2023 at 2:30:47 AM UTC-7 mc.ca...@gmail.com
>> wrote:
>>
>>> That would make a viable candidate. The response on the recent weekly
>>> releases has been overall very positive.
>>>
>>> +1 for 2.387.
>>>
>>> Best,
>>> Alex
>>>
>>> On Tuesday, 24 January 2023 at 10:03:57 UTC+1 timja...@gmail.com wrote:
>>>
 Hi all,

 It's time to select the next LTS baseline.
 The best candidate right now appears to be 2.387

 See recent changelogs: https://www.jenkins.io/changelog/

 Thanks
 Tim

>>> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/e418c827-235d-4352-a501-0e6b85c7500en%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-3BidQLHADWue_e1xuOxt3mvaBBhnZNZGRBZ2wY%3DWLx6pxTg%40mail.gmail.com.

Re: Removing inactive Core maintainers to reduce risk

[Tim Jacomb]

While I’m very much +1 for the change I think it should’ve been discussed
on the mailing list publicly

On Sun, 29 Jan 2023 at 13:52, 'wfoll...@cloudbees.com' via Jenkins
Developers  wrote:

> Thanks for the positive feedback!
>
> >  we decided
> Decision was made between Damien and me.
> It was discussed with a few other people and as we got mainly just ultra
> positive response, widen the discussion before the act did not seem
> necessary. Especially when such a change can be reversed without problems.
>
> Concerning the activities, the remaining people did at least a PR review
> during the last year. This is not strictly requiring the write permission,
> but I don't want to do something that could be seen as a witch hunt.
> This kind of risk reduction was rarely done in the past, I don't want to
> be too aggressive on that. Starting small and increasing the scope over
> time. CERT membership and VPN/infra access will follow soon.
>
> Wadeck
>
> On Saturday, January 28, 2023 at 9:59:24 AM UTC+1 mc.ca...@gmail.com
> wrote:
>
>> Thanks for your ongoing efforts to make our repositories secure!
>>
>> > Was this decision made in concert with other core maintainers
>>
>> I was not aware of such a change, but I heavily endorse the cleanup :)
>>
>> Alex
>>
>> On Friday, 27 January 2023 at 16:59:41 UTC+1 m...@basilcrow.com wrote:
>>
>>> On Fri, Jan 27, 2023 at 1:06 AM 'wfoll...@cloudbees.com' via Jenkins
>>> Developers  wrote:
>>> >
>>> > For that reason we have decided to remove inactive contributors from
>>> the ‘core’ team.
>>>
>>> Thanks! Strongly agree that this is a great move.
>>>
>>> > we decided
>>>
>>> Was this decision made in concert with other core maintainers or
>>> unilaterally?
>>>
>>> > one year without any activity in the affected repositories qualifies
>>> as inactive
>>>
>>> Is this one year without any _general_ activity (e.g., opening a PR)
>>> or one year without any _maintainer_ activity (e.g., merging or
>>> closing a PR)? Write permissions are needed for the latter but not the
>>> former. Given the stated goal to reduce the number of people with
>>> unnecessary write access, the latter definition makes more sense to
>>> me.
>>>
>>> Basil
>>>
>> --
> 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/007096da-aac2--93ec-44466cb3527an%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-3BifT9RQXNOMQf2UM-dvrq1dJAXOUx0XagtjO5ak2pZSg1g%40mail.gmail.com.

Next LTS baseline

[Tim Jacomb]

Hi all,

It's time to select the next LTS baseline.
The best candidate right now appears to be 2.387

See recent changelogs: https://www.jenkins.io/changelog/

Thanks
Tim

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3Bifa0vcgowGppU0rMFUZnEeaEHtt-3pD9VBmOns6PAMYhA%40mail.gmail.com.

Re: Managing clouds UI in Jenkins

[Tim Jacomb]

Seems reasonable to me although a prototype would allow giving better
feedback :)

On Thu, 19 Jan 2023 at 09:55, Vincent Latombe 
wrote:

> Hello,
>
> I've been looking at cloud configuration recently, and these are my naive
> thoughts about it. Let me know what you think of it.
>
> Clouds configuration was moved from Configure System to Manage Nodes and
> Clouds through #4339  (already
> 3 years ago)
>
> [image: Capture d’écran 2023-01-19 à 10.38.54.png]
>
> Looking at the "Manage nodes and clouds" page, beyond the "Configure
> Clouds" in the sidebar, it is still very focused on nodes, not so much on
> clouds (even though there is an optional computerSet view for each cloud).
>
> The "Configure Clouds" screen lists all configured clouds. As mentioned in
> #4339 , in practice these
> take a lot of vertical space due to the model complexity that comes with
> some cloud implementations.
>
> Clouds have an 'index' view, accessible through
> /manage/cloud//. I don't think any implementation implements
> this page so this is currently just a title, and it doesn't have any
> sidebar.
>
> I think it would be more consistent to have :
> - at the top, a button to add a new cloud, next to the button "new node"
> - this needs a new screen to add a new cloud, similar to how we declare a
> new node
> - have a list of clouds directly in the "Manage nodes and clouds" screen,
> with clickable name and configure link
> - a more complete index screen for individual clouds. Sidebar would
> include a link to configure, and the main page would include the current
> 'computerSet' view. Sidebar could include additional actions contributed
> from plugins going forward.
> - a configure screen for an individual cloud
> - remove the "Configure clouds" link, since now clouds would be
> configurable individually.
>
> Cheers,
>
> Vincent
>
> --
> 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-zGCi7efXHgj59TMQbCamN7x03yzysL45tj4Z%3DZ5tC1%3DgAew%40mail.gmail.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3Biek-sjMX_1dD7cuX_6rd3zwbpsswP-Ycw6bu-riPbwdNg%40mail.gmail.com.

2.375.3 release lead

[Tim Jacomb]

Hello

Is anyone interested in being the release lead for 2.375.3?

Planned dates can be seen on the event calendar:
https://www.jenkins.io/events/#event-calendar
Release candidate by 25th January
Release on 8th February

The documentation is at:
https://github.com/jenkins-infra/release/blob/master/.github/ISSUE_TEMPLATE/1-lts-release-checklist.md

I'll be available to answer any questions and provide guidance (along with
hopefully other past release leads)

We chat in #jenkins-release on libera IRC,
https://www.jenkins.io/chat/#jenkins-release or on the bridged matrix
channel.

Anyone interested?

Thanks
Tim

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3BicL-NbYrWzoYV2YXG8oKSbNmUi2h5Rww0sWaNPP%3Dq_jZA%40mail.gmail.com.

Re: Migration to Java11 and modules

[Tim Jacomb]

I'm not aware of hitting any modules issues, this is the normal pull
request that has been applied:
https://github.com/jenkinsci/support-core-plugin/pull/421

at a guess 30+ plugins with no issues, likely more.

On Tue, 3 Jan 2023 at 13:08, Ullrich Hafner 
wrote:

> I’m currently starting the Java 11 migration of my plugins and my local
> builds are failing due to several Java modules failures (package x.y.z is
> declared in the unnamed module, but a.b.c does not use it,  error: module
> not found: x.y.z).
>
> Do we already have some guidelines on how to migrate a plugin to Java 11?
> Do we need to create module-info.java files for plugins? How do we access
> libraries that use modules? Or has someone already finished the the
> migration so I can have a look at the necessary steps?
>
>
>
> --
> 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/B889703A-0666-413D-A413-CEE697B9E36B%40gmail.com
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3BidUfpZmrXYL66xc4B1ZTTbH8WwvK4VwQ4q5cNaWb2NCdg%40mail.gmail.com.

2.375.2 release lead

[Tim Jacomb]

Hello

Is anyone interested in being the release lead for 2.375.2?

Planned dates can be seen on the event calendar:
https://www.jenkins.io/events/#event-calendar
Release candidate by 14th December
Release on 11th January

The documentation is at:
https://github.com/jenkins-infra/release
/blob/master/.github/ISSUE_TEMPLATE/1-lts-release-checklist.md

I'll be available to answer any questions and provide guidance (along with
hopefully other past release leads)

We chat in #jenkins-release on libera IRC,
https://www.jenkins.io/chat/#jenkins-release or on the bridged matrix
channel.

Anyone interested?

(apologies for the short notice)

Thanks
Tim

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3BieROUYLECxOGUsCySnYg7m%3DLac%3DTEozo-Za4JfzRTOF4g%40mail.gmail.com.

Re: Revert of breadcrumb bar accessibility change

[Tim Jacomb]

Jan has offered a partial reversion instead of a full one
https://github.com/jenkinsci/jenkins/pull/6912#issuecomment-1331319966

I think that would be more appropriate here given the issue is only with
one particular part of it

On Fri, 9 Dec 2022 at 16:05, 'wfoll...@cloudbees.com' via Jenkins
Developers  wrote:

> Thanks Basil for the message (I especially liked the references).
>
> I can only +1 your proposal as I was thinking about that in
> https://github.com/jenkinsci/jenkins/pull/6912#issuecomment-1331141923.
> Compared to you, I didn't take the time to move the idea further, thanks
> for the effort.
>
> The change itself is good, it's more about the number of related issues
> that could be adjusted before, i.e. just a matter of time.
>
>
> On Friday, December 9, 2022 at 8:01:16 AM UTC-8 m...@basilcrow.com wrote:
>
>> The Jenkins core maintainers aspire to deliver First Customer Ship (FCS)
>>  quality all the time on
>> the main branch . The
>> integration of jenkinsci/jenkins#6912
>>  has destabilized the
>> main branch, resulting in approximately a dozen pull requests to correct
>> issues with the initial integration. When the main branch is not in a
>> stable state, new problems are far more likely to be introduced, a timeless
>> phenomenon described by Jeff Bonwick as the Quality Death Spiral
>> . The overall quality of the
>> delivered software, not any one project, is what matters; therefore, I am
>> proposing a revert of jenkinsci/jenkins#6912
>> .
>>
>> There is past precedent for this: when the Jetty 10 upgrade was
>> integrated, it destabilized the main branch. It was quickly reverted, then
>> reintegrated later when all known issues had been addressed. The revert of
>> jenkinsci/jenkins#6912 
>> is also intended to be temporary: once the issues caused by the original
>> change are addressed (including JENKINS-70169
>>  and
>> jenkinsci/design-library-plugin#182
>> ), we
>> fully hope and expect for it to be reintegrated and delivered in its final
>> form.
>>
> --
> 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/8a1ad83d-9216-468e-9f10-a1d2aeb72d14n%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-3Bifoc8s%2BCcSC-eTh4ocuecsHrYgo-bV17R2c%3DL3Go9VFqQ%40mail.gmail.com.

Re: JDK19 is now available on ci.jenkins.io

[Tim Jacomb]

I would prefer not to have that, UI will be weird and confusing I think.
Interested maintainers can opt-in

On Fri, 9 Dec 2022 at 07:57, 'Stephane Merle' via Jenkins Developers <
jenkinsci-dev@googlegroups.com> wrote:

> We were thinking of renaming jdk19 to jdk-edge and have this version
> following all new jdk versions almost automatically. And in the same time,
> modifying the buildpluging to build on this one too but without failing ...
> just informative (except if a specific flag is set to true, like
> failonedge: true for example).
> That way seems interesting for developers to see how there plugin behave
> also on the last jdk (not lts).
>
> What do you think?
>
>
> On Thu, Dec 8, 2022 at 10:15 PM Basil Crow  wrote:
>
>> What Tim said. I am not the biggest fan of an edge label either as
>> this goes against the principle of reproducible builds. The Java 19
>> agent label can be deprecated in the agent documentation when Java 20
>> is released (which is minimal effort on the operational side). In
>> general consumers of non-LTS versions of Java should realize that by
>> signing up to consume a non-LTS version they will need to soon move to
>> the next non-LTS version soon or else risk being out of luck when
>> upstream drops support for that non-LTS version.
>>
>> --
>> 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/CAFwNDjpYJKTE%3D-zZT3uUfDV2_vsEf40AUs9TaC2JG6D%2BSd40MA%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/CAO%2B-N1p9AqH8htOFCfHwaxKoWaFS475vkqNz_Dyeq7%3DF8u4G6Q%40mail.gmail.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3BidZJ%3D_7sR4rodLvwDsAuT-D6X1qLBR5aR6bDHwSoh%3Dj-A%40mail.gmail.com.

Re: JDK19 is now available on ci.jenkins.io

[Tim Jacomb]

Personally I'm not the biggest fan of edge I'd rather get a clear error
that the Java version has been removed or a deprecation error in my build
than the Java versions has been randomly changed to another major version.

I think that we would want a deprecation period after 20 is out (and maybe
some batch automated PRs to update consumers as they should be easily
searchable), then removing 19, i.e. not keeping a non LTS version forever.


On Thu, 8 Dec 2022 at 19:52, 'wfoll...@cloudbees.com' via Jenkins
Developers  wrote:

> +1 for the edge approach, to not create "superficial" tech debt
>
> On Thursday, December 8, 2022 at 8:34:12 AM UTC-8 slide wrote:
>
>> I think the edge idea is a good one. This reduces the churn on
>> Jenkinsfile changes to support building on the latest. It would be nice if
>> we, as plugin developers, could opt in to failures on the edge or not,
>> meaning that a build failure on the latest jdk would not cause the build to
>> fail, unless an option was set to true.
>>
>> On Thu, Dec 8, 2022 at 9:18 AM Damien Duportal 
>> wrote:
>>
>>> > Given this is the first time (I think) that a non-LTS JDK is provided,
>>> what are the plans around supporting this?
>>>
>>> We did not have any plan as we did not thought that much. Interesting
>>> point!
>>>
>>> > Will it be removed once JDK 20 exists?
>>>
>>> I guess yes. That would break pipelines using JDK19 though. Would that
>>> make sense to provide a support policy in the infra that would explain we
>>> follow the JDK lifecycles?
>>>
>>> Also, would that make sense to, instead, provide a "jdk-edge" that would
>>> be always the latest non LTS JDK instead (intermediate status: if there are
>>> no version AND it's name edge, we make it explicit that it could break at
>>> any time)?
>>> Le jeudi 8 décembre 2022 à 17:09:34 UTC+1, db...@cloudbees.com a écrit :
>>>
 On Thu, Dec 8, 2022 at 11:02 AM 'Stephane Merle' via Jenkins Developers
  wrote:

> Hello dear developers,
>
> I’m happy to announce that in order to allow contributors to prepare
> the future of Jenkins by working in advance with new JDK, we’ve added 
> JDK19
> on ci.jenkins.io.
>

 Given this is the first time (I think) that a non-LTS JDK is provided,
 what are the plans around supporting this? Will it be removed once JDK 20
 exists? Once JDK 21 (next LTS) exists? Will it be supported indefinitely?

>>> --
>>> 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/ba7929ca-ae1e-4619-a31b-4b01be0068a3n%40googlegroups.com
>>> 
>>> .
>>>
>>
>>
>> --
>> Website: http://earl-of-code.com
>>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/091d8d5b-8164-420c-b5fc-b6b86583bf2en%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-3BidX2WwL1v5GFmGLhKrmq1iMMG1%3DmT6o6LFN4TS-3mLppQ%40mail.gmail.com.

Re: Next baseline shift

[Tim Jacomb]

 +1 to any time after 2.375.1

On 28 Nov 2022 at 22:38:58, Basil Crow  wrote:

> On Mon, Nov 28, 2022 at 1:30 PM 'Jesse Glick' via Jenkins Developers
>  wrote:
>
> Not really any of those […] I was soliciting opinions on whether it
> sounded desirable and safe enough to try
>
>
> And I was pointing out that it is of more practical value to discuss
> designs alongside concrete implementation plans rather than to merely
> discuss designs in the abstract. In any case, I think it is desirable
> and safe enough to try, and I am not going to try it. I would prefer
> to focus this discussion on things that people are willing to commit
> to implementing.
>
> --
> 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/CAFwNDjr4RgMeyj91qqrmEK3Nfg-LqufRgCP49HAutXVpQLrbaw%40mail.gmail.com
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3Bieczm9df2DrUjXVXWua6_1o-qQXmx-qfhdPBgo%3Ddy%3D05Q%40mail.gmail.com.

Re: End of year holidays and Jenkins 2.375.2 release schedule

[Tim Jacomb]

Is there an issue with what’s already in the calendar?

On Tue, 22 Nov 2022 at 16:32, 'wfoll...@cloudbees.com' via Jenkins
Developers  wrote:

> For the delay of the LTS realease, with pleasure! :-)
>
> For the RC, no opinion.
>
> On Tuesday, November 22, 2022 at 3:53:47 PM UTC+1 Mark Waite wrote:
>
>> In the past few years, we've  taken a break from our regular LTS schedule
>> over the holiday season.  I propose we take a break this year, though with
>> a variation from past years.
>>
>> The 2.375.1 LTS release is scheduled for Nov 30.  Four weeks after that
>> would be Dec 28.  I propose that we move the 2.375.2 release candidate date
>> one week to Dec 21 and then delay the 2.375.2 LTS release by two weeks
>> until Jan 11, 2023.
>>
>> I propose that release dates continue on a 4 week cadence after the Jan
>> 11, 2023 release, so the dates would be:
>>
>>- Nov 30, 2022 - Jenkins 2.375.1 release
>>- Dec 21, 2022 - Jenkins 2.375.2 release candidate
>>- Jan 11, 2023 - Jenkins 2.375.2 release
>>- Jan 25, 2023 - Jenkins 2.375.3 release candidate
>>- Feb 8, 2023 - Jenkins 2.375.3 release
>>
>> Comments and discussion are welcomed.
>>
>> 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/633d0536-bbde-4a07-9d28-deb88afd0e8bn%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-3Bie%2BiDtXpXQujMtAFYnxrQq1OCxF188T_N5EvxaszE1Fsg%40mail.gmail.com.

2.375.1 release lead

[Tim Jacomb]

Hello

Is anyone interested in being the release lead for 2.375.1?

Planned dates can be seen on the event calendar:
https://www.jenkins.io/events/#event-calendar
Release candidate by 16th November
Release on 30th November

The documentation is at:
https://github.com/jenkins-infra/release/blob/master/.github/ISSUE_TEMPLATE/1-lts-release-checklist.md

I'll be available to answer any questions and provide guidance (along with
hopefully other past release leads)

We chat in #jenkins-release on libera IRC,
https://www.jenkins.io/chat/#jenkins-release or on the bridged matrix
channel.

Anyone interested?

Thanks
Tim

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3BidYW_C1q9xPjBFaAO21VvKaXsrPDxN4wgkGiFP1f%3DF6oA%40mail.gmail.com.

Re: Next LTS baseline selection

[Tim Jacomb]

Hi all

2.375 is selected as the next baseline.

Thanks
Tim

On Mon, 31 Oct 2022 at 21:18, Tim Jacomb  wrote:

> https://issues.jenkins.io/browse/JENKINS-69966 is very much a real issue,
> but it has a fix on the plugin so I wouldn't worry too much about it.
>
> 2.375 looks to be a good baseline to me.
>
> On Fri, 28 Oct 2022 at 14:21, Alexander Brandes 
> wrote:
>
>> As an alternative to 2.375, I'd like to bring up 2.372 as a possible
>> candidate. 2.375 ships a (possible) issue tracked in JENKINS-69966
>> <https://issues.jenkins.io/browse/JENKINS-69966>.
>> 2.372 <https://www.jenkins.io/changelog/#v2.372> is a much less recent
>> weekly release, with a better rating than 2.375 and less big changes, which
>> could result in possible regressions. It was released almost a month ago
>> with no community reported issues, according to the changelog.
>>
>> On Tuesday, 25 October 2022 at 17:48:11 UTC+2 m...@basilcrow.com wrote:
>>
>>> On Tue, Oct 25, 2022 at 7:42 AM 'wfoll...@cloudbees.com' via Jenkins
>>> Developers  wrote:
>>> >
>>> > To ease this kind of discussion, it could be interesting to introduce
>>> only very minor features or bug fixes before the LTS selection, so that we
>>> have more time to test them. But it's a different topic :p
>>>
>>> FTR there is something written about this at
>>>
>>> https://github.com/jenkinsci/jenkins/blob/e7df5eb5285ec965621a02d589f2543d09885723/docs/MAINTAINERS.adoc#step-2-is-it-a-good-time-to-merge
>>> although it refers more to security releases than creating a new
>>> stable branch. But yes I personally would not have merged the
>>> abovementioned three frontend changes so close to the branching date.
>>> If any issues are discovered in the next week, we can revert the
>>> relevant commits from the stable branch, or create the stable branch
>>> from an earlier point and backport the bug fixes to it like you
>>> mentioned.
>>>
>> --
>> 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/3bda553b-1102-490d-8d54-fe0d9bf3be2an%40googlegroups.com
>> <https://groups.google.com/d/msgid/jenkinsci-dev/3bda553b-1102-490d-8d54-fe0d9bf3be2an%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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3BicRBTV10yOP%3DX%2BwzQoGtCcLixmhqd16d7CQK8O2Fw4GFA%40mail.gmail.com.

Re: Next LTS baseline selection

[Tim Jacomb]

https://issues.jenkins.io/browse/JENKINS-69966 is very much a real issue,
but it has a fix on the plugin so I wouldn't worry too much about it.

2.375 looks to be a good baseline to me.

On Fri, 28 Oct 2022 at 14:21, Alexander Brandes 
wrote:

> As an alternative to 2.375, I'd like to bring up 2.372 as a possible
> candidate. 2.375 ships a (possible) issue tracked in JENKINS-69966
> .
> 2.372  is a much less recent
> weekly release, with a better rating than 2.375 and less big changes, which
> could result in possible regressions. It was released almost a month ago
> with no community reported issues, according to the changelog.
>
> On Tuesday, 25 October 2022 at 17:48:11 UTC+2 m...@basilcrow.com wrote:
>
>> On Tue, Oct 25, 2022 at 7:42 AM 'wfoll...@cloudbees.com' via Jenkins
>> Developers  wrote:
>> >
>> > To ease this kind of discussion, it could be interesting to introduce
>> only very minor features or bug fixes before the LTS selection, so that we
>> have more time to test them. But it's a different topic :p
>>
>> FTR there is something written about this at
>>
>> https://github.com/jenkinsci/jenkins/blob/e7df5eb5285ec965621a02d589f2543d09885723/docs/MAINTAINERS.adoc#step-2-is-it-a-good-time-to-merge
>> although it refers more to security releases than creating a new
>> stable branch. But yes I personally would not have merged the
>> abovementioned three frontend changes so close to the branching date.
>> If any issues are discovered in the next week, we can revert the
>> relevant commits from the stable branch, or create the stable branch
>> from an earlier point and backport the bug fixes to it like you
>> mentioned.
>>
> --
> 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/3bda553b-1102-490d-8d54-fe0d9bf3be2an%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-3BidzMEMRBypemBsLwUqZmbEhy%2BAjDcB2SKj3ebQRiXTXrw%40mail.gmail.com.

Re: Hosting

[Tim Jacomb]

Always room for more :)

On Thu, 27 Oct 2022 at 15:11, Adrien Lecharpentier <
adrien.lecharpent...@gmail.com> wrote:

> I would also be happy to help on the hosting process.
> Is there any room for me to help?
>
> Le dim. 9 oct. 2022 à 20:11, 'Herve Le Meur' via Jenkins Developers <
> jenkinsci-dev@googlegroups.com> a écrit :
>
>> Wiling to help too :)
>> I'll take care of your request tomorrow morning NotMyFault.
>>
>> Le dim. 9 oct. 2022, 20:01, Alexander Brandes  a
>> écrit :
>>
>>> Submitted https://github.com/jenkins-infra/helpdesk/issues/3163
>>>
>>> On Sunday, 9 October 2022 at 19:49:03 UTC+2 ga...@gavinmogan.com wrote:
>>>
>>>> I think you'll have to request via helpdesk permissions for
>>>> https://github.com/orgs/jenkins-infra/teams/hosting/members
>>>>
>>>> On Sun, Oct 9, 2022 at 9:07 AM Alexander Brandes 
>>>> wrote:
>>>>
>>>>> Hey,
>>>>>
>>>>> I'd be up to assist with handling the RPU too.
>>>>>
>>>>> Best regards,
>>>>> Alex
>>>>>
>>>>> On Sunday, 9 October 2022 at 17:53:13 UTC+2 slide wrote:
>>>>>
>>>>>> I can help with that. I know the process is different from when I was
>>>>>> doing it before, but I can come up to speed.
>>>>>>
>>>>>> On Sat, Oct 8, 2022, 21:11 'Gavin Mogan' via Jenkins Developers <
>>>>>> jenkin...@googlegroups.com> wrote:
>>>>>>
>>>>>>> I'm looking for someone interested in replacing me. Right now it
>>>>>>> seems to just be tim and myself. Tim's been amazing and processing all 
>>>>>>> the
>>>>>>> new plugin requests. Wrote tooling to help verify things, etc. He's 
>>>>>>> already
>>>>>>> doing a ton of other things, so I've been trying to help out with the
>>>>>>> maintainer change request approvals, but the process is so fuzzy its 
>>>>>>> just
>>>>>>> draining me, which dumps more on him.
>>>>>>>
>>>>>>> The job entails monitoring PRs on
>>>>>>> https://github.com/jenkins-infra/repository-permissions-updater
>>>>>>> Making sure the request is either approved from an existing
>>>>>>> maintainer, the plugin is labeled adopt this plugin, or the takeover
>>>>>>> process has been followed.
>>>>>>>
>>>>>>> Gavin
>>>>>>>
>>>>>>> On Thu, Aug 26, 2021 at 2:24 AM Baptiste Mathus 
>>>>>>> wrote:
>>>>>>>
>>>>>>>> I am ready to help again on hosting.
>>>>>>>>
>>>>>>>> Similar to how Gavin phrased it, I'll help move tickets through the
>>>>>>>> pipe.
>>>>>>>>
>>>>>>>> Cheers
>>>>>>>>
>>>>>>>> Le jeu. 26 août 2021 à 08:23, Tim Jacomb  a
>>>>>>>> écrit :
>>>>>>>>
>>>>>>>>> You can just click leave team
>>>>>>>>>
>>>>>>>>> On Wed, 25 Aug 2021 at 22:33, Slide  wrote:
>>>>>>>>>
>>>>>>>>>> I should probably be removed from that team as well.
>>>>>>>>>>
>>>>>>>>>> On Wed, Aug 25, 2021 at 1:18 PM Tim Jacomb 
>>>>>>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>>> Oleg has permissions on the team or Olivier:
>>>>>>>>>>> https://github.com/orgs/jenkins-infra/teams/hosting/members
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On Wed, 25 Aug 2021 at 21:03, Slide  wrote:
>>>>>>>>>>>
>>>>>>>>>>>> Those are the basics, just the bot checker (jenkins-admin:
>>>>>>>>>>>> check HOSTING-) in the jenkins-hosting channel.
>>>>>>>>>>>>
>>>>>>>>>>>> On Wed, Aug 25, 2021 at 12:20 PM 'Gavin Mogan' via Jenkins
>>>>>>>>>>>> Developers  wrote:
>>>>>>>>>>>>
>>>>>&g

Re: Proposal: Alexander Brandes (@NotMyFault) to join the Core team

[Tim Jacomb]

Thanks all, I’ve added Alex to the core team now

Welcome aboard

On Wed, 19 Oct 2022 at 20:35, Alexander Brandes 
wrote:

> Hey,
>
> thanks for the thoroughly positive feedback and approval, I submitted a
> request to join the team on GitHub:
> https://github.com/orgs/jenkinsci/teams/core (I am the pending one :P)
>
> Best regards,
> Alex
>
> On Tuesday, 18 October 2022 at 19:45:15 UTC+2 damien@gmail.com wrote:
>
>> +1
>>
>> Alex involvement on the project speaks for itself!
>>
>> Le lundi 17 octobre 2022 à 19:33:09 UTC+2, ga...@gavinmogan.com a écrit :
>>
>>> Nobody on the governance meeting was against it
>>>
>>> On Mon, Oct 17, 2022 at 10:14 AM Oleg Nenashev 
>>> wrote:
>>>
>>>> +1, thanks for all contributions @NotMyFault!
>>>>
>>>> P.S: On behalf of the exclusive weekly release trainwreck club, please
>>>> make sure to tweet "Not my fault" the first time you break the weekly
>>>> release :P
>>>>
>>>>
>>>> On Saturday, October 15, 2022 at 7:58:15 PM UTC+2
>>>> adrien.lec...@gmail.com wrote:
>>>>
>>>>> of course +1.
>>>>>
>>>>>
>>>>> Le sam. 15 oct. 2022 à 18:31, Alexander Brandes 
>>>>> a écrit :
>>>>>
>>>>>> Thanks everyone, I'd be very happy to join the core team :)
>>>>>>
>>>>>> On Friday, 14 October 2022 at 13:48:48 UTC+2 hle...@cloudbees.com
>>>>>> wrote:
>>>>>>
>>>>>>> +1
>>>>>>>
>>>>>>> On Fri, Oct 14, 2022 at 1:18 PM James Nord 
>>>>>>> wrote:
>>>>>>>
>>>>>>>> +1
>>>>>>>>
>>>>>>>> On Thu, 13 Oct 2022 at 20:16, Pedro Amaral 
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> +1
>>>>>>>>>
>>>>>>>>> On Thu, Oct 13, 2022 at 10:12 AM 'Kevin Martens' via Jenkins
>>>>>>>>> Developers  wrote:
>>>>>>>>>
>>>>>>>>>> +1 from me too!
>>>>>>>>>>
>>>>>>>>>> On Thu, Oct 13, 2022 at 5:52 AM 'Olblak' via Jenkins Developers <
>>>>>>>>>> jenkin...@googlegroups.com> wrote:
>>>>>>>>>>
>>>>>>>>>>> +1  :)
>>>>>>>>>>>
>>>>>>>>>>> On Thu, Oct 13, 2022, at 11:39 AM, 'Stephane Merle' via Jenkins
>>>>>>>>>>> Developers wrote:
>>>>>>>>>>>
>>>>>>>>>>> +1 for me too
>>>>>>>>>>> good luck Alexander
>>>>>>>>>>>
>>>>>>>>>>> On Thu, Oct 13, 2022 at 9:44 AM 'Daniel Beck' via Jenkins
>>>>>>>>>>> Developers  wrote:
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On Thu, Oct 13, 2022 at 9:11 AM Tim Jacomb 
>>>>>>>>>>> wrote:
>>>>>>>>>>>
>>>>>>>>>>> I would like to propose Alexander Brandes (@NotMyFault
>>>>>>>>>>> <https://github.com/notmyfault>) to join the Jenkins Core team.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> +1
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> 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/CAMo7PtJFQvvfqtNixCGOk34quz7Fm_bu0as_QNOVxX%2BXY5jvwA%40mail.gmail.com
>>>>>>>>>>> <https://groups.google.com/d/msgid/jenkinsci-dev/CAMo7PtJFQvvfqtNixCGOk34quz7Fm_b

Re: ATH broswer supprt

[Tim Jacomb]

I highly doubt it works, fine to remove I think

On Fri, 14 Oct 2022 at 15:43, 'jn...@cloudbees.com' via Jenkins Developers <
jenkinsci-dev@googlegroups.com> wrote:

> Hi all,
>
> Does anyone use the HTMLUnit browser in the jenkins
> acceptance-test-harness suite?
>
> I am doing some cleaning and I know that chrome and firefox are used, but
> looking at the others also.
>
> I think it is safe to nuke InternetExplorer support from orbit, and I
> would be amazed if HTMLUnit actually worked correctly in the ATH - but
> surprises do happen.
>
> /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 jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/ff761284-6811-4bb4-8902-cf7e14dfd4f0n%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-3BieYzupM4hnP-adCY16KhNHsx0fuC0qT4a6MmPKOTPKYJA%40mail.gmail.com.

Proposal: Alexander Brandes (@NotMyFault) to join the Core team

[Tim Jacomb]

Hi

I would like to propose Alexander Brandes (@NotMyFault
) to join the Jenkins Core team.

Contributions:

   - Pull requests (108)
   

(in
   jenkinsci/jenkins)
   - Pull requests (644)
   

   (in jenkinsci)
   - Reviews (503)
   

   - Issues reported (88)
   


He has a signed CLA already

.

Thanks
Tim

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3BifnH3YDdPinO2JAQP6cJcGO0r2VMU1j645pzypHXx1y0A%40mail.gmail.com.

2.361.3 release lead

[Tim Jacomb]

Hello

Is anyone interested in being the release lead for 2.361.3?

Planned dates can be seen on the event calendar:
https://www.jenkins.io/events/#event-calendar
Release candidate by 19th October
Release on 2nd November

The documentation is at:
https://github.com/jenkins-infra/release
/blob/master/.github/ISSUE_TEMPLATE/1-lts-release-checklist.md

I'll be available to answer any questions and provide guidance (along with
hopefully other past release leads)

We chat in #jenkins-release on libera IRC,
https://www.jenkins.io/chat/#jenkins-release

Anyone interested?

Thanks
Tim

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3BifE%2Bs_Azixgco2DC%3D3LLC%2Bh2sNXLRyAgCSz_Fg4a%2BkE-g%40mail.gmail.com.

Re: [Adoption] thin-backup-plugin

[Tim Jacomb]

He approved it via GiHub

On Mon, 26 Sep 2022 at 12:31, Oleg Nenashev  wrote:

> +1. Note that there were recent updates by  Thomas Fuerer 16 days ago:
> https://github.com/jenkinsci/thin-backup-plugin/pull/30
> It would be nice to have explicit confirmation from him just in case
>
> On Sunday, September 25, 2022 at 1:40:17 PM UTC+2 Mark Waite wrote:
>
>> I see the "Up for adoption" message in the README at
>> https://github.com/jenkinsci/thin-backup-plugin/blob/master/README.md
>>
>> +1 from me to have Stefan adopt the plugin.  His contributions to Jenkins
>> core have been consistent and have regularly improved Jenkins core.
>>
>> Mark Waite
>>
>> On Sunday, September 25, 2022 at 5:28:23 AM UTC-6 stefan@gmail.com
>> wrote:
>>
>>> Hi,
>>> I would like to adopt a plugin:
>>>
>>>- *Link*: https://github.com/jenkinsci/thin-backup-plugin
>>>- *Pull requests*:
>>>   - https://github.com/jenkinsci/thin-backup-plugin/pull/34
>>>   - https://github.com/jenkinsci/thin-backup-plugin/pull/35
>>>   - https://github.com/jenkinsci/thin-backup-plugin/pull/36
>>>- *Status*: for adoption
>>>- *GitHub Username*: StefanSpieker
>>>- *Jenkins Infrastructure ID*: stefan_spieker
>>>- *Repository Permission Updater PR*:
>>>https://github.com/jenkins-infra/repository-permissions-updater/pull/2818
>>>
>>> I plan to update and modernize the plugin.
>>>
>>> Best regards,
>>> Stefan Spieker
>>>
>> --
> 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/8cb58764-70e3-46f4-89d2-5fea0164289an%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-3BicyNM1zYXZVCkPHj%3Dw83968mDyb8SpGeRNPEYrFgB02mQ%40mail.gmail.com.

Re: pipeline-graph-view-plugin on infra.ci.jenkins.io

[Tim Jacomb]

+1

On Fri, 16 Sep 2022 at 18:01, 'Herve Le Meur' via Jenkins Developers <
jenkinsci-dev@googlegroups.com> wrote:

> Hello,
>
> https://github.com/jenkinsci/pipeline-graph-view-plugin/ has received a
> lot of updates lately, and we would like to install it on
> infra.ci.jenkins.io in order to test it and make feedback.
>
> Any objections?
>
> Regards and great weekend all,
>
> Hervé for the Jenkins Infra Team
>
> --
> 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/CAL-LwjxKhxKeRpXEe0e7vY1xDLAozE21Wocpe2E%3DuvWfcE_GJw%40mail.gmail.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3BifQmw-%2BFyCTNn%3D1Zg4mMyfMk2JV7MjutQ5x6oukqv6Yiw%40mail.gmail.com.

2.361.2 release lead

[Tim Jacomb]

Hello

Is anyone interested in being the release lead for 2.361.2?

Planned dates can be seen on the event calendar:
https://www.jenkins.io/events/#event-calendar
Release candidate by 21st September
Release on 5th October

The documentation is at:
https://github.com/jenkins-infra/release
/blob/master/.github/ISSUE_TEMPLATE/1-lts-release-checklist.md

I'll be available to answer any questions and provide guidance (along with
hopefully other past release leads)

We chat in #jenkins-release on libera IRC,
https://www.jenkins.io/chat/#jenkins-release

Anyone interested?

Thanks
Tim

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3BieSh52u1mwwOLYmNWv7ugYK5Z4SSUvucsoktPUHv9Rm8g%40mail.gmail.com.

Re: ASM in core

[Tim Jacomb]

If core no longer uses it the. Yes absolutely +1

On Thu, 18 Aug 2022 at 05:40, Basil Crow  wrote:

> Recent weeklies no longer consume ASM. So shall we detach it to a
> library plugin?
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CAFwNDjr6H53AJNa9YedKtSUOwNg4B7EayJshWZWW7TC3gucXfw%40mail.gmail.com
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3Bifx-6m9qy1ZWkj8Deh%2BHe1ynGP4ofU6tJufibu8UXsVEA%40mail.gmail.com.

Re: Forked repositories in GitHub

[Tim Jacomb]

It currently still forks although there’s instructions telling people to
delete their repo or raise a support ticket if it gets messed up

On Wed, 17 Aug 2022 at 00:29, 'Gavin Mogan' via Jenkins Developers <
jenkinsci-dev@googlegroups.com> wrote:

> This is a one time operation for all past repos? What happens to all the
> new ones? Is the script pushing a new repo now (I forgot)?
>
> Totally on board with fixing all the old repos, not being able to search
> them kinds sucks.
>
> On Tue, Aug 16, 2022 at 4:05 PM Mark Waite 
> wrote:
>
>> +1 from me
>>
>> On Tue, Aug 16, 2022, 2:32 PM Tim Jacomb  wrote:
>>
>>> GitHub support have offered to make the jenkinsci organisation the root
>>> of all of the fork networks
>>>
>>> See
>>>
>>> https://github.com/jenkins-infra/helpdesk/issues/2272#issuecomment-1216867119
>>>
>>>
>>> Any objections or +1s?
>>>
>>> Thanks
>>> Tim
>>>
>>> On Wed, 4 Aug 2021 at 16:52, Tim Jacomb  wrote:
>>>
>>>> I replied with Daniel's support ticket number (569994)
>>>>
>>>> and got this back:
>>>>
>>>> Hi Tim,
>>>>
>>>> Thanks for your patience here. I checked internally once more and found
>>>> that we can, in fact, do this for you. We've gone ahead and detached the
>>>> repository into its own fork network.
>>>>
>>>> Feel free to reach out if you have any additional questions about this!
>>>>
>>>> On Wed, 28 Jul 2021 at 17:38, Slide  wrote:
>>>>
>>>>> It would be super ideal to do transferring if we could figure out a
>>>>> good process for it, we lose GitHub Issues and some other things when we
>>>>> fork as is.
>>>>>
>>>>> On Wed, Jul 28, 2021 at 8:33 AM Tim Jacomb 
>>>>> wrote:
>>>>>
>>>>>> Wouldn't creating a repo and pushing the code instead of forking work
>>>>>> during the hosting process?
>>>>>>
>>>>>>
>>>>>> On Wed, 28 Jul 2021 at 15:02, Jesse Glick 
>>>>>> wrote:
>>>>>>
>>>>>>> On Wed, Jul 28, 2021 at 2:48 AM timja...@gmail.com <
>>>>>>> timjaco...@gmail.com> wrote:
>>>>>>>
>>>>>>>> Seem's like GitHub won't break the fork relationship anymore
>>>>>>>> without both sides agreeing to it?
>>>>>>>>
>>>>>>>
>>>>>>> This could be a real problem for us. We still have a bunch of repos
>>>>>>> with misleading fork status, like
>>>>>>> https://github.com/jenkinsci/plugin-pom rather prominently. There
>>>>>>> should be some provision by which a “fork” which has way more activity 
>>>>>>> than
>>>>>>> the “origin” can unilaterally break the relationship. Of course you can
>>>>>>> delete and recreate the repo with Git history intact but you will lose 
>>>>>>> all
>>>>>>> PR history, which is intolerable.
>>>>>>>
>>>>>>> --
>>>>>>> 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/SkKoCccPrOc/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/CANfRfr1XZbUvJER_5-LMFd8i1d1RTaFy6JPLhwq9pG9uLE_ZVg%40mail.gmail.com
>>>>>>> <https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr1XZbUvJER_5-LMFd8i1d1RTaFy6JPLhwq9pG9uLE_ZVg%40mail.gmail.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.
>>>>>> T

Re: Forked repositories in GitHub

[Tim Jacomb]

GitHub support have offered to make the jenkinsci organisation the root of
all of the fork networks

See
https://github.com/jenkins-infra/helpdesk/issues/2272#issuecomment-1216867119


Any objections or +1s?

Thanks
Tim

On Wed, 4 Aug 2021 at 16:52, Tim Jacomb  wrote:

> I replied with Daniel's support ticket number (569994)
>
> and got this back:
>
> Hi Tim,
>
> Thanks for your patience here. I checked internally once more and found
> that we can, in fact, do this for you. We've gone ahead and detached the
> repository into its own fork network.
>
> Feel free to reach out if you have any additional questions about this!
>
> On Wed, 28 Jul 2021 at 17:38, Slide  wrote:
>
>> It would be super ideal to do transferring if we could figure out a good
>> process for it, we lose GitHub Issues and some other things when we fork as
>> is.
>>
>> On Wed, Jul 28, 2021 at 8:33 AM Tim Jacomb  wrote:
>>
>>> Wouldn't creating a repo and pushing the code instead of forking work
>>> during the hosting process?
>>>
>>>
>>> On Wed, 28 Jul 2021 at 15:02, Jesse Glick  wrote:
>>>
>>>> On Wed, Jul 28, 2021 at 2:48 AM timja...@gmail.com <
>>>> timjaco...@gmail.com> wrote:
>>>>
>>>>> Seem's like GitHub won't break the fork relationship anymore without
>>>>> both sides agreeing to it?
>>>>>
>>>>
>>>> This could be a real problem for us. We still have a bunch of repos
>>>> with misleading fork status, like
>>>> https://github.com/jenkinsci/plugin-pom rather prominently. There
>>>> should be some provision by which a “fork” which has way more activity than
>>>> the “origin” can unilaterally break the relationship. Of course you can
>>>> delete and recreate the repo with Git history intact but you will lose all
>>>> PR history, which is intolerable.
>>>>
>>>> --
>>>> 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/SkKoCccPrOc/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/CANfRfr1XZbUvJER_5-LMFd8i1d1RTaFy6JPLhwq9pG9uLE_ZVg%40mail.gmail.com
>>>> <https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr1XZbUvJER_5-LMFd8i1d1RTaFy6JPLhwq9pG9uLE_ZVg%40mail.gmail.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.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3Bie4r6MsTyNum4R57DSe3eMO7yNSVt1qbndVZviE%3D57Eug%40mail.gmail.com
>>> <https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3Bie4r6MsTyNum4R57DSe3eMO7yNSVt1qbndVZviE%3D57Eug%40mail.gmail.com?utm_medium=email_source=footer>
>>> .
>>>
>>
>>
>> --
>> Website: http://earl-of-code.com
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Jenkins Developers" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to jenkinsci-dev+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-dev/CAPiUgVf5HMgWmy%2BrQbnTH1p02Ngo9dXfqtR19SG%3DcxR_NLyWxw%40mail.gmail.com
>> <https://groups.google.com/d/msgid/jenkinsci-dev/CAPiUgVf5HMgWmy%2BrQbnTH1p02Ngo9dXfqtR19SG%3DcxR_NLyWxw%40mail.gmail.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3Bid6aSGqdh_JCMjvmANiin4TVbvOnMRLKGbF%2B89uM5iDFg%40mail.gmail.com.

Re: Merging multiple build steps into one (with nested Describables)

[Tim Jacomb]

What version are you building against? I think recent weekly (and the
upcoming LTS) has that help issue fixed

RE: design library and warnings, mind filing an issue for that?

On Sun, 14 Aug 2022 at 17:14, Tim Van Holder 
wrote:

> Hi,
>
> I'm in the process of adjusting a plugin that has a dozen build steps to
> use a single step instead (all steps are subcommands of a single executable
> and/or subcommands of those subcommands). There are two parts to this.
>
> The first is writing the new step/builder. The idea is to use a new
> extension point / describable for each "level" of command. This mostly
> seems to work fine.
> However, I ran into two issues so far:
>
>1. you can use @Symbol to assign a simple symbol to make things like "
>dotnet(buildServer(shutdown())" work; but there seems to be no
>checking that such a symbol is valid/usable, neither at build time nor at
>run time. For example, I had "package" as symbol (for "dotnet list
>package"); it was only when I tried to use it in a pipeline that any
>error occurred (because package is a reserved word). It would
>certainly be useful to get a diagnostic for that at maintenance/build time
>(this assumes Groovy is the only supported/intended context for those
>symbols; otherwise checking for reserved words might be tricky).
>2. I'm using  for the nested
>describables which mostly works nicely. However, this does not surface any
>help files for the selected describable in the UI. Is that a bug or by
>design? I tried adding
>
>
>  
>
>
>to the config.jelly for such a describable, but although that does
>render the question mark icon, it doesn't actually do anything when
>clicked. If it's a bug (or missing feature), what's the appropriate place
>to report it? Otherwise, what's the best way to make it work? Should I copy
>the  dropdownDescriptorSelector jelly and modify that?
>
>
> The second part is dealing with deprecating the "old" build steps.
>
> For free-style projects this was very easy. I just adjusted their
> descriptors to return false from isApplicable(). That hides them from the
> UI for new configuration but leaves existing projects usable. I then added
> a "this step is deprecated" banner to their config.jelly (note: it would be
> really useful if the Jenkins Design Library also documented style elements,
> such as using a div with class="alert alert-warning" for a warning
> banner). Great - clutter removed from the "Add build step" UI.
>
> The only thing that would be additionally useful is an automated migration
> step; I wonder if there's any way I could have a button/link in the
> config.jelly that would allow me to construct the new step based on the old
> step's properties and have the UI take that new step into account for the
> project being edited?
>
> However, these are all Builders implementing SimpleBuildStep to be usable
> from pipelines as well. And there seems to be no way to mark those as "do
> not use". While the snippet generator does have a "deprecated/advanced"
> section, that is entirely based on a StepDescriptor implementing
> isAdvanced() - but these are Builders, so they have no StepDescriptor.
> What are my options for this? I don't think I can just have a second
> descriptor for the same class, moving the @Symbol to that one. So my only
> option would seem to be to essentially create a new set of Steps just so
> they could have descriptors marking themselves as advanced - but that would
> involve the symbols being associated with those new classes; would that
> break anything? The old class would remain a Builder and executable the
> same way, so if the old class name got persisted anywhere (e.g. for a job
> that was suspended), that *should* still work. Or should I just not care
> about clutter in the snippet generator interface at all?
>
> I do still think it would be a useful thing if there was a way to set up a
> builder/step so that the snippet generator hides it in its entirety. This
> could be as easy as calling descriptor.isApplicable, passing in either a
> "fake" AbstractProject implementation (SnippetGeneratorProject or
> something) or by passing in whatever AbstractProject applies to pipeline
> projects.
> Alternatively, perhaps it could move steps to the deprecated/advanced
> section if they are marked @Deprecated? Or is all this just a consequence
> of the steps in question getting run via a meta-step?
>
> --
> 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/CAKMi--C2%3Dhm77jbPZ1zEvVeZ_8ZMXhg8zzW5%2Bkfi2FeYd%2BExfA%40mail.gmail.com
> 

Re: Prettier for formatting supported languages in Jenkins core

[Tim Jacomb]

We have eslint as well to do things like what you said

My preference is for opinionated formatters so we don’t have to worry about
debating options and it does a really good job by just automatically
formatting it, you don’t get red lines in your IDE as you type distracting
you like you do with eslint if you’re using it for formatting, as the
expectation is you run the format before committing

Places where the formatted is doing some we really don’t want can have an
ignore comment added to it

On Sat, 13 Aug 2022 at 05:59, 'Gavin Mogan' via Jenkins Developers <
jenkinsci-dev@googlegroups.com> wrote:

> I know i said I had issues with prettier being opinionated, but my
> issue wasn't the opinions it had, just that it wasn't very flexible.
> My personal projects I usually import one of the opinionated rulesets
> to eslint and have it done, but eslint is infinitely configurable,
> while my experience, at least when I last used it, prettier was
> frustrating to manage. I'm all about tooling being opinionated.
>
> So absolutely not against prettier, just more of a "have you look at
> eslint instead? it also has the ability to keep an eye on other things
> like using undefined variables"
>
> On Tue, Aug 9, 2022 at 3:31 PM Basil Crow  wrote:
> >
> > On Tue, Aug 9, 2022 at 2:46 AM 'wfoll...@cloudbees.com' via Jenkins
> Developers  wrote:
> > >
> > > I think it's the key point about the complaints again Prettier, it's a
> very
> > > opinionated, meaning that it's not about our subjectivity, but reusing
> the
> > > one from its author. There is no truth about what must be done or not
> around
> > > this kind of style, hence the desire to have this discussion, to find a
> > > consensus about the "community subjectivity" instead of relying on
> someone
> > > else['s] opinion.
> >
> > Please read my previous post about this topic if you have not already.
> Ceding control of some subjective preferences to an opinionated tool with
> few (if any) configuration options can be uncomfortable at first, but in my
> experience the benefits outweigh the disadvantages in the long term. These
> benefits include never having to deal with a PR that includes a mix of
> formatting and logic changes (faster code reviews), being able to write
> code more quickly without having to make formatting decisions, and being
> able to read code more easily when it is all written in a consistent style.
> >
> > I have implemented automatic formatting in large organizations many
> times in my career, and in all cases people complained a little at first
> but then grew to like it. I myself disliked some of the opinions of the
> authors of the tools I was putting in place, but putting my own advice into
> practice I decided to set aside my own opinions for the sake of group
> cohesion and the benefits described above.
> >
> > --
> > 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/CAFwNDjpz6ieWaXWQx8coavENczXDTDTkr3ei7dq86Q4XdXZrgw%40mail.gmail.com
> .
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CAG%3D_DuvtX1pat5VdtsoN7QrLa%2BTfbDr%2B8u0DFxpGwP3%2BCQXHqg%40mail.gmail.com
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3Bif%2BmVBMFrUdTecV%2Bb-E7pa5CeNMMjWpWjjg1QWALKVF4w%40mail.gmail.com.

Re: Updating Azure Artifact Manager plugin to use Azure CDN

[Tim Jacomb]

I think you want to change either:
https://github.com/jenkinsci/azure-artifact-manager-plugin/blob/master/src/main/java/com/microsoft/jenkins/artifactmanager/AzureBlobVirtualFile.java#L178-L185

or

https://github.com/jenkinsci/azure-artifact-manager-plugin/blob/7989b9c6a1c504f52ef80a80a5f2c89bccb78c61/src/main/java/com/microsoft/jenkins/artifactmanager/AzureBlobVirtualFile.java#L197

It would help if you sent a branch with that you've tried or at least a
diff.

On Fri, 12 Aug 2022 at 00:38, 'Ian Boudreaux' via Jenkins Developers <
jenkinsci-dev@googlegroups.com> wrote:

> Hi all,
>
> I am trying to update the Azure Artifact manager plugin
>  to be capable of
> using an Azure content delivery network (CDN) link for the produced
> artifacts available through Jenkins instead of the direct Azure blob
> storage links. The reason I am doing this is because downloads from the
> blob storage directly are throttled and downloads from the CDN are
> considerably faster, especially for geographically distributed users.
>
> This is also my first time trying to modify a Jenkins plugin, so I do
> acknowledge a lack of knowledge in general Jenkins plugin development. That
> being said, I've been investigating the Azure Artifact Manager source code
> for a couple days and I've determined this:
>
>1. toExternalURL in the AzureBlobVirtualFile class
>
> ,
>seems to be what determines the final link that users would see in Jenkins
>to click upon that would download the blob artifact from the CDN. I removed
>the "sas" variable from this URL and confirmed that the generated URL in
>Jenkins that a user sees was missing the shared access signature and thus
>inaccessible, so this confirmed it for me.
>2. I also know that, eventually, I would need to update the Azure
>storage plugin  to
>take in a CDN URL through the Jenkins Azure Storage credential, do
>validation on that URL, and then pass that URL into the Azure Artifact
>Manager plugin
>
> That being said, the first problem I am having is finding a way to
> manually change the external URL in the Azure Artifact Manager so that it
> uses the CDN URL instead of the blob storage URL to prove this is possible
> before I dive deeper into the Azure storage plugin and passing the
> credential around.
>
> I've tried modifying the toExternalUrl method in the AzureBlobVirtualFile
> class by replacing the blob storage endpoint URL string with a manually
> input string of my CDN endpoint URL, but no matter what I try (except
> removing the '"sas" variable) I get a NullPointerException when trying to
> change the external URL string to anything other than a string that points
> to the blob storage endpoint URL:
>
>- java.lang.NullPointerException
>   - at
>   
> com.microsoftopentechnologies.windowsazurestorage.helper.AzureStorageAccount.convertToStorageAccountInfo(AzureStorageAccount.java:254)
>   - at
>   
> com.microsoft.jenkins.artifactmanager.Utils.getStorageAccount(Utils.java:90)
>   - at
>   
> com.microsoft.jenkins.artifactmanager.AzureArtifactManager.archive(AzureArtifactManager.java:123)
>   - at
>   hudson.tasks.ArtifactArchiver.perform(ArtifactArchiver.java:258)
>
> Does anyone have any ideas on where to go from here? All I really need to
> do is swap the endpoint URL link at the very end of the artifact archiving
> process so that the artifact link that shows in Jenkins points to the CDN
> URL instead of the blob storage URL.
>
> Thanks!
> Ian
>
> --
> 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/432a78bf-c750-455b-aa5c-d1d01c09f3b9n%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-3Bif_9bp-t6N2Lr_RjD%3Dr-1Vt1JhN7xa5xj_JJFLUBU8eew%40mail.gmail.com.

Re: How to align a checkbox with an optionalBlock vertically?

[Tim Jacomb]

If you share a branch with the code you have that is not working how you
want someone is more likely to be able to help

On Fri, 12 Aug 2022 at 08:05, Nikhil Bhoski  wrote:

> Any input on this would be appreciated. Is it a Bug in Jenkins Jelly
> format that optional block and simple checkbox are not alined vertically in
> UI
>
> Regards
> Nikhil
>
> On Thursday, 11 August 2022 at 13:01:10 UTC+5:30 Nikhil Bhoski wrote:
>
>> I am stuck with same situation , With optional block if checkboxes are
>> used then on UI both these checkboxes are looking non aligned .
>> any solution on this would be appriciated. @shih let me know how did you
>> handle this.
>>
>> Regards
>> Nikhil
>>
>>
>>
>> On Thursday, 31 January 2019 at 13:06:10 UTC+5:30 shih...@gmail.com
>> wrote:
>>
>>> Hi all,
>>>
>>> I want to align a checkbox with an optionalBlock vertically. How can I
>>> do it? Does jenkins support styles?
>>>
>>> [image: 123.png]
>>>
>>> --
> 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/af1e9d99-352e-4fb6-8fda-79812feba6e8n%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-3Bifb-7soEMX9%2B3MxO8_mXXM_JeUEsD2Fqm_OFX9mekU1LA%40mail.gmail.com.

Prettier for formatting supported languages in Jenkins core

[Tim Jacomb]

Hi all

Looking for any feedback on the proposal of using prettier for formatting
Jenkins core with the supported languages:

   - JavaScript
   - CSS
   - HTML
   - Markdown
   - Yaml

See:
https://github.com/jenkinsci/jenkins/pull/6863

Thanks
Tim

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3Biek97wctPi3CnAR-LE8su9msz5GuwN2x6PyRSO3UkSyhg%40mail.gmail.com.

Re: 2.361.1 release lead

[Tim Jacomb]

Hi Kris

Thanks for your interest, if you can create an issue at
https://github.com/jenkins-infra/release/issues/new?assignees==lts-checklist=1-lts-release-checklist.md
We'll be able to help you.

Cheers
Tim

On Fri, 5 Aug 2022 at 10:33, Kris Stern  wrote:

> Hi Tim,
>
> I am interested, even though I have never done it before. But I might need
> extra help in getting started though.
>
> Best,
> Kris
> --
> *From:* jenkinsci-dev@googlegroups.com 
> on behalf of Tim Jacomb 
> *Sent:* 05 August 2022 17:25
> *To:* Jenkins Developers 
> *Subject:* 2.361.1 release lead
>
> Hello
>
> Is anyone interested in being the release lead for 2.361.1?
>
> Planned dates can be seen on the event calendar:
> https://www.jenkins.io/events/#event-calendar
> <https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.jenkins.io%2Fevents%2F%23event-calendar=05%7C01%7C%7Ce4aaf501b4b8489ae31508da76c484eb%7C84df9e7fe9f640afb435%7C1%7C0%7C637952883668917266%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=H7N0pBDi1dtFK3Bi4jwf07uxZmanvkrlcYFFpF7YCj4%3D=0>
> Release candidate by 24th August
> Release on 7th September
>
> The documentation is at:
> https://github.com/jenkins-infra/release
> /blob/master/.github/ISSUE_TEMPLATE/1-lts-release-checklist.md
> <https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fjenkins-infra%2Frelease%2Fblob%2Fmaster%2F.github%2FISSUE_TEMPLATE%2F1-lts-release-checklist.md=05%7C01%7C%7Ce4aaf501b4b8489ae31508da76c484eb%7C84df9e7fe9f640afb435%7C1%7C0%7C637952883668917266%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=r6qTTtgnKkY6rfJvubRqmEGnO3TUmLlyWLbwePHASm0%3D=0>
>
> I'll be available to answer any questions and provide guidance (along with
> hopefully other past release leads)
>
> We chat in #jenkins-release on libera IRC,
> https://www.jenkins.io/chat/#jenkins-release
> <https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.jenkins.io%2Fchat%2F%23jenkins-release=05%7C01%7C%7Ce4aaf501b4b8489ae31508da76c484eb%7C84df9e7fe9f640afb435%7C1%7C0%7C637952883668917266%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=VWj%2BEMX4GnKcpciu3VzBaF7QYgaN3K5e1kNADkKDLe8%3D=0>
>
> Anyone interested?
>
> Thanks
> Tim
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3BieaaK9Pfv43XxtsCpiSx-3JAPRSO%2Bt52NBODYZ2dWNVDA%40mail.gmail.com
> <https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgroups.google.com%2Fd%2Fmsgid%2Fjenkinsci-dev%2FCAH-3BieaaK9Pfv43XxtsCpiSx-3JAPRSO%252Bt52NBODYZ2dWNVDA%2540mail.gmail.com%3Futm_medium%3Demail%26utm_source%3Dfooter=05%7C01%7C%7Ce4aaf501b4b8489ae31508da76c484eb%7C84df9e7fe9f640afb435%7C1%7C0%7C637952883668917266%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=fAnrtoQhu79fX6kqhRyp7uCubhNKc1FKwDZIL%2BJTquo%3D=0>
> .
>
> --
> 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/OS3P286MB14312B27FF35A6F70FD21370A19E9%40OS3P286MB1431.JPNP286.PROD.OUTLOOK.COM
> <https://groups.google.com/d/msgid/jenkinsci-dev/OS3P286MB14312B27FF35A6F70FD21370A19E9%40OS3P286MB1431.JPNP286.PROD.OUTLOOK.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3Bid7eHapLZ0vtKiX3avY8aunFxi5gDrojpOJf16V59FEdg%40mail.gmail.com.

2.361.1 release lead

[Tim Jacomb]

Hello

Is anyone interested in being the release lead for 2.361.1?

Planned dates can be seen on the event calendar:
https://www.jenkins.io/events/#event-calendar
Release candidate by 24th August
Release on 7th September

The documentation is at:
https://github.com/jenkins-infra/release
/blob/master/.github/ISSUE_TEMPLATE/1-lts-release-checklist.md

I'll be available to answer any questions and provide guidance (along with
hopefully other past release leads)

We chat in #jenkins-release on libera IRC,
https://www.jenkins.io/chat/#jenkins-release

Anyone interested?

Thanks
Tim

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3BieaaK9Pfv43XxtsCpiSx-3JAPRSO%2Bt52NBODYZ2dWNVDA%40mail.gmail.com.

Re: Next LTS baseline

[Tim Jacomb]

Hello

2.361 has been selected as the next baseline

Thanks
Tim

On Tue, 2 Aug 2022 at 23:43, Olivier Lamy  wrote:

> As explained in the PR there are no real security issues but some
> companies using scanners may have to live a long time with alarms etc...
> And they don't have any "safe" (by "safe" I mean CVEs free :))  solution
> to upgrade before the version with Jetty 10.0.11 land into LTS (and I do
> not mention companies who are not ready yet to upgrade to java 11)
> anyway no big drama here I was just thinking as solution to help
> users/companies with strict restrictions.
> This may not happen and we cannot support old versions forever but as long
> as we have a LTS with java 8 there can be some need for it.
>
> On Wed, 3 Aug 2022 at 08:17, Basil Crow  wrote:
>
>> Are we talking about the version of Jetty to be shipped in 2.346.3 or
>> the version of Jetty to be shipped in 2.361.1?
>>
>> 2.361.1 is far enough away that I would be in favor of a backport of
>> Jetty 10.0.11, once it has been in the weekly release for a week or
>> two without serious regressions. This would not require us to make any
>> exception to the usual rules.
>>
>> For 2.346.3 I am not sure there is a need to do any Jetty backporting,
>> but I would be willing to discuss it if there was a need.
>>
>> --
>> 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/CAFwNDjpcek4uaLV3WqGV%2Bgt5ncvJdXyT9ZwfNCA-P152OtqkSg%40mail.gmail.com
>> .
>>
>
>
> --
> Olivier Lamy
> http://twitter.com/olamy | http://linkedin.com/in/olamy
>
> --
> 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/CAPoyBqQ%3DRDT3ot0MaRFJW%2BMWSs54vnphj6SS_J73RhhQ4iyH_Q%40mail.gmail.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3BifZ4i65SNZj%2B0N%2B78pokLF%3DD_2uV0ATtKP4y3jKy7u1Sg%40mail.gmail.com.

Re: Next LTS baseline

[Tim Jacomb]

(as mentioned on the PR)

My concern with backporting the Jetty changes is that this PR will never go
to weekly as weekly is now on Jetty 10.
But if we don't backport it, that would mean security scanners complaining
about a new LTS line which isn't ideal...

On Tue, 2 Aug 2022 at 22:06, Olivier Lamy  wrote:

> Hi
> If LTS will be 2.361 it would be good to have winstone upgrade in.
> https://github.com/jenkinsci/jenkins/pull/6955
> it will avoid all security scanners to complain with false alarms on the
> Jetty versions.
>
> On Sat, 30 Jul 2022 at 06:23, 'Daniel Beck' via Jenkins Developers <
> jenkinsci-dev@googlegroups.com> wrote:
>
>>
>>
>> On Fri, Jul 29, 2022 at 7:53 PM Alexander Brandes 
>> wrote:+1 for 2.361
>>
>>>
>>> It's worth to mention that 2.361 contains several regression fixes too,
>>> which you don't want to miss out.
>>>
>>
>> They could always be backported into 2.360.x. So the question to ask is,
>> do we want everything in 2.361?
>>
>> FWIW I think 2.361 looks reasonable, all bad feedback is about a plugin
>> that isn't even bundled, and the changes look reasonable enough.
>>
>> --
>> 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/CAMo7PtKj6xQzPNc7d3ozpPQC4-03W%3D4ynYCUkVD%3DLyAHF2xO7w%40mail.gmail.com
>> 
>> .
>>
>
>
> --
> Olivier Lamy
> http://twitter.com/olamy | http://linkedin.com/in/olamy
>
> --
> 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/CAPoyBqQXCEMSf0iZ9n6Ymu-KxBHc%2BV%2B0paKSq%2Bouiusj0SSRgA%40mail.gmail.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3Bif8DmJC%3DcJuA%3Da-TuGyQf9UK5woV6Gs%3DBUSaD-2gsNjeQ%40mail.gmail.com.

Re: maven-jellydoc-plugin and maven-stapler-plugin

[Tim Jacomb]

+1

On Thu, 28 Jul 2022 at 23:50, Basil Crow  wrote:

> I would like to request a transfer of
> https://github.com/kohsuke/maven-jellydoc-plugin from the kohsuke
> GitHub organization to the jenkinsci GitHub organization and
> permissions for both that repository and
> https://github.com/jenkinsci/maven-stapler-plugin in order to release
> new versions that are compatible with current Maven APIs. If and when
> a consensus is reached that we would like to proceed with this plan, I
> will reach out to Kohsuke to begin the transfer.
>
> --
> 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/CAFwNDjrRGSbTdSqZuD2VtkJPyELSqYostw4kZQz5tY9_pp9YZg%40mail.gmail.com
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3Bic7ZKRDu4ck7TZQVcAohs9wuMWMBNBbfosuyCyvpc2W0A%40mail.gmail.com.

Re: comment-ops-bot available in jenkinsci and jenkins-infra

[Tim Jacomb]

I think something like this should sort out the concerns of permissive
defaults:
https://github.com/timja/github-comment-ops/pull/56#issuecomment-1193852554

something along the lines of (allowed at org and repo level):

config:
  commands:
- name: transfer
  permission: member
  enabled: true
- name: labels
  permission: member
  allowed_labels: ['enhancement', 'chore', 'bug']
  enabled: true
- name: close
  enabled: false
- name: reopen
  enabled: false



On Mon, 25 Jul 2022 at 12:37, 'Daniel Beck' via Jenkins Developers <
jenkinsci-dev@googlegroups.com> wrote:

>
>
> On Mon, Jul 25, 2022 at 12:20 PM Tim Jacomb  wrote:
>
>> > Can we have review requests enabled by default while label changes are
>> opt in?
>>
>> I'm not sure if that would scale across the number of infrequently
>> touched repositories that we have.
>>
>
> Infrequently touched repos are the problem for overly permissive defaults,
> since it would take forever for someone with a higher level of access to
> notice vandalism and fix it up.
>
> The link does not discuss opt in, just how to define an opt out. That's
> the wrong question to ask.
>
> --
> 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/CAMo7PtJNNvbCzLV%3Df%3DD1q3weXnEDA2pawndK-FNpJhW%2BVofP_w%40mail.gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/CAMo7PtJNNvbCzLV%3Df%3DD1q3weXnEDA2pawndK-FNpJhW%2BVofP_w%40mail.gmail.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3BifuvwQ6cYtixN4X8-3sjxKO3Tb6-XitEVPBUsX7k4PqDQ%40mail.gmail.com.

Re: comment-ops-bot available in jenkinsci and jenkins-infra

[Tim Jacomb]

> Can we have review requests enabled by default while label changes are
opt in?

I'm not sure if that would scale across the number of infrequently touched
repositories that we have.

There's some good discussion happening in:
https://github.com/timja/github-comment-ops/pull/56

On Mon, 25 Jul 2022 at 11:06, 'Daniel Beck' via Jenkins Developers <
jenkinsci-dev@googlegroups.com> wrote:

>
> On Mon, Jul 25, 2022 at 12:03 PM Alexander Brandes 
> wrote:
>
>> opt out.
>>
>
> Can we have review requests enabled by default while label changes are opt
> in?
>
> --
> 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/CAMo7Pt%2BdzMxsgC__3e1BeTMdquGawX35S2KMVe2Duz8T-tsbUA%40mail.gmail.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3Bidtb-aaYqM83Dc-KpExbbMs5Ww6oBdQbsiLTe%3DabV%3Dfqg%40mail.gmail.com.

Re: comment-ops-bot available in jenkinsci and jenkins-infra

[Tim Jacomb]

> What if I don't want randos on the internet messing up labeling of open
PRs in repos I maintain?
There's an issue here:
https://github.com/timja/github-comment-ops/issues/54
I'm not sure how to scale that though, I thought about adding topic
controls but that would mean an extra API call on each request eating into
rate limits.

There could be a DSL in a config file or environment variable that excludes
repositories / repositories:command, but that would mean maintainers would
have to opt-out centrally.

The extent of them messing up is limited to the set of labels you have
configured and you will get a notification for any action they do.

-

At Daniel's request I've temporarily limited the repositories in the
jenkinsci org to:

   - jenkins
   - design-library-plugin
   - jenkins-infra-test-plugin

This is to gather feedback and in a couple of weeks if there's no
objections we can enable globally.

Thanks
Tim

On Mon, 25 Jul 2022 at 10:46, 'Daniel Beck' via Jenkins Developers <
jenkinsci-dev@googlegroups.com> wrote:

>
> On Mon, Jul 25, 2022 at 10:22 AM Tim Jacomb  wrote:
>
>> It requires no organization permissions, which means anyone can request a
>> review and add labels to issues and pull requests.
>>
>
> What if I don't want randos on the internet messing up labeling of open
> PRs in repos I maintain?
>
> --
> 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/CAMo7PtLqpyt4qKhWcG2e-z8ht3Dg4WACTLzje_fqfoEf27dLuw%40mail.gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/CAMo7PtLqpyt4qKhWcG2e-z8ht3Dg4WACTLzje_fqfoEf27dLuw%40mail.gmail.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3BiciMcaqVPb--Ct2tz5ye2yY4k7Kb-ZHsHDfPBuH_65WoQ%40mail.gmail.com.

comment-ops-bot available in jenkinsci and jenkins-infra

[Tim Jacomb]

Hi all

I've created a comment-ops bot that can be used to help manage issues and
pull requests on GitHub.
The features it has currently are:

   - /close
  - Issues only
   - /label 
   - /remove-label 
   - /reopen
  - Issues only
   - /reviewer(s) 
   - /transfer 

It can be found at:
https://github.com/timja/github-comment-ops/

Examples:
https://github.com/jenkinsci/jenkins-infra-test-plugin/issues/42
https://github.com/jenkinsci/jenkins-infra-test-plugin/pull/40

Demo at UX sig:
https://www.youtube.com/watch?v=t1BSLRPNeQ4=2060s

It requires no organization permissions, which means anyone can request a
review and add labels to issues and pull requests.

I plan to update the Jenkins core pull request template to suggest users do
this in the near future.

Please provide any feedback here or in the issues of the repositories:
https://github.com/timja/github-comment-ops/issues

Thanks
Tim

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3BidByweqsZndytDLz3Bh7XxN0tehMFy3m84Rc6aft7ZCGQ%40mail.gmail.com.

Re: Grant timja immediate permissions to commons-lang3-api plugin

[Tim Jacomb]

I've temporarily reverted it
https://github.com/jenkinsci/configuration-as-code-plugin/releases/tag/1511.vb_f985b_894e40

Once the plugin is sorted we will re-add it to JCasC. We have fairly
frequent pain in conflicts from both commons-text and commons-lang3 and
this was an attempt to put an end to that.

On Tue, 19 Jul 2022 at 07:42, 'Daniel Beck' via Jenkins Developers <
jenkinsci-dev@googlegroups.com> wrote:

>
> On Tue, Jul 19, 2022 at 5:31 AM Mark Waite 
> wrote:
>
>> The preferred fix needs a new release of the commons-lang3-api plugin
>> <https://github.com/jenkinsci/commons-lang3-api-plugin/>.  The current
>> maintainer has not responded to previous requests nor to the current
>> request
>> <https://github.com/jenkins-infra/repository-permissions-updater/pull/2659>
>> that asks to grant Tim Jacomb permission to maintain the plugin.
>>
>> The usual process would require a 2 week wait for the adoption request to
>> "time out".  I propose an exception in this case based on the need to
>> deliver a new release of the commons-lang3-api-plugin.  Tim is the Jenkins
>> release officer, a long-standing contributor to the Jenkins project, and a
>> strong contributor.
>>
>> I propose that Tim be granted permission immediately to maintain the  
>> commons-lang3-api
>> plugin <https://github.com/jenkinsci/commons-lang3-api-plugin/> as
>> requested in the RPU pull request
>> <https://github.com/jenkins-infra/repository-permissions-updater/pull/2659>
>> .
>>
>
> As I wrote in the RPU PR, the easy fix without plugin governance
> challenges is to remove the ill-advised dependency from
> configuration-as-code, reverting
> jenkinsci/configuration-as-code-plugin#1979
> <https://github.com/jenkinsci/configuration-as-code-plugin/pull/1979> [of
> which Tim is already a maintainer]. It seems unnecessary to go over
> maintainers' heads while that's an option. While this is the only plugin
> with the dependency, there's no benefit in conflict prevention anyway, and
> the PR provides no justification.
>
> --
> 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/CAMo7PtJDj1tMO9Sc04b3bar6v3MFXf10NnL555Wg%3DtWoEWCUpA%40mail.gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/CAMo7PtJDj1tMO9Sc04b3bar6v3MFXf10NnL555Wg%3DtWoEWCUpA%40mail.gmail.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3Bicz2rTT0TJZ7G_EcNwsonP3P5PAmuU9DTTzagMV592agA%40mail.gmail.com.

Re: Let renovate handle dependency updates in jenkinsci/jenkins

[Tim Jacomb]

+1 for renovate for at least JS deps, dependabot doesn’t support yarn v3
either so we would need to move at that point anyway

On Mon, 18 Jul 2022 at 22:09, 'Gavin Mogan' via Jenkins Developers <
jenkinsci-dev@googlegroups.com> wrote:

> I'm a big fan of renovate, so I think its a good idea, but I also
> don't touch core, so have no idea what the impact would be.
>
> On Mon, Jul 18, 2022 at 1:19 PM Alexander Brandes 
> wrote:
> >
> > Small ammandment: The semantic commit messages on the PoC can be turned
> off, but are picked up, because recent (my) commits use them.
> >
> > On Monday, 18 July 2022 at 22:15:32 UTC+2 Alexander Brandes wrote:
> >>
> >> Hey everyone,
> >>
> >> dependabot does a good job at handling single artifacts, but it does a
> bad to no job handling modules of monorepos, see babel -cli, -core, -env,
> etc. for example.
> >>
> >> This typically leads me to moving several submodule dependency update
> PRs into a single PR, before reviewing, considering updating one part of a
> dependency without the other often doesn't work out well.
> >> See #6878 and #6879 landing in #6877 for such a case.
> >> This is just one example, there are more dependencies that fall into
> this category.
> >>
> >> I create a PoC of using renovate over dependabot on core available on
> https://github.com/NotMyFault/jenkins-renovate-poc
> >> renovate is very well able to create these kinds of "merged" PRs for
> submodules of a dependency, see #4 for example.
> >>
> >> For the reasons outlined above, I'd like to see renovate to handle
> dependency updates in core in the future.
> >>
> >> Kind regards
> >> Alex
> >
> > --
> > 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/456baae8-e49f-4d87-8d3e-0038257ea5d4n%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/CAG%3D_DuusFce4CdvXeoxb6Hck_t2kiOs77%3DoE5Hz8J6H%2BM0ZxsA%40mail.gmail.com
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3BicFOunUH429B%3DByT3Dg0P05aNgTusuBzc2zRyiY4EoBxw%40mail.gmail.com.

Release lead for 2.346.3

[Tim Jacomb]

Hello

Is anyone interested in being the release lead for 2.346.3?

Planned dates can be seen on the event calendar:
https://www.jenkins.io/events/#event-calendar
Release candidate by 27th July
Release on 10th August

The documentation is at:
https://github.com/jenkins-infra/release
/blob/master/.github/ISSUE_TEMPLATE/1-lts-release-checklist.md

I'll be available to answer any questions and provide guidance (along with
hopefully other past release leads)

We chat in #jenkins-release on libera IRC,
https://www.jenkins.io/chat/#jenkins-release

Anyone interested?

Thanks
Tim

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3BicFi3GQd2ExEAas06j3CTnr5y%2B0BA-vj9E14KqePUzBHg%40mail.gmail.com.

Re: New member of jenkins.io triage team

[Tim Jacomb]

+1

On Wed, 6 Jul 2022 at 06:50, 'Gavin Mogan' via Jenkins Developers <
jenkinsci-dev@googlegroups.com> wrote:

> No objections by me.
>
> On Tue, Jul 5, 2022 at 2:01 PM Mark Waite 
> wrote:
> >
> > Kevin Martens has been running Jenkins Docs office hours (Europe) and
> contributing to Jenkins documentation.  I'd like to add him to the
> jenkins.io triage team in preparation for him eventually becoming a copy
> editor.
> >
> > The process that has been outlined previously is that we first assign
> people to the triage team, then mentor them for a time.  Once there is a
> pattern of contributed reviews, then the docs officer or the contributor
> proposes that they be added to the copy editors team.
> >
> > I propose that the following regular attendees at Docs office hours be
> added to the jenkins.io triage team:
> >
> > Kevin Martens  - Changelog and upgrade guide for 2.346.1, Docs office
> hours (Europe) leader, screenshot update pull requests, helped with docs
> projects in She Code Africa Contributnon
> >
> > During the mentoring period, he will need to submit an individual
> contributor license agreement and become a member of the jenkins-infra
> organization.  Once the mentoring period is complete and the ICLA's have
> been submitted, we'll propose that he be made a copy editor.
> >
> > 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/d4a01ebe-d437-4ef1-bb29-33170f249674n%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/CAG%3D_Dus_Gg%2BTykcPYDk8bHhhdfryg0-sv0pHvD2%3DqEspBUZQ9w%40mail.gmail.com
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3BicYOOsLygrjpkqxatbnfLJ%3DqA7OecG1HKyfs41YLEZFWw%40mail.gmail.com.

Re: New Plugin With Multiple Components Hosting Question

[Tim Jacomb]

Hi

All libraries used in a plugin must be published publicly, open source
approved license, and to an artifact repository that anyone can pull from
normally either maven central or Jenkins repository.

Basically we can host it or you can push it to maven central if it makes
sense outside of Jenkins

Thanks
Tim

On Thu, 30 Jun 2022 at 19:55, Mark Diesburg  wrote:

> We will be submitting a new Jenkins plugin very shortly to integrate
> Jenkins into one of our products. Before pushing the plugin source to
> GitHub and starting the process we have a question on what should be
> submitted to the jenkinsci for hosting
>
>
>
> Our Jenkins plugin is comprised of three main Java components. These are
> separate components because they are each separately useful and extensible.
> The rest-client component is the starting point for potentially building a
> complete standalone Java client that can be used to directly interact with
> our products REST API. The reporting-tool can be used to submit automation
> results to our product from anywhere without requiring customers to write
> their own JUnit/xUnit parser to do so. As a result, they are effectively
> dependencies that the actual Jenkins plugin uses to accomplish the desired
> plugin integration.
>
>
>
> The summary of the components is:
>
>- A rest-client component
>   - Capable of connecting to, sending HTTP calls to, and interpreting
>   results from our product’s REST API.
>- A reporting-tool component
>   - Responsible for taking in report files, parsing them, and
>   converting their data into objects that can be sent to the rest-client 
> to
>   submit the build data using the rest-client to handle interacting with 
> our
>   products REST API.
>- A test-management plugin component
>   - The actual “plugin” portion of the Jenkins plugin.
>   - Responsible for handling configuring the integration within
>   Jenkins.
>   - Captures output from runs in Jenkins and uses the reporting-tool
>   component parse the data and then submit build results to our product.
>
>
>
> We could submit just the source for the test-management plugin portion
> with reference to the other two components on GitHub since they can be used
> independently for other purposes.
>
>
>
> Would this be acceptable?
>
>
>
> Or would we have to submit all three components and also host the
> rest-client and reporting-tool components separately on GitHub in case
> someone wanted to use them for other purposes?
>
>
>
> Thanks for any input!
>
> --
> 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/17390df4-6af9-4c0e-a214-93d41deaf80dn%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-3BicNybR0Ffv-CDJtbwCZVHVMNU6eJ6qG5CWBifesNwdJ6Q%40mail.gmail.com.

Re: Security approval required on UI-related PRs in Jenkins core

[Tim Jacomb]

I'd suggest another label for security review complete but needs fixes.

There's currently 12 PRs showing as blocked by needing security review (1
or 2 of these may need a fix and a label could make that clearer)
https://github.com/jenkinsci/jenkins/pulls?q=is%3Apr+is%3Aopen+sort%3Aupdated-desc+label%3Aneeds-security-review

Cheers
Tim

On Wed, 22 Jun 2022 at 20:31, 'wfoll...@cloudbees.com' via Jenkins
Developers  wrote:

> The team got "triage" permission, so that they can add the newly created
> label "security-approved", so that it's easier to understand when it's good
> to go. That will also "solve" Daniel's concern about regular review ;-)
>
> On Wednesday, June 22, 2022 at 9:30:47 PM UTC+2 db...@cloudbees.com wrote:
>
>> On Wed, Jun 22, 2022 at 9:26 PM 'wfoll...@cloudbees.com' via Jenkins
>> Developers  wrote:
>>
>>> Great idea Alex =>  *@jenkinsci/core-security-review* created
>>>
>>> Thanks for the feedback and yes Tim, I will allocate more people to
>>> those reviews, compared to the hosting requests that were mainly
>>> out-of-order stuff we are doing.
>>>
>>
>> I would like to retain the ability to review core PRs without those
>> reviews automatically counting towards security review, so please be
>> mindful in the handling of this reviewer group. (In particular, me
>> requesting changes for other reasons should not carry the same weight as
>> rejecting a PR for security reasons.)
>>
> --
> 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/cdc1485d-e683-4033-aff5-3b1410e10481n%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-3Bifqo9SnxNRVidFxoh-%3DhFMGwtMPVPeqdwMw9PXHts1w_Q%40mail.gmail.com.

Re: Is there interest for GitHub issues in core components?

[Tim Jacomb]

Hi Basil

I've updated the JEP, could you please take another look when you have time?

Thanks
Tim

On Mon, 27 Jun 2022 at 20:14, Tim Jacomb  wrote:

> Yes there's been some work / plans around this for a while. (~2 years)
>
> A number of issues around it here:
> https://github.com/jenkins-infra/helpdesk/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc+keycloak
>
> No progress on it recently though.
>
> On Mon, 27 Jun 2022 at 19:29, Richard Bywater  wrote:
>
>> Have been following the thread and realise it's only one of the points
>> mentioned but if a barrier to accessing Jira is the login, has any thought
>> been given to allowing GitHub credentials to be used to access Jira? (Not
>> sure about underlying authentication system to know how easy or hard this
>> would be though )
>>
>> Richard.
>>
>> On Tue, 28 Jun 2022, 3:53 am Basil Crow,  wrote:
>>
>>> On Mon, Jun 27, 2022 at 1:15 AM Tim Jacomb  wrote:
>>> >
>>> > Thanks for the feedback, I've created a JEP to capture and address it.
>>>
>>> I read it, but not all of the points are addressed.
>>>
>>> > GitHub conveys a lot more information about the status of issues, pull
>>> requests and releases than Jira does.
>>>
>>> On the contrary, GitHub does not provide enough information about the
>>> status of issues, forcing label-based workarounds. For example, there
>>> is no dedicated field for status (e.g., "Fixed but unreleased", "Won't
>>> fix", "Cannot reproduce", etc) and no capability for searching by
>>> status across components. And there is no dedicated UI element for
>>> linking issues (e.g., "Caused by", "Duplicates", "Depends on", etc)
>>> and viewing issues by links (e.g., viewing all bugs caused by a
>>> particular change). There is also no ability to add custom fields
>>> (e.g., "Released version"). The Jira Query Language (JQL) is a
>>> powerful way to search for issues, and as far as I can tell there is
>>> no equivalent in GitHub.
>>>
>>> > Jira allows explicit relationships to be set on links. GitHub requires
>>> you to type 'Caused by' and 'Depends on' yourself.
>>>
>>> That is an understatement: GitHub does not support relationships to be
>>> set on links at all. Even if you type "Caused by" and "Depends on"
>>> yourself, there is no way to e.g. view all the bugs that were caused
>>> by a particular change for a given component.
>>>
>>> > GitHub projects can be used to group issues that are across
>>> components. If that project doesn't use GitHub issues then […] A tracking
>>> issue can be created that links to a Jira epic or query
>>>
>>> As I wrote in
>>> https://groups.google.com/g/jenkinsci-dev/c/9sZipk1PHns/m/uy8LVZQsAAAJ
>>> this suggested workaorund is burdensome and therefore unacceptable to
>>> me. The only solution that is not burdensome for users is for the
>>> entire Jenkins project to use a single issue tracker for all
>>> components.
>>>
>>> > Jira's mobile support is very poor, commenting doesn't work on mobile
>>> web
>>>
>>> Sometimes people have written things to me on GitHub that do not make
>>> sense, and when I ask for clarification they explain away their
>>> writing by saying that they were using their mobile device. I think a
>>> good solution to this problem is to discourage people from using
>>> mobile devices when interacting on issue trackers. I would prefer to
>>> interact with people in an environment where they can write clearly
>>> and deliberately and edit their writing using a keyboard before
>>> submitting it.
>>>
>>> > Newly opened issues are labelled with `needs-triage`.
>>>
>>> This proposed triage process, which is based on issue labels, seems
>>> like it will add additional barriers to new contributors. Today,
>>> anyone with a Jira account can triage issues, but it seems like to
>>> manage issue labels in the proposed system users will first need to be
>>> given GitHub triage permissions.
>>>
>>> --
>>> 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
>>> 

Re: Is there interest for GitHub issues in core components?

[Tim Jacomb]

Yes there's been some work / plans around this for a while. (~2 years)

A number of issues around it here:
https://github.com/jenkins-infra/helpdesk/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc+keycloak

No progress on it recently though.

On Mon, 27 Jun 2022 at 19:29, Richard Bywater  wrote:

> Have been following the thread and realise it's only one of the points
> mentioned but if a barrier to accessing Jira is the login, has any thought
> been given to allowing GitHub credentials to be used to access Jira? (Not
> sure about underlying authentication system to know how easy or hard this
> would be though )
>
> Richard.
>
> On Tue, 28 Jun 2022, 3:53 am Basil Crow,  wrote:
>
>> On Mon, Jun 27, 2022 at 1:15 AM Tim Jacomb  wrote:
>> >
>> > Thanks for the feedback, I've created a JEP to capture and address it.
>>
>> I read it, but not all of the points are addressed.
>>
>> > GitHub conveys a lot more information about the status of issues, pull
>> requests and releases than Jira does.
>>
>> On the contrary, GitHub does not provide enough information about the
>> status of issues, forcing label-based workarounds. For example, there
>> is no dedicated field for status (e.g., "Fixed but unreleased", "Won't
>> fix", "Cannot reproduce", etc) and no capability for searching by
>> status across components. And there is no dedicated UI element for
>> linking issues (e.g., "Caused by", "Duplicates", "Depends on", etc)
>> and viewing issues by links (e.g., viewing all bugs caused by a
>> particular change). There is also no ability to add custom fields
>> (e.g., "Released version"). The Jira Query Language (JQL) is a
>> powerful way to search for issues, and as far as I can tell there is
>> no equivalent in GitHub.
>>
>> > Jira allows explicit relationships to be set on links. GitHub requires
>> you to type 'Caused by' and 'Depends on' yourself.
>>
>> That is an understatement: GitHub does not support relationships to be
>> set on links at all. Even if you type "Caused by" and "Depends on"
>> yourself, there is no way to e.g. view all the bugs that were caused
>> by a particular change for a given component.
>>
>> > GitHub projects can be used to group issues that are across components.
>> If that project doesn't use GitHub issues then […] A tracking issue can be
>> created that links to a Jira epic or query
>>
>> As I wrote in
>> https://groups.google.com/g/jenkinsci-dev/c/9sZipk1PHns/m/uy8LVZQsAAAJ
>> this suggested workaorund is burdensome and therefore unacceptable to
>> me. The only solution that is not burdensome for users is for the
>> entire Jenkins project to use a single issue tracker for all
>> components.
>>
>> > Jira's mobile support is very poor, commenting doesn't work on mobile
>> web
>>
>> Sometimes people have written things to me on GitHub that do not make
>> sense, and when I ask for clarification they explain away their
>> writing by saying that they were using their mobile device. I think a
>> good solution to this problem is to discourage people from using
>> mobile devices when interacting on issue trackers. I would prefer to
>> interact with people in an environment where they can write clearly
>> and deliberately and edit their writing using a keyboard before
>> submitting it.
>>
>> > Newly opened issues are labelled with `needs-triage`.
>>
>> This proposed triage process, which is based on issue labels, seems
>> like it will add additional barriers to new contributors. Today,
>> anyone with a Jira account can triage issues, but it seems like to
>> manage issue labels in the proposed system users will first need to be
>> given GitHub triage permissions.
>>
>> --
>> 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/CAFwNDjriE6Xf_hLN_y_XEbyApJ39qSo0Pn%2BRB%3Da_iCH_9CB2eQ%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.goog

Re: Is there interest for GitHub issues in core components?

[Tim Jacomb]

Hi all

Thanks for the feedback, I've created a JEP to capture and address it.

https://github.com/jenkinsci/jep/pull/390

Cheers
Tim

On Wed, 15 Jun 2022 at 16:55, Basil Crow  wrote:

> On Mon, May 23, 2022 at 1:25 PM Tim Jacomb  wrote:
> > Is there any interest in moving core components to GitHub issues?
>
> Not from me. There is, on the other hand, an interest from me (for the
> reasons described in
> https://groups.google.com/g/jenkinsci-dev/c/9sZipk1PHns/m/mqtV7K8uAAAJ)
> for us to
>
> > (a) stop accepting new issues on GitHub for all core components and (b)
> move any existing core component issues from GitHub to Jira.
>
> On Mon, Jun 13, 2022 at 6:55 AM Tim Jacomb  wrote:
> > That thread is nearly 2 years old
>
> But my recent posts in that thread are less than a month old.
>
> > the new GitHub projects and issues have come a long way in that time.
>
> Yet I still cannot mark one GitHub issue as caused by or depending on
> another GitHub issue, and I still cannot efficiently move a GitHub
> issue from the incorrect component to the correct component.
>
> > The barrier to entry on Jira is a lot higher than on GitHub, many people
> struggle to report issues.
>
> I do not think the barrier to entry on Jira is prohibitively high. As
> others have noted, reporting issues requires a certain degree of due
> diligence, including writing steps to reproduce, expected results, and
> actual results.
>
> --
> 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/CAFwNDjr6e0R-qpSm9bvcDKwmOMOHyyc_6aLaF42RwAruMQ8neA%40mail.gmail.com
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3Bic%3DHcRy_oecT4Bn%3DQ1pgmWM9UWOMVQ2va4aZo2uRoQ%2BoA%40mail.gmail.com.

Re: Proposal: Jenkins Core PR reviewers team

[Tim Jacomb]

Taking the 4 +1s, I've added Alex to the Core PR reviewers team.

On Mon, 20 Jun 2022 at 19:15, Basil Crow  wrote:

> On Mon, Jun 20, 2022 at 2:19 AM Alexander Brandes 
> wrote:
> > where the latter would only be for review requests
>
> +1 from me that Alex becomes part of the "core PR reviewers" team.
>
> > I'm already inheriting these permissions as release team member.
>
> Yes, for "release activities, e.g. backporting, build fixes" (per this
> message
> ).
>
> --
> 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/CAFwNDjpP1hWXbf%2BksiOZWffwKe_BWDrF9k4DWd_krfDffrBfGA%40mail.gmail.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3BiehRonL58ieHuvpoTsmosQ3Wm2KUZGZ4Z8k2DELb54HuQ%40mail.gmail.com.

Release lead 2.346.2

[Tim Jacomb]

Hello

Is anyone interested in being the release lead for 2.346.2?

Planned dates can be seen on the event calendar:
https://www.jenkins.io/events/#event-calendar
Release candidate by 29th June
Release on 13th July

The documentation is at:
https://github.com/jenkins-infra/release/blob/master/.github/ISSUE_TEMPLATE/1-lts-release-checklist.md

I'll be available to answer any questions and provide guidance (along with
hopefully other past release leads)

We chat in #jenkins-release on libera IRC,
https://www.jenkins.io/chat/#jenkins-release

Anyone interested?

Thanks
Tim

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3Bicy-yn7W00rMrJejaBauqaRHGK%2BYA%3DqsiNxu8KqFXQUPw%40mail.gmail.com.

Re: Security approval required on UI-related PRs in Jenkins core

[Tim Jacomb]

Hi Wadeck

We can monitor this in the short term.
My concern would be around responsiveness and turn around time.

RPU hosting requests already can take a fair amount of time if there’s a
few at a time

 It already takes a long time to get some of the UI pull requests in. As
long as the security team are in early and actively reviewing, (and that
means looking at all the pull requests currently active) too then fine.

We already have a big backlog of pull requests that we were asked to hold
off on the last few weeks due to the security release, so if these could be
looked at ASAP then that would be great.

Let’s add this as an agenda item for the next UX sig meeting to review how
it’s going

Thanks
Tim

On Wed, 22 Jun 2022 at 18:37, 'wfoll...@cloudbees.com' via Jenkins
Developers  wrote:

> Today the Jenkins project released a security version
>  that contains
> several high severity vulnerabilities. Five vulnerabilities from Jenkins
> core were introduced very recently during UI improvement work.
>
> Such security issues discovered after a merge implies that we are
> investing a lot of energy/time to correct it and providing all the
> necessary data in terms of vulnerability management. The difference between
> finding them during review and after a release is really huge.
>
> For this reason, as the security officer and effective as of today, I want
> to block the merge of any UI-related PRs until they have received at least
> one approval from someone in CERT.
>
> To set expectations, if a PR is approved but then substantial change is
> committed, the approval must be dismissed and re-requested. The second
> approval is expected to be quicker.
>
> This process is expected to provide better security coverage of the
> upcoming changes and thus, reducing the likelihood of introducing
> vulnerabilities.
>
> In order to not be a blocker for the UI improvement project, I will assign
> more people from my team to review the PRs. The job done by the UI team is
> amazing and should continue.
>
> This new policy will be revised over time and ideally removed in the
> mid-term.
>
> Do you have any concerns related to this?
>
> Wadeck Follonier
>
> Security Officer
>
> --
> 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/7846d76d-2bc0-4829-a4a2-d9035e10592fn%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-3BidHtahVSzY6Q%2BrHEHxYBLCMA_EU3idGBperOOfY4GHT7w%40mail.gmail.com.

Re: Proposal: Jenkins Core PR reviewers team

[Tim Jacomb]

+1 although I'd also be +1 on core maintainer status as well for Alex.

He's helped out a lot recently

Cheers
Tim

On Sun, 19 Jun 2022 at 17:36, Alexander Brandes 
wrote:

> Hey everyone,
>
> late reply but I would be interested in joining as well.
>
> Since I joined the release team a few months ago to take care of the last
> point release and the upcoming 2.346 LTS release, I moderate a bunch of
> core PRs by applying labels, fixing up changelog entries, PR titles or
> spinning up ATH and bom runs, if needed; granted by the permissions as
> release team member, besides the typical reviews for PRs.
> Aside the LTS PRs, I merged a few minor ones in the past fulfilling the
> requirements to be eligible for a merge too, to facilitate a backport into
> LTS or to unblock and prevent a delay of a weekly release e.g.
>
> Kind regards
> Alex
>
> On Friday, 16 April 2021 at 22:51:04 UTC+2 Oleg Nenashev wrote:
>
>> Welcome aboard Basil! I have updated the permissions and added you to the
>> Jenkins Core PR reviewers team.
>>
>> Just for the record, the Pull request review guidelines and other
>> maintainer docs are available here
>> <https://github.com/jenkinsci/jenkins/blob/master/docs/MAINTAINERS.adoc#pull-request-review-process>.
>> We are always interested in onboarding more core maintainers, and everyone
>> is welcome to participate.
>>
>> Best regards,
>> Oleg Nenashev
>>
>>
>> On Thu, Apr 15, 2021 at 10:35 PM Oleg Nenashev 
>> wrote:
>>
>>> +1. I will grant Basil permissions tomorrow if no negative feedback. And
>>> again, thanks to Basil for all the contributions to Jenkins!
>>>
>>> On Thu, Apr 15, 2021, 22:33 Tim Jacomb  wrote:
>>>
>>>> +1
>>>>
>>>> On Thu, 15 Apr 2021 at 19:07, Mark Waite  wrote:
>>>>
>>>>> +1 from me that Basil becomes part of the core PR reviewers team.
>>>>>
>>>>> On Thu, Apr 15, 2021 at 11:54 AM Basil Crow 
>>>>> wrote:
>>>>>
>>>>>> I'm interested in joining the Core PR reviewers team 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-de...@googlegroups.com.
>>>>>> To view this discussion on the web visit
>>>>>> https://groups.google.com/d/msgid/jenkinsci-dev/CAFwNDjrnHZmDg-JmtP%2B3fO%3Df1w_uNRFevrOy9dHfsq29n0xDnA%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/CAO49JtFoN%3DsiPzRHcLHJyJbs1xBqnFVAkfQONGcwcE4a90hGhw%40mail.gmail.com
>>>>> <https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtFoN%3DsiPzRHcLHJyJbs1xBqnFVAkfQONGcwcE4a90hGhw%40mail.gmail.com?utm_medium=email_source=footer>
>>>>> .
>>>>>
>>>> --
>>>> 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/0sdrcSOQW64/unsubscribe
>>>> .
>>>> To unsubscribe from this group and all its topics, send an email to
>>>> jenkinsci-de...@googlegroups.com.
>>>> To view this discussion on the web visit
>>>> https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3BifbZ_nDppzESg7VQSzM3-HKzk96V%2B7WYDP5-LFwoHZhRg%40mail.gmail.com
>>>> <https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3BifbZ_nDppzESg7VQSzM3-HKzk96V%2B7WYDP5-LFwoHZhRg%40mail.gmail.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.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/b3c16811-4f63-4550-99ed-02179c2e1b5en%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-dev/b3c16811-4f63-4550-99ed-02179c2e1b5en%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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3Bidk-comtFzXQA4o640QaSL2kd0gTEXqr%3DD8Su76UoERbg%40mail.gmail.com.

Re: Workflow approval for first time contributors

[Tim Jacomb]

Hi Alex

Workflow approval is a GitHub actions only thing.

Unless it’s very spammy I don’t think it’s something to worry about, we
often block these sort of people for 24 hours in case they continue.

We get this sort of thing occasionally but it’s not normally that many

Cheers
Tim


On Sat, 18 Jun 2022 at 08:32, Alexander Brandes 
wrote:

> Hey everyone,
>
> I would like to propose to enable workflow approval
> 
>  for
> first time contributors, at least for jenkinsci/jenkins, if we don't want
> to enforce it on the organization.
>
> Not every new contributor proposes a PR with good intentions, see
> https://github.com/jenkinsci/jenkins/pull/6669 for a recent core PR
> example.
>
> While these kinds of "contributions" cause no real harm to a repository
> itself, they do waste resources, especially if you do that on core or other
> core repositories like ATH, bom, etc.
>
> Enabling workflow approval for new contributors requires maintainers to
> click a button on the repository to allow the workflow to start, if the PR
> has been submitted by a first time contributor, which sounds fine to me,
> instead of watching builds on ci.jenkins taking hours for nothing.
>
> Kind regards,
> ~Alex
>
> --
> 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/da121788-6e8c-48f3-a3be-cfc4f158a85fn%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-3Bidt0O6QLK0tn%3DFFzveqxtCQGUUg9JFdBZ1e4oECPee7%2Bw%40mail.gmail.com.

Re: javadoc issue due to Java11 on jenkins?

[Tim Jacomb]

Throwing a couple of suggestions out there:
- build on 17
- backport to Java8?
- try a couple of those options out from the linked post but as James said
they all have issues by the looks of it

On Wed, 15 Jun 2022 at 17:33, 'jn...@cloudbees.com' via Jenkins Developers <
jenkinsci-dev@googlegroups.com> wrote:

> Good find Basil,
>
> the above issue I mentioned with search seems to be
> https://bugs.openjdk.org/browse/JDK-8215291  which is alas also fixed in
> Java 12
>
> Stack overflow[1] mentions some workarounds, but they appear to have other
> issues.
>
> /James
>
> [1]
> https://stackoverflow.com/questions/52326318/maven-javadoc-search-redirects-to-undefined-url
>
> On Wednesday, June 15, 2022 at 5:29:12 PM UTC+1 jn...@cloudbees.com wrote:
>
>> I am seeing some issues with the actual jenkins java11 javadoc too.
>> Smells like bugs in javadoc - but it may be out invocation of it is not
>> correct.
>>
>> The search seems to be broken - when you follow a link to a type you get
>> linked to a page that starts https://javadoc.jenkins.io/undefined  e.g.
>> https://javadoc.jenkins.io/undefined/hudson/security/AccessControlled.html)
>>  it only seems to do the right thing when what you are searching for is a
>> package but reliably fails for types.
>>
>> /James
>>
>> On Tuesday, June 14, 2022 at 7:08:14 PM UTC+1 m...@basilcrow.com wrote:
>>
>>> The problem can be reproduced by going to any Jenkins plugin today and
>>> running mvn javadoc:javadoc with Java 8. The problem does not occur
>>> when running the same Maven command with Java 11. So one solution is to
>>> perform the release with Java 11 (as we are doing with Jenkins core today).
>>>
>>> I suspect this may have something to do with the renaming of
>>> package-list to element-list in Java 10. I see
>>> https://javadoc.jenkins.io/element-list but
>>> https://javadoc.jenkins.io/package-list gives a 404 (Javadoc built with
>>> Java 11). In contrast, I see
>>> https://javadoc.jenkins.io/component/jenkins-test-harness/package-list
>>> but
>>> https://javadoc.jenkins.io/component/jenkins-test-harness/element-list
>>> gives a 404 (Javadoc built with Java 8). If this theory is correct, another
>>> solution might be to symlink package-list to element-list as was
>>> effectively done in gradle/gradle@
>>> 5e88351dd456a5252d21f3a7ad25bff1b62a2fd2
>>> 
>>> .
>>>
>> --
> 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/bcb4529f-7531-4e62-9dbc-836ea265bf98n%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-3BiegTCk7AGMVJcDbgeK%2BTuwCa6-TcqBWk%3DB%3DWZDaOVsHrw%40mail.gmail.com.

Re: javadoc issue due to Java11 on jenkins?

[Tim Jacomb]

Interesting.

I don't _think_ the one week early has any impact other than just raising
the problem earlier.

You're likely the first to hit this though.

Can you tell if the javadoc was published for the plugin or if there's any
issue with it?

We can test it out on the test plugin
 to not impact
users.

Thanks
Tim

On Tue, 14 Jun 2022 at 14:26, 'jn...@cloudbees.com' via Jenkins Developers <
jenkinsci-dev@googlegroups.com> wrote:

> Hi all
>
> Just released a plugin and I have the following warning
>
> [WARNING] javadoc: warning - Error fetching URL:
> https://javadoc.jenkins.io/
>
> The javadoc for jenkins was recently switch to Java11 (seems a week early)
> and this means that plugins can no longer link correctly when
> compiling/releasing with Java 11, presumably as the file that javadoc
> download for the cross referencing is missing.
>
> Given plugins will still be targeting Java8 (and older Jenkins versions
> for a while) has anyone else seen this or though about it?
>
> /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 jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/7f90a8dd-a811-44a1-870b-b13781063988n%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-3Bif9qcZQa%2B7Q45v4E%3DDHeGuGyZ-sAmH%3Dw%2B9b9nbnLVJh8w%40mail.gmail.com.

Re: Jenkinsci Cloudevents plugin

[Tim Jacomb]

Or alternatively create a new plugin for CDEvents if the cloud events
heritage doesn't make sense any more.

Once you've got it working you could then go through the hosting process
.

Thanks
Tim



On Tue, 14 Jun 2022 at 13:18, Mark Waite  wrote:

>
>
> On Tuesday, June 14, 2022 at 6:08:41 AM UTC-6 Ger McMahon wrote:
>
>> My name is Ger McMahon and work for Fidelity Investments. As part of
>> being an end user member of Continuous Delivery Foundation (CDF), we want
>> to get more involved in open source projects and especially ones related to
>> the CDF. We have a particular interest in the Jenkinsci Cloudevents
>> plugin  and understand
>> the project has been dormant since it was created as part of the Google
>> Summer of Code. Fidelity would have an interest on taking on this project,
>> either through mutating the current implementation or forking to align with
>> the new CDEvents project  from CDF.
>>
>>
>>
>> I wanted to connect with the jenkinsci-dev group to determine the next
>> steps and appreciate any information or feedback.
>>
>>
>>
> Welcome to the developer community!  Great to have your interest in
> CloudEvents and happy to have your help.  The "Adopt a plugin"
> 
> process says:
>
> Be sure to provide the following information:
>
>-
>
>Link to a plugin you want to adopt -
>https://github.com/jenkinsci/cloudevents-plugin
>-
>
>The status of the plugin ("for adoption" or "abandoned") - abandoned
>-
>
>Link(s) to pull requests you want to deliver, if applicable - I don't
>see any yet, though refer to the "Contributing to Open Source"
>
> 
>document and the "Modernizing a plugin" video series
> for suggested starter
>pull requests
>-
>
>Your GitHub username/id (e.g. oleg-nenashev for
>https://github.com/oleg-nenashev/) - You'll need to provide this one
>-
>
>Your Jenkins infrastructure account id. Create your account
> if you don’t have one. - You'll need to
>provide this one
>-
>
>The link to the "Repository Permission Updater" PR described below -
>You'll need to provide this one based on the instructions
>
> Be sure that you follow the instructions for the contents of the pull
> request and its comments.
>
> Thanks again,
> 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/93cc484d-de7e-497e-9396-3b84d7761a56n%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-3BidrQYOxj6-AT78de3WfrcBZK0G1fqqk1FP3G%2B-%3DXN5ctw%40mail.gmail.com.

Re: BOM build errors due to conflict of baseline 2.319.3 and 2.319.1

[Tim Jacomb]

Hi Ulli

Since you've bumped past a baseline that is still supported in bom you need
to pin the previous version of the dependency in the bom that your plugin
doesn't support now.

i.e. add

echarts-api 5.3.2-1
to
https://github.com/jenkinsci/bom/blob/master/bom-2.303.x/pom.xml

Thanks
Tim


On Mon, 13 Jun 2022 at 11:49, 'jn...@cloudbees.com' via Jenkins Developers <
jenkinsci-dev@googlegroups.com> wrote:

> > There was quite a long and controversial discussion around that topic in
> this mailing list (and the associated PR).
>
> Thanks Ulli, for some reason I missed that, which is a shame.
>
> I can not help you wrt the BOM specifics, perhaps Jesse/Basil or Tim can
> help.
>
> /James
>
> On Monday, June 13, 2022 at 10:38:36 AM UTC+1 ullrich...@gmail.com wrote:
>
>> Am 13.06.2022 um 11:11 schrieb 'jn...@cloudbees.com' via Jenkins
>> Developers :
>>
>> Hi Ulli,
>>
>> Can you clarify what these guidelines are and where they are (I did not
>> see anything in a scan of the ML, nor on jenkins.io)?
>>
>> With my Jenkins user hat on I would be somewhat annoyed if I had to
>> upgrade Jenkins to get a small bug fix for a plugin.
>>
>> Upgrading to every  `.1`  LTS is ok - but I am surprised there is any
>> guideline saying to update to a `.2` and a `.3`?
>>
>> /James
>>
>>
>>
>> https://www.jenkins.io/doc/developer/plugin-development/choosing-jenkins-baseline/
>>
>> There was quite a long and controversial discussion around that topic in
>> this mailing list (and the associated PR).
>>
>> On Friday, June 10, 2022 at 5:49:14 PM UTC+1 ullrich...@gmail.com wrote:
>>
>>> I recently updated my plugins to follow the new guidelines to use 2.319.3
>>> rather than 2.319.1 as a plugin baseline. But now all my plugin upgrade
>>> PRs fail in the BOM project (https://github.com/jenkinsci/bom/pulls).
>>> What do I need to do to get those PR builds working?
>>>
>>
>> --
>> 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/38dccdf2-2b81-422c-9202-74f2584b410bn%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/ae9415ea-6764-4b21-ae87-217f185e5af4n%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-3Bic1AiFfzHRGkE_gKqf2ioF32iu5ZgnUkntuKoqB5H-7zg%40mail.gmail.com.

Re: Is there interest for GitHub issues in core components?

[Tim Jacomb]

Hi James

That thread is nearly 2 years old and the new GitHub projects and issues
have come a long way in that time.

To demonstrate some of what this could look like I did a POC migration
based on the INFRA one:
https://github.com/timja/jenkins-gh-issues-poc/issues

I recreated 2 dashboards that we currently use in Jira:

UX:
https://github.com/users/timja/projects/3/views/1

Core maintainers:
https://github.com/users/timja/projects/4/views/3

There's a tool you can use to subscribe to labels in GitHub like with Jira
(not built-in but hopefully one day):
https://github.com/orgs/github-community/discussions/16645

There's some sorting limitations which means I couldn't fully re-create the
core maintainers dashboard unfortunately:
https://github.com/github-community/community/discussions/8518



We can certainly enhance our Jira setup but I don't see it being as smooth
and nicely integrated as GitHub is.
The barrier to entry on Jira is a lot higher than on GitHub, many people
struggle to report issues.

I have started writing a draft JEP to put some more words together but
interested in any feedback on the above.
(I'm aware EPIC links are not included in the export, I plan to fix that)
(Web links exporting doesn't work unfortunately
https://jira.atlassian.com/browse/JRASERVER-44537)

Thanks
Tim

On Mon, 13 Jun 2022 at 10:19, 'jn...@cloudbees.com' via Jenkins Developers <
jenkinsci-dev@googlegroups.com> wrote:

> https://groups.google.com/g/jenkinsci-dev/c/9sZipk1PHns/m/mqtV7K8uAAAJ
> would report there is the opposite.
>
> Whilst Jira is a PITA, GitHub issues for me has more drawbacks.
>
> We seem to be missing some improvements to Jira that would make it much
> nicer day to day,
> e.g.
> https://confluence.atlassian.com/jirasoftwareserver/configuring-development-tools-938845350.html
>
>
> /James
> On Monday, May 23, 2022 at 9:25:10 PM UTC+1 timja...@gmail.com wrote:
>
>> Hello
>>
>> Is there any interest in moving core components to GitHub issues?
>>
>> It would involve things like:
>> - Issue migration
>> - LTS backporting flow updates
>> - Documentation updates
>> - Dashboards / reporting - maybe something like
>> https://github.com/marketplace/actions/issue-dashboard
>>
>> I would be happy to prototype something / prepare a JEP if there's
>> interest.
>>
>> Thanks
>> Tim
>>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/16d883f7-0f80-4cfd-9837-5e57040a9288n%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-3BifhX7cZrpLtammM0FiojKZGG501FQJYY%3Dq2NKQxmtmMGQ%40mail.gmail.com.

Re: Backporting for LTS 2.346.1 started

[Tim Jacomb]

Fine to delay the extra week

On Tue, 7 Jun 2022 at 12:01, Alexander Brandes  wrote:

> Hey Wadeck,
>
> thanks for the clarification from the views of the security team, that
> sounds reasonable. I'd want to go ahead and merge the PR later today,
> considering nobody expressed blocking reviews in over a week.
>
> To 1), that's a call Tim has to agree to as well. But like you already
> stated, delaying them might not be the best solution, however, I have no
> strong objections about it, if the security team needs a bit more time in
> advance.
>
> ~ Alex
>
> On Tuesday, 7 June 2022 at 18:20:52 UTC+2 wfoll...@cloudbees.com wrote:
>
>> Hey there, especially Alex,
>>
>> Usually we have a two weeks period for the RC, once the backports are
>> merged. In this case, we have a PR that is still pending, ~one week after
>> the expected delay.
>> PR in question: https://github.com/jenkinsci/jenkins/pull/6618
>>
>> So, two questions:
>> 1) Is it OK if we are *postponing the release by one additional week*?
>> a) to have two weeks of test for the RC, b) to get more time for the
>> security release that requires to have that PR merged. It would mean that
>> the LTS will be released on June 22. (and thus the Java 11 should be
>> postponed again)
>> 2) When do you plan to merge the PR?
>>
>> The second wave of backports seems to contain important fixes, so
>> postponing those seems to be not really an option.
>>
>> Best regards,
>>
>> Wadeck
>> On Tuesday, May 31, 2022 at 8:37:24 PM UTC+2 m...@basilcrow.com wrote:
>>
>>> On Fri, May 27, 2022 at 3:03 AM Alexander Brandes 
>>> wrote:
>>> >
>>> > If there are no objections against it, I'd like to use the additional
>>> time and start a secondary backporting process from past weekly releases to
>>> integrate the new LTS candidates.
>>>
>>> +1
>>>
>> --
> 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/5c711ab6-94ba-446d-bf30-e1659fa82368n%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-3BidocRQoDFsq4%3DQBBeMRftnh-V55eUSLUN8t5YtMC3Tf8w%40mail.gmail.com.

Re: [Jenkins Docker Images] Request for maintainer access

[Tim Jacomb]

+1

I've granted access, welcome aboard

On Wed, 25 May 2022 at 11:35, Mark Waite  wrote:

>
> On Wed, May 25, 2022 at 4:08 AM Damien Duportal wrote:
>
>> Hello dear contributors, maintainers, readers.
>>
>>
>> I'm writing this email to request a maintainer access (GitHub handle
>> "dduportal") to the following repositories:
>>
>> - https://github.com/jenkinsci/docker
>> - https://github.com/jenkinsci/docker-agent
>> - https://github.com/jenkinsci/docker-ssh-agent
>> - https://github.com/jenkinsci/docker-inbound-agent
>>
>>
>> The reason for this request are the following:
>>
>> - With the persona  of Jenkins Infrastructure officer and team member,
>> the ability to operate these repositories to ensure fast CI/CD process on
>> the infra are key (reality check: we always had maintainers whom did the
>> review work so we never were slowed down, but it would be a "plus")
>> - With the persona of contribuor who want to increase his area of
>> contribution:
>>   * I've already contributed to these repositories in the past years on
>> many topics (from build process to bugfix or features) and I plan to
>> propose more contribution in the upcomings weeks/months
>>   * I'm spending more personal time on helping users on their issues on
>> this area  and I also plan and commit to help more (triaging, writing JEP,
>> and helping more)
>>
>> Of course, this is a question that can be answered by YES or NO: it is
>> for the actual maintainers and Jenkins board and the community to decide
>> (and I would accept whatever answer is given of course without complaining).
>>
>>
> +1 from me to grant maintainer access to Damien for those repositories.
> My answer is YES
>
> 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/CAO49JtFEW%3DSUngTF1NZhXn2757s0jeoqbXJYWb2EMJjbnP%3D%2Bvw%40mail.gmail.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3Bie-M84UJ18T9bxYue4X3AkWq8jiCttGGcsKPBaeJNA50w%40mail.gmail.com.

Is there interest for GitHub issues in core components?

[Tim Jacomb]

Hello

Is there any interest in moving core components to GitHub issues?

It would involve things like:
- Issue migration
- LTS backporting flow updates
- Documentation updates
- Dashboards / reporting - maybe something like
https://github.com/marketplace/actions/issue-dashboard

I would be happy to prototype something / prepare a JEP if there's interest.

Thanks
Tim

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3BidMmF0s5qS%2BfpJwOitPCmBiRYRGqajSJfKcVjhU2w3%3DDA%40mail.gmail.com.

Re: 2.346.1 release lead

[Tim Jacomb]

@Mark Waite  to be clear were you asking for an
RC delay as well or just the final release date?

On Fri, 13 May 2022 at 15:02, Tim Jacomb  wrote:

> Thanks! Go for it
>
> On Fri, 13 May 2022 at 14:52, Alexander Brandes 
> wrote:
>
>> Heyo all,
>>
>> I'd like to take care of it, if possible.
>>
>> ~Alex
>>
>> On Friday, 13 May 2022 at 00:06:02 UTC+2 timja...@gmail.com wrote:
>>
>>> Sure, I've moved the release date 2 weeks out.
>>>
>>> New dates:
>>> RC: 18th May
>>> Release day: 15th June
>>>
>>> On Tue, 10 May 2022 at 17:51, Mark Waite  wrote:
>>>
>>>>
>>>>
>>>> On Tue, May 10, 2022 at 9:23 AM Tim Jacomb wrote:
>>>>
>>>>> Hello
>>>>>
>>>>> Is anyone interested in being the release lead for 2.346.1?
>>>>>
>>>>> Planned dates can be seen on the event calendar:
>>>>> https://www.jenkins.io/events/#event-calendar
>>>>> Release candidate by 18th May
>>>>> Release on 1st June
>>>>>
>>>>>
>>>> Would you be willing to consider a 2 week delay in that final release
>>>> date, so that it would be June 15 rather than June 1?
>>>>
>>>> The original scheduled date to select the LTS baseline was April 20,
>>>> 2022.  We delayed that by a little less than 3 weeks so that we could
>>>> assure that the selected LTS baseline had fewer open issues and good
>>>> ratings.  We've had great results from that effort, but I still feel that
>>>> we need three weeks to watch for issues in the selected baseline (2.346),
>>>> then two weeks to test the release candidate.  That's removing one week
>>>> from our usual pattern of four weeks from baseline selection to release
>>>> candidate then two weeks from release candidate to release.
>>>>
>>>> I acknowledge that the final decision on release date is best decided
>>>> by you as the release officer.  I'm lobbying for the delay of the release
>>>> date but fully accept that the decision is yours to make, not mine.  Thanks
>>>> for being the Jenkins release officer and thanks so much for your
>>>> contributions to Jenkins.
>>>>
>>>> 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-de...@googlegroups.com.
>>>> To view this discussion on the web visit
>>>> https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtHfBQVdgbdWPbYZWsEMxq%3DUO%2BF4eHW5EvCcsDRgYBextg%40mail.gmail.com
>>>> <https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtHfBQVdgbdWPbYZWsEMxq%3DUO%2BF4eHW5EvCcsDRgYBextg%40mail.gmail.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.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-dev/12b049d5-1811-4da4-a59b-f468df396ac3n%40googlegroups.com
>> <https://groups.google.com/d/msgid/jenkinsci-dev/12b049d5-1811-4da4-a59b-f468df396ac3n%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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3Bif9HqM1JzmfDUwyP3q8tZV-gxyfxL%3DMCcuML4REws7%2Bzw%40mail.gmail.com.