Re: Jenkins LTS Debian signing key?

['Dirk Heinrichs' via Jenkins Users]

Am Donnerstag, dem 30.03.2023 um 10:44 -0700 schrieb Mark Waite:


> Jenkins LTS 2.387.2 (April 5, 2023) will resolve that warning, so long as the 
> new PGP public key has been installed by following the instructions in the 
> Linux installation 
> page

Please note that these instructions contain a small mistake. The key should be 
downloaded to "/etc/apt/keyrings", unless it is later managed by a package, 
which is not the case here (see 
https://wiki.debian.org/DebianRepository/UseThirdParty).
 Would be great if that could be corrected (or, as recommended by Debian, a 
package be provided for managing the keyring after the initial setup).

If you need to install Jenkins LTS with the Linux installer between now and 
April 5, your choices include:

  *   Override the package manager to ignore the expired PGP key
  *   Use a container image like 
jenkins/jenkins:2.387.1-jdk11
  *   Install the war file without the Linux installer


  *   Download the deb directly and install via "apt-get install /path/to/file"

HTH...

Dirk

--

Dirk Heinrichs
Senior Systems Engineer, Delivery Pipeline
OpenText ™ Discovery | Recommind
Phone: +49 2226 15966 18
Email: dhein...@opentext.com
Website: 
www.recommind.de
Recommind GmbH, Von-Liebig-Straße 1, 53359 Rheinbach
Vertretungsberechtigte Geschäftsführer Gordon Davies, Madhu Ranganathan, 
Christian Waida, Registergericht Amtsgericht Bonn, Registernummer HRB 10646
This e-mail may contain confidential and/or privileged information. If you are 
not the intended recipient (or have received this e-mail in error) please 
notify the sender immediately and destroy this e-mail. Any unauthorized 
copying, disclosure or distribution of the material in this e-mail is strictly 
forbidden
Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. 
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten 
haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. 
Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail sind nicht 
gestattet.

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

Re: Jenkins LTS Debian signing key?

[alan.l...@gmail.com]

Thanks.  I'll disable the checks and wait for the release.  Thanks for the 
info.


On Thursday, March 30, 2023 at 11:44:11 AM UTC-6 Mark Waite wrote:

> On Thursday, March 30, 2023 at 11:13:20 AM UTC-6 Alan Sparks wrote:
>
> Tried to build a Jenkins image here this morning and getting signing 
> errors on the repo:
>
> W: An error occurred during the signature verification. The repository is 
> not updated and the previous index files will be used. GPG error: 
> https://pkg.jenkins.io/debian-stable binary/ Release: The following 
> signatures were invalid: EXPKEYSIG FCEF32E745F2C3D5 Jenkins Project
>
> W: Failed to fetch http://pkg.jenkins.io/debian-stable/binary/Release.gpg 
>  The following signatures were invalid: EXPKEYSIG FCEF32E745F2C3D5 Jenkins 
> Project
>
> W: Some index files failed to download. They have been ignored, or old 
> ones used instead.
>
>
> I see a post on the Jenkins blog about the key changing, but it says April 
> 5, and we're not then yet.  What has changed for Ubuntu users?  the old key 
> doesn't seem to work, nor does the new one.  I'm using the same repo 
> configuration:
> deb https://pkg.jenkins.io/debian-stable binary/
>
> What has changed?
>
>
> The GPG private key that signs the Jenkins 2.387.1 deb file expired March 
> 30, 2023.  A comment 
> 
>  
> to the blog post 
>  
> says:
>
> > Users installing Jenkins LTS 2.387.1 after March 31, 2023 may see a 
> warning or an error noting that the PGP key has expired.
>
> > Jenkins LTS 2.387.2 (April 5, 2023) will resolve that warning, so long 
> as the new PGP public key has been installed by following the instructions 
> in the Linux installation page 
> 
> You're correct that the old key does not work (because it has expired) and 
> that the new key does not work with the old releases (because they were not 
> signed with the new key). 
>
> The new key works with new releases (like Jenkins 2.397 released March 28, 
> 2023 and Jenkins 2.387.2 that will be released April 5, 2023).
>
> If you need to install Jenkins LTS with the Linux installer between now 
> and April 5, your choices include:
>
>- Override the package manager to ignore the expired PGP key
>- Use a container image like jenkins/jenkins:2.387.1-jdk11 
>
> 
>- Install the war file without the Linux installer
>
> Mark Waite
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/862e7b7f-5d75-4cbe-92bf-69e058a1fbc7n%40googlegroups.com.

Re: Jenkins LTS Debian signing key?

[Mark Waite]

On Thursday, March 30, 2023 at 11:13:20 AM UTC-6 Alan Sparks wrote:

Tried to build a Jenkins image here this morning and getting signing errors 
on the repo:

W: An error occurred during the signature verification. The repository is 
not updated and the previous index files will be used. GPG error: 
https://pkg.jenkins.io/debian-stable binary/ Release: The following 
signatures were invalid: EXPKEYSIG FCEF32E745F2C3D5 Jenkins Project
W: Failed to fetch http://pkg.jenkins.io/debian-stable/binary/Release.gpg 
 The following signatures were invalid: EXPKEYSIG FCEF32E745F2C3D5 Jenkins 
Project
W: Some index files failed to download. They have been ignored, or old ones 
used instead.

I see a post on the Jenkins blog about the key changing, but it says April 
5, and we're not then yet.  What has changed for Ubuntu users?  the old key 
doesn't seem to work, nor does the new one.  I'm using the same repo 
configuration:
deb https://pkg.jenkins.io/debian-stable binary/

What has changed?


The GPG private key that signs the Jenkins 2.387.1 deb file expired March 
30, 2023.  A comment 

 
to the blog post 
 
says:

> Users installing Jenkins LTS 2.387.1 after March 31, 2023 may see a 
warning or an error noting that the PGP key has expired.

> Jenkins LTS 2.387.2 (April 5, 2023) will resolve that warning, so long as 
the new PGP public key has been installed by following the instructions in 
the Linux installation page 

You're correct that the old key does not work (because it has expired) and 
that the new key does not work with the old releases (because they were not 
signed with the new key). 

The new key works with new releases (like Jenkins 2.397 released March 28, 
2023 and Jenkins 2.387.2 that will be released April 5, 2023).

If you need to install Jenkins LTS with the Linux installer between now and 
April 5, your choices include:

   - Override the package manager to ignore the expired PGP key
   - Use a container image like jenkins/jenkins:2.387.1-jdk11 
   

   - Install the war file without the Linux installer

Mark Waite

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/a46275a2-3ee3-405d-9142-5bc2d325119cn%40googlegroups.com.

Re: Jenkins LTS Debian signing key?

[Alex Earl]

I take that back, it only works for the weekly release, not the stable.

On Thu, Mar 30, 2023 at 10:36 AM Alex Earl  wrote:

> I just ran into the same thing, I updated to the new key and it works fine
> now.
>
> On Thu, Mar 30, 2023 at 10:13 AM alan.l...@gmail.com <
> alan.l.spa...@gmail.com> wrote:
>
>> Tried to build a Jenkins image here this morning and getting signing
>> errors on the repo:
>>
>> W: An error occurred during the signature verification. The repository is
>> not updated and the previous index files will be used. GPG error:
>> https://pkg.jenkins.io/debian-stable binary/ Release: The following
>> signatures were invalid: EXPKEYSIG FCEF32E745F2C3D5 Jenkins Project <
>> jenkinsci-bo...@googlegroups.com>
>> W: Failed to fetch http://pkg.jenkins.io/debian-stable/binary/Release.gpg
>>  The following signatures were invalid: EXPKEYSIG FCEF32E745F2C3D5 Jenkins
>> Project 
>> W: Some index files failed to download. They have been ignored, or old
>> ones used instead.
>>
>> I see a post on the Jenkins blog about the key changing, but it says
>> April 5, and we're not then yet.  What has changed for Ubuntu users?  the
>> old key doesn't seem to work, nor does the new one.  I'm using the same
>> repo configuration:
>> deb https://pkg.jenkins.io/debian-stable binary/
>>
>> What has changed?
>>
>> Following instructions for 2.387.1at:
>>
>> https://www.jenkins.io/doc/book/installing/linux/#long-term-support-release
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Jenkins Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to jenkinsci-users+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-users/54ae60e4-9408-482f-844d-5abb50abc4den%40googlegroups.com
>> 
>> .
>>
>
>
> --
> Website: http://earl-of-code.com
>


-- 
Website: http://earl-of-code.com

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

Re: Jenkins LTS Debian signing key?

[Alex Earl]

I just ran into the same thing, I updated to the new key and it works fine
now.

On Thu, Mar 30, 2023 at 10:13 AM alan.l...@gmail.com <
alan.l.spa...@gmail.com> wrote:

> Tried to build a Jenkins image here this morning and getting signing
> errors on the repo:
>
> W: An error occurred during the signature verification. The repository is
> not updated and the previous index files will be used. GPG error:
> https://pkg.jenkins.io/debian-stable binary/ Release: The following
> signatures were invalid: EXPKEYSIG FCEF32E745F2C3D5 Jenkins Project <
> jenkinsci-bo...@googlegroups.com>
> W: Failed to fetch http://pkg.jenkins.io/debian-stable/binary/Release.gpg
>  The following signatures were invalid: EXPKEYSIG FCEF32E745F2C3D5 Jenkins
> Project 
> W: Some index files failed to download. They have been ignored, or old
> ones used instead.
>
> I see a post on the Jenkins blog about the key changing, but it says April
> 5, and we're not then yet.  What has changed for Ubuntu users?  the old key
> doesn't seem to work, nor does the new one.  I'm using the same repo
> configuration:
> deb https://pkg.jenkins.io/debian-stable binary/
>
> What has changed?
>
> Following instructions for 2.387.1at:
> https://www.jenkins.io/doc/book/installing/linux/#long-term-support-release
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/54ae60e4-9408-482f-844d-5abb50abc4den%40googlegroups.com
> 
> .
>


-- 
Website: http://earl-of-code.com

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

Jenkins LTS Debian signing key?

[alan.l...@gmail.com]

Tried to build a Jenkins image here this morning and getting signing errors 
on the repo:

W: An error occurred during the signature verification. The repository is 
not updated and the previous index files will be used. GPG error: 
https://pkg.jenkins.io/debian-stable binary/ Release: The following 
signatures were invalid: EXPKEYSIG FCEF32E745F2C3D5 Jenkins Project 

W: Failed to fetch http://pkg.jenkins.io/debian-stable/binary/Release.gpg 
 The following signatures were invalid: EXPKEYSIG FCEF32E745F2C3D5 Jenkins 
Project 
W: Some index files failed to download. They have been ignored, or old ones 
used instead.

I see a post on the Jenkins blog about the key changing, but it says April 
5, and we're not then yet.  What has changed for Ubuntu users?  the old key 
doesn't seem to work, nor does the new one.  I'm using the same repo 
configuration:
deb https://pkg.jenkins.io/debian-stable binary/

What has changed?

Following instructions for 2.387.1at:
https://www.jenkins.io/doc/book/installing/linux/#long-term-support-release

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/54ae60e4-9408-482f-844d-5abb50abc4den%40googlegroups.com.

Re: Regarding unable to view the jobs in jenkins

[nick.sorokin via Jenkins Users]

Hi Ashok,


From my experience the java.lang.NoSuchMethodError exception is usually thrown 
when Java classpath contains incompatible modules and this is caused by 
configuration error, e.g. two different versions of the same package are 
present. To troubleshoot this I need the following info (unfortunately, I do 
not have experience with MacOS, so, forgive me my silly :-( questions):

1. How Jenkins was installed on MacOS? Jenkins docs have the page 
https://www.jenkins.io/download/lts/macos/ with installation instructions for 
MacOS - did you followed it?
2. How Jenkins service is configured? Service configuration file will be 
sufficient
3. How JVMs are installed? Can different versions of Java co-exist in MacOS?
4. How JVMs are configured for Jenkins? This information is available in Jenkins on 
page Manage Jenkins -> Global Tool Configuration -> JDK (screenshot will be OK)
5. How Jenkins build is configured to use Java8? It would be nice if yoe can 
send the config.xml file for this job - it is located in 
/var/lib/jenkins/jobs/{JobName}/ folder (the path may differ - this was taken 
fron Linux)
6. Can I have a full execution log for the failing build?

In addition - I have found this chat on stackoverflow - 
https://stackoverflow.com/questions/74249679/jenkins-groovy-unix-script-error-java-lang-nosuchmethoderror-boolean-mightbepo
 - you can have a look


I suggest you to send the info directly to my e-mail - this thread in jenkins-user group become clotted and unmanageable 


Regards,
Nick



On 30/03/2023 10:21, Ashok Reddy  wrote:

Hi Nick,

I have upgraded the jenkins version to 2.387.1 and am using java8 for 
building our applications.

I have been facing the following issue:

*java.lang.NoSuchMethodError: 
org.kohsuke.groovy.sandbox.SandboxTransformer.mightBePositionalArgumentConstructor(Lorg/codehaus/groovy/ast/expr/VariableExpression;)Z at com.cloudbees.groovy.cps.SandboxCpsTransformer.visitAssignmentOrCast(SandboxCpsTransformer.java:93) at com.cloudbees.groovy.cps.CpsTransformer$42.run(CpsTransformer.java:1171) at com.cloudbees.groovy.cps.CpsTransformer.makeChildren(CpsTransformer.java:446)*


*Note: I did a few findings about issue *

*1). Groovy libraries and groovy plugin issue*

*Not sure how to proceed to fix this issue.*

*Thanks in advance for your help.*

*
*


On Wed, Mar 29, 2023 at 3:34 PM 'Nikolay Sorokin' via Jenkins Users 
> wrote:


Hi Ashok,

To find the answers to the questions asked by your boss I would like
to have more details about your Jenkins environment, both
for 2.176.1 version and the version you are testing. The initial 
information I'll be looking for include:
- what operation system is used for both instances: MAC OS for
jenkins, which is currently facing issues and another one is using
RHEL7.9
- how Jenkins is installed, i.e. what application server is used,
how it is started, etc.; Java -jar jenkins.war , application server-
Tomcat
- how different versions of Java are installed: Java -1.8

Additional information may be required further.

If you wish to keep this information confidential you may send it to
me directly to nick.soro...@gmail.com 

As to upgrade path: your initial Jenkins is really too old and most
likely there is no upgrade path from your version to the latest one
- there were too many changes in Jenkins API. However you may try to
migrate the required jobs from old system to a new one.

With best regards,
Nick


-- 
You received this message because you are subscribed to the Google

Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it,
send an email to jenkinsci-users+unsubscr...@googlegroups.com
.
To view this discussion on the web visit

https://groups.google.com/d/msgid/jenkinsci-users/702099d5-5341-4a80-aa68-5d343703ea17n%40googlegroups.com
 
.

--
You received this message because you are subscribed to a topic in the 
Google Groups "Jenkins Users" group.
To unsubscribe from this topic, visit 
https://groups.google.com/d/topic/jenkinsci-users/gLKZx7Rjj1Q/unsubscribe .
To unsubscribe from this group and all its topics, send an email to 
jenkinsci-users+unsubscr...@googlegroups.com 
.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAKRLcHi3xN9ebwfQPZyZH_W83%2BTB8vp9ncH%3D3%2BaN1h7VKLZnEw%40mail.gmail.com 

Re: Regarding unable to view the jobs in jenkins

[Ashok Reddy]

Hi Nick,

I have upgraded the jenkins version to 2.387.1 and am using java8 for
building our applications.
I have been facing the following issue:

*java.lang.NoSuchMethodError:
org.kohsuke.groovy.sandbox.SandboxTransformer.mightBePositionalArgumentConstructor(Lorg/codehaus/groovy/ast/expr/VariableExpression;)Z
at 
com.cloudbees.groovy.cps.SandboxCpsTransformer.visitAssignmentOrCast(SandboxCpsTransformer.java:93)
at 
com.cloudbees.groovy.cps.CpsTransformer$42.run(CpsTransformer.java:1171)
at 
com.cloudbees.groovy.cps.CpsTransformer.makeChildren(CpsTransformer.java:446)*

*Note: I did a few findings about issue *

* 1). Groovy libraries and groovy plugin issue*

*Not sure how to proceed to fix this issue.*

*Thanks in advance for your help.*



On Wed, Mar 29, 2023 at 3:34 PM 'Nikolay Sorokin' via Jenkins Users <
jenkinsci-users@googlegroups.com> wrote:

> Hi Ashok,
>
> To find the answers to the questions asked by your boss I would like to
> have more details about your Jenkins environment, both for 2.176.1 version
> and the version you are testing. The initial  information I'll be looking
> for include:
> - what operation system is used for both instances: MAC OS for jenkins,
> which is currently facing issues and another one is using RHEL7.9
> - how Jenkins is installed, i.e. what application server is used, how it
> is started, etc.; Java -jar jenkins.war , application server- Tomcat
> - how different versions of Java are installed: Java -1.8
>
> Additional information may be required further.
>
> If you wish to keep this information confidential you may send it to me
> directly to nick.soro...@gmail.com
>
> As to upgrade path: your initial Jenkins is really too old and most likely
> there is no upgrade path from your version to the latest one - there were
> too many changes in Jenkins API. However you may try to migrate the
> required jobs from old system to a new one.
>
> With best regards,
> Nick
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/702099d5-5341-4a80-aa68-5d343703ea17n%40googlegroups.com
> 
> .
>

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