I noticed that transisiton between 2.263.4 and 2.277.1 is very problematic
because of backwards compatibility breaking changes.
https://www.jenkins.io/doc/upgrade-guide/2.277/#upgrading-to-jenkins-lts-2-277-1
When I have to do it on instances I manage, I create a copy and by trial
and error meth
An example I forgot to add to previous post, when I was upgrading 2.204.6
to latest LTS on one of my instance:
Do upgrade of:
1.
Compatible plugins
2.
Core to 2.222.4
3.
Compatible plugins
4.
Core to 2.263.4
5.
Compatible plugins
6.
It seems that the Jenkins Coveirty Plugin is not compatible with Java 17
yet I suspect. I am waiting for Coverity Support to get back to me to
verify. Who do I contact to report this BUG?
On Tuesday, September 13, 2022 at 10:19:47 AM UTC-4 Chris Hardy wrote:
> The slave node PATH value was chan
Bonjour,
I understand that your answer is for a jenkins server configured with jcasc.
But I wanted to know, if there is a way from a Jenkins installed manually
to create a jcasc conf file to reproduce it easily ?
Thanks in advance,
Christine
Le mer. 14 sept. 2022 à 14:43, 'Dirk Heinrichs' via Je
Hi,
With jcasc plugin installed you view your config as demonstrated in jcasc
project page.
Arnaud
Le ven. 16 sept. 2022, 16:40, leroy bouche a écrit :
> Bonjour,
>
> I understand that your answer is for a jenkins server configured with
> jcasc.
> But I wanted to know, if there is a way from
