I had to re run a build for the dependency issue just before I replied to
you last night…
I haven’t seen this dependency issue before, how long have you been seeing
it?
On Fri, 11 Jun 2021 at 01:16, Bryan Stopp wrote:
> Yeah - basically i have to monitor the runs on a merge to main because if
Yeah - basically i have to monitor the runs on a merge to main because if i
don't and it fails, i can't re-run. Which defeats the whole idea of CD :(
Hopefully the network issues are resolved now and the errors my builds were
experiencing won't happen anymore.
-Stopp
On Thursday, June 10,
Hi, I would like to adopt the rabbitmq-consumer-plugin.
I have tried to reach the maintainer over github & mail over many weeks.
Url: https://github.com/jenkinsci/rabbitmq-consumer-plugin
PR of interest: https://github.com/jenkinsci/rabbitmq-consumer-plugin/pull/5
My profile:
On Thu, Jun 10, 2021 at 11:28 AM Tim Jacomb wrote:
>
> It would be good to see a more recent report given we’re on version 9 in core
> to see if anything has changed in recent versions
Great point, Tim. Core 2.273 shipped with ASM 5.0.3, prior to the
upgrade of JNR (and therefore the accidental
You should be able to run it from the page for the master build =/
This is what I see on a plugin I have with CD enabled:
[image: image.png]
On Wed, 9 Jun 2021 at 17:51, Bryan Stopp wrote:
> I'm still not seeing what you are seeing.
>
> Yes, if i look at a failed PR run
>
On Thu, Jun 10, 2021 at 10:48 AM jn...@cloudbees.com
wrote:
> JenkinsRule / RestartableJenkinsRule and any other junit test not using
> `RealisticJenkinsRule` do not use the hierarchical Jenkins classloader and
> are hence completely unrealistic when it comes to classloading. They use the
>
Update:
The operation went well for the EC2 agents update. Maven 3.8.1 is now
generally available.
However, the Azure Agent update did not go as expected: more analysis is
required (TL;DR; what looks like to be the latest VM image does not have
the expected dependencies).
It should worked
> am not planning on opening any such PRs, and I am not sure why you
would think that I am. Please remember that I am a volunteer and am
just trying to help where I can. An encouraging and constructive tone
would be appreciated.
Apologies for the offence.
> I trust you, but I am having a hard
Dear James,
On Thu, Jun 10, 2021 at 10:34 AM jn...@cloudbees.com
wrote:
>
> Thus care needs to be taken before any library is updated
Of course. Yet such care was not taken when JNR was updated in
December 2020. That is why nobody noticed that the JNR update also
pulled in a new ASM update, and
Let me try and rephrase this.
We can not be stuck with 10 year old versions of thing, we all agree on
that, but we also agree we can not just upgrade something and break
plugins[1]. The current semi policy is no breaking changes (which is why
we have not even removed deprecated code in
On Thu, Jun 10, 2021 at 10:03 AM jn...@cloudbees.com
wrote:
>
> 1 -> Which is fine until the library evolves in a binary incompatible way..
> and the ASM library is KNOWN to do this.
> 2-> has many pitfalls and this only works if no one else depends on your
> plugin otherwise they also get
> 1. Exclude the library on the plugin side (e.g. how Token Macro excludes
ASM)
2. Mask the library's classes (e.g. how JaCoCo masks ASM classes)2 ->
3. Shade the library into the plugin
1 -> Which is fine until the library evolves in a binary incompatible way..
and the ASM library is KNOWN
> . Even if you shade in ASM, you trade one problem
for another in that newer Java releases are unable to run Jenkins (I'd
give a pass for Java 16 since they changed some stuff related to
poking at internals).
How so, you upgrade the shaded library. You can also keep the original
shaded
ASM has been shipped by core, unshaded, as a transitive dependency of
JNR (_not_ JNA) since JNR was introduced in 2013. Removing core's
dependency on JNR (and therefore its transitive dependency on unshaded
ASM) is a large and yet unscoped project; similarly, hiding core
dependencies from plugins
I don't remember seeing formal docs about it, but I believe it was
changed for two reasons:
1. Dependency simplifications in general. That's been an ongoing
effort by multiple people, particularly in Jenkins Core.
2. ASM needs to be upgraded more often now that Java itself is
released more often.
Hello dear all,
Today at 13:30 UTC, a configuration update will be applied on the
ci.jenkins.io cloud agents configuration.
The scope is an update of the VM templates used for EC2 Cloud agents and
Azure VMs. The ACI (Azure Container Instances) agents are NOT in the scope.
The business values
Thanks for your suggestion, Oleg!
It's likely better for us to keep all the updates together for the
Contributors Summit, that way they will be easier to consume for all
interested parties.
Would it be possible for a contributor who can't make it on the 25th to
record an update on behalf of a
Hi All,
I would like you to answer this survey for a better monitoring and
troubleshooting experience!
In the GSoC2021 Remoting Monitoring project, we are trying to collect and
export the monitoring and troubleshooting data of *the Jenkins remoting
layer* using OpenTelemetry.
Jenkins admins
Hi all,
I have just noticed a few PRs (some merged) to change ASM in core or
libraries that core depdns on (stapler).
I think we need to revert these and have a bigger think about ASM.
ASM historically (and I believe still true) evolved in a non compatible way.
In the past I have seen that
TL;DR - New centralized community site - https://community.jenkins.io -
please join and try it out.
Hey Everyone,
Gavin Here. I'm excited to announce a new sponsored Discourse server -
https://community.jenkins.io, a new centralized communication platform we
are trying. Yea yea. I know we have a
20 matches
Mail list logo
