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
Hi,
I've started this doodle
https://doodle.com/poll/h7acxvmbuxrumpwn?utm_source=poll_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
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
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
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
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
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
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 -
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
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
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 ;) ).
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
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
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
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.
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
[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.
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
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
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:
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
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
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:
>
>
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
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
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
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
27 matches
Mail list logo
