[JIRA] (JENKINS-61928) Notify-error: java.lang.NullPointerException from GerritHandler
Title: Message Title jack you commented on JENKINS-61928 Re: Notify-error: java.lang.NullPointerException from GerritHandler we have several Jenkins server. and install same gerrit-trigger plugin. just one of them meet this issue. I'd like to know what is possible reason. some job misconfiguration on Jenkins? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205805.1587025257000.12897.1587099240119%40Atlassian.JIRA.
[JIRA] (JENKINS-61203) Read-only system - Plugin manager
Title: Message Title Oleg Nenashev updated JENKINS-61203 Jenkins / JENKINS-61203 Read-only system - Plugin manager Change By: Oleg Nenashev Status: In Review Resolved Resolution: Fixed Released As: Jenkins 2.232 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204753.1582562528000.12892.1587097920565%40Atlassian.JIRA.
[JIRA] (JENKINS-61660) Lack of spacing between setup wizard form errors
Title: Message Title Oleg Nenashev updated JENKINS-61660 Jenkins / JENKINS-61660 Lack of spacing between setup wizard form errors Change By: Oleg Nenashev Status: In Review Resolved Resolution: Fixed Released As: Jenkins 2.232 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205390.1585039651000.12895.1587097920618%40Atlassian.JIRA.
[JIRA] (JENKINS-61711) Git plugin global config incorrectly reports git not in PATH
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-61711 Git plugin global config incorrectly reports git not in PATH Change By: Oleg Nenashev Labels: configuration lts-candidate newbie-friendly Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205537.1585325185000.12887.1587097860634%40Atlassian.JIRA.
[JIRA] (JENKINS-61711) Git plugin global config incorrectly reports git not in PATH
Title: Message Title Oleg Nenashev updated JENKINS-61711 Jenkins / JENKINS-61711 Git plugin global config incorrectly reports git not in PATH Change By: Oleg Nenashev Status: In Review Resolved Resolution: Fixed Released As: Jenkins 2.232 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205537.1585325185000.12884.1587097860590%40Atlassian.JIRA.
[JIRA] (JENKINS-61711) Git plugin global config incorrectly reports git not in PATH
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-61711 Git plugin global config incorrectly reports git not in PATH Change By: Oleg Nenashev Environment: Jenkins 2. 22 222 .1Git plugin 4.2.2Git client plugin 3.2.1 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205537.1585325185000.12890.1587097860678%40Atlassian.JIRA.
[JIRA] (JENKINS-61945) Develop an app using react, react native as front end and spring boot as the back end. With mysql as the database.
Title: Message Title Nirmal Kumar assigned an issue to Nirmal Kumar Jenkins / JENKINS-61945 Develop an app using react, react native as front end and spring boot as the back end. With mysql as the database. Change By: Nirmal Kumar Assignee: heff neff Nirmal Kumar Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205825.1587095927000.12881.1587096060331%40Atlassian.JIRA.
[JIRA] (JENKINS-61945) Develop an app using react, react native as front end and spring boot as the back end. With mysql as the database.
Title: Message Title Nirmal Kumar assigned an issue to heff neff Jenkins / JENKINS-61945 Develop an app using react, react native as front end and spring boot as the back end. With mysql as the database. Change By: Nirmal Kumar Assignee: Craig Rodrigues heff neff Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205825.1587095927000.12879.1587096060282%40Atlassian.JIRA.
[JIRA] (JENKINS-61945) Develop an app using react, react native as front end and spring boot as the back end. With mysql as the database.
Title: Message Title Nirmal Kumar created an issue Jenkins / JENKINS-61945 Develop an app using react, react native as front end and spring boot as the back end. With mysql as the database. Issue Type: Epic Assignee: Craig Rodrigues Components: build-flow-plugin Created: 2020-04-17 03:58 Priority: Minor Reporter: Nirmal Kumar Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You
[JIRA] (JENKINS-61944) hello
Title: Message Title Hana Muluneh created an issue Jenkins / JENKINS-61944 hello Issue Type: Bug Assignee: Joseph Petersen (old) Components: accurev-plugin Created: 2020-04-17 03:11 Priority: Minor Reporter: Hana Muluneh Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe
[JIRA] (JENKINS-61943) Jenkins2, P4 Plugin: Error must create client ' to access local files
Title: Message Title David Rodriguez created an issue Jenkins / JENKINS-61943 Jenkins2, P4 Plugin: Error must create client ' to access local files Issue Type: Bug Assignee: Unassigned Attachments: build.log, job-config.xml Components: p4-plugin Created: 2020-04-17 01:34 Environment: OS: Ubuntu 18.04 JDK 1.8.0_181 P4 Plugin v Jenkins v2.222.1 P4 Plugin v1.10.12 Jenkins master in container (image: jenkins/jenkins:2.222.1) Jenkin slaves in container (image: jenkins/jnlp-slave:3.27-1) Labels: jenkins plugin Priority: Critical Reporter: David Rodriguez Getting error message "must create client 'ip-10-21-2-84' to access local files". It appears when the job is executed on the jenkins slave the P4 client is not being created. Does the p4 plugin create the workspace and manages the workspace view. Or does the p4 plugin require an additional setup that I might be missing. Job Configuration: Reference attached job config.xml Build log attached. Note that I also tested the job on a jenkins slave that was not in a container. Got the same error. When I ran 'p4 client' and set-up the root and mapping, the jenkins job
[JIRA] (JENKINS-61942) Can this be configured to use bitbucket server
Title: Message Title richard mauchline created an issue Jenkins / JENKINS-61942 Can this be configured to use bitbucket server Issue Type: Story Assignee: Aytunc BEKEN Components: multibranch-action-triggers-plugin Created: 2020-04-17 00:19 Priority: Minor Reporter: richard mauchline Hello I am unable to define our local Bitbucket server - only bitbucket.org Is this by design, or is it something configurable (or potentially configurable)? Thanks very much Add Comment This message was sent by
[JIRA] (JENKINS-61941) bitbucket server
Title: Message Title richard mauchline created an issue Jenkins / JENKINS-61941 bitbucket server Issue Type: Task Assignee: Aytunc BEKEN Components: multibranch-action-triggers-plugin Created: 2020-04-17 00:16 Priority: Minor Reporter: richard mauchline Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups
[JIRA] (JENKINS-61597) FreeBSD OS version label is wrong in a FreeBSD jail
Title: Message Title Mark Waite updated JENKINS-61597 Jenkins / JENKINS-61597 FreeBSD OS version label is wrong in a FreeBSD jail Change By: Mark Waite Status: In Review Resolved Resolution: Fixed Released As: platformlabeler 6.0 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205294.1584676136000.12866.1587081420169%40Atlassian.JIRA.
[JIRA] (JENKINS-61597) FreeBSD OS version label is wrong in a FreeBSD jail
Title: Message Title Mark Waite closed an issue as Fixed Jenkins / JENKINS-61597 FreeBSD OS version label is wrong in a FreeBSD jail Change By: Mark Waite Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205294.1584676136000.12867.1587081420422%40Atlassian.JIRA.
[JIRA] (JENKINS-35255) Show all warnings in source code visualization
Title: Message Title Timothy Brackett commented on JENKINS-35255 Re: Show all warnings in source code visualization If this does get implemented at some point, it should probably be an option. Particularly if JENKINS-55598 is implemented, a combined warnings view may be complicated. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.170957.1464766478000.12863.1587075480325%40Atlassian.JIRA.
[JIRA] (JENKINS-61940) Show multiple source files and all line ranges in source code view
Title: Message Title Timothy Brackett created an issue Jenkins / JENKINS-61940 Show multiple source files and all line ranges in source code view Issue Type: Improvement Assignee: Ulli Hafner Components: warnings-ng-plugin Created: 2020-04-16 22:11 Priority: Minor Reporter: Timothy Brackett Some warnings span multiple files, and it would be nice to see all related files. One trivial example is GNU CC's reorder warning for C++ where the warning shows up in the initializer list, but references the header file. More involved cases are MicroFocus Fortify and Synopsis Coverity which trace execution potentially through multiple classes or translation units. Add Comment
[JIRA] (JENKINS-61937) hpi:run fails on Java 8 when the plugin depends on 2.230+
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-61937 hpi:run fails on Java 8 when the plugin depends on 2.230+ Change By: Jesse Glick Priority: Major Blocker Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205817.1587074062000.12858.1587074943876%40Atlassian.JIRA.
[JIRA] (JENKINS-61939) Duplicate warnings not eliminated/combined
Title: Message Title Timothy Brackett created an issue Jenkins / JENKINS-61939 Duplicate warnings not eliminated/combined Issue Type: Bug Assignee: Ulli Hafner Components: warnings-ng-plugin Created: 2020-04-16 22:06 Environment: Jenkins 2.204.1, Warnings Next Generation 8.1.0, Git Forensics 0.7.0, Forensics API 0.7.0 Red Hat Enterprise Linux 7.7 x86_64 Java 1.8 Priority: Minor Reporter: Timothy Brackett Duplicate cppCheck warnings are not combined or removed. Add Comment
[JIRA] (JENKINS-61937) hpi:run fails on Java 8 when the plugin depends on 2.230+
Title: Message Title Daniel Beck created an issue Jenkins / JENKINS-61937 hpi:run fails on Java 8 when the plugin depends on 2.230+ Issue Type: Bug Assignee: Unassigned Components: core, maven-hpi-plugin Created: 2020-04-16 21:54 Labels: regression Priority: Major Reporter: Daniel Beck https://github.com/jenkinsci/jenkins/pull/3947/files#r408456990 Add Comment
[JIRA] (JENKINS-61938) Can aws-secrets-manager-credentials-provider-plugin be configured to use a credential binding for authentication?
Title: Message Title red der created an issue Jenkins / JENKINS-61938 Can aws-secrets-manager-credentials-provider-plugin be configured to use a credential binding for authentication? Issue Type: New Feature Assignee: Chris Kilding Components: aws-secrets-manager-credentials-provider-plugin Created: 2020-04-16 21:54 Environment: Jenkins cjoc on GKE Priority: Minor Reporter: red der It seems like the AWS-secrets-manager-credentials-provider-plugin plugin assumes your running on EC2 (with a role) or have injected aws creds via env vars directly into the master's session Id like to just configure access via a credential binding like I can for most of the other plugins So I can tell the aws-secrets-manager-credentials-provider-plugin which cred binding to use which has AWS access keys with read access to Secrets Manager Add Comment
[JIRA] (JENKINS-61920) java.lang.ClassNotFoundException: javax.annotation.CheckForNull
Title: Message Title Daniel Beck commented on JENKINS-61920 Re: java.lang.ClassNotFoundException: javax.annotation.CheckForNull charly ghislain Thanks for the update. I'll rewrite this issue then, as I've already closed another as a duplicate for the log warnings. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205795.1586974471000.12846.1587073800387%40Atlassian.JIRA.
[JIRA] (JENKINS-61920) java.lang.ClassNotFoundException: javax.annotation.CheckForNull
Title: Message Title
Daniel Beck updated an issue
Jenkins / JENKINS-61920
java.lang.ClassNotFoundException: javax.annotation.CheckForNull
Change By:
Daniel Beck
Im unable to add any build step to a freestyle job.Loading a newly created job, some requests on the $stapler endpoint get a 400 response:!image-2020-04-15-20-07-07-810.png! Selecting any step to add produces a supplemental error 400 (body is an empty array). In the logs, i see a lot of class not found:{noformat}jenkins_jenkins.1.zgbcwngkyxe4@ramipont| 2020-04-15 18:07:54.686+ [id=15] WARNING j.t.i.j.MissingClassTelemetry#reportException: Added a missed class for missing class telemetry. Class: javax.annotation.Nullablejenkins_jenkins.1.zgbcwngkyxe4@ramipont| java.lang.ClassNotFoundException: javax.annotation.Nullablejenkins_jenkins.1.zgbcwngkyxe4@ramipont|at jenkins.util.AntClassLoader.findClassInComponents(AntClassLoader.java:1387)jenkins_jenkins.1.zgbcwngkyxe4@ramipont|at jenkins.util.AntClassLoader.findClass(AntClassLoader.java:1342)jenkins_jenkins.1.zgbcwngkyxe4@ramipont|at jenkins.util.AntClassLoader.loadClass(AntClassLoader.java:1089)jenkins_jenkins.1.zgbcwngkyxe4@ramipont|at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521)jenkins_jenkins.1.zgbcwngkyxe4@ramipont|at java.base/java.lang.Class.forName0(Native Method)jenkins_jenkins.1.zgbcwngkyxe4@ramipont|at java.base/java.lang.Class.forName(Class.java:398)jenkins_jenkins.1.zgbcwngkyxe4@ramipont|at java.base/sun.reflect.generics.factory.CoreReflectionFactory.makeNamedType(CoreReflectionFactory.java:114)jenkins_jenkins.1.zgbcwngkyxe4@ramipont|at java.base/sun.reflect.generics.visitor.Reifier.visitClassTypeSignature(Reifier.java:125)jenkins_jenkins.1.zgbcwngkyxe4@ramipont|at java.base/sun.reflect.generics.tree.ClassTypeSignature.accept(ClassTypeSignature.java:49)jenkins_jenkins.1.zgbcwngkyxe4@ramipont|at java.base/sun.reflect.annotation.AnnotationParser.parseSig(AnnotationParser.java:440)jenkins_jenkins.1.zgbcwngkyxe4@ramipont|at java.base/sun.reflect.annotation.AnnotationParser.parseAnnotation2(AnnotationParser.java:242)jenkins_jenkins.1.zgbcwngkyxe4@ramipont|at java.base/sun.reflect.annotation.AnnotationParser.parseAnnotation(AnnotationParser.java:227)jenkins_jenkins.1.zgbcwngkyxe4@ramipont|at java.base/sun.reflect.annotation.AnnotationParser.parseParameterAnnotations2(AnnotationParser.java:185)jenkins_jenkins.1.zgbcwngkyxe4@ramipont|at java.base/sun.reflect.annotation.AnnotationParser.parseParameterAnnotations(AnnotationParser.java:162)jenkins_jenkins.1.zgbcwngkyxe4@ramipont|at java.base/java.lang.reflect.Executable.parseParameterAnnotations(Executable.java:78)jenkins_jenkins.1.zgbcwngkyxe4@ramipont|at java.base/java.lang.reflect.Executable.sharedGetParameterAnnotations(Executable.java:551)jenkins_jenkins.1.zgbcwngkyxe4@ramipont|at
[JIRA] (JENKINS-60738) Override github hook url is not being saved
Title: Message Title Evan Bluhm commented on JENKINS-60738 Re: Override github hook url is not being saved I've found that reverting the github-plugin to 1.29.4 lets me save/edit the override hook url. I'm very suspicious that https://github.com/jenkinsci/github-plugin/pull/221 has unintentionally broken some functionality in the /configure page. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203992.1578734105000.12839.1587073620230%40Atlassian.JIRA.
[JIRA] (JENKINS-61936) AWS Artifact-Manager-S3-plugin uploads in series not parallel
Title: Message Title Hutson Betts commented on JENKINS-61936 Re: AWS Artifact-Manager-S3-plugin uploads in series not parallel As an example, teams I work with often set the Archive Artifacts include list to be `.`. They archive hundreds, and quite often, thousands of small files consisting of compiled assets; _javascript_, CSS, images, etc. There is a often cited solution to pre-zip files into a single archive file before using the Archive Artifacts feature to store the artifact. However, in practice, we find the extra step of pre-zipping files to be a point of friction/contention with our user base. As AWS S3 allows a high rate of simultaneous uploads, it seems reasonable to avoid burdening our users with the added friction, while also leveraging S3's support for a large number of simultaneous uploads. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205816.1587071092000.12836.1587073380268%40Atlassian.JIRA.
[JIRA] (JENKINS-61936) AWS Artifact-Manager-S3-plugin uploads in series not parallel
Title: Message Title Hutson Betts stopped work on JENKINS-61936 Change By: Hutson Betts Status: In Progress Open Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205816.1587071092000.12834.1587073020337%40Atlassian.JIRA.
[JIRA] (JENKINS-61936) AWS Artifact-Manager-S3-plugin uploads in series not parallel
Title: Message Title Hutson Betts started work on JENKINS-61936 Change By: Hutson Betts Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205816.1587071092000.12832.1587073020283%40Atlassian.JIRA.
[JIRA] (JENKINS-60738) Override github hook url is not being saved
Title: Message Title Allen Servedio commented on JENKINS-60738 Re: Override github hook url is not being saved We are hitting the same issue. So far the only ways we have found around this is by using configuration as code and/or running a console script to update the plugin's XML file to add the XML into it (then restarting Jenkins). Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203992.1578734105000.12828.1587072900642%40Atlassian.JIRA.
[JIRA] (JENKINS-61920) java.lang.ClassNotFoundException: javax.annotation.CheckForNull
Title: Message Title charly ghislain commented on JENKINS-61920 Re: java.lang.ClassNotFoundException: javax.annotation.CheckForNull for the record, the proxy config DID change with the addition of the http/2 protocol, which was causing the issue. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205795.1586974471000.12811.1587072840418%40Atlassian.JIRA.
[JIRA] (JENKINS-61920) java.lang.ClassNotFoundException: javax.annotation.CheckForNull
Title: Message Title charly ghislain commented on JENKINS-61920 Re: java.lang.ClassNotFoundException: javax.annotation.CheckForNull thinking about it, the problem i had seems in fact unrelated to the warnings in the log, and this ticket title. So feel free to close it. If it is relevant, I will open another one for the proxy issue, sorry for the confusion. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205795.1586974471000.12808.1587072600116%40Atlassian.JIRA.
[JIRA] (JENKINS-61920) java.lang.ClassNotFoundException: javax.annotation.CheckForNull
Title: Message Title charly ghislain commented on JENKINS-61920 Re: java.lang.ClassNotFoundException: javax.annotation.CheckForNull Jenkins was exposed through an apache reverse proxy, which overrides the error responses with an error page. After connecting through a tunnel directly to jenkins, i couldn't reproduce the error, so it is probably related to the proxy configuration - which never changed for a long time if im not mistaken. Im gonna check if I missed anything in the changelog or if I can fix the proxy config and post it here. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205795.1586974471000.12806.1587072300118%40Atlassian.JIRA.
[JIRA] (JENKINS-61926) Added a missed class for missing class telemetry. Class: javax.annotation.Nonnull
Title: Message Title Daniel Beck closed an issue as Duplicate This seems to be a subset of what's reported in JENKINS-61920, so closing as a duplicate. Jenkins / JENKINS-61926 Added a missed class for missing class telemetry. Class: javax.annotation.Nonnull Change By: Daniel Beck Status: Open Closed Resolution: Duplicate Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-61920) java.lang.ClassNotFoundException: javax.annotation.CheckForNull
Title: Message Title Daniel Beck commented on JENKINS-61920 Re: java.lang.ClassNotFoundException: javax.annotation.CheckForNull FYI James Nord for the change to annotations. FYI Ramon Leon because there's probably no need to spam the log this badly with the same message over and over. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205795.1586974471000.12799.1587071640343%40Atlassian.JIRA.
[JIRA] (JENKINS-61920) java.lang.ClassNotFoundException: javax.annotation.CheckForNull
Title: Message Title Daniel Beck commented on JENKINS-61920 Re: java.lang.ClassNotFoundException: javax.annotation.CheckForNull However, I can confirm extreme log spam by 2020-04-16 21:08:02.605+ [id=84] WARNING j.t.i.j.MissingClassTelemetry#reportException: Added a missed class for missing class telemetry. Class: javax.annotation.Nonnull java.lang.ClassNotFoundException: javax.annotation.Nonnull and 2020-04-16 21:08:01.101+ [id=84] WARNING j.t.i.j.MissingClassTelemetry#reportException: Added a missed class for missing class telemetry. Class: javax.annotation.CheckForNull java.lang.ClassNotFoundException: javax.annotation.CheckForNull all with the same stack trace at jenkins.util.AntClassLoader.findClassInComponents(AntClassLoader.java:1387) at jenkins.util.AntClassLoader.findClass(AntClassLoader.java:1342) at jenkins.util.AntClassLoader.loadClass(AntClassLoader.java:1089) at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521) at java.base/java.lang.Class.forName0(Native Method) at java.base/java.lang.Class.forName(Class.java:398) at java.base/sun.reflect.generics.factory.CoreReflectionFactory.makeNamedType(CoreReflectionFactory.java:114) at java.base/sun.reflect.generics.visitor.Reifier.visitClassTypeSignature(Reifier.java:125) at java.base/sun.reflect.generics.tree.ClassTypeSignature.accept(ClassTypeSignature.java:49) at java.base/sun.reflect.annotation.AnnotationParser.parseSig(AnnotationParser.java:440) at java.base/sun.reflect.annotation.AnnotationParser.parseAnnotation2(AnnotationParser.java:242) at java.base/sun.reflect.annotation.AnnotationParser.parseAnnotations2(AnnotationParser.java:121) at java.base/sun.reflect.annotation.AnnotationParser.parseAnnotations(AnnotationParser.java:73) at java.base/java.lang.reflect.Executable.declaredAnnotations(Executable.java:604) at java.base/java.lang.reflect.Executable.declaredAnnotations(Executable.java:602) at java.base/java.lang.reflect.Executable.getAnnotation(Executable.java:572) at java.base/java.lang.reflect.Method.getAnnotation(Method.java:695) at com.google.inject.spi.InjectionPoint.getAtInject(InjectionPoint.java:492) at com.google.inject.spi.InjectionPoint.getInjectionPoints(InjectionPoint.java:690) at com.google.inject.spi.InjectionPoint.forInstanceMethodsAndFields(InjectionPoint.java:380) at com.google.inject.internal.MembersInjectorStore.createWithListeners(MembersInjectorStore.java:93) at com.google.inject.internal.MembersInjectorStore.access$000(MembersInjectorStore.java:37) at com.google.inject.internal.MembersInjectorStore$1.create(MembersInjectorStore.java:45) at com.google.inject.internal.MembersInjectorStore$1.create(MembersInjectorStore.java:42) at com.google.inject.internal.FailableCache$1.load(FailableCache.java:37) at com.google.common.cache.LocalCache$LoadingValueReference.loadFuture(LocalCache.java:3568) at
[JIRA] (JENKINS-61371) API tokens not persisted until user config screen is saved
Title: Message Title James Nord commented on JENKINS-61371 Re: API tokens not persisted until user config screen is saved Jesse Glick in core there is a sync between user information from Operations Center to masters when you login. you can opt out (I think it's opt-out not opt-in in the users preferences). if you are opted in you have to set the token for the user operations center and then login to the master so it is synced. (at least from memory) this may (or may not) be what you saw. that said I'm sure I think I saw this (again on core) but operations center login was certainly not involved at that time. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205024.1583509348000.12791.1587071520302%40Atlassian.JIRA.
[JIRA] (JENKINS-60738) Override github hook url is not being saved
Title: Message Title Tymofii Polekhin commented on JENKINS-60738 Re: Override github hook url is not being saved We're facing the same issue with both 2.204.1 and 2.222.1 versions, all plugins updated to latest UI changes to the Webhook override part isn't saved, configuration-as-code works, direct update via groovy script through plugin java api woks as well After master reboot UI picks up the changes, and displays them properly, but you still unable to modify in the UI Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203992.1578734105000.12787.1587071220204%40Atlassian.JIRA.
[JIRA] (JENKINS-61936) AWS Artifact-Manager-S3-plugin uploads in series not parallel
Title: Message Title
Beryl Snyder created an issue
Jenkins / JENKINS-61936
AWS Artifact-Manager-S3-plugin uploads in series not parallel
Issue Type:
Improvement
Assignee:
Unassigned
Components:
artifact-manager-s3-plugin
Created:
2020-04-16 21:04
Environment:
Artifact-Manager-S3-plugin Version
Labels:
plugin performance
Priority:
Minor
Reporter:
Beryl Snyder
Looking at https://github.com/jenkinsci/artifact-manager-s3-plugin and the uploads appear to happen in series for 10K, 5KB files upload time is around 20 mins, for a 100MB zip file it is a few second. I’ve tried to fix it, but I’m not a Java developer or have any Jenkins plugin development experience , and have no idea what I’m doing. The original line, https://github.com/jenkinsci/artifact-manager-s3-plugin/blob/master/src/main/java/io/jenkins/plugins/artifact_manager_jclouds/JCloudsArtifactManager.java#L189 for (Map.Entry entry : artifactUrls.entrySet()) { client.uploadFile(new File(f, entry.getKey()), contentTypes.get(entry.getKey()), entry.getValue(), listener); } My change, Map.Entry entry : artifactUrls.entrySet().parallelStream().forEach( client.uploadFile(new File(f, entry.getKey()), contentTypes.get(entry.getKey()), entry.getValue(), listener));
[JIRA] (JENKINS-61920) java.lang.ClassNotFoundException: javax.annotation.CheckForNull
Title: Message Title Daniel Beck commented on JENKINS-61920 Re: java.lang.ClassNotFoundException: javax.annotation.CheckForNull Please provide a complete list of installed plugins and their versions. It's not possible to reproduce this issue with the information provided. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205795.1586974471000.12783.1587071100271%40Atlassian.JIRA.
[JIRA] (JENKINS-61920) java.lang.ClassNotFoundException: javax.annotation.CheckForNull
Title: Message Title Daniel Beck commented on JENKINS-61920 Re: java.lang.ClassNotFoundException: javax.annotation.CheckForNull Are there other interesting log messages? Perhaps in the response body of the HTTP 400 responses? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205795.1586974471000.12780.1587070740129%40Atlassian.JIRA.
[JIRA] (JENKINS-61926) Added a missed class for missing class telemetry. Class: javax.annotation.Nonnull
Title: Message Title Daniel Beck commented on JENKINS-61926 Re: Added a missed class for missing class telemetry. Class: javax.annotation.Nonnull It's a core feature that records "Class missing" exceptions. Hence the name. IOW, that part seems to work as expected. Just the real culprit isn't being logged it seems. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205803.158701692.12776.1587070680186%40Atlassian.JIRA.
[JIRA] (JENKINS-61920) java.lang.ClassNotFoundException: javax.annotation.CheckForNull
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-61920 java.lang.ClassNotFoundException: javax.annotation.CheckForNull Change By: Daniel Beck Labels: regression Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205795.1586974471000.12774.1587070560217%40Atlassian.JIRA.
[JIRA] (JENKINS-61935) Declarative Syntax Generator gives wrong format for timestamps option
Title: Message Title
Ken Rachynski created an issue
Jenkins / JENKINS-61935
Declarative Syntax Generator gives wrong format for timestamps option
Issue Type:
Bug
Assignee:
Unassigned
Components:
pipeline
Created:
2020-04-16 20:38
Environment:
Jenkins 2.222.1, all plugins up to date
Priority:
Minor
Reporter:
Ken Rachynski
With a pipeline job configured, go to the declarative directive generator. Pick `options` and add `timestamps`. The generated syntax is options { timestamps } However, the documentation clearly states (in the example only, though) that the format should be options { timestamps() }
Add Comment
[JIRA] (JENKINS-61822) Unable to authorize blueocean with github
Title: Message Title Liam Newman commented on JENKINS-61822 Re: Unable to authorize blueocean with github There is a new version of github-api and blueocean coming shortly. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205672.1586165744000.12762.1587069480295%40Atlassian.JIRA.
[JIRA] (JENKINS-61822) Unable to authorize blueocean with github
Title: Message Title Liam Newman assigned an issue to Liam Newman Jenkins / JENKINS-61822 Unable to authorize blueocean with github Change By: Liam Newman Assignee: Liam Newman Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205672.1586165744000.12751.1587069420595%40Atlassian.JIRA.
[JIRA] (JENKINS-61932) "Learn more" link from new "Welcome" page is a broken redirect
Title: Message Title Mark Waite updated JENKINS-61932 My mistake, should not be closed until the fix is released in a new Jenkins version Jenkins / JENKINS-61932 "Learn more" link from new "Welcome" page is a broken redirect Change By: Mark Waite Status: Closed Fixed but Unreleased Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205812.1587050215000.12749.1587069420569%40Atlassian.JIRA.
[JIRA] (JENKINS-61356) Unable to connect to slave via Launch Agent mode(SSH)
Title: Message Title Ivan Fernandez Calvo updated an issue Jenkins / JENKINS-61356 Unable to connect to slave via Launch Agent mode(SSH) Change By: Ivan Fernandez Calvo Component/s: ssh-slaves-plugin Component/s: ssh-agent-plugin Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204941.158343741.12732.1587066300233%40Atlassian.JIRA.
[JIRA] (JENKINS-61356) Unable to connect to slave via Launch Agent mode(SSH)
Title: Message Title
Ivan Fernandez Calvo edited a comment on JENKINS-61356
Re: Unable to connect to slave via Launch Agent mode(SSH)
Thinking on common pitfalls I make a change on my configuration to create the credential with the PUBLIC key (totally wrong thing) and guess what the same error{code}SSHLauncher{host='ssh-agent', port=22, credentialsId='12187fc5-6f2d-4343-ad41-7a4a8c683b85', jvmOptions='', javaPath='', prefixStartSlaveCmd='', suffixStartSlaveCmd='', launchTimeoutSeconds=210, maxNumRetries=10, retryWaitTime=15, sshHostKeyVerificationStrategy=hudson.plugins.sshslaves.verifiers.NonVerifyingKeyVerificationStrategy, tcpNoDelay=true, trackCredentials=true}[04/16/20 19:32:34] [SSH] Opening SSH connection to ssh-agent:22.[04/16/20 19:32:34] [SSH] WARNING: SSH Host Keys are not being verified. Man-in-the-middle attacks may be possible against this connection.ERROR: Server rejected the 1 private key(s) for jenkins (credentialId:12187fc5-6f2d-4343-ad41-7a4a8c683b85/method:publickey)ERROR: Failed to authenticate as jenkins with credential=12187fc5-6f2d-4343-ad41-7a4a8c683b85java.io.IOException: Publickey authentication failed. at com.trilead.ssh2.auth.AuthenticationManager.authenticatePublicKey(AuthenticationManager.java:358) at com.trilead.ssh2.Connection.authenticateWithPublicKey(Connection.java:472) at com.cloudbees.jenkins.plugins.sshcredentials.impl.TrileadSSHPublicKeyAuthenticator.doAuthenticate(TrileadSSHPublicKeyAuthenticator.java:109) at com.cloudbees.jenkins.plugins.sshcredentials.SSHAuthenticator.authenticate(SSHAuthenticator.java:436) at com.cloudbees.jenkins.plugins.sshcredentials.SSHAuthenticator.authenticate(SSHAuthenticator.java:473) at hudson.plugins.sshslaves.SSHLauncher.openConnection(SSHLauncher.java:863) at hudson.plugins.sshslaves.SSHLauncher$1.call(SSHLauncher.java:435) at hudson.plugins.sshslaves.SSHLauncher$1.call(SSHLauncher.java:422) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748)Caused by: java.io.IOException: PEM problem: it is of unknown type at com.trilead.ssh2.crypto.PEMDecoder.decodeKeyPair(PEMDecoder.java:500) at com.trilead.ssh2.auth.AuthenticationManager.authenticatePublicKey(AuthenticationManager.java:292) ... 11 more[04/16/20 19:32:34] [SSH] Authentication failed.Authentication failed.[04/16/20 19:32:34] Launch failed - cleaning up connection[04/16/20 19:32:34] [SSH] Connection closed.{code}[~clsmith4] Are you sure you are creating the Jenkins credential with the PRIVATE key(something like this one https://github.com/kuisathaverat/jenkins-issues/blob/master/JENKINS-61356/ssh-agent/ssh/rsa-key) and the authorized_keys with the PUBLIC key (https://github.com/kuisathaverat/jenkins-issues/blob/master/JENKINS-61356/ssh-agent/ssh/rsa-key.pub)Other common pitfalls with the same result are to copy and paste the key in an editor that does not support Unix line breaks and save the key with windows linebreaks, add spaces on any part of the key, in general, anything that modifies the original ARMOR format of the key break the key. To have a key pair that is confirmed that fails could help to be sure that the problem is not in the plugin or Jenkins
[JIRA] (JENKINS-61356) Unable to connect to slave via Launch Agent mode(SSH)
Title: Message Title
Ivan Fernandez Calvo edited a comment on JENKINS-61356
Re: Unable to connect to slave via Launch Agent mode(SSH)
Thinking on common pitfalls I make a change on my configuration to create the credential with the PUBLIC key (totally wrong thing) and guess what the same error{code}SSHLauncher{host='ssh-agent', port=22, credentialsId='12187fc5-6f2d-4343-ad41-7a4a8c683b85', jvmOptions='', javaPath='', prefixStartSlaveCmd='', suffixStartSlaveCmd='', launchTimeoutSeconds=210, maxNumRetries=10, retryWaitTime=15, sshHostKeyVerificationStrategy=hudson.plugins.sshslaves.verifiers.NonVerifyingKeyVerificationStrategy, tcpNoDelay=true, trackCredentials=true}[04/16/20 19:32:34] [SSH] Opening SSH connection to ssh-agent:22.[04/16/20 19:32:34] [SSH] WARNING: SSH Host Keys are not being verified. Man-in-the-middle attacks may be possible against this connection.ERROR: Server rejected the 1 private key(s) for jenkins (credentialId:12187fc5-6f2d-4343-ad41-7a4a8c683b85/method:publickey)ERROR: Failed to authenticate as jenkins with credential=12187fc5-6f2d-4343-ad41-7a4a8c683b85java.io.IOException: Publickey authentication failed. at com.trilead.ssh2.auth.AuthenticationManager.authenticatePublicKey(AuthenticationManager.java:358) at com.trilead.ssh2.Connection.authenticateWithPublicKey(Connection.java:472) at com.cloudbees.jenkins.plugins.sshcredentials.impl.TrileadSSHPublicKeyAuthenticator.doAuthenticate(TrileadSSHPublicKeyAuthenticator.java:109) at com.cloudbees.jenkins.plugins.sshcredentials.SSHAuthenticator.authenticate(SSHAuthenticator.java:436) at com.cloudbees.jenkins.plugins.sshcredentials.SSHAuthenticator.authenticate(SSHAuthenticator.java:473) at hudson.plugins.sshslaves.SSHLauncher.openConnection(SSHLauncher.java:863) at hudson.plugins.sshslaves.SSHLauncher$1.call(SSHLauncher.java:435) at hudson.plugins.sshslaves.SSHLauncher$1.call(SSHLauncher.java:422) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748)Caused by: java.io.IOException: PEM problem: it is of unknown type at com.trilead.ssh2.crypto.PEMDecoder.decodeKeyPair(PEMDecoder.java:500) at com.trilead.ssh2.auth.AuthenticationManager.authenticatePublicKey(AuthenticationManager.java:292) ... 11 more[04/16/20 19:32:34] [SSH] Authentication failed.Authentication failed.[04/16/20 19:32:34] Launch failed - cleaning up connection[04/16/20 19:32:34] [SSH] Connection closed.{code}[~clsmith4] Are you sure you are creating the Jenkins credential with the PRIVATE key(something like this one https://github.com/kuisathaverat/jenkins-issues/blob/master/JENKINS-61356/ssh-agent/ssh/rsa-key) and the authorized_keys with the PUBLIC key (https://github.com/kuisathaverat/jenkins-issues/blob/master/JENKINS-61356/ssh-agent/ssh/rsa-key.pub) Other common pitfalls with the same result are to copy and paste the key in an editor that does not support Unix line breaks and save the key with windows linebreaks, add spaces on any part of the key, in general, anything that modifies the original ARMOR format of the key break the key.
[JIRA] (JENKINS-61356) Unable to connect to slave via Launch Agent mode(SSH)
Title: Message Title
Ivan Fernandez Calvo commented on JENKINS-61356
Re: Unable to connect to slave via Launch Agent mode(SSH)
Thinking on common pitfalls I make a change on my configuration to create the credential with the PUBLIC key (totally wrong thing) and guess what the same error
SSHLauncher{host='ssh-agent', port=22, credentialsId='12187fc5-6f2d-4343-ad41-7a4a8c683b85', jvmOptions='', javaPath='', prefixStartSlaveCmd='', suffixStartSlaveCmd='', launchTimeoutSeconds=210, maxNumRetries=10, retryWaitTime=15, sshHostKeyVerificationStrategy=hudson.plugins.sshslaves.verifiers.NonVerifyingKeyVerificationStrategy, tcpNoDelay=true, trackCredentials=true}
[04/16/20 19:32:34] [SSH] Opening SSH connection to ssh-agent:22.
[04/16/20 19:32:34] [SSH] WARNING: SSH Host Keys are not being verified. Man-in-the-middle attacks may be possible against this connection.
ERROR: Server rejected the 1 private key(s) for jenkins (credentialId:12187fc5-6f2d-4343-ad41-7a4a8c683b85/method:publickey)
ERROR: Failed to authenticate as jenkins with credential=12187fc5-6f2d-4343-ad41-7a4a8c683b85
java.io.IOException: Publickey authentication failed.
at com.trilead.ssh2.auth.AuthenticationManager.authenticatePublicKey(AuthenticationManager.java:358)
at com.trilead.ssh2.Connection.authenticateWithPublicKey(Connection.java:472)
at com.cloudbees.jenkins.plugins.sshcredentials.impl.TrileadSSHPublicKeyAuthenticator.doAuthenticate(TrileadSSHPublicKeyAuthenticator.java:109)
at com.cloudbees.jenkins.plugins.sshcredentials.SSHAuthenticator.authenticate(SSHAuthenticator.java:436)
at com.cloudbees.jenkins.plugins.sshcredentials.SSHAuthenticator.authenticate(SSHAuthenticator.java:473)
at hudson.plugins.sshslaves.SSHLauncher.openConnection(SSHLauncher.java:863)
at hudson.plugins.sshslaves.SSHLauncher$1.call(SSHLauncher.java:435)
at hudson.plugins.sshslaves.SSHLauncher$1.call(SSHLauncher.java:422)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Caused by: java.io.IOException: PEM problem: it is of unknown type
at com.trilead.ssh2.crypto.PEMDecoder.decodeKeyPair(PEMDecoder.java:500)
at com.trilead.ssh2.auth.AuthenticationManager.authenticatePublicKey(AuthenticationManager.java:292)
... 11 more
[04/16/20 19:32:34] [SSH] Authentication failed.
Authentication failed.
[04/16/20 19:32:34] Launch failed - cleaning up connection
[04/16/20 19:32:34] [SSH] Connection closed.
Charles Smith Are you sure you are creating the Jenkins credential with the PRIVATE key(something like this one https://github.com/kuisathaverat/jenkins-issues/blob/master/JENKINS-61356/ssh-agent/ssh/rsa-key) and the authorized_keys with the PUBLIC key (https://github.com/kuisathaverat/jenkins-issues/blob/master/JENKINS-61356/ssh-agent/ssh/rsa-key.pub)
[JIRA] (JENKINS-61356) Unable to connect to slave via Launch Agent mode(SSH)
Title: Message Title Ivan Fernandez Calvo commented on JENKINS-61356 Re: Unable to connect to slave via Launch Agent mode(SSH) This is my test environment https://github.com/kuisathaverat/jenkins-issues/tree/master/JENKINS-61356 and the key is generated with this ssh-keygen version ssh -V OpenSSH_8.1p1, LibreSSL 2.7.3 The key generated with this command ssh-keygen -t rsa –b 4096 -N "" I use JCasC to configure a credential with the key https://github.com/kuisathaverat/jenkins-issues/blob/master/JENKINS-61356/jenkins/jenkins_home/jenkins.yaml#L11-L59 and I've added the public key to the authorized key in the agent, https://github.com/kuisathaverat/jenkins-issues/blob/master/JENKINS-61356/ssh-agent/ssh/authorized_keys I cannot replicate the issue on the latest Jenkins core (2.30) and the latest plugins Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from
[JIRA] (JENKINS-61371) API tokens not persisted until user config screen is saved
Title: Message Title Jesse Glick commented on JENKINS-61371 Re: API tokens not persisted until user config screen is saved James Nord may have seen this recently. Just happened to me now in CloudBees Core. There was an empty in $JENKINS_HOME/users/*/config.xml. Not sure what triggers this. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205024.1583509348000.12711.1587064980268%40Atlassian.JIRA.
[JIRA] (JENKINS-61923) SSO integration with jenkins
Title: Message Title ashok nallama updated an issue Jenkins / JENKINS-61923 SSO integration with jenkins Change By: ashok nallama Hi Team , I am uing using my company sso and trying to hookup with the jenkins .. it would be really great if someone could provide help here.. B After i downloaded the url auth plugin from the jenkins plugins i got the errors as like this below when i entered the targeturl and login url as below..!url auth.PNG! problem occurred while processing the request. Please check [our bug tracker|https://jenkins.io/redirect/issue-tracker] to see if a similar problem has already been reported. If it is already reported, please vote and put a comment on it to let us gauge the impact of the problem. If you think this is a new issue, please file a new issue. When you file an issue, make sure to add the entire stack trace, along with the version of Jenkins and relevant plugins. [The users list|https://jenkins.io/redirect/users-mailing-list] might be also useful in understanding what has happened.h2. Stack tracejava.lang.IllegalStateException: unknown char '<'(60) in ||| Submit Form Note: Since your browser does not support _javascript_, you must press the Resume button once to proceed. at org.mortbay.util.ajax.JSON.handleUnknown(JSON.java:788) at org.mortbay.util.ajax.JSON.parse(JSON.java:777) at org.mortbay.util.ajax.JSON.parse(JSON.java:603) at org.mortbay.util.ajax.JSON.parse(JSON.java:164) at cf.pgmann.plugins.urlauth.UrlAuthToken.(UrlAuthToken.java:45) at cf.pgmann.plugins.urlauth.UrlSecurityRealm$3.doFilter(UrlSecurityRealm.java:82) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:171) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1604) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:49) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1604) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:82) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1604) at org.kohsuke.stapler.DiagnosticThreadNameFilter.doFilter(DiagnosticThreadNameFilter.java:30) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1604) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:545) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:566) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:127) at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:235) at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:1607) at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:233) at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1297) at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:188) at
[JIRA] (JENKINS-61356) Unable to connect to slave via Launch Agent mode(SSH)
Title: Message Title Ivan Fernandez Calvo commented on JENKINS-61356 Re: Unable to connect to slave via Launch Agent mode(SSH) SHA-256 is supported https://github.com/jenkinsci/trilead-ssh2/blob/3322e54a48f500487ddb6862be42e289e7d87e08/src/com/trilead/ssh2/transport/KexManager.java#L435-L439 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204941.158343741.12702.1587063720293%40Atlassian.JIRA.
[JIRA] (JENKINS-61923) SSO integration with jenkins
Title: Message Title ashok nallama updated an issue Jenkins / JENKINS-61923 SSO integration with jenkins Change By: ashok nallama Hi Team , I am uing my company sso and trying to hookup with the jenkins .. it would be really great if someone could provide help here.. B After i downloaded the url auth plugin from the jenkins plugins i got the errors as like this below when i entered the targeturl and login url as below..!url auth.PNG! problem occurred while processing the request. Please check [our bug tracker|https://jenkins.io/redirect/issue-tracker] to see if a similar problem has already been reported. If it is already reported, please vote and put a comment on it to let us gauge the impact of the problem. If you think this is a new issue, please file a new issue. When you file an issue, make sure to add the entire stack trace, along with the version of Jenkins and relevant plugins. [The users list|https://jenkins.io/redirect/users-mailing-list] might be also useful in understanding what has happened.h2. Stack tracejava.lang.IllegalStateException: unknown char '<'(60) in ||| Submit Form Note: Since your browser does not support _javascript_, you must press the Resume button once to proceed. at org.mortbay.util.ajax.JSON.handleUnknown(JSON.java:788) at org.mortbay.util.ajax.JSON.parse(JSON.java:777) at org.mortbay.util.ajax.JSON.parse(JSON.java:603) at org.mortbay.util.ajax.JSON.parse(JSON.java:164) at cf.pgmann.plugins.urlauth.UrlAuthToken.(UrlAuthToken.java:45) at cf.pgmann.plugins.urlauth.UrlSecurityRealm$3.doFilter(UrlSecurityRealm.java:82) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:171) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1604) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:49) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1604) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:82) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1604) at org.kohsuke.stapler.DiagnosticThreadNameFilter.doFilter(DiagnosticThreadNameFilter.java:30) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1604) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:545) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:566) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:127) at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:235) at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:1607) at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:233) at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1297) at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:188) at
[JIRA] (JENKINS-61356) Unable to connect to slave via Launch Agent mode(SSH)
Title: Message Title Matt Sicker commented on JENKINS-61356 Re: Unable to connect to slave via Launch Agent mode(SSH) It seems like it might be related to the message digests allowed. SHA-1 has been deprecated in openssh, so maybe it's possible that trilead doesn't support SHA-256 or something? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204941.158343741.12690.1587063480190%40Atlassian.JIRA.
[JIRA] (JENKINS-61356) Unable to connect to slave via Launch Agent mode(SSH)
Title: Message Title Ivan Fernandez Calvo commented on JENKINS-61356 Re: Unable to connect to slave via Launch Agent mode(SSH) Reading the issue I do not know which version of trilead-ssh2 or trilead-api plugins are installed. I am gonna try with an RSA key generated with the following command ssh-keygen -t rsa –b 4096 that it is the only command I saw in the comments but IIRC this exact command is the one I use so I would not replicate the issue. I will provide the test environment in a while after my tests. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204941.158343741.12687.1587061140233%40Atlassian.JIRA.
[JIRA] (JENKINS-61932) "Learn more" link from new "Welcome" page is a broken redirect
Title: Message Title Mark Waite updated JENKINS-61932 Confirmed that the link now briefly shows a working redirect and then shows the destination of the redirect. Thanks for the speedy resolution! Jenkins / JENKINS-61932 "Learn more" link from new "Welcome" page is a broken redirect Change By: Mark Waite Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an
[JIRA] (JENKINS-61932) "Learn more" link from new "Welcome" page is a broken redirect
Title: Message Title Mark Waite closed an issue as Fixed Jenkins / JENKINS-61932 "Learn more" link from new "Welcome" page is a broken redirect Change By: Mark Waite Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205812.1587050215000.12654.1587056580435%40Atlassian.JIRA.
[JIRA] (JENKINS-61932) "Learn more" link from new "Welcome" page is a broken redirect
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-61932 "Learn more" link from new "Welcome" page is a broken redirect Change By: Mark Waite Summary: "Learn more" link from new "Welcome" page is a broken redireect redirect Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205812.1587050215000.12647.1587055380148%40Atlassian.JIRA.
[JIRA] (JENKINS-61356) Unable to connect to slave via Launch Agent mode(SSH)
Title: Message Title Matt Sicker commented on JENKINS-61356 Re: Unable to connect to slave via Launch Agent mode(SSH) I think we've isolated this to being a problem in trilead, or at least in our fork of it. The last active developer there is Ivan Fernandez Calvo. Perhaps this is something supported upstream that's not merged into our fork? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204941.158343741.12645.1587055200197%40Atlassian.JIRA.
[JIRA] (JENKINS-61923) SSO integration with jenkins
Title: Message Title ashok nallama updated an issue Jenkins / JENKINS-61923 SSO integration with jenkins Change By: ashok nallama Hi Team , After i downloaded the url auth plugin from the jenkins plugins i got the errors as like this below when i entered the targeturl and login url as below.. !url auth.PNG! problem occurred while processing the request. Please check [our bug tracker|https://jenkins.io/redirect/issue-tracker] to see if a similar problem has already been reported. If it is already reported, please vote and put a comment on it to let us gauge the impact of the problem. If you think this is a new issue, please file a new issue. When you file an issue, make sure to add the entire stack trace, along with the version of Jenkins and relevant plugins. [The users list|https://jenkins.io/redirect/users-mailing-list] might be also useful in understanding what has happened.h2. Stack tracejava.lang.IllegalStateException: unknown char '<'(60) in ||| Submit Form Note: Since your browser does not support _javascript_, you must press the Resume button once to proceed. at org.mortbay.util.ajax.JSON.handleUnknown(JSON.java:788) at org.mortbay.util.ajax.JSON.parse(JSON.java:777) at org.mortbay.util.ajax.JSON.parse(JSON.java:603) at org.mortbay.util.ajax.JSON.parse(JSON.java:164) at cf.pgmann.plugins.urlauth.UrlAuthToken.(UrlAuthToken.java:45) at cf.pgmann.plugins.urlauth.UrlSecurityRealm$3.doFilter(UrlSecurityRealm.java:82) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:171) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1604) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:49) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1604) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:82) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1604) at org.kohsuke.stapler.DiagnosticThreadNameFilter.doFilter(DiagnosticThreadNameFilter.java:30) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1604) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:545) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:566) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:127) at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:235) at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:1607) at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:233) at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1297) at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:188) at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:485) at
[JIRA] (JENKINS-49076) Cannot set custom PATH inside docker container
Title: Message Title
Oleksandr Shmyrko commented on JENKINS-49076
Re: Cannot set custom PATH inside docker container
Daniel Sorensen, indeed, it works, and that's a good example. I just want to note that passing environment argument to the docker command will override original PATH value defined in image with the one from Jenkins host, and in some conditions it may produce not the result you expect (this was actually described in JENKINS-43590). Here is such example:
pipeline {
agent any
environment {
NODEJS_VERSION = "NodeJS 12.16.2"
}
stages {
stage('Nodejs inside OpenJDK container 1') {
agent {
docker {
reuseNode true
image 'openjdk:11.0-jdk-slim'
args """
-v ${JENKINS_HOME}/tools:${JENKINS_HOME}/tools
-e PATH="${PATH}:${tool("${NODEJS_VERSION}")}/bin"
"""
// Original PATH from openjdk image:
// PATH=/usr/local/openjdk-11/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
}
}
tools { nodejs "${NODEJS_VERSION}" }
environment {
PATH_JENKINS_ORIGINAL = "${PATH}"
}
steps {
sh 'env | sort'
sh 'node --version'
catchError(buildResult: 'SUCCESS',
stageResult: 'FAILURE',
message: 'cannot find java') {
sh 'java --version'
}
}
}
stage('Nodejs inside OpenJDK container 2') {
agent {
docker {
reuseNode true
image 'openjdk:11.0-jdk-slim'
args """
-v ${JENKINS_HOME}/tools:${JENKINS_HOME}/tools
"""
}
}
tools { nodejs "${NODEJS_VERSION}" }
environment {
NODEJS_BIN_PATH = "${tool("${NODEJS_VERSION}")}/bin"
PATH_JENKINS_ORIGINAL = "${PATH}"
}
steps {
sh '''
env | sort
export PATH=${PATH}:${NODEJS_BIN_PATH}
node --version
java --version
'''
}
}
}
}
Add Comment
[JIRA] (JENKINS-61923) SSO integration with jenkins
Title: Message Title ashok nallama updated an issue Jenkins / JENKINS-61923 SSO integration with jenkins Change By: ashok nallama Attachment: url auth.PNG Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205799.158698536.12614.1587054780166%40Atlassian.JIRA.
[JIRA] (JENKINS-60480) github is deprecating basic authentication using password
Title: Message Title Christopher Sang commented on JENKINS-60480 Re: github is deprecating basic authentication using password Github is removing all support for basic auth on Nov 13, 2020 (with service brownouts on Sep 30 and Oct 28) https://developer.github.com/changes/2020-02-14-deprecating-password-auth/ I have been using an access token with the "Username with password" credential type, but I don't think this will continue to work, as the branch source plugin is still sending those credentials via basic auth: https://github.com/jenkinsci/github-branch-source-plugin/blob/9d1f48ec47eb5d44f668936d0811a6715fcc6f35/src/main/java/org/jenkinsci/plugins/github_branch_source/Connector.java#L406 https://github.com/github-api/github-api/blob/5c9474d1c891121f11ce9c31b51d42216a8e416f/src/main/java/org/kohsuke/github/GitHubClient.java#L119-L123 Is the branch source plugin currently capable of sending the credentials via the HTTP Authorization header, or will this require a code change? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203567.1576268869000.12608.1587054720315%40Atlassian.JIRA.
[JIRA] (JENKINS-61932) "Learn more" link from new "Welcome" page is a broken redireect
Title: Message Title Daniel Beck updated JENKINS-61932 Jenkins / JENKINS-61932 "Learn more" link from new "Welcome" page is a broken redireect Change By: Daniel Beck Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205812.1587050215000.12605.1587053820276%40Atlassian.JIRA.
[JIRA] (JENKINS-61932) "Learn more" link from new "Welcome" page is a broken redireect
Title: Message Title Daniel Beck started work on JENKINS-61932 Change By: Daniel Beck Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205812.1587050215000.12594.1587053220234%40Atlassian.JIRA.
[JIRA] (JENKINS-61932) "Learn more" link from new "Welcome" page is a broken redireect
Title: Message Title Daniel Beck assigned an issue to Daniel Beck Jenkins / JENKINS-61932 "Learn more" link from new "Welcome" page is a broken redireect Change By: Daniel Beck Assignee: Daniel Beck Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205812.1587050215000.12585.1587052980954%40Atlassian.JIRA.
[JIRA] (JENKINS-61934) Impossible to use custom image from an other subscription
Title: Message Title
Cyril Pottiers created an issue
Jenkins / JENKINS-61934
Impossible to use custom image from an other subscription
Issue Type:
Improvement
Assignee:
Azure DevOps
Components:
azure-vm-agents-plugin
Created:
2020-04-16 15:49
Environment:
Jenkins ver. 2.222.1 Plugin azure-vm-agent 1.4.1
Priority:
Minor
Reporter:
Cyril Pottiers
We have an entreprise subscription (subA) where we manage all our images templates. Jenkins is deployed in subB and we configure the plugin to use the custom image in subA ( /subscriptions/subA/resourceGroups/rg-templates/providers/Microsoft.Compute/images/template-jenkins-slave) We have an exception during the slave construction :
com.microsoft.azure.CloudException: Status code 403, {"error":{"code":"AuthorizationFailed","message":"The client 'x' with object id 'xxx' does not have authorization to perform action 'Microsoft.Compute/images/read' over scope '/subscriptions/subB/resourceGroups/rg-templates/providers/Microsoft.Compute/images/template-jenkins-slave' or the scope is invalid. If access was recently granted, please refresh your credentials."}}: The client 'xxx' with object id 'xxx' does not have authorization to perform action 'Microsoft.Compute/images/read' over scope '/subscriptions/subB/resourceGroups/rg-templates/providers/Microsoft.Compute/images/template-jenkins-slave' or the scope is invalid. If access was recently granted, please refresh your credentials.
The plugin try to get the custom image from subB and not subA ... note : with az CLI, we can create a VM in subB that fetches a custom image from subA
[JIRA] (JENKINS-61933) Unable to LogIN With vALID cREDENTIALS
Title: Message Title vinay katamoni created an issue Jenkins / JENKINS-61933 Unable to LogIN With vALID cREDENTIALS Issue Type: Bug Assignee: vinay katamoni Components: login-theme-plugin Created: 2020-04-16 15:48 Labels: pipeline Priority: Major Reporter: vinay katamoni Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-61850) TFS pull request verification build uses wrong branch
Title: Message Title Gan Ainm edited a comment on JENKINS-61850 Re: TFS pull request verification build uses wrong branch Strangely, the build succeeds when the commit to be merged has been committed in the TFS Git repository itself. When the change is pushed into the TFS Git repository from a clone using a different user name and e-mail address, the pull request verification build fails as described above. Once user.name and user.email on the clone are set to be identical to the TFS Git repository, the pull request verification build after the push succeeds. This seems really strange! Another thing is that the build succeeds when it is triggered by a Jenkins Service Hook in TFS but it fails if it is triggered by a TFS branch policy validation build. The error message is produced by the Jenkins Git plugin, so I assume _that_ is the source of the strange behavior. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205713.1586436018000.12569.1587051720192%40Atlassian.JIRA.
[JIRA] (JENKINS-61932) "Learn more" link from new "Welcome" page is a broken redireect
Title: Message Title
Mark Waite updated an issue
Jenkins / JENKINS-61932
"Learn more" link from new "Welcome" page is a broken redireect
Change By:
Mark Waite
The "Learn more" link that is included in the new "Welcome" page for first time users is a redirect that does not direct to a working page.Steps to duplicate the problem:# Download and run Jenkins 2.231 {{$ docker run --rm -p 8080:8080 -i -t jenkins/jenkins:2.231}}# Install plugins including the ssh build agents plugin# Confirm the welcome page appears# Click the "Learn more" link on the welcome page !screencapture-testing-a-markwaite-net-8080-2020-04-16-09_10_01-edit.png|thumbnail! # Browser will open https://jenkins.io/redirects/distributed-builds !screencapture- testing jenkins - a io - markwaite redirects - net distributed - 8080 builds -2020-04-16- 09_10_01-edit 09_18_10 .png|thumbnail!
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google
[JIRA] (JENKINS-61932) "Learn more" link from new "Welcome" page is a broken redireect
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-61932 "Learn more" link from new "Welcome" page is a broken redireect Change By: Mark Waite Attachment: screencapture-jenkins-io-redirects-distributed-builds-2020-04-16-09_18_10.png Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205812.1587050215000.12560.1587050340106%40Atlassian.JIRA.
[JIRA] (JENKINS-61932) "Learn more" link from new "Welcome" page is a broken redireect
Title: Message Title
Mark Waite updated an issue
Jenkins / JENKINS-61932
"Learn more" link from new "Welcome" page is a broken redireect
Change By:
Mark Waite
The "Learn more" link that is included in the new "Welcome" page for first time users is a redirect that does not direct to a working page.Steps to duplicate the problem:# Download and run Jenkins 2.231 {{$ docker run --rm -p 8080:8080 -i -t jenkins/jenkins:2.231}}# Install plugins including the ssh build agents plugin# Confirm the welcome page appears# Click the "Learn more" link on the welcome page # Browser will open https://jenkins.io/redirects/distributed-builds!screencapture-testing-a-markwaite-net-8080-2020-04-16-09_10_01-edit.png|thumbnail!
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-53579) Asynchronous cleanup not removing renamed workspace directories on slaves
Title: Message Title Jakub Bochenski edited a comment on JENKINS-53579 Re: Asynchronous cleanup not removing renamed workspace directories on slaves > I would expect Jenkins to establish a permission mapping between its euid and container's root. Can you suggest a technical solution to this. It would be useful but I see no robust and easy way to do it EDIT: my argument is same as https://issues.jenkins-ci.org/browse/JENKINS-53579?focusedCommentId=374472=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-374472 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194059.1536919955000.12558.1587050280998%40Atlassian.JIRA.
[JIRA] (JENKINS-61932) "Learn more" link from new "Welcome" page is a broken redireect
Title: Message Title Mark Waite created an issue Jenkins / JENKINS-61932 "Learn more" link from new "Welcome" page is a broken redireect Issue Type: Bug Assignee: Unassigned Attachments: screencapture-testing-a-markwaite-net-8080-2020-04-16-09_10_01-edit.png Components: core Created: 2020-04-16 15:16 Environment: Jenkins 2.231 Priority: Minor Reporter: Mark Waite The "Learn more" link that is included in the new "Welcome" page for first time users is a redirect that does not direct to a working page. Steps to duplicate the problem: Download and run Jenkins 2.231 $ docker run --rm -p 8080:8080 -i -t jenkins/jenkins:2.231 Install plugins including the ssh build agents plugin Confirm the welcome page appears Click the "Learn more" link on the welcome page
[JIRA] (JENKINS-53579) Asynchronous cleanup not removing renamed workspace directories on slaves
Title: Message Title Jakub Bochenski commented on JENKINS-53579 Re: Asynchronous cleanup not removing renamed workspace directories on slaves > I would expect Jenkins to establish a permission mapping between its euid and container's root. Can you suggest a technical solution to this. It would be useful but I see no robust and easy way to do it Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194059.1536919955000.12509.1587050160568%40Atlassian.JIRA.
[JIRA] (JENKINS-61923) SSO integration with jenkins
Title: Message Title ashok nallama commented on JENKINS-61923 Re: SSO integration with jenkins Hi Can someone respond to this as kind of urgent for us?? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205799.158698536.12501.1587048960113%40Atlassian.JIRA.
[JIRA] (JENKINS-61725) Create tests for PitScore (in AutoGrader)
Title: Message Title Mitja Oldenbourg updated an issue Jenkins / JENKINS-61725 Create tests for PitScore (in AutoGrader) Change By: Mitja Oldenbourg Comment: Ich werde ihn heute stellen. Das Aufsetzen der Umgebung hat mich leider ein bisschen Zeit gekostet. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205551.1585338673000.12493.1587044520258%40Atlassian.JIRA.
[JIRA] (JENKINS-61722) Create tests for TestScore (in AutoGrader)
Title: Message Title Mitja Oldenbourg commented on JENKINS-61722 Re: Create tests for TestScore (in AutoGrader) Ich werde ihn heute stellen. Das Aufsetzen der Umgebung hat mich leider ein bisschen Zeit gekostet. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205548.1585338376000.12495.1587044520282%40Atlassian.JIRA.
[JIRA] (JENKINS-61931) Unable to use JNLP sidecar container without internet
Title: Message Title
Mads Nielsen updated an issue
Jenkins / JENKINS-61931
Unable to use JNLP sidecar container without internet
Change By:
Mads Nielsen
Short background:If the container name is not "jnlp" the plugin will automatically insert a JNLP container, that pulls from docker hub. Naturally this does not work within a corporate network without internet connection.If a private registry proxy is used it currently not possible to tell the Kubernetes plugin to use a different registry. Currently there are two REALLY bad workarounds: * Start Jenkins with a property: org.csanchez.jenkins.plugins.kubernetes.PodTemplateBuilder.defaultImage (BAD: requires us to maintain image version using this property) * Configure docker to use private docker registry by default. This is a big change, and not recommended. Suggestion: What about the option to prefix the default image with a custom docker registry? This could be an advanced UI option that when left alone does not change the behavior.For instance: {code:java}@VisibleForTestingstatic final String DEFAULT_JNLP_IMAGE = System99 System .getProperty(PodTemplateStepExecution.class.getName() + ".defaultImage", "jenkins/jnlp-slave:4.0.1-1");{code}What if we using like a UI option could prefix the fallback "jenkins/jnlp-slave:4.0.1-1" to "$registry/jenkins/jnlp-slave:4.0.1-1". That way, the plugin would maintain the version to be used, but be able to fetch from another registry.
Add Comment
This message was sent by Atlassian Jira
[JIRA] (JENKINS-61931) Unable to use JNLP sidecar container without internet
Title: Message Title Mads Nielsen created an issue Jenkins / JENKINS-61931 Unable to use JNLP sidecar container without internet Issue Type: Bug Assignee: Unassigned Components: kubernetes-plugin Created: 2020-04-16 13:39 Priority: Minor Reporter: Mads Nielsen Short background: If the container name is not "jnlp" the plugin will automatically insert a JNLP container, that pulls from docker hub. Naturally this does not work within a corporate network without internet connection. If a private registry proxy is used it currently not possible to tell the Kubernetes plugin to use a different registry. Currently there are two REALLY bad workarounds: Start Jenkins with a property: org.csanchez.jenkins.plugins.kubernetes.PodTemplateBuilder.defaultImage (BAD: requires us to maintain image version using this property) Configure docker to use private docker registry by default. This is a big change, and not recommended. Suggestion: What about the option to prefix the default image with a custom docker registry? This could be an advanced UI option that when left alone does not change the behavior. For instance: @VisibleForTesting static final String DEFAULT_JNLP_IMAGE = System99.getProperty(PodTemplateStepExecution.class.getName() + ".defaultImage", "jenkins/jnlp-slave:4.0.1-1"); What if we using like a UI option could prefix the fallback "jenkins/jnlp-slave:4.0.1-1" to "$registry/jenkins/jnlp-slave:4.0.1-1". That way, the plugin
[JIRA] (JENKINS-61742) host network not saved
Title: Message Title Vincent Latombe closed an issue as Duplicate Jenkins / JENKINS-61742 host network not saved Change By: Vincent Latombe Status: Open Closed Resolution: Duplicate Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205571.1585574166000.12468.1587042240337%40Atlassian.JIRA.
[JIRA] (JENKINS-61930) Config as Code official compatibility
Title: Message Title Vincent Latombe updated JENKINS-61930 Jenkins / JENKINS-61930 Config as Code official compatibility Change By: Vincent Latombe Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205808.1587041975000.12466.1587042120297%40Atlassian.JIRA.
[JIRA] (JENKINS-61930) Config as Code official compatibility
Title: Message Title Vincent Latombe started work on JENKINS-61930 Change By: Vincent Latombe Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205808.1587041975000.12464.1587042060272%40Atlassian.JIRA.
[JIRA] (JENKINS-61930) Config as Code official compatibility
Title: Message Title Vincent Latombe assigned an issue to Vincent Latombe Jenkins / JENKINS-61930 Config as Code official compatibility Change By: Vincent Latombe Assignee: Vincent Latombe Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205808.1587041975000.12462.1587042060243%40Atlassian.JIRA.
[JIRA] (JENKINS-61930) Config as Code official compatibility
Title: Message Title Vincent Latombe created an issue Jenkins / JENKINS-61930 Config as Code official compatibility Issue Type: Improvement Assignee: Unassigned Components: kubernetes-plugin Created: 2020-04-16 12:59 Priority: Minor Reporter: Vincent Latombe We have no known issue with Config-as-code, but we don't have testing either. This ticket tracks testing effort. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-61451) Kubernetes plugin version 1.25.0 failed to load
Title: Message Title Vincent Latombe closed an issue as Not A Defect So? The update center shouldn't offer versions you can't install so the only way this could happen happen is by installing the plugin manually, which is your responsibility. The version requirement is mentioned in the release notes https://github.com/jenkinsci/kubernetes-plugin/releases/tag/kubernetes-1.25.0 Jenkins / JENKINS-61451 Kubernetes plugin version 1.25.0 failed to load Change By: Vincent Latombe Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) --
[JIRA] (JENKINS-49076) Cannot set custom PATH inside docker container
Title: Message Title
Daniel Sorensen commented on JENKINS-49076
Re: Cannot set custom PATH inside docker container
It now works to set custom PATH inside Docker container in a declarative pipeline by using the environment argument -e to the Docker commands. e.g.
agent {
docker {
image 'amazoncorretto:8u202'
label 'docker'
args '''
-v $HOME/tools:$HOME/tools
-v $HOME/.m2/:$HOME/.m2
-e PATH="$PATH:/var/lib/jenkins/tools/hudson.tasks.Maven_MavenInstallation/MVN-360/bin"
'''
}
[Pipeline] sh
+ env
+ grep PATH
PATH=/sbin:/usr/sbin:/bin:/usr/bin:/usr/local/bin:/var/lib/jenkins/tools/hudson.tasks.Maven_MavenInstallation/MVN-360/bin
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit
[JIRA] (JENKINS-61929) Triggering build on pull request
Title: Message Title Martin Trgina updated an issue Jenkins / JENKINS-61929 Triggering build on pull request Change By: Martin Trgina Labels: Bitbucket jenkins Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205806.1587038404000.12371.1587038580226%40Atlassian.JIRA.
[JIRA] (JENKINS-61929) Triggering build on pull request
Title: Message Title Martin Trgina created an issue Jenkins / JENKINS-61929 Triggering build on pull request Issue Type: New Feature Assignee: Kristy Hughes Components: atlassian-bitbucket-server-integration-plugin Created: 2020-04-16 12:00 Priority: Major Reporter: Martin Trgina Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed
[JIRA] (JENKINS-53579) Asynchronous cleanup not removing renamed workspace directories on slaves
Title: Message Title Gilles Dartiguelongue commented on JENKINS-53579 Re: Asynchronous cleanup not removing renamed workspace directories on slaves For some reason, here the problems appears on jobs that are using Docker images running root user inside. I would expect Jenkins to establish a permission mapping between its euid and container's root. What is even stranger is that not all files created in the relevant steps are surviving. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194059.1536919955000.12337.1587034620755%40Atlassian.JIRA.
[JIRA] (JENKINS-57390) Enable credentials in triggers using declarative pipelines
Title: Message Title Mikhail Politaev commented on JENKINS-57390 Re: Enable credentials in triggers using declarative pipelines Hello team! Is it planned to be implemented in Jenkins? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199172.155743169.12330.1587034440200%40Atlassian.JIRA.
[JIRA] (JENKINS-61913) build log spammed for expected behaviour when agent does not have install cached
Title: Message Title
James Nord updated an issue
Jenkins / JENKINS-61913
build log spammed for expected behaviour when agent does not have install cached
Change By:
James Nord
when using the plugin to install the JDK to an ephemeral agent after the first time of installing the JDK on *any* agent all subsequent builds contain logspam that the agent does not have the downloaded file.this is expected as the downloaded JDK is cached on the master not the agent - and for ephemeral agents (cloud agents) they likely won't have the JDK downlaoded (although if you build an image they may.thus on every build for every stage that uses a new cloud agent you get the following stack trace in the build log {noformat}12:36:11 Installing AdoptOpenJDK to /home/jenkins/agent/tools/hudson.model.JDK/jdk- 8u24212 8u24212 :36:11 Installing AdoptOpenJDK to /home/jenkins/agent/tools/hudson.model.JDK/jdk- 8u24212 8u24212 :36:11 ERROR: Failed to download file:/var/jenkins_home/caches/adoptopenjdk/LINUX/amd64/jdk8u242-b08.zip from agent; will retry from master12 master12 :36:11 Also: hudson.remoting.Channel$CallSiteStackTrace: Remote call to JNLP4-connect connection from x.x.x.3/x.x.x.3: 4906412 4906412 :36:11 at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1788) 12:36:11 at hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:356) 12:36:11 at hudson.remoting.Channel.call(Channel.java:998) 12:36:11 at hudson.FilePath.act(FilePath.java:1069) 12:36:11 at hudson.FilePath.act(FilePath.java:1058) 12:36:11 at hudson.FilePath.installIfNecessaryFrom(FilePath.java:914) 12:36:11 at hudson.FilePath.installIfNecessaryFrom(FilePath.java:850) 12:36:11 at io.jenkins.plugins.adoptopenjdk.AdoptOpenJDKInstaller.performInstallation(AdoptOpenJDKInstaller.java:121) 12:36:11 at hudson.tools.InstallerTranslator.getToolHome(InstallerTranslator.java:69) 12:36:11 at hudson.tools.ToolLocationNodeProperty.getToolHome(ToolLocationNodeProperty.java:109) 12:36:11 at hudson.tools.ToolInstallation.translateFor(ToolInstallation.java:206) 12:36:11 at hudson.model.JDK.forNode(JDK.java:148) 12:36:11 at hudson.model.JDK.forNode(JDK.java:60) 12:36:11 at org.jenkinsci.plugins.workflow.steps.ToolStep$Execution.run(ToolStep.java:152) 12:36:11 at org.jenkinsci.plugins.workflow.steps.ToolStep$Execution.run(ToolStep.java:133) 12:36:11 at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47) 12:36:11 at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 12:36:11 at java.util.concurrent.FutureTask.run(FutureTask.java:266) 12:36:11 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) 12:36:11 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) 12:36:11 java.io.FileNotFoundException: /var/jenkins_home/caches/adoptopenjdk/LINUX/amd64/jdk8u242-b08.zip (No such file or directory) 12:36:11 at
[JIRA] (JENKINS-61489) New Job Screen : missing some french translations
Title: Message Title Jean-Baptiste Le Duigou commented on JENKINS-61489 Re: New Job Screen : missing some french translations Several PRs have already been created: * https://github.com/jenkinsci/workflow-multibranch-plugin/pull/95 * https://github.com/jenkinsci/pipeline-plugin/pull/449 * https://github.com/jenkinsci/cloudbees-folder-plugin/pull/145 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205174.1584344824000.12318.1587027090530%40Atlassian.JIRA.
[JIRA] (JENKINS-61489) New Job Screen : missing some french translations
Title: Message Title Jean-Baptiste Le Duigou commented on JENKINS-61489 Re: New Job Screen : missing some french translations The remaining one would be on the repo https://github.com/jenkinsci/github-branch-source-plugin Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205174.1584344824000.12320.1587027120296%40Atlassian.JIRA.
[JIRA] (JENKINS-61928) Notify-error: java.lang.NullPointerException from GerritHandler
Title: Message Title
jack you updated an issue
Jenkins / JENKINS-61928
Notify-error: java.lang.NullPointerException from GerritHandler
Change By:
jack you
{code:java} 2020-04-02 21:42:37.626+ [id=1683] SEVERE c.s.t.g.g.GerritHandler#notifyListeners: When notifying listener: com.sonyericsson.hudson.plugins.gerrit.trigger.hudsontrigger.EventListener@45284163 about event: PatchsetCreated: Change-Id for #1926138: I142a51940327661ae5b639305bea0d98c6da5cd2 PatchSet: 22020-04-02 21:42:37.626+ [id=1683] SEVERE c.s.t.g.g.GerritHandler#notifyListeners: Notify-error: java.lang.NullPointerException2020-04-02 21:42:37.627+ [id=1683] SEVERE c.s.t.g.g.GerritHandler#notifyListeners: When notifying listener: com.sonyericsson.hudson.plugins.gerrit.trigger.hudsontrigger.EventListener@b28e8f38 about event: PatchsetCreated: Change-Id for #1926138: I142a51940327661ae5b639305bea0d98c6da5cd2 PatchSet: 22020-04-02 21:42:37.627+ [id=1683] SEVERE c.s.t.g.g.GerritHandler#notifyListeners: Notify-error: java.lang.NullPointerException {code} merge event also meet this SEVERE error{code:java}Apr 14, 2020 8:53:08 AM SEVERE com.sonymobile.tools.gerrit.gerritevents.GerritHandler notifyListenersWhen notifying listener: com.sonyericsson.hudson.plugins.gerrit.trigger.hudsontrigger.EventListener@ace42b95 about event: com.sonymobile.tools.gerrit.gerritevents.dto.events.ChangeMerged@d1ac08ebApr 14, 2020 8:53:08 AM SEVERE com.sonymobile.tools.gerrit.gerritevents.GerritHandler notifyListenersNotify-error: java.lang.NullPointerException{code}I have one Jenkins server meet above issue lately. although Jenkins meet this issue, but seems gerrit-trigger event is sent to job successfully.I have one more question, why same patchset it report this error many times(about 50+ times)Could you gerrit-trigger experts help me check what is happening?Gerrit-trigger 2.30Jenkins 2.204.2
Add Comment
[JIRA] (JENKINS-61916) [JEP-200] http-request-plugin java.lang.SecurityException: Rejected: org.apache.http.HttpHost
Title: Message Title
Robert Ibram updated an issue
Jenkins / JENKINS-61916
[JEP-200] http-request-plugin java.lang.SecurityException: Rejected: org.apache.http.HttpHost
Change By:
Robert Ibram
Hello,First of all, I already read the [https://wiki.jenkins.io/display/JENKINS/Plugins+affected+by+fix+for+JEP-200] but I don't have any proxy configured.Also checked the https://issues.jenkins-ci.org/browse/JENKINS-51741.I try to create a http request as follows:{code:java}private String getResponse(def apiUrl, def requestBody){ def response = httpRequest httpMode: "POST",url: apiUrl, authentication: ' someApiKey ', customHeaders: [[name: 'Content-type', value: 'application/xml']], requestBody: requestBody, ignoreSslErrors: true return response.getContent() } {code}When trying to execute this inside my Jenkins Pipeline I get the following error:{code:java}18:15:16 java.lang.SecurityException: Rejected: org.apache.http.HttpHost; see https://jenkins.io/redirect/class-filter/18:15:16 at hudson.remoting.ClassFilter.check(ClassFilter.java:77)18:15:16 at hudson.remoting.MultiClassLoaderSerializer$Input.resolveClass(MultiClassLoaderSerializer.java:133)18:15:16 at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1620)18:15:16 at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1521)18:15:16 at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1781)18:15:16 at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1353)18:15:16 at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:2018)18:15:16 at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1942)18:15:16 at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1808)18:15:16 at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1353)18:15:16 at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:2018)18:15:16 at java.io.ObjectInputStream.defaultReadObject(ObjectInputStream.java:503)18:15:16 at java.lang.Throwable.readObject(Throwable.java:914)18:15:16 at sun.reflect.GeneratedMethodAccessor31.invoke(Unknown Source)18:15:16 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)18:15:16 at java.lang.reflect.Method.invoke(Method.java:498)18:15:16 at java.io.ObjectStreamClass.invokeReadObject(ObjectStreamClass.java:1058)18:15:16 at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1909)18:15:16 at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1808)18:15:16 at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1353)18:15:16 at java.io.ObjectInputStream.readObject(ObjectInputStream.java:373)18:15:16 at hudson.remoting.UserRequest.deserialize(UserRequest.java:290)18:15:16 at hudson.remoting.UserResponse.retrieve(UserRequest.java:385)18:15:16 at hudson.remoting.Channel.call(Channel.java:955)18:15:16 Caused:
[JIRA] (JENKINS-61928) Notify-error: java.lang.NullPointerException from GerritHandler
Title: Message Title jack you created an issue Jenkins / JENKINS-61928 Notify-error: java.lang.NullPointerException from GerritHandler Issue Type: Bug Assignee: rsandell Components: gerrit-trigger-plugin Created: 2020-04-16 08:20 Priority: Major Reporter: jack you 2020-04-02 21:42:37.626+ [id=1683] SEVERE c.s.t.g.g.GerritHandler#notifyListeners: When notifying listener: com.sonyericsson.hudson.plugins.gerrit.trigger.hudsontrigger.EventListener@45284163 about event: PatchsetCreated: Change-Id for #1926138: I142a51940327661ae5b639305bea0d98c6da5cd2 PatchSet: 2 2020-04-02 21:42:37.626+ [id=1683] SEVERE c.s.t.g.g.GerritHandler#notifyListeners: Notify-error: java.lang.NullPointerException 2020-04-02 21:42:37.627+ [id=1683] SEVERE c.s.t.g.g.GerritHandler#notifyListeners: When notifying listener: com.sonyericsson.hudson.plugins.gerrit.trigger.hudsontrigger.EventListener@b28e8f38 about event: PatchsetCreated: Change-Id for #1926138: I142a51940327661ae5b639305bea0d98c6da5cd2 PatchSet: 2 2020-04-02 21:42:37.627+ [id=1683] SEVERE c.s.t.g.g.GerritHandler#notifyListeners: Notify-error: java.lang.NullPointerException merge event also meet this SEVERE error Apr 14, 2020 8:53:08 AM SEVERE com.sonymobile.tools.gerrit.gerritevents.GerritHandler notifyListenersWhen notifying listener: com.sonyericsson.hudson.plugins.gerrit.trigger.hudsontrigger.EventListener@ace42b95 about event: com.sonymobile.tools.gerrit.gerritevents.dto.events.ChangeMerged@d1ac08eb Apr 14, 2020 8:53:08 AM SEVERE com.sonymobile.tools.gerrit.gerritevents.GerritHandler notifyListenersNotify-error: java.lang.NullPointerException I have one Jenkins server meet above issue lately. although Jenkins meet
[JIRA] (JENKINS-45832) Support for PowerShell Core on Linux
Title: Message Title Martin Bauer resolved as Fixed https://github.com/jenkinsci/powershell-plugin/releases/tag/powershell-1.4 Linux support was released on 1.4 Jenkins / JENKINS-45832 Support for PowerShell Core on Linux Change By: Martin Bauer Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view
[JIRA] (JENKINS-49113) PowerShell Core not showing objects
Title: Message Title Martin Bauer resolved as Fixed https://github.com/jenkinsci/powershell-plugin/releases/tag/powershell-1.4 Linux support was released on 1.4 Jenkins / JENKINS-49113 PowerShell Core not showing objects Change By: Martin Bauer Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view
