Re: ASM in core

[Basil Crow]

On Tue, Jan 4, 2022 at 5:09 PM 'Jesse Glick' via Jenkins Developers
 wrote:
>
> That basically takes us back to the unfortunate state we were in with 
> Kohsuke’s series of shaded & repackaged ASM libraries, where we could not 
> give a clear answer as to what we were actually bundling, and security 
> scanners complained, etc. Not sure that is an improvement.

Does not seem so bad if limited to Stapler (and a deprecated code path
within Stapler at that). In the old status quo, plugins were also
consuming the shaded copy, which would no longer be necessary. Once
ASM is detached to an API plugin, plugins like SCM: API and Token
Macro can consume the ASM API plugin without shading. The version of
the shaded ASM consumed by Stapler would be updated by Dependabot;
hopefully that addresses the security concern.

> Right, you sometimes get into trouble when you try to use the library from 
> the same Maven module that Shades it. Better to create a separate module in 
> the reactor which solely Shades the library, then depend on that module from 
> Stapler core. https://github.com/jenkinsci/docker-traceability-plugin/pull/18 
> shows the idea.

Thank you for the pointer. That seems like an example I can follow.

> Another possibility is to write a minimal bytecode parser that just groks the 
> symbol table, list of methods with their binary signatures, and method 
> parameter metadata.

Like 
https://github.com/paul-hammant/paranamer/blob/master/paranamer/src/java/com/thoughtworks/paranamer/BytecodeReadingParanamer.java
for example (though that is a stripped-down version of ASM, but the
same basic concept). But whether we reuse that or write our own, the
result would still be ~1,000 lines of low-level code for us to
maintain compared to letting the ASM experts do it for us. Does not
seem like a great use of time 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/CAFwNDjptU9hBk2%3D%3DcRV794%3DHi4rVFNP01xFgCL4GcrZ1zeda%3Dw%40mail.gmail.com.

Re: Google Summer of Code (GSoC) 2022: Call for organizers, mentors, and project ideas

[Alyssa Tong]

Hi,

I've started this doodle
https://doodle.com/poll/h7acxvmbuxrumpwn?utm_source=poll&utm_medium=link for
the GSoC knowledge transfer.  Pls vote for a date & time.  All are welcome
to join the call.

Thank you,
alyssa

On Tue, Jan 4, 2022 at 9:18 AM Alyssa Tong  wrote:

> Hi Oleg,
>
> You've suggested 4 great project ideas. Kris Stern is interested in
> co-mentoring the Jenkinsfile Runner Action for GitHub Actions, I will have
> you both down as mentors for this idea. As for the other 3 project ideas,
> if there's no other volunteers shall we skip them as to respect your time
> w/ family, etc.
>
> thanks,
> alyssa
>
> On Thu, Dec 16, 2021 at 1:43 AM Oleg Nenashev 
> wrote:
>
>> Hi Alyssa,
>>
>> Thanks a lot for taking care of it! I might be able to participate as org
>> admin in some capacity, but I cannot commit much time next year. My
>> personal situation is still complicated, and I'm not sure how much time I
>> will be able to dedicate to Jenkins in general. I will be also Ieading GSoC
>> in Keptn so I will definitely be around in the program.
>>
>> Regarding mentorship and potential projects, this year I will be
>> potentially available for the following projects/areas:
>>
>>- Improving Cloud Events plugin and aligning it with the emerging CD
>>Events Standard
>>- Jenkins and OpenTelemetry
>>- Jenkinsfile executor service for Keptn (powered by Jenkinsfile
>>Runner)
>>- Jenkinsfile Runner Action for GitHub Actions
>>
>> Let me know if anyone is interested in those projects :)
>>
>> Best regards,
>> Oleg
>> On Wednesday, December 15, 2021 at 2:23:28 AM UTC+1 alytong13 wrote:
>>
>>> Hi All,
>>>
>>> I have started this thread on HERE
>>> 
>>>  but thought i'd post it here as well.
>>>
>>> Much like the past 5 years, we are planning to participate in GSoC 2022
>>> .
>>>
>>> *About GSoC: *
>>>
>>> GSoC is a mentorship program focused on welcoming new contributors into
>>> the community and helping them learn best practices that will help them be
>>> long term OSS contributors.
>>>
>>> GSoC is an annual, global program that has been for college students. In
>>> 2022 GSoC is expanding its program to encourage all newcomers of open
>>> source that are 18 years and older. The program will no longer be solely
>>> focused on university students or recent graduates.
>>>
>>> *Important dates:*
>>>
>>>- Project application registration opens in February 2022
>>>- Registration for GSoC contributors opens in April 2022. See
>>>eligibility here 2 
>>>
>>> 2022 will be the sixth year the Jenkins project participates in GSoC. As
>>> we prepare for this program, we are *looking for volunteers in the
>>> following areas:*
>>>
>>>-
>>>
>>>Organization administrators (Org admins): This role is to make sure
>>>the Project Ideas list is solid. Org admins are the final authority about
>>>matters such as which GSoC contributor projects will be accepted, who 
>>> will
>>>mentor whom, and what the end date will be for a coding project.
>>>-
>>>
>>>Topics & Mentors: Here’s how to submit project ideas
>>>
>>>
>>> If you have any questions, or want to get involved, there is a Gitter
>>> channel  and a dedicated mailing
>>> list . Please
>>> join the Jenkins GSoC mailing list
>>>  if you would
>>> like to be kept up to date on GSoC information.
>>>
>>> Lastly, Oleg Nenashev, the driver of Jenkins GSoC for the past years,
>>> will be hosting a walk thru of GSoC best practices. This would be great if
>>> you’re thinking about joining me as an org admin. More to come on this soon.
>>>
>>> BR,
>>> alyssa
>>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Jenkins Developers" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to jenkinsci-dev+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-dev/458549a6-b88e-406c-874c-b203659b0d77n%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/CAC9wNaygxt5tpR6Ba0L1Zo86am0oAc2XZdnhnQoSHhMTyoGtyg%40mail.gmail.com.

Re: ASM in core

['Jesse Glick' via Jenkins Developers]

On Tue, Jan 4, 2022 at 5:22 PM Basil Crow  wrote:

> So should I look into the shading approach further?


That basically takes us back to the unfortunate state we were in with
Kohsuke’s series of shaded & repackaged ASM libraries, where we could not
give a clear answer as to what we were actually bundling, and security
scanners complained, etc. Not sure that is an improvement.

accomplish the shading by making a dedicated module for the shaded JAR, but
> I didn't quite follow the concept
>

Right, you sometimes get into trouble when you try to *use* the library
from the same Maven module that Shades it. Better to create a separate
module in the reactor which solely Shades the library, then depend on that
module from Stapler core.
https://github.com/jenkinsci/docker-traceability-plugin/pull/18 shows the
idea.

Another possibility is to write a minimal bytecode parser that just groks
the symbol table, list of methods with their binary signatures, and method
parameter metadata.

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

Re: ASM in core

[Basil Crow]

On Tue, Jan 4, 2022 at 1:05 PM 'Jesse Glick' via Jenkins Developers
 wrote:
>
> `access-modifier` is not a big deal since it is used only at compile 
> time—need not be shipped in core.

But as of jenkinsci/plugin-pom#480 plugins get their (compile time!)
access-modifier-annotation dependency from core, so even if we didn't
have to ship the ASM JAR in the WAR we'd still have to deal with
awkward Enforcer errors in plugins, which is definitely not ideal.

> The usage in Stapler is an obstacle.

So should I look into the shading approach further? I can't remember
what problems I ran into the last time I tried to do this with Guava,
but I found it quite difficult. I think at one point one of the
CloudBees Maven gurus recommended that I accomplish the shading by
making a dedicated module for the shaded JAR, but I didn't quite
follow the concept and I haven't been able to find any examples of
this online. If you have any pointers to a working example of this
approach that would definitely help.

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

Re: ASM in core

['Jesse Glick' via Jenkins Developers]

On Tue, Jan 4, 2022 at 3:07 PM Basil Crow  wrote:

> the only remaining consumers of ASM in core will be Stapler and
> access-modifier
>

`access-modifier` is not a big deal since it is used only at compile
time—need not be shipped in core.

The usage in Stapler is an obstacle. IIUC until a plugin is built with
https://github.com/jenkinsci/plugin-pom/releases/tag/plugin-4.19 or newer
(or explicitly specifies a name in `@QueryParameter`), some web methods
will fail to receive parameters, producing an error at
https://github.com/jenkinsci/stapler/blob/980e6ca1a29aa31cee1356e2a4e22ac5274a86fa/core/src/main/java/org/kohsuke/stapler/QueryParameter.java#L68
[sic] (or, rarely, in `@Header`).

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

Re: Java 11 as minimum? (Jetty 9.4.x EOL)

[Matt Sicker]

I’ll note the illegal reflection is only an issue starting with Java 16, and 
that can be “fixed” with some add-opens CLI options to Java. See for example 
how the ErrorProne compiler plugin requires several of those flags in a build 
with recent Java versions (and I’d expect similar for Lombok and other projects 
that access JDK internals).

—
Matt Sicker

> On Jan 4, 2022, at 09:34, Basil Crow  wrote:
> 
> On Mon, Jan 3, 2022 at 12:48 PM Mark Waite  wrote:
>> 
>> I think there are changes that are as yet undiscovered on the removal of 
>> Java 8 support.  I believe that finding and fixing those surprises will need 
>> more time.
> 
> We are already aware of issues with WebSockets (fixed), JAXB (fixed in
> all but the least used plugins), Linux agent installers (nobody seems
> to care), and illegal reflective access warnings (not blocking). I
> doubt we will discover many new issues with switching the _runtime_ to
> Java 11 in any but the least used plugins.
> 
> On the other hand, switching _builds_ and _tests_ to Java 11 does
> often require the usual plugin refresh process: updating the plugin
> parent POM and plugin BOM, dealing with Enforcer, updating the
> Jenkinsfile, adjusting annotations, tweaking mocks, suppressing
> SpotBugs false positives that only show up on Java 11, triaging
> miscellaneous test failures, etc. This seems to be the majority of the
> remaining work, but it does not affect end users.
> 
> I am not sure that additional time will incentivize the completion of
> the remaining work, whether it be production changes to long-tail
> plugins or build metadata updates. If a plugin is unmaintained or its
> maintainer has not yet refreshed it by June 2022, I doubt that this
> status will change by September 2022. If anything, delaying the
> release until September may (ironically) decrease the perceived need
> to take action on the part of plugin maintainers.
> 
> My point is not that risk does not exist, but that additional time is
> not likely to reduce risk. Therefore, I see no reason to wait until
> September.
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/CAFwNDjpespJqVCcHCqGUVK4QUQvv1UPd3Y%2BtM%2B2Ek5Hq39-rBA%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/870E34A5-9F72-4CAA-A00F-B03E7BA04CC6%40gmail.com.

Re: ASM in core

[Basil Crow]

Once JNR is removed from core in jenkinsci/jenkins#5979 (which is
blocked on the merge, release, and widespread adoption of
jenkinsci/pam-auth-plugin#20), then the only remaining consumers of
ASM in core will be Stapler [1] and access-modifier [2]. It would be
nice to eliminate these dependencies from core, which would allow us
to detach ASM to an API plugin. I think we all agree that keeping ASM
in core is a maintenance burden.

I suppose we could shade ASM into Stapler and access-modifier, but the
last time I tried to do this for Guava I ran into weird Maven issues
(MNG-5899?) and have not yet figured out a way to work around them.

If anyone can think of a more clever way to eliminate our dependency
on ASM, I would love to hear it.

[1] 
https://github.com/jenkinsci/stapler/blob/980e6ca1a29aa31cee1356e2a4e22ac5274a86fa/core/src/main/java/org/kohsuke/stapler/ClassDescriptor.java#L320-L407
[2] 
https://github.com/jenkinsci/lib-access-modifier/blob/b68c0122e7cfc4772fb2f8ab485b2157fdfa53f8/access-modifier-annotation/src/main/java/org/kohsuke/accmod/restrictions/ProtectedExternally.java#L64-L78

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

Google Summer of Code (GSoC)2022: Project ideas

[Alyssa Tong]

Hi All,

Happy New Year!

I wanted to share the project ideas as it stands at the moment. We are in
need of additional mentors, as shown below. And of course, additional
project ideas/mentors are welcome.

*1 - Jenkinsfile Runner Action for GitHub Actions *
Mentors: Oleg Nenashev, Kris Stern

*2 - Automatic Specification Generator for Jenkins REST API
*
Mentors: Kristin Whetstone, additional mentor(s) needed




*3 - Plugin Installation Manager Tool Improvements
*
Mentors
needed


*4
- Doc Generator *
Mentors: Mark Waite, additional mentor(s) needed

*5 - Configuration as Code Drift Detector*
Mentors: Jean-Marc Meessen, additional mentor(s) needed

BR,
alyssa

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

Re: Jakarta Mail and Jakarta Activation

['Jesse Glick' via Jenkins Developers]

On Tue, Jan 4, 2022 at 12:40 PM Basil Crow  wrote:

> I think the needs of the Jenkins project would be best served if we had
> the ability to merge and release PRs for those odds and ends, but this
> isn't simple to arrange because they generally live in Kohsuke's own
> GitHub organization rather than ours.
>

https://docs.google.com/document/d/1GRwJCfybnW8X273cPhOc2q4kdpqocX2zm_857DBGCY8/edit#heading=h.5vguh37qr0en
FYI

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

Re: Jakarta Mail and Jakarta Activation

[Tim Jacomb]

It’s no problem to get those transferred in, we did a few last year

Generally just raise an issue in the repo about transferring to jenkinsci
feel free to ping me on them

On Tue, 4 Jan 2022 at 17:40, Basil Crow  wrote:

> On Mon, Jan 3, 2022 at 12:57 PM Basil Crow  wrote:
> >
> > Yeah, there are 41 such plugins, the most notable of which are Mailer,
> > Email Extension, and Pipeline: Basic Steps.
>
> I maintain Email Extension, so I looked into migrating it to Jakarta
> Mail. Unfortunately the test suite depends on mock-javamail, which is
> an old Kohsuke project that (like args4j and a number of other odds
> and ends) does not seem to be as actively maintained as it once was. I
> think the needs of the Jenkins project would be best served if we had
> the ability to merge and release PRs for those odds and ends, but this
> isn't simple to arrange because they generally live in Kohsuke's own
> GitHub organization rather than ours. Needless to say, I am very
> grateful for Kohsuke's contributions and I do not mean to imply
> anything negative about the current state of affairs, but as he has
> stepped away from Jenkins it is becoming a bit of a pain point. I
> would love to help get these odds and ends back in shape in whatever
> way Kohsuke and the Jenkins project consider appropriate, regardless
> of which GitHub organization the repositories belong to.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/CAFwNDjppXutFmNOeAEuFNbtVmFAC0Rkyh--Wkjo5R%3DzhLu07wg%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-3BifeNvoXnzTFfNRMx_jLo16a8kNxgmFPCCaHXky%2BPtNcvQ%40mail.gmail.com.

Re: [jenkins-infra] Succession of timeouts during Docker actions on ci.jenkins.io

[Damien Duportal]

Thanks for reporting and pinging us!

I confirm that this timeout error is not related to the Jenkins Kubernetes 
plugin issue that we face on others Jenkins instances (it’s a VM agent with a 
Docker Engine in this case).
(The "fabric8" component from the error stack was misleading @Mark ;) ).


We (infra-team) started to check this issue earlier today, and we are on the 
process to reproduce it.

@Chris, If you have any way to configure the maven-docker plugin to report the 
equivalent of the commands `docker ps`, `docker logs ` and 
`docker inspect ` that would be awesome.
Also, if you can try to pull the latest moto image (which is the tag used) and 
see if it continues working on your environment?

=> On our side we will continue diagnostics tomorrow, by executing the commands 
on an ephemeral VM based on the same template as ci.jenkins.io 
 to see if we can reproduce the issue with the exact 
same tools (same kernel, same Docker, same Maven, same JDK). We’ll keep you 
updated.

Cheers

Damien

> Le 4 janv. 2022 à 17:47, Tim Jacomb  a écrit :
> 
> Hmm this isn’t what we were discussing though, this is using ci.Jenkins.io 
>  which uses a different cluster as far as I know
> 
> Cc infra
> 
> On Tue, 4 Jan 2022 at 15:19, Mark Waite  > wrote:
> 
> 
> On Tuesday, January 4, 2022 at 5:57:04 AM UTC-7 Chris Kilding wrote:
> Hi, 
> 
> Timeouts related to the Docker Maven Plugin are causing some plugin builds to 
> fail on ci.jenkins.io . The error message is usually 
> along the lines of: 
> 
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute 
> goal io.fabric8:docker-maven-plugin:0.38.0:start (start-moto) on project 
> : I/O Error 
> 
> 
> 
> Yes.  The Azure Kubernetes Service made a change in December that amplified 
> some existing issues in the Jenkins public kubernetes cluster.  The infra 
> team is actively working to resolve the issue.
> 
> It was discussed in today's infra team meeting.  A recording of the infra 
> team meeting should be available on community.jenkins.io 
>  within the next 24-36 hours.
> 
> 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/5cfb6653-2b8c-4449-b2d5-ccae2e5a1a3cn%40googlegroups.com
>  
> .
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Jenkins Infrastructure" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to jenkins-infra+unsubscr...@googlegroups.com 
> .
> To view this discussion on the web, visit 
> https://groups.google.com/d/msgid/jenkins-infra/CAH-3Bie4Gd2ueR7Hma9%2ByGrnCN-abUABcwTQbCgzjkkXqydf8Q%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/D5EBFC89-7612-4BC0-A940-BF9211A6D514%40gmail.com.

Re: Jakarta Mail and Jakarta Activation

[Basil Crow]

On Mon, Jan 3, 2022 at 12:57 PM Basil Crow  wrote:
>
> Yeah, there are 41 such plugins, the most notable of which are Mailer,
> Email Extension, and Pipeline: Basic Steps.

I maintain Email Extension, so I looked into migrating it to Jakarta
Mail. Unfortunately the test suite depends on mock-javamail, which is
an old Kohsuke project that (like args4j and a number of other odds
and ends) does not seem to be as actively maintained as it once was. I
think the needs of the Jenkins project would be best served if we had
the ability to merge and release PRs for those odds and ends, but this
isn't simple to arrange because they generally live in Kohsuke's own
GitHub organization rather than ours. Needless to say, I am very
grateful for Kohsuke's contributions and I do not mean to imply
anything negative about the current state of affairs, but as he has
stepped away from Jenkins it is becoming a bit of a pain point. I
would love to help get these odds and ends back in shape in whatever
way Kohsuke and the Jenkins project consider appropriate, regardless
of which GitHub organization the repositories belong to.

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

Re: New Year blogpost for Jenkins

[Mark Waite]

On Tue, Jan 4, 2022 at 10:06 AM 'Gavin Mogan' via Jenkins Developers <
jenkinsci-dev@googlegroups.com> wrote:

> I was thinking about it last night. We got a few new sponsors this year
>
> * netlify
> * digital ocean
> * 1password
>
> probably more, would be nice to mention them
>
>
Thanks for the reminder!  Yes, I'll include a section of thanks for the new
and renewed sponsors.  Will need to check the sponsorship dates to be sure
the post is accurate, but Algolia for search, Netlify for status site and
preview sites, 1password for securing passwords, Oracle for
archives.jenkins.io, Digital Ocean for Kubernetes agents, and more,.

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

Re: Google Summer of Code (GSoC) 2022: Call for organizers, mentors, and project ideas

[Alyssa Tong]

Hi Oleg,

You've suggested 4 great project ideas. Kris Stern is interested in
co-mentoring the Jenkinsfile Runner Action for GitHub Actions, I will have
you both down as mentors for this idea. As for the other 3 project ideas,
if there's no other volunteers shall we skip them as to respect your time
w/ family, etc.

thanks,
alyssa

On Thu, Dec 16, 2021 at 1:43 AM Oleg Nenashev 
wrote:

> Hi Alyssa,
>
> Thanks a lot for taking care of it! I might be able to participate as org
> admin in some capacity, but I cannot commit much time next year. My
> personal situation is still complicated, and I'm not sure how much time I
> will be able to dedicate to Jenkins in general. I will be also Ieading GSoC
> in Keptn so I will definitely be around in the program.
>
> Regarding mentorship and potential projects, this year I will be
> potentially available for the following projects/areas:
>
>- Improving Cloud Events plugin and aligning it with the emerging CD
>Events Standard
>- Jenkins and OpenTelemetry
>- Jenkinsfile executor service for Keptn (powered by Jenkinsfile
>Runner)
>- Jenkinsfile Runner Action for GitHub Actions
>
> Let me know if anyone is interested in those projects :)
>
> Best regards,
> Oleg
> On Wednesday, December 15, 2021 at 2:23:28 AM UTC+1 alytong13 wrote:
>
>> Hi All,
>>
>> I have started this thread on HERE
>> 
>>  but thought i'd post it here as well.
>>
>> Much like the past 5 years, we are planning to participate in GSoC 2022
>> .
>>
>> *About GSoC: *
>>
>> GSoC is a mentorship program focused on welcoming new contributors into
>> the community and helping them learn best practices that will help them be
>> long term OSS contributors.
>>
>> GSoC is an annual, global program that has been for college students. In
>> 2022 GSoC is expanding its program to encourage all newcomers of open
>> source that are 18 years and older. The program will no longer be solely
>> focused on university students or recent graduates.
>>
>> *Important dates:*
>>
>>- Project application registration opens in February 2022
>>- Registration for GSoC contributors opens in April 2022. See
>>eligibility here 2 
>>
>> 2022 will be the sixth year the Jenkins project participates in GSoC. As
>> we prepare for this program, we are *looking for volunteers in the
>> following areas:*
>>
>>-
>>
>>Organization administrators (Org admins): This role is to make sure
>>the Project Ideas list is solid. Org admins are the final authority about
>>matters such as which GSoC contributor projects will be accepted, who will
>>mentor whom, and what the end date will be for a coding project.
>>-
>>
>>Topics & Mentors: Here’s how to submit project ideas
>>
>>
>> If you have any questions, or want to get involved, there is a Gitter
>> channel  and a dedicated mailing
>> list . Please
>> join the Jenkins GSoC mailing list
>>  if you would
>> like to be kept up to date on GSoC information.
>>
>> Lastly, Oleg Nenashev, the driver of Jenkins GSoC for the past years,
>> will be hosting a walk thru of GSoC best practices. This would be great if
>> you’re thinking about joining me as an org admin. More to come on this soon.
>>
>> BR,
>> alyssa
>>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/458549a6-b88e-406c-874c-b203659b0d77n%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/CAC9wNazjPCtLp6YALZbLXKs%2BVmn2qxxBGeo94nVgVrjhC2UCoQ%40mail.gmail.com.

Re: Fwd: Succession of timeouts during Docker actions on ci.jenkins.io

[Chris Kilding]

Mark - good to know that there has been an AKS change, I'll stay tuned for 
updates from the infra team.

Jesse - Thanks for the Testcontainers suggestion. The way the Docker containers 
are spun up in the test suite hasn't changed in a long time, so I'll give this 
a go and see if it helps.

Chris

On Tue, 4 Jan 2022, at 5:01 PM, 'Jesse Glick' via Jenkins Developers wrote:
> [Somehow did not get sent to the list. Reposting:]
> 
> On Tue, Jan 4, 2022 at 7:57 AM Chris Kilding  > wrote:
>> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute 
>> goal io.fabric8:docker-maven-plugin:0.38.0:start (start-moto) on project 
>> : I/O Error
> 
> This is rather opaque. The console log suggests some error during container 
> start but does not give details.
> 
> No other plugin I am aware of uses `docker-maven-plugin` for ITs this way. 
> The normal idiom is to use Testcontainers, which (unlike 
> `AWSSecretsManagerRule`) will automatically start the test service as part of 
> the test itself (no need for `maven-failsafe-plugin`) on any free server 
> port. May be worth experimenting with other ways of running Docker from your 
> tests, in case the problem is specific to `docker-maven-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/CANfRfr3f9fxROvx5vQhK5e%3DhDZouTAUDR%3DJBawjfPf4nz2xuBw%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/a2d64bd5-a254-4129-82f7-11b6ec7934ac%40www.fastmail.com.

Re: New Year blogpost for Jenkins

['Gavin Mogan' via Jenkins Developers]

I was thinking about it last night. We got a few new sponsors this year

* netlify
* digital ocean
* 1password

probably more, would be nice to mention them

On Mon, Jan 3, 2022 at 4:59 PM Mark Waite  wrote:
>
> I placed the New Year blogpost on the Docs Office Hours agenda for this week. 
>  Will be discussed during the Asia / Pacific hours in the next 2 hours, then 
> will be discussed again during Europe / Americas hours on Thursday.
>
> See the Jenkins calendar for the precise times of Docs Office Hours.
>
> Mark Waite
>
> On Friday, December 24, 2021 at 7:42:00 AM UTC-7 Mark Waite wrote:
>>
>> On Friday, December 24, 2021 at 7:14:05 AM UTC-7 Oleg Nenashev wrote:
>>>
>>> Hi all,
>>>
>>> So the New Year's coming soon. So now we will need a yearly a report for 
>>> the Continuous Delivery Foundation. I guess we would like to have a 
>>> standard Jenkins blog post this year, right?
>>>
>>> Would anyone be interested to contribute to this blog post? I might be able 
>>> to coordinate the effort though I'm not sure this is very appropriate. I 
>>> haven't been as active for in the community this year as used to be before.
>>>
>>
>> Thanks for the reminder!  I'd like to contribute to that blog post.  I think 
>> we have many things to highlight for this year, including:
>>
>> Outreach events
>>
>> 5 completed projects in Google Summer of Code
>> Over 90 pull requests from Hacktoberfest contributors
>> 5 women in Africa mentored by the She Code Africa contributhon
>> 4 students mentored in master project for Jenkins security
>>
>> New features
>>
>> Configuration form modernization
>> Spring and XStream upgrades
>> Guava upgrade
>> Java 11 now the default in Docker images
>> 6 plugins adopted by contributors
>>
>> Security fixes and improvements
>>
>> 19 security advisories published
>> Apache Log4j 2 incident managed
>>
>> Plugins and Documentation
>>
>> Confluence wiki attack mitigated
>> Plugins site search and documentation site search
>> 38 blog posts
>> Documentation for 200 more plugins migrated to GitHub
>>
>> Social
>>
>> Community.jenkins.io is growing
>> 3000 more followers on Twitter
>> 13000 more followers on LinkedIn
>> Over 9 views on YouTube
>> IRC chat moved to Libera chat
>>
>> I'm open to other highlights that should be noted in the blog post.
>>
>>
>>> Best regards,
>>> Oleg Nenashev
>
> --
> You received this message because you are subscribed to the Google Groups 
> "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to jenkinsci-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/54c9aad0-a87c-456d-9cf1-783e809cd96an%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_Duswcs04F64QXtj6hMRPLm83kj5o-p-5MLxopWj%2BeohiuQ%40mail.gmail.com.

Fwd: Succession of timeouts during Docker actions on ci.jenkins.io

['Jesse Glick' via Jenkins Developers]

[Somehow did not get sent to the list. Reposting:]

On Tue, Jan 4, 2022 at 7:57 AM Chris Kilding 
wrote:

> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal io.fabric8:docker-maven-plugin:0.38.0:start (start-moto) on project
> : I/O Error
>

This is rather opaque. The console log suggests some error during container
start but does not give details.

No other plugin I am aware of uses `docker-maven-plugin` for ITs this way.
The normal idiom is to use Testcontainers, which (unlike
`AWSSecretsManagerRule`) will automatically start the test service as part
of the test itself (no need for `maven-failsafe-plugin`) on any free server
port. May be worth experimenting with other ways of running Docker from
your tests, in case the problem is specific to `docker-maven-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/CANfRfr3f9fxROvx5vQhK5e%3DhDZouTAUDR%3DJBawjfPf4nz2xuBw%40mail.gmail.com.

Re: Succession of timeouts during Docker actions on ci.jenkins.io

[Tim Jacomb]

Hmm this isn’t what we were discussing though, this is using ci.Jenkins.io
which uses a different cluster as far as I know

Cc infra

On Tue, 4 Jan 2022 at 15:19, Mark Waite  wrote:

>
>
> On Tuesday, January 4, 2022 at 5:57:04 AM UTC-7 Chris Kilding wrote:
>
>> Hi,
>>
>> Timeouts related to the Docker Maven Plugin are causing some plugin
>> builds to fail on ci.jenkins.io. The error message is usually along the
>> lines of:
>>
>> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
>> goal io.fabric8:docker-maven-plugin:0.38.0:start (start-moto) on project
>> : I/O Error
>>
>>
>>
> Yes.  The Azure Kubernetes Service made a change in December that
> amplified some existing issues in the Jenkins public kubernetes cluster.
> The infra team is actively working to resolve the issue.
>
> It was discussed in today's infra team meeting.  A recording of the infra
> team meeting should be available on community.jenkins.io within the next
> 24-36 hours.
>
> 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/5cfb6653-2b8c-4449-b2d5-ccae2e5a1a3cn%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-3Bie4Gd2ueR7Hma9%2ByGrnCN-abUABcwTQbCgzjkkXqydf8Q%40mail.gmail.com.

Re: Google Summer of Code (GSoC) 2022: Call for organizers, mentors, and project ideas

[Alyssa Tong]

thank you for the doc Oleg

On Tue, Jan 4, 2022 at 7:49 AM Oleg Nenashev  wrote:

> Sure, and welcome back Alyssa!
>
> I agree with Jean-Marc that some async updates to the guidelines would be
> awesome. Note that the Jenkins GSoC org admin runbook (referenced from the
> Jenkins GSoC project main page) is available here and is waiting for
> comments/questions:
> https://docs.google.com/document/d/1AeeIBfzst3VeI-hdRNlfPvp8NgcGneqI2uEkQoZ88q4/edit?usp=sharing
> . I will not be able to work on it until Jan 13+ as well, but I might be
> able to address some comments and questions if any
>
> BR, Oleg
>
>
>
>
> On Tue, Jan 4, 2022 at 4:41 PM Alyssa Tong  wrote:
>
>> Hi Oleg et al,
>>
>> Happy 2022 😊
>> I was on a much needed Christmas break and am now back.  I'm picking this
>> back up, pls standby for additional communications on this today as i'll
>> try to move this forward to next steps.
>>
>> Apologies for the delay.
>>
>> alyssa
>>
>> On Tue, Jan 4, 2022 at 6:55 AM Jean-Marc Meessen <
>> jean-m...@meessen-web.org> wrote:
>>
>>> Hello Oleg,
>>>
>>> Thank you for your interest and dedication on making GSoC 2022 a success
>>> for the Jenkins Project. It is good to know that you will be available to
>>> contribute from January 13th.
>>>
>>> Please note that neither Alyssa nor Mark are back from the Christmas/New
>>> Year break (circumstances made it a long break).
>>>
>>> Seen the heavy timezone and personal availability contrains, an
>>> asynchronous hand-over seems best suited. Any written hand-over or coaching
>>> would thus help.
>>>
>>> WDYT?
>>>
>>> /- Jmm
>>>
>>> On Monday, 3 January 2022 at 18:05:51 UTC+1 Oleg Nenashev wrote:
>>>
 Hi all,

 So the Christmas break is over, and we should return to this topic as
 soon as possible. Currently we are not ready to work with students who
 already go to our website. We have not archived the previous year
 properly,  we don't have a list of project ideas for the upcoming year.
 When I was sent to the garden leave by my previous company, Mark Waite took
 an action to coordinate that. I guess there were other more important
 topics, but now it is critical if you want to have a good students
 contributing to the project. We already lose them, because the most
 successful students start looking into Google summer of code before the
 Christmas.

 If Alyssa and Jean-Marc are not available to work on that and to
 organize knowledge transfers as we agreed one month ago, I will take over
 this task after January 13th. I cannot work on that earlier due to the
 personal reasons (important court hearings).

 Best regards,
 Oleg Nenashev




 On Sat, 25 Dec 2021, 13:09 Oleg Nenashev,  wrote:

> It is not enough to send an email to get org admins or mentors
> unfortunately.
> A little bit more effort and direct outreach is needed.
>
> On Monday, December 20, 2021 at 5:06:56 PM UTC+1 alytong13 wrote:
>
>> Hi Oleg,
>>
>> The knowledge transfer was mentioned in my original email, I didn't
>> see volunteers for org admins. Nonetheless, let me follow up w/ a doodle
>> for timing, for after the new years, and we'll take it from there.
>>
>> Thank you,
>> alyssa
>>
>> On Sat, Dec 18, 2021 at 4:35 AM Oleg Nenashev 
>> wrote:
>>
>>> Hello Alyssa and Jean-Marc,
>>>
>>> Did you have a chance to start a poll for the knowledge transfer
>>> meeting, and maybe a first coordination one?
>>>
>>> Taking the timing, it is very unlikely that it's going to happen
>>> before the new year at this stage
>>>
>>> Best regards,
>>> Oleg
>>>
>>> On Thu, 16 Dec 2021, 19:50 Alyssa Tong,  wrote:
>>>
 Thank you Kris and Oleg for your responses.  Your inputs are noted
 and I will circle back once we have more on project ideas and mentors.

 BR,
 alyssa

 On Thu, Dec 16, 2021 at 3:42 AM Kris Stern 
 wrote:

> Hi Alyssa and Oleg,
>
> I am interested in volunteering and mentoring in GSoC 2022 for
> Jenkins. In particular, I would like to work on the project idea
> "Jenkinsfile Runner Action for GitHub Actions" as listed in Oleg's 
> email.
>
> Maybe I should introduce myself a bit to begin. I started
> contributing to open-source in late 2018/early 2019, first working on 
> some
> astronomy software development, as my PhD project was in astrophysics 
> then.
> Also, I was previously a GSoC contributor in 2019 and 2020, working 
> under
> the mentorship of OpenAstronomy, and was able to successfully 
> complete both
> projects. Professionally currently I work in the IT sector, on 
> software
> engineering. I am based in Hong Kong, but am comfortable working 
> 

Re: Google Summer of Code (GSoC) 2022: Call for organizers, mentors, and project ideas

[Oleg Nenashev]

Sure, and welcome back Alyssa!

I agree with Jean-Marc that some async updates to the guidelines would be
awesome. Note that the Jenkins GSoC org admin runbook (referenced from the
Jenkins GSoC project main page) is available here and is waiting for
comments/questions:
https://docs.google.com/document/d/1AeeIBfzst3VeI-hdRNlfPvp8NgcGneqI2uEkQoZ88q4/edit?usp=sharing
. I will not be able to work on it until Jan 13+ as well, but I might be
able to address some comments and questions if any

BR, Oleg




On Tue, Jan 4, 2022 at 4:41 PM Alyssa Tong  wrote:

> Hi Oleg et al,
>
> Happy 2022 😊
> I was on a much needed Christmas break and am now back.  I'm picking this
> back up, pls standby for additional communications on this today as i'll
> try to move this forward to next steps.
>
> Apologies for the delay.
>
> alyssa
>
> On Tue, Jan 4, 2022 at 6:55 AM Jean-Marc Meessen <
> jean-m...@meessen-web.org> wrote:
>
>> Hello Oleg,
>>
>> Thank you for your interest and dedication on making GSoC 2022 a success
>> for the Jenkins Project. It is good to know that you will be available to
>> contribute from January 13th.
>>
>> Please note that neither Alyssa nor Mark are back from the Christmas/New
>> Year break (circumstances made it a long break).
>>
>> Seen the heavy timezone and personal availability contrains, an
>> asynchronous hand-over seems best suited. Any written hand-over or coaching
>> would thus help.
>>
>> WDYT?
>>
>> /- Jmm
>>
>> On Monday, 3 January 2022 at 18:05:51 UTC+1 Oleg Nenashev wrote:
>>
>>> Hi all,
>>>
>>> So the Christmas break is over, and we should return to this topic as
>>> soon as possible. Currently we are not ready to work with students who
>>> already go to our website. We have not archived the previous year
>>> properly,  we don't have a list of project ideas for the upcoming year.
>>> When I was sent to the garden leave by my previous company, Mark Waite took
>>> an action to coordinate that. I guess there were other more important
>>> topics, but now it is critical if you want to have a good students
>>> contributing to the project. We already lose them, because the most
>>> successful students start looking into Google summer of code before the
>>> Christmas.
>>>
>>> If Alyssa and Jean-Marc are not available to work on that and to
>>> organize knowledge transfers as we agreed one month ago, I will take over
>>> this task after January 13th. I cannot work on that earlier due to the
>>> personal reasons (important court hearings).
>>>
>>> Best regards,
>>> Oleg Nenashev
>>>
>>>
>>>
>>>
>>> On Sat, 25 Dec 2021, 13:09 Oleg Nenashev,  wrote:
>>>
 It is not enough to send an email to get org admins or mentors
 unfortunately.
 A little bit more effort and direct outreach is needed.

 On Monday, December 20, 2021 at 5:06:56 PM UTC+1 alytong13 wrote:

> Hi Oleg,
>
> The knowledge transfer was mentioned in my original email, I didn't
> see volunteers for org admins. Nonetheless, let me follow up w/ a doodle
> for timing, for after the new years, and we'll take it from there.
>
> Thank you,
> alyssa
>
> On Sat, Dec 18, 2021 at 4:35 AM Oleg Nenashev 
> wrote:
>
>> Hello Alyssa and Jean-Marc,
>>
>> Did you have a chance to start a poll for the knowledge transfer
>> meeting, and maybe a first coordination one?
>>
>> Taking the timing, it is very unlikely that it's going to happen
>> before the new year at this stage
>>
>> Best regards,
>> Oleg
>>
>> On Thu, 16 Dec 2021, 19:50 Alyssa Tong,  wrote:
>>
>>> Thank you Kris and Oleg for your responses.  Your inputs are noted
>>> and I will circle back once we have more on project ideas and mentors.
>>>
>>> BR,
>>> alyssa
>>>
>>> On Thu, Dec 16, 2021 at 3:42 AM Kris Stern 
>>> wrote:
>>>
 Hi Alyssa and Oleg,

 I am interested in volunteering and mentoring in GSoC 2022 for
 Jenkins. In particular, I would like to work on the project idea
 "Jenkinsfile Runner Action for GitHub Actions" as listed in Oleg's 
 email.

 Maybe I should introduce myself a bit to begin. I started
 contributing to open-source in late 2018/early 2019, first working on 
 some
 astronomy software development, as my PhD project was in astrophysics 
 then.
 Also, I was previously a GSoC contributor in 2019 and 2020, working 
 under
 the mentorship of OpenAstronomy, and was able to successfully complete 
 both
 projects. Professionally currently I work in the IT sector, on software
 engineering. I am based in Hong Kong, but am comfortable working around
 different time zones outside of the Asia Pacific (or APAC) area.

 Please let me know how I may proceed further.

 Thanks!

 Best,
 Kris Stern, PhD

 --

Re: Google Summer of Code (GSoC) 2022: Call for organizers, mentors, and project ideas

[Alyssa Tong]

Hi Oleg et al,

Happy 2022 😊
I was on a much needed Christmas break and am now back.  I'm picking this
back up, pls standby for additional communications on this today as i'll
try to move this forward to next steps.

Apologies for the delay.

alyssa

On Tue, Jan 4, 2022 at 6:55 AM Jean-Marc Meessen 
wrote:

> Hello Oleg,
>
> Thank you for your interest and dedication on making GSoC 2022 a success
> for the Jenkins Project. It is good to know that you will be available to
> contribute from January 13th.
>
> Please note that neither Alyssa nor Mark are back from the Christmas/New
> Year break (circumstances made it a long break).
>
> Seen the heavy timezone and personal availability contrains, an
> asynchronous hand-over seems best suited. Any written hand-over or coaching
> would thus help.
>
> WDYT?
>
> /- Jmm
>
> On Monday, 3 January 2022 at 18:05:51 UTC+1 Oleg Nenashev wrote:
>
>> Hi all,
>>
>> So the Christmas break is over, and we should return to this topic as
>> soon as possible. Currently we are not ready to work with students who
>> already go to our website. We have not archived the previous year
>> properly,  we don't have a list of project ideas for the upcoming year.
>> When I was sent to the garden leave by my previous company, Mark Waite took
>> an action to coordinate that. I guess there were other more important
>> topics, but now it is critical if you want to have a good students
>> contributing to the project. We already lose them, because the most
>> successful students start looking into Google summer of code before the
>> Christmas.
>>
>> If Alyssa and Jean-Marc are not available to work on that and to organize
>> knowledge transfers as we agreed one month ago, I will take over this task
>> after January 13th. I cannot work on that earlier due to the personal
>> reasons (important court hearings).
>>
>> Best regards,
>> Oleg Nenashev
>>
>>
>>
>>
>> On Sat, 25 Dec 2021, 13:09 Oleg Nenashev,  wrote:
>>
>>> It is not enough to send an email to get org admins or mentors
>>> unfortunately.
>>> A little bit more effort and direct outreach is needed.
>>>
>>> On Monday, December 20, 2021 at 5:06:56 PM UTC+1 alytong13 wrote:
>>>
 Hi Oleg,

 The knowledge transfer was mentioned in my original email, I didn't see
 volunteers for org admins. Nonetheless, let me follow up w/ a doodle for
 timing, for after the new years, and we'll take it from there.

 Thank you,
 alyssa

 On Sat, Dec 18, 2021 at 4:35 AM Oleg Nenashev 
 wrote:

> Hello Alyssa and Jean-Marc,
>
> Did you have a chance to start a poll for the knowledge transfer
> meeting, and maybe a first coordination one?
>
> Taking the timing, it is very unlikely that it's going to happen
> before the new year at this stage
>
> Best regards,
> Oleg
>
> On Thu, 16 Dec 2021, 19:50 Alyssa Tong,  wrote:
>
>> Thank you Kris and Oleg for your responses.  Your inputs are noted
>> and I will circle back once we have more on project ideas and mentors.
>>
>> BR,
>> alyssa
>>
>> On Thu, Dec 16, 2021 at 3:42 AM Kris Stern 
>> wrote:
>>
>>> Hi Alyssa and Oleg,
>>>
>>> I am interested in volunteering and mentoring in GSoC 2022 for
>>> Jenkins. In particular, I would like to work on the project idea
>>> "Jenkinsfile Runner Action for GitHub Actions" as listed in Oleg's 
>>> email.
>>>
>>> Maybe I should introduce myself a bit to begin. I started
>>> contributing to open-source in late 2018/early 2019, first working on 
>>> some
>>> astronomy software development, as my PhD project was in astrophysics 
>>> then.
>>> Also, I was previously a GSoC contributor in 2019 and 2020, working 
>>> under
>>> the mentorship of OpenAstronomy, and was able to successfully complete 
>>> both
>>> projects. Professionally currently I work in the IT sector, on software
>>> engineering. I am based in Hong Kong, but am comfortable working around
>>> different time zones outside of the Asia Pacific (or APAC) area.
>>>
>>> Please let me know how I may proceed further.
>>>
>>> Thanks!
>>>
>>> Best,
>>> Kris Stern, PhD
>>>
>>> --
>>> *From:* jenkin...@googlegroups.com  on
>>> behalf of Oleg Nenashev 
>>> *Sent:* 16 December 2021 17:43
>>> *To:* Jenkins Developers 
>>> *Subject:* Re: Google Summer of Code (GSoC) 2022: Call for
>>> organizers, mentors, and project ideas
>>>
>>> Hi Alyssa,
>>>
>>> Thanks a lot for taking care of it! I might be able to participate
>>> as org admin in some capacity, but I cannot commit much time next year. 
>>> My
>>> personal situation is still complicated, and I'm not sure how much time 
>>> I
>>> will be able to dedicate to Jenkins in general. I will be also Ieading 
>>> GSoC
>>> in Keptn so I will definitely be around

Re: Java 11 as minimum? (Jetty 9.4.x EOL)

[Basil Crow]

On Mon, Jan 3, 2022 at 12:48 PM Mark Waite  wrote:
>
> I think there are changes that are as yet undiscovered on the removal of Java 
> 8 support.  I believe that finding and fixing those surprises will need more 
> time.

We are already aware of issues with WebSockets (fixed), JAXB (fixed in
all but the least used plugins), Linux agent installers (nobody seems
to care), and illegal reflective access warnings (not blocking). I
doubt we will discover many new issues with switching the _runtime_ to
Java 11 in any but the least used plugins.

On the other hand, switching _builds_ and _tests_ to Java 11 does
often require the usual plugin refresh process: updating the plugin
parent POM and plugin BOM, dealing with Enforcer, updating the
Jenkinsfile, adjusting annotations, tweaking mocks, suppressing
SpotBugs false positives that only show up on Java 11, triaging
miscellaneous test failures, etc. This seems to be the majority of the
remaining work, but it does not affect end users.

I am not sure that additional time will incentivize the completion of
the remaining work, whether it be production changes to long-tail
plugins or build metadata updates. If a plugin is unmaintained or its
maintainer has not yet refreshed it by June 2022, I doubt that this
status will change by September 2022. If anything, delaying the
release until September may (ironically) decrease the perceived need
to take action on the part of plugin maintainers.

My point is not that risk does not exist, but that additional time is
not likely to reduce risk. Therefore, I see no reason to wait until
September.

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

Re: Succession of timeouts during Docker actions on ci.jenkins.io

[Mark Waite]

On Tuesday, January 4, 2022 at 5:57:04 AM UTC-7 Chris Kilding wrote:

> Hi, 
>
> Timeouts related to the Docker Maven Plugin are causing some plugin builds 
> to fail on ci.jenkins.io. The error message is usually along the lines 
> of: 
>
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute 
> goal io.fabric8:docker-maven-plugin:0.38.0:start (start-moto) on project 
> : I/O Error 
>
>
>
Yes.  The Azure Kubernetes Service made a change in December that amplified 
some existing issues in the Jenkins public kubernetes cluster.  The infra 
team is actively working to resolve the issue.

It was discussed in today's infra team meeting.  A recording of the infra 
team meeting should be available on community.jenkins.io within the next 
24-36 hours.

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/5cfb6653-2b8c-4449-b2d5-ccae2e5a1a3cn%40googlegroups.com.

Re: Google Summer of Code (GSoC) 2022: Call for organizers, mentors, and project ideas

[Jean-Marc Meessen]

Hello Oleg,

Thank you for your interest and dedication on making GSoC 2022 a success 
for the Jenkins Project. It is good to know that you will be available to 
contribute from January 13th.

Please note that neither Alyssa nor Mark are back from the Christmas/New 
Year break (circumstances made it a long break).

Seen the heavy timezone and personal availability contrains, an 
asynchronous hand-over seems best suited. Any written hand-over or coaching 
would thus help.

WDYT?

/- Jmm

On Monday, 3 January 2022 at 18:05:51 UTC+1 Oleg Nenashev wrote:

> Hi all,
>
> So the Christmas break is over, and we should return to this topic as soon 
> as possible. Currently we are not ready to work with students who already 
> go to our website. We have not archived the previous year properly,  we 
> don't have a list of project ideas for the upcoming year. When I was sent 
> to the garden leave by my previous company, Mark Waite took an action to 
> coordinate that. I guess there were other more important topics, but now it 
> is critical if you want to have a good students contributing to the 
> project. We already lose them, because the most successful students start 
> looking into Google summer of code before the Christmas.
>
> If Alyssa and Jean-Marc are not available to work on that and to organize 
> knowledge transfers as we agreed one month ago, I will take over this task 
> after January 13th. I cannot work on that earlier due to the personal 
> reasons (important court hearings).
>
> Best regards,
> Oleg Nenashev
>
>
>
>
> On Sat, 25 Dec 2021, 13:09 Oleg Nenashev,  wrote:
>
>> It is not enough to send an email to get org admins or mentors 
>> unfortunately.
>> A little bit more effort and direct outreach is needed.
>>
>> On Monday, December 20, 2021 at 5:06:56 PM UTC+1 alytong13 wrote:
>>
>>> Hi Oleg,
>>>
>>> The knowledge transfer was mentioned in my original email, I didn't see 
>>> volunteers for org admins. Nonetheless, let me follow up w/ a doodle for 
>>> timing, for after the new years, and we'll take it from there.
>>>
>>> Thank you,
>>> alyssa
>>>
>>> On Sat, Dec 18, 2021 at 4:35 AM Oleg Nenashev  
>>> wrote:
>>>
 Hello Alyssa and Jean-Marc,

 Did you have a chance to start a poll for the knowledge transfer 
 meeting, and maybe a first coordination one?

 Taking the timing, it is very unlikely that it's going to happen before 
 the new year at this stage

 Best regards,
 Oleg

 On Thu, 16 Dec 2021, 19:50 Alyssa Tong,  wrote:

> Thank you Kris and Oleg for your responses.  Your inputs are noted and 
> I will circle back once we have more on project ideas and mentors. 
>
> BR,
> alyssa
>
> On Thu, Dec 16, 2021 at 3:42 AM Kris Stern  
> wrote:
>
>> Hi Alyssa and Oleg,
>>
>> I am interested in volunteering and mentoring in GSoC 2022 for 
>> Jenkins. In particular, I would like to work on the project idea 
>> "Jenkinsfile Runner Action for GitHub Actions" as listed in Oleg's 
>> email. 
>>
>> Maybe I should introduce myself a bit to begin. I started 
>> contributing to open-source in late 2018/early 2019, first working on 
>> some 
>> astronomy software development, as my PhD project was in astrophysics 
>> then. 
>> Also, I was previously a GSoC contributor in 2019 and 2020, working 
>> under 
>> the mentorship of OpenAstronomy, and was able to successfully complete 
>> both 
>> projects. Professionally currently I work in the IT sector, on software 
>> engineering. I am based in Hong Kong, but am comfortable working around 
>> different time zones outside of the Asia Pacific (or APAC) area. 
>>
>> Please let me know how I may proceed further. 
>>
>> Thanks!
>>
>> Best,
>> Kris Stern, PhD
>>
>> --
>> *From:* jenkin...@googlegroups.com  on 
>> behalf of Oleg Nenashev 
>> *Sent:* 16 December 2021 17:43
>> *To:* Jenkins Developers 
>> *Subject:* Re: Google Summer of Code (GSoC) 2022: Call for 
>> organizers, mentors, and project ideas 
>>  
>> Hi Alyssa,
>>
>> Thanks a lot for taking care of it! I might be able to participate as 
>> org admin in some capacity, but I cannot commit much time next year. My 
>> personal situation is still complicated, and I'm not sure how much time 
>> I 
>> will be able to dedicate to Jenkins in general. I will be also Ieading 
>> GSoC 
>> in Keptn so I will definitely be around in the program.
>>
>> Regarding mentorship and potential projects, this year I will be 
>> potentially available for the following projects/areas:
>>
>>- Improving Cloud Events plugin and aligning it with the emerging 
>>CD Events Standard
>>- Jenkins and OpenTelemetry
>>- Jenkinsfile executor service for Keptn (powered by Jenkinsfile 
>>Runner)
>>

Re: Backward compatibility policy regarding dependent plugins

['Jesse Glick' via Jenkins Developers]

On Tue, Jan 4, 2022 at 3:15 AM 'Réda Housni Alaoui' via Jenkins Developers <
jenkinsci-dev@googlegroups.com> wrote:

> I guess at least @DataBoundSetter and @DataBoundConstructor would have to
> be kept for pipeline scripts.
>

If you are talking about a `Step` or a `Describable` used by one, yes that
would be required for backward compatibility with existing Pipeline script.
You are advised to write a `JenkinsRule`-based test (which passes against
the former code) that defines a script (`WorkflowJob` /
`CpsFlowDefinition`) using the affected fields, `buildAndAssertSuccess`,
and assert that the settings were used. `SnippetizerTester` (add a test dep
on the `tests` classifier of `workflow-cps`) is also helpful for validating
unusual or complex cases.

For configuration used in other parts of Jenkins, including build steps in
traditional job types (`config.xml`) as well as global/folder/etc.
settings, what matters is not these methods but the serial form of fields
as determined by XStream, which you can evolve compatibly in various ways
such as `readResolve`. Such changes are best tested using `@LocalData`. You
also typically want to test via `JenkinsRule.configRoundtrip`.

What about the getters?
>

In any `Describable`, a `@DataBoundSetter` method, or a
`@DataBoundConstructor` parameter, must be paired with a getter of
corresponding name and identical type. (You can also use `public` fields:
`final` to correspond to a `@DataBoundConstructor` param, or nonfinal and
marked with `@DataBoundSetter` rather than using a getter-setter pair.) For
structures used solely by Pipeline, the getter is required to introspect
default values in the syntax generator screen, and I think it is also used
when saving step arguments to the build record (visible in certain
visualizations such as Blue Ocean and the Pipeline Steps link). For
structures used in XML-persisted parts of Jenkins, the getter allows for
form reconfiguration.

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

Succession of timeouts during Docker actions on ci.jenkins.io

[Chris Kilding]

Hi,

Timeouts related to the Docker Maven Plugin are causing some plugin builds to 
fail on ci.jenkins.io. The error message is usually along the lines of:

org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal 
io.fabric8:docker-maven-plugin:0.38.0:start (start-moto) on project : 
I/O Error

Some examples:

- 
https://ci.jenkins.io/job/Plugins/job/aws-secrets-manager-secret-source-plugin/job/PR-33/1/console
- 
https://ci.jenkins.io/job/Plugins/job/aws-secrets-manager-secret-source-plugin/job/PR-36/1/console
- 
https://ci.jenkins.io/job/Plugins/job/aws-secrets-manager-secret-source-plugin/job/PR-34/1/console
- 
https://ci.jenkins.io/job/Plugins/job/aws-secrets-manager-credentials-provider-plugin/job/PR-166/1/console

I don't get this error running these builds on my laptop, and this error only 
seems to have started happening in the past month or so. Did anything about 
Docker change on the ci.jenkins.io build agents recently?

Regards,

Chris

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/0fc5f87e-842b-4479-ae85-c025ed2c9030%40www.fastmail.com.

Re: Backward compatibility policy regarding dependent plugins

['Réda Housni Alaoui' via Jenkins Developers]

Thank you for this input Jesse.

So if I went down this road, I guess at least @DataBoundSetter and 
@DataBoundConstructor would have to be kept for pipeline scripts. What 
about the getters? Do they hold the same value? Are getters (can be ?) used 
by pipeline scripts?
(Sorry for asking so many questions, I don't know all possible use cases of 
a Jenkins plugin :) )

Le lundi 3 janvier 2022 à 21:33:03 UTC+1, Jesse Glick a écrit :

> On Fri, Dec 31, 2021 at 8:14 AM 'Réda Housni Alaoui' via Jenkins 
> Developers  wrote:
>
>> Looking at https://plugins.jenkins.io/sonar-gerrit/#dependencies, I do 
>> not see any public dependent plugin.
>> What's the policy in this kind of situation?
>>
>> Should I go ahead and potentially break compatibility with private 
>> dependent plugins?
>>
>
> I would not waste time trying to preserve compatibility with a 
> hypothetical dependent plugin, unless you have some particular reason to 
> believe that such a plugin might exist. Anyone wishing to have their usages 
> taken into consideration ought to be publishing their own plugin on the 
> Jenkins update center and hosting on @jenkinsci. We routinely remove 
> unwanted APIs from Jenkins core and API-oriented plugins that appear to 
> have no usage in the known ecosystem. Occasionally a documented public 
> method will really have a known usage solely in a private plugin, but this 
> is pretty uncommon, and I would not expect a miscellaneous Java setter in 
> an end-user plugin to be used like that.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/6758db53-044d-4e39-ab54-60e5a488a9abn%40googlegroups.com.