[JIRA] (JENKINS-61173) Audit trail plugin stop working unexpectedly
Title: Message Title An Nguyen commented on JENKINS-61173 Re: Audit trail plugin stop working unexpectedly Pierre Beitz the issue has gone after restarting Jenkins Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.204713.1582259655000.5832.1582615500195%40Atlassian.JIRA.
[JIRA] (JENKINS-28530) Jenkins RobotFramework show multiconfiguration results in List View
Title: Message Title Aleksi Simell closed an issue as Done Jenkins / JENKINS-28530 Jenkins RobotFramework show multiconfiguration results in List View Change By: Aleksi Simell Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.162969.1432224353000.5823.1582610760421%40Atlassian.JIRA.
[JIRA] (JENKINS-61209) Issue in catchError functionality, Post feature is not working as expected
Title: Message Title
shubham srivastava updated an issue
Jenkins / JENKINS-61209
Issue in catchError functionality, Post feature is not working as expected
Change By:
shubham srivastava
i have three stages {noformat}pipeline {agent {node {label "myNode"}}stages {stage("Stage 1") {steps {catchError(buildResult: 'UNSTABLE', catchInterruptions: false, message: 'stage failed', stageResult: 'FAILURE') {bat 'exit 1'}}post {success {println "stage 1 Message from post: success."}unstable {println "stage 1 Message from post: unstable"}failure {println "Stage 1 Message from post: failure."}}}stage("Stage 2") {steps {catchError(buildResult: 'UNSTABLE', catchInterruptions: false, message: 'stage failed', stageResult: 'FAILURE') {bat "exit 0"}}post {success {println "stage 2 Message from post: success."}unstable {println "stage 2 Message from post: unstable"}failure {println "stage 2 Message from post: failure."}}} stage("Stage 3") {steps {catchError(buildResult: 'FAILURE', catchInterruptions: false, message: 'stage failed', stageResult: 'UNSTABLE') {bat "exit 0 1 "}}post {success {println "stage 3 Message from post: success."}unstable {println "stage 3 Message from post: unstable"}failure {println "stage 3 Message from post: failure."}}}}}{noformat}As per the documentation, my output should be{noformat}Stage 1 Message from post: failure.stage 2 Message from post: success.stage 3 Message from post: success unstable .{noformat}But actually the output is{noformat}Stage 1 Message from post: failure.stage 2 Message from post: unstablestage 3 Message from post: failure{noformat}After the analysis i found out that the post feature in stage block are working according to the buildResult rather than stage result.Post feature is working fine only for the first stage which got failed in the pipeline not for the subsequent stage.
[JIRA] (JENKINS-61209) Issue in catchError functionality, Post feature is not working as expected
Title: Message Title
shubham srivastava updated an issue
Jenkins / JENKINS-61209
Issue in catchError functionality, Post feature is not working as expected
Change By:
shubham srivastava
i have three stages {noformat}pipeline {agent {node {label "myNode"}}stages {stage("Stage 1") {steps {catchError(buildResult: 'UNSTABLE', catchInterruptions: false, message: 'stage failed', stageResult: 'FAILURE') {bat 'exit 1'}}post {success {println "stage 1 Message from post: success."}unstable {println "stage 1 Message from post: unstable"}failure {println "Stage 1 Message from post: failure."}}}stage("Stage 2") {steps {catchError(buildResult: 'UNSTABLE', catchInterruptions: false, message: 'stage failed', stageResult: 'FAILURE') {bat "exit 0"}}post {success {println "stage 2 Message from post: success."}unstable {println "stage 2 Message from post: unstable"}failure {println "stage 2 Message from post: failure."}}} stage("Stage 3") {steps {catchError(buildResult: 'FAILURE', catchInterruptions: false, message: 'stage failed', stageResult: 'UNSTABLE') {bat "exit 0"}}post {success {println "stage 3 Message from post: success."}unstable {println "stage 3 Message from post: unstable"}failure {println "stage 3 Message from post: failure."}}}}}{noformat}As per the documentation, my output should be{noformat}Stage 1 Message from post: failure.stage 2 Message from post: success.stage 3 Message from post: unstable success .{noformat}But actually the output is{noformat}Stage 1 Message from post: failure.stage 2 Message from post: unstablestage 3 Message from post: failure{noformat}After the analysis i found out that the post feature in stage block are working according to the buildResult rather than stage result.Post feature is working fine only for the first stage which got failed in the pipeline not for the subsequent stage.
[JIRA] (JENKINS-61212) CLI, Agent -websockets DeploymentException: Handshake response not received
Title: Message Title Fred Vogt updated an issue Jenkins / JENKINS-61212 CLI, Agent -websockets DeploymentException: Handshake response not received Change By: Fred Vogt Summary: CLI, Agent -websockets hangs, then DeploymentException: Handshake response not received Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.204765.1582603216000.5817.1582603680061%40Atlassian.JIRA.
[JIRA] (JENKINS-61212) CLI, Agent -websockets hangs, then DeploymentException: Handshake response not received
Title: Message Title
Fred Vogt updated an issue
Jenkins / JENKINS-61212
CLI, Agent -websockets hangs, then DeploymentException: Handshake response not received
Change By:
Fred Vogt
Testing CLI, agent connections with the new '-websocket' functionality added by [JEP-222| [ https://github.com/jenkinsci/jep/blob/master/jep/222/README.adoc] ] . Jetty access log shows:{code:java}172.18.0.3 - - [25/Feb/2020:01:48:06 +] "GET /cli/ws HTTP/1.1" 101 0 "-" "-" {code}CLI output:{code:java}javax.websocket.DeploymentException: Handshake response not received. at org.glassfish.tyrus.client.ClientManager$3$1.run(ClientManager.java:694) at org.glassfish.tyrus.client.ClientManager$3.run(ClientManager.java:712)... at org.glassfish.tyrus.client.ClientManager$SameThreadExecutorService.execute(ClientManager.java:866) at java.base/java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:118) at org.glassfish.tyrus.client.ClientManager.connectToServer(ClientManager.java:511) at org.glassfish.tyrus.client.ClientManager.connectToServer(ClientManager.java:355) at hudson.cli.CLI.webSocketConnection(CLI.java:323) at hudson.cli.CLI._main(CLI.java:301) at hudson.cli.CLI.main(CLI.java:95){code}When I attach a debugger to the Jenkins server it seems to get stuck here: [https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/cli/CLIAction.java#L255]
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-61212) CLI, Agent -websockets hangs, then DeploymentException: Handshake response not received
Title: Message Title
Fred Vogt updated an issue
Jenkins / JENKINS-61212
CLI, Agent -websockets hangs, then DeploymentException: Handshake response not received
Change By:
Fred Vogt
Testing CLI, agent connections with the new '-websocket' functionality added by [ JEP-222 |[https://github . com/jenkinsci/jep/blob/master/jep/222/README.adoc]]. Jetty access log shows:{code :java }172.18.0.3 - - [25/Feb/2020:01:48:06 +] "GET /cli/ws HTTP/1.1" 101 0 "-" "-" {code} CLI output:{code :java }javax.websocket.DeploymentException: Handshake response not received. at org.glassfish.tyrus.client.ClientManager$3$1.run(ClientManager.java:694) at org.glassfish.tyrus.client.ClientManager$3.run(ClientManager.java:712)... at org.glassfish.tyrus.client.ClientManager$SameThreadExecutorService.execute(ClientManager.java:866) at java.base/java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:118) at org.glassfish.tyrus.client.ClientManager.connectToServer(ClientManager.java:511) at org.glassfish.tyrus.client.ClientManager.connectToServer(ClientManager.java:355) at hudson.cli.CLI.webSocketConnection(CLI.java:323) at hudson.cli.CLI._main(CLI.java:301) at hudson.cli.CLI.main(CLI.java:95){code} When I attach a debugger to the Jenkins server it seems to get stuck here: [ https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/cli/CLIAction.java#L255 ]
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-61212) CLI, Agent -websockets hangs, then DeploymentException: Handshake response not received
Title: Message Title Fred Vogt created an issue Jenkins / JENKINS-61212 CLI, Agent -websockets hangs, then DeploymentException: Handshake response not received Issue Type: Bug Assignee: Unassigned Components: cli Created: 2020-02-25 04:00 Environment: jdk11, Docker Jenkins 2.222 https Priority: Minor Reporter: Fred Vogt Testing CLI, agent connections with the new '-websocket' functionality added by JEP-222. Jetty access log shows: 172.18.0.3 - - [25/Feb/2020:01:48:06 +] "GET /cli/ws HTTP/1.1" 101 0 "-" "-" CLI output: javax.websocket.DeploymentException: Handshake response not received. at org.glassfish.tyrus.client.ClientManager$3$1.run(ClientManager.java:694) at org.glassfish.tyrus.client.ClientManager$3.run(ClientManager.java:712) ... at org.glassfish.tyrus.client.ClientManager$SameThreadExecutorService.execute(ClientManager.java:866) at java.base/java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:118) at org.glassfish.tyrus.client.ClientManager.connectToServer(ClientManager.java:511) at org.glassfish.tyrus.client.ClientManager.connectToServer(ClientManager.java:355) at hudson.cli.CLI.webSocketConnection(CLI.java:323) at hudson.cli.CLI._main(CLI.java:301) at hudson.cli.CLI.main(CLI.java:95)
[JIRA] (JENKINS-61211) QueueItemAuthenticator causes Build Queue contention
Title: Message Title
Allan BURDAJEWICZ updated an issue
Jenkins / JENKINS-61211
QueueItemAuthenticator causes Build Queue contention
Change By:
Allan BURDAJEWICZ
When using the Authorize Project plugin to configure authorization for build execution, this has severe consequences on the overall performances of a Jenkins master because it request information repeatedly "trying to get user details for impersonation" from the Security Realm. This can happen during in a thread that hold the {{Queue.Lock}}An instance will periodically become unavailable or take a very long time in builds especially when the build queue becomes large or when a lot of builds are happening all at the same time. If start a fresh instance with 2 master executors, configure a "Project default Build Authorization" under *Manage Jenkins > configure Global Security*, then create a single pipeline and execute it, you will see through FINE logging of {{hudson.model.User}} that the {{User#getUserDetailsForImpersonation} is requested 8 times:{code}Feb 24, 2020 2:42:42 PM FINE hudson.model.User getUserDetailsForImpersonationImpersonation of the user admin was a successFeb 24, 2020 2:42:42 PM FINE hudson.model.User getUserDetailsForImpersonationImpersonation of the user admin was a successFeb 24, 2020 2:42:42 PM FINE hudson.model.User getUserDetailsForImpersonationImpersonation of the user admin was a successFeb 24, 2020 2:42:42 PM FINE hudson.model.User getUserDetailsForImpersonationImpersonation of the user admin was a successFeb 24, 2020 2:42:42 PM FINE hudson.model.User getUserDetailsForImpersonationImpersonation of the user admin was a successFeb 24, 2020 2:42:42 PM FINE hudson.model.User getUserDetailsForImpersonationImpersonation of the user admin was a successFeb 24, 2020 2:42:42 PM FINE hudson.model.User getUserDetailsForImpersonationImpersonation of the user admin was a successFeb 24, 2020 2:42:42 PM FINE hudson.model.User getUserDetailsForImpersonationImpersonation of the user admin was a success{code} ### h3. WorkaroundCaching can be configured at the Security Realm level depending on the solution (for example for LDAP / Active directory). ### h3. Improvement ProposalI do however think that something could be improved and that since impersonation is happening so frequently, maybe the [UserDetailsCache|https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/jenkins/security/UserDetailsCache.java] can be used to improve performance.
[JIRA] (JENKINS-61211) QueueItemAuthenticator causes Build Queue contention
Title: Message Title
Allan BURDAJEWICZ updated an issue
Jenkins / JENKINS-61211
QueueItemAuthenticator causes Build Queue contention
Change By:
Allan BURDAJEWICZ
When using the Authorize Project plugin to configure authorization for build execution, this has severe consequences on the overall performances of a Jenkins master because it request information repeatedly "trying to get user details for impersonation" from the Security Realm. This can happen during in a thread that hold the {{Queue.Lock}}An instance will periodically become unavailable or take a very long time in builds especially when the build queue becomes large or when a lot of builds are happening all at the same time. If start a fresh instance with 2 master executors, configure a "Project default Build Authorization" under *Manage Jenkins > configure Global Security*, then create a single pipeline and execute it, you will see through FINE logging of {{hudson.model.User}} that the {{User#getUserDetailsForImpersonation} is requested 8 times:{code} eb Feb 24, 2020 2:42:42 PM FINE hudson.model.User getUserDetailsForImpersonationImpersonation of the user admin was a successFeb 24, 2020 2:42:42 PM FINE hudson.model.User getUserDetailsForImpersonationImpersonation of the user admin was a successFeb 24, 2020 2:42:42 PM FINE hudson.model.User getUserDetailsForImpersonationImpersonation of the user admin was a successFeb 24, 2020 2:42:42 PM FINE hudson.model.User getUserDetailsForImpersonationImpersonation of the user admin was a successFeb 24, 2020 2:42:42 PM FINE hudson.model.User getUserDetailsForImpersonationImpersonation of the user admin was a successFeb 24, 2020 2:42:42 PM FINE hudson.model.User getUserDetailsForImpersonationImpersonation of the user admin was a successFeb 24, 2020 2:42:42 PM FINE hudson.model.User getUserDetailsForImpersonationImpersonation of the user admin was a successFeb 24, 2020 2:42:42 PM FINE hudson.model.User getUserDetailsForImpersonationImpersonation of the user admin was a success{code}### WorkaroundCaching can be configured at the Security Realm level depending on the solution (for example for LDAP / Active directory). ### Improvement ProposalI do however think that something could be improved and that since impersonation is happening so frequently, maybe the [UserDetailsCache|https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/jenkins/security/UserDetailsCache.java] can be used to improve performance.
[JIRA] (JENKINS-61211) QueueItemAuthenticator causes Build Queue contention
Title: Message Title Allan BURDAJEWICZ updated JENKINS-61211 Jenkins / JENKINS-61211 QueueItemAuthenticator causes Build Queue contention Change By: Allan BURDAJEWICZ Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.204764.158259701.5812.1582600020314%40Atlassian.JIRA.
[JIRA] (JENKINS-61211) QueueItemAuthenticator causes Build Queue contention
Title: Message Title
Allan BURDAJEWICZ updated an issue
Jenkins / JENKINS-61211
QueueItemAuthenticator causes Build Queue contention
Change By:
Allan BURDAJEWICZ
When using the Authorize Project plugin to configure authorization for build execution, this has severe consequences on the overall performances of a Jenkins master because it request information repeatedly "trying to get user details for impersonation" from the Security Realm. This can happen during in a thread that hold the {{Queue.Lock}}An instance will periodically become unavailable or take a very long time in builds especially when the build queue becomes large or when a lot of builds are happening all at the same time. If start a fresh instance with 2 master executors, configure a "Project default Build Authorization" under * * Manage Jenkins > configure Global Security* * , then create a single pipeline and execute it, you will see through FINE logging of {{hudson.model.User}} that the {{User#getUserDetailsForImpersonation} is requested 8 times:{code}eb 24, 2020 2:42:42 PM FINE hudson.model.User getUserDetailsForImpersonationImpersonation of the user admin was a successFeb 24, 2020 2:42:42 PM FINE hudson.model.User getUserDetailsForImpersonationImpersonation of the user admin was a successFeb 24, 2020 2:42:42 PM FINE hudson.model.User getUserDetailsForImpersonationImpersonation of the user admin was a successFeb 24, 2020 2:42:42 PM FINE hudson.model.User getUserDetailsForImpersonationImpersonation of the user admin was a successFeb 24, 2020 2:42:42 PM FINE hudson.model.User getUserDetailsForImpersonationImpersonation of the user admin was a successFeb 24, 2020 2:42:42 PM FINE hudson.model.User getUserDetailsForImpersonationImpersonation of the user admin was a successFeb 24, 2020 2:42:42 PM FINE hudson.model.User getUserDetailsForImpersonationImpersonation of the user admin was a successFeb 24, 2020 2:42:42 PM FINE hudson.model.User getUserDetailsForImpersonationImpersonation of the user admin was a success{code}### WorkaroundCaching can be configured at the Security Realm level depending on the solution (for example for LDAP / Active directory). ### Improvement ProposalI do however think that something could be improved and that since impersonation is happening so frequently, maybe the [UserDetailsCache|https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/jenkins/security/UserDetailsCache.java] can be used to improve performance.
[JIRA] (JENKINS-61211) QueueItemAuthenticator causes Build Queue contention
Title: Message Title Allan BURDAJEWICZ assigned an issue to Allan BURDAJEWICZ Jenkins / JENKINS-61211 QueueItemAuthenticator causes Build Queue contention Change By: Allan BURDAJEWICZ Assignee: Allan BURDAJEWICZ Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.204764.158259701.5808.1582599960122%40Atlassian.JIRA.
[JIRA] (JENKINS-61211) QueueItemAuthenticator causes Build Queue contention
Title: Message Title Allan BURDAJEWICZ started work on JENKINS-61211 Change By: Allan BURDAJEWICZ Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.204764.158259701.5809.1582599960252%40Atlassian.JIRA.
[JIRA] (JENKINS-61211) QueueItemAuthenticator causes Build Queue contention
Title: Message Title
Allan BURDAJEWICZ created an issue
Jenkins / JENKINS-61211
QueueItemAuthenticator causes Build Queue contention
Issue Type:
Improvement
Assignee:
Unassigned
Components:
core
Created:
2020-02-25 02:16
Environment:
core:2.222
Labels:
performance
Priority:
Major
Reporter:
Allan BURDAJEWICZ
When using the Authorize Project plugin to configure authorization for build execution, this has severe consequences on the overall performances of a Jenkins master because it request information repeatedly "trying to get user details for impersonation" from the Security Realm. This can happen during in a thread that hold the Queue.Lock An instance will periodically become unavailable or take a very long time in builds especially when the build queue becomes large or when a lot of builds are happening all at the same time. If start a fresh instance with 2 master executors, configure a "Project default Build Authorization" under *Manage Jenkins > configure Global Security*, then create a single pipeline and execute it, you will see through FINE logging of hudson.model.User that the {{User#getUserDetailsForImpersonation} is requested 8 times:
eb 24, 2020 2:42:42 PM FINE hudson.model.User getUserDetailsForImpersonation
Impersonation of the user admin was a success
Feb 24, 2020 2:42:42 PM FINE hudson.model.User getUserDetailsForImpersonation
Impersonation of the user admin was a
[JIRA] (JENKINS-60111) Pipeline extremely slow when triggered by a user in comparison with the time triggered pipeline
Title: Message Title Allan BURDAJEWICZ updated an issue Jenkins / JENKINS-60111 Pipeline extremely slow when triggered by a user in comparison with the time triggered pipeline Change By: Allan BURDAJEWICZ Component/s: core Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.202957.1573231443000.5802.1582595760288%40Atlassian.JIRA.
[JIRA] (JENKINS-51542) Git checkout is slower than the command line execution
Title: Message Title Mark Waite commented on JENKINS-51542 Re: Git checkout is slower than the command line execution As far as I can tell, must users gain significantly more from using a reference repository and an intentionally narrow refspec than from an isolated shallow clone. Those are just my observations, not anything that I've rigorously compared in a controlled environment. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.190925.1527240014000.5791.1582591320323%40Atlassian.JIRA.
[JIRA] (JENKINS-61164) Configure Clouds - no credentials visible for vSphere Cloud
Title: Message Title Nick Jones updated JENKINS-61164 Jenkins / JENKINS-61164 Configure Clouds - no credentials visible for vSphere Cloud Change By: Nick Jones Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.204698.1582196162000.5789.1582590480403%40Atlassian.JIRA.
[JIRA] (JENKINS-51542) Git checkout is slower than the command line execution
Title: Message Title
Marcelo Oliveira edited a comment on JENKINS-51542
Re: Git checkout is slower than the command line execution
FYI, I was also having this problem and it boiled down to shallow depth = 1 clone, not sure if it's the same but it may help others.3m30s with depth =1{noformat}00:00:02.788 > /usr/bin/git fetch --tags --progress --depth=1 -- g...@git.xyz.com:repo.git +refs/heads/*:refs/remotes/origin/* # timeout=150 00:03:26.147 > /usr/bin/git config remote.origin.url g...@git.xyz.com:repo.git # timeout=60{noformat}40s normal fetch {noformat}00:00:02.472 > /usr/bin/git fetch --tags --progress -- g...@git.xyz.com:apps/repo.git +refs/heads/*:refs/remotes/origin/* # timeout=150 00:00:42.424 > /usr/bin/git config remote.origin.url g...@git.xyz.com:apps/repo.git # timeout=60 {noformat}*Node:*git version 2.23.0git-lfs/2.10.0 (GitHub; darwin amd64; go 1.13.6)*Jenkins:*git-client 3.1.1git-plugin: 4.1.1.*Git server:*GitLab Enterprise Edition 12.7.2-ee Maybe the server spends more time figuring out the shallow copy than just send the pack files?
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
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.190925.1527240014000.5767.1582589280928%40Atlassian.JIRA.
[JIRA] (JENKINS-51542) Git checkout is slower than the command line execution
Title: Message Title
Marcelo Oliveira edited a comment on JENKINS-51542
Re: Git checkout is slower than the command line execution
FYI, I was also having this problem and it boiled down to shallow depth = 1 clone, not sure if it's the same but it may help others. 3m30s ~3m24s with depth =1{noformat}00:00:02.788 > /usr/bin/git fetch --tags --progress --depth=1 -- g...@git.xyz.com:repo.git +refs/heads/*:refs/remotes/origin/* # timeout=150 00:03:26.147 > /usr/bin/git config remote.origin.url g...@git.xyz.com:repo.git # timeout=60{noformat} ~ 40s normal fetch{noformat}00:00:02.472 > /usr/bin/git fetch --tags --progress -- g...@git.xyz.com:apps/repo.git +refs/heads/*:refs/remotes/origin/* # timeout=15000:00:42.424 > /usr/bin/git config remote.origin.url g...@git.xyz.com:apps/repo.git # timeout=60 {noformat}*Node:*git version 2.23.0git-lfs/2.10.0 (GitHub; darwin amd64; go 1.13.6)*Jenkins:*git-client 3.1.1git-plugin: 4.1.1.*Git server:*GitLab Enterprise Edition 12.7.2-eeMaybe the server spends more time figuring out the shallow copy than just send the pack files?
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
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.190925.1527240014000.5769.1582589280974%40Atlassian.JIRA.
[JIRA] (JENKINS-60536) Jenkins job hangs in Jira call after git rev-list command
Title: Message Title Taylor Nelson commented on JENKINS-60536 Re: Jenkins job hangs in Jira call after git rev-list command David France this is affecting our team as well – same stack trace as yours. Your fix did unclog our pipelines temporarily, and then we ran into issues regarding JENKINS-56987 sometime last week which completely broke the plugin again. The current state of the pull request for 56987 involves deleting all the apache files that you modified in your fork to get the connection to stop freezing. So now we are freezing again. It's been a long few weeks with these plugin problems! Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.203639.1576745651000.5756.1582589280766%40Atlassian.JIRA.
[JIRA] (JENKINS-51542) Git checkout is slower than the command line execution
Title: Message Title Marcelo Oliveira commented on JENKINS-51542 Re: Git checkout is slower than the command line execution FYI, I was also having this problem and it boiled down to shallow depth = 1 clone, not sure if it's the same but it may help others. 3m30s with depth =1 00:00:02.788 > /usr/bin/git fetch --tags --progress --depth=1 -- g...@git.xyz.com:repo.git +refs/heads/*:refs/remotes/origin/* # timeout=150 00:03:26.147 > /usr/bin/git config remote.origin.url g...@git.xyz.com:repo.git # timeout=60 40s normal fetch 00:00:02.472 > /usr/bin/git fetch --tags --progress -- g...@git.xyz.com:apps/repo.git +refs/heads/*:refs/remotes/origin/* # timeout=150 00:00:42.424 > /usr/bin/git config remote.origin.url g...@git.xyz.com:apps/repo.git # timeout=60 Node: git version 2.23.0 git-lfs/2.10.0 (GitHub; darwin amd64; go 1.13.6) Jenkins: git-client 3.1.1 git-plugin: 4.1.1. Git server: GitLab Enterprise Edition 12.7.2-ee Maybe the server spends more time figuring out the shallow copy than just send the pack files? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-61169) Non-Serializable exception thrown on wrong object
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-61169 Non-Serializable exception thrown on wrong object Change By: Daniel Beck Component/s: workflow-cps-plugin Component/s: core Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.204705.1582220575000.5736.1582588740231%40Atlassian.JIRA.
[JIRA] (JENKINS-61194) Plugin installation is getting failed for various plugins
Title: Message Title Daniel Beck closed an issue as Cannot Reproduce Looks like a temporary infra issue. Jenkins / JENKINS-61194 Plugin installation is getting failed for various plugins Change By: Daniel Beck Status: Open Closed Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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
[JIRA] (JENKINS-60518) java.lang.AssertionError: InstanceIdentity is missing its singleton
Title: Message Title Jesse Glick resolved as Incomplete Hard to say what happened without steps to reproduce I am afraid. Jenkins / JENKINS-60518 java.lang.AssertionError: InstanceIdentity is missing its singleton Change By: Jesse Glick Status: Open Resolved Resolution: Incomplete Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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
[JIRA] (JENKINS-37984) org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script
Title: Message Title Greg Turner commented on JENKINS-37984 Re: org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script I've been rewriting a scripted pipeline to declarative to reduce the complexity and readability but have also run into this same issue with what I'd consider "a typical use-case" of Jenkins. I'm trying to reduce the size but still up against the limit. I understand this is probably not an easy fix but some assurance that this will be fixed in a future release would be helpful. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.174127.1473169024000.5644.1582587121718%40Atlassian.JIRA.
[JIRA] (JENKINS-56833) Hundreds of REST calls to JOB_URL/runs/2/nodes/?limit=10000
Title: Message Title Gavin Mogan commented on JENKINS-56833 Re: Hundreds of REST calls to JOB_URL/runs/2/nodes/?limit=1 Ryan Fenton-Garcia Please open a new issue This one was resolved by making executor info an optional plugin, so only those that need it (and I recommend you uninstall the executor plugin), and doesn't break things, can have it installed if its hitting a different endpoint. Its a new bug, and the new owners will need to take a look at it Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.198492.1554122782000.5641.1582586760205%40Atlassian.JIRA.
[JIRA] (JENKINS-56833) Hundreds of REST calls to JOB_URL/runs/2/nodes/?limit=10000
Title: Message Title Ryan Fenton-Garcia edited a comment on JENKINS-56833 Re: Hundreds of REST calls to JOB_URL/runs/2/nodes/?limit=1 I think I'm still seeing this currently with the Blue Ocean Aggregator 1.22.0!BO-Network.png!!BO Nodes and Stuff.png! It also gives like... a pretty sexy view that's just locked to the bottom of the last step of the stage view. No matter where you scroll, the ?limit=1 request gets made and the view is reset and snapped back to the bottom of the page. It's a super frustrating user experience. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.198492.1554122782000.5638.1582584000278%40Atlassian.JIRA.
[JIRA] (JENKINS-56833) Hundreds of REST calls to JOB_URL/runs/2/nodes/?limit=10000
Title: Message Title Ryan Fenton-Garcia commented on JENKINS-56833 Re: Hundreds of REST calls to JOB_URL/runs/2/nodes/?limit=1 I think I'm still seeing this currently with the Blue Ocean Aggregator 1.22.0 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.198492.1554122782000.5635.1582583880283%40Atlassian.JIRA.
[JIRA] (JENKINS-56833) Hundreds of REST calls to JOB_URL/runs/2/nodes/?limit=10000
Title: Message Title Ryan Fenton-Garcia updated an issue Jenkins / JENKINS-56833 Hundreds of REST calls to JOB_URL/runs/2/nodes/?limit=1 Change By: Ryan Fenton-Garcia Attachment: BO Nodes and Stuff.png Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.198492.1554122782000.5633.1582583880255%40Atlassian.JIRA.
[JIRA] (JENKINS-56833) Hundreds of REST calls to JOB_URL/runs/2/nodes/?limit=10000
Title: Message Title Ryan Fenton-Garcia updated an issue Jenkins / JENKINS-56833 Hundreds of REST calls to JOB_URL/runs/2/nodes/?limit=1 Change By: Ryan Fenton-Garcia Attachment: BO-Network.png Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.198492.1554122782000.5629.1582583820302%40Atlassian.JIRA.
[JIRA] (JENKINS-55548) The "check_process_state_resource" plugin does not exist.
Title: Message Title Mark Waite closed an issue as Cannot Reproduce Cannot duplicate the report. Jenkins / JENKINS-55548 The "check_process_state_resource" plugin does not exist. Change By: Mark Waite Status: Open Closed Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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-50758) Jenkins Jobs not visible
Title: Message Title Mark Waite closed an issue as Cannot Reproduce After over 18 months without a response, closing as cannot duplicate Jenkins / JENKINS-50758 Jenkins Jobs not visible Change By: Mark Waite Status: Open Closed Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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-53314) how to parameterize default "workspace" folder name, jenkins on Tomcat on windows
Title: Message Title Mark Waite closed an issue as Fixed Please don't use the Jenkins issue tracker for questions. The mailing lists and the chat systems are better suited to answering questions. Jenkins / JENKINS-53314 how to parameterize default "workspace" folder name, jenkins on Tomcat on windows Change By: Mark Waite Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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,
[JIRA] (JENKINS-61210) Missing Git remote and browser URLs when executing Job DSL via CasC
Title: Message Title Bryan Burke created an issue Jenkins / JENKINS-61210 Missing Git remote and browser URLs when executing Job DSL via CasC Issue Type: Bug Assignee: Kristy Hughes Attachments: casc_dsl_badxml.txt, casc_dsl_workaround.txt, direct_dsl_goodxml.txt, plugin_versions.txt Components: atlassian-bitbucket-server-integration-plugin, configuration-as-code-plugin, job-dsl-plugin Created: 2020-02-24 20:42 Environment: Docker image: jenkins/jenkins:lts Jenkins version: 2.204.2 For plugin versions, see: plugin_versions.txt Priority: Minor Reporter: Bryan Burke When creating a Bitbucket Server SCM pipeline seed job using Job DSL in CasC, the generated XML is missing the Git remote and browser URLs, causing the job to fail. Opening the job configuration and immediately saving it without making any changes populates the URLs in the XML. Steps to reproduce, with log entries and example CasC YAML: casc_dsl_badxml.txt The key log entry appears to be: c.a.b.j.i.scm.BitbucketSCM#: No Bitbucket Server configuration for serverId Bitbucket This message seems to indicate that CasC may be executing the Job DSL script before applying the CasC YAML that defines the Bitbucket server. When executing the exact same Job DSL script via a freestyle job after CasC completes, the generated XML correctly contains the Git remote and browser URLs. Steps to verify: direct_dsl_goodxml.txt Using the Job DSL
[JIRA] (JENKINS-61184) Jira Trigger Plugin Issue
Title: Message Title Wisen Tanasa commented on JENKINS-61184 Re: Jira Trigger Plugin Issue Usama Tariq Thanks for raising this issue. This plug-in is open sourced, and is not maintained by the Jenkins team. I've closed this as a duplicate. In the mean time, feel free to submit a pull request to the project and I'm more than happy to merge it. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.204728.1582314984000.5604.1582576440123%40Atlassian.JIRA.
[JIRA] (JENKINS-61184) Jira Trigger Plugin Issue
Title: Message Title Wisen Tanasa closed an issue as Duplicate Jenkins / JENKINS-61184 Jira Trigger Plugin Issue Change By: Wisen Tanasa Status: Open Closed Resolution: Duplicate Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.204728.1582314984000.5595.1582576200229%40Atlassian.JIRA.
[JIRA] (JENKINS-61184) Jira Trigger Plugin Issue
Title: Message Title Wisen Tanasa assigned an issue to Unassigned Jenkins / JENKINS-61184 Jira Trigger Plugin Issue Change By: Wisen Tanasa Assignee: Dan Alvizu Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.204728.1582314984000.5593.1582576080279%40Atlassian.JIRA.
[JIRA] (JENKINS-61193) When using proxy also export the no_proxy hosts.
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-61193 When using proxy also export the no_proxy hosts. Change By: Mark Waite Labels: newbie-friendly Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.204739.1582532685000.5590.1582574820150%40Atlassian.JIRA.
[JIRA] (JENKINS-61193) When using proxy also export the no_proxy hosts.
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-61193 When using proxy also export the no_proxy hosts. Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.204739.1582532685000.5588.1582574760133%40Atlassian.JIRA.
[JIRA] (JENKINS-61209) Issue in catchError functionality, Post feature is not working as expected
Title: Message Title
shubham srivastava updated an issue
Jenkins / JENKINS-61209
Issue in catchError functionality, Post feature is not working as expected
Change By:
shubham srivastava
i have two three stages {noformat}pipeline {agent {node {label "myNode"}}stages {stage("Stage 1") {steps {catchError(buildResult: 'UNSTABLE', catchInterruptions: false, message: 'stage failed', stageResult: 'FAILURE') {bat 'exit 1'}}post {success {println "stage 1 Message from post: success."}unstable {println "stage 1 Message from post: unstable"}failure {println "Stage 1 Message from post: failure."}}}stage("Stage 2") {steps {catchError(buildResult: 'UNSTABLE', catchInterruptions: false, message: 'stage failed', stageResult: 'FAILURE') {bat "exit 0"}}post {success {println "stage 2 Message from post: success."}unstable {println "stage 2 Message from post: unstable"}failure {println "stage 2 Message from post: failure."}}} stage("Stage 3") {steps {catchError(buildResult: 'FAILURE', catchInterruptions: false, message: 'stage failed', stageResult: 'UNSTABLE') {bat "exit 0" }} post { success {println "stage 3 Message from post: success."}unstable {println "stage 3 Message from post: unstable"}failure {println "stage 3 Message from post: failure."}}}}}{ noformat}As per the documentation, my output should be{noformat}Stage 1 Message from post: failure.stage 2 Message from post: success. stage 3 Message from post: unstable. {noformat}But actually the output is{noformat}Stage 1 Message from post: failure.stage 2 Message from post: unstable stage 3 Message from post: failure {noformat}After the analysis i found out that the post feature in stage block are working according to the buildResult rather than stage result. Post feature is working fine only for the first stage which got failed in the pipeline not for the subsequent stage.
[JIRA] (JENKINS-48822) Make git plugin browser URL guessing clearer and easier to understand
Title: Message Title Gyanesha Prajjwal commented on JENKINS-48822 Re: Make git plugin browser URL guessing clearer and easier to understand Sir, I have made a pull request by adding only an extension point for inferring browser. I haven't made any additional changes. Kindly look into this and suggest the required changes and other steps which I need to take. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.187606.1515167094000.5566.1582569780130%40Atlassian.JIRA.
[JIRA] (JENKINS-53794) jira-trigger-plugin fails to trigger job and throws error
Title: Message Title Usama Tariq commented on JENKINS-53794 Re: jira-trigger-plugin fails to trigger job and throws error Stefan Cordes, Please suggest the solution for following ticket: https://issues.jenkins-ci.org/browse/JENKINS-61184 Regards Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.194307.1537972591000.5553.1582569660464%40Atlassian.JIRA.
[JIRA] (JENKINS-61209) Issue in catchError functionality, Post feature is not working as expected
Title: Message Title
shubham srivastava created an issue
Jenkins / JENKINS-61209
Issue in catchError functionality, Post feature is not working as expected
Issue Type:
Bug
Assignee:
Andrew Bayer
Components:
pipeline-model-definition-plugin
Created:
2020-02-24 18:37
Environment:
Jenkins 2.190.3
Labels:
pipeline
Priority:
Major
Reporter:
shubham srivastava
i have two stages
pipeline {
agent {
node {
label "myNode"
}
}
stages {
stage("Stage 1") {
steps {
catchError(buildResult: 'UNSTABLE', catchInterruptions: false, message: 'stage failed', stageResult: 'FAILURE') {
bat 'exit 1'
}
}
post {
success {
println "stage 1 Message from post: success."
}
unstable {
println "stage 1 Message from post: unstable"
}
failure {
println "Stage 1 Message from post: failure."
}
}
}
stage("Stage 2") {
steps {
catchError(buildResult: 'UNSTABLE', catchInterruptions: false, message: 'stage failed', stageResult: 'FAILURE') {
bat "exit 0"
}
}
post {
[JIRA] (JENKINS-59256) Login issue
Title: Message Title Mark Waite closed an issue as Cannot Reproduce Closing pending more details being provided so that others can duplicate the problem Jenkins / JENKINS-59256 Login issue Change By: Mark Waite Status: Open Closed Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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
[JIRA] (JENKINS-44990) PatternSyntaxException: Illegal/unsupported escape sequence near index 10 workspace\CopyToSlave
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-44990 PatternSyntaxException: Illegal/unsupported escape sequence near index 10 workspace\CopyToSlave Change By: Mark Waite Component/s: copy-to-slave-plugin Component/s: _unsorted Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.183075.1497952114000.5545.1582568100127%40Atlassian.JIRA.
[JIRA] (JENKINS-43768) Allow setup the name of the containers launched
Title: Message Title Mark Waite closed an issue as Cannot Reproduce After over 12 months with no response, closing this as "Cannot Reproduce". Jenkins / JENKINS-43768 Allow setup the name of the containers launched Change By: Mark Waite Status: Open Closed Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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-42456) When change the job name at that time get java.io.IOException
Title: Message Title Mark Waite closed an issue as Cannot Reproduce I confirmed with Jenkins 2.222 on Windows 10 that a job can be renamed from "BOS - LIVE - Task - 01" to "BOS - LIVE - Task - 01 - Test 404 Page Not Found". The job was initially empty, then I added a git repository and run mvn compile, then renamed the job. Jenkins / JENKINS-42456 When change the job name at that time get java.io.IOException Change By: Mark Waite Status: Open Closed Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are
[JIRA] (JENKINS-61207) Read-only system - System log access
Title: Message Title Tim Jacomb created an issue Jenkins / JENKINS-61207 Read-only system - System log access Issue Type: Story Assignee: Unassigned Components: core Created: 2020-02-24 17:02 Priority: Minor Reporter: Tim Jacomb Allow users with Jenkins.SYSTEM_READ to view the system log (note they shouldn't be able to create new log recorders just view pre-configured ones) Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-61208) Read-only system - View admin monitors
Title: Message Title Tim Jacomb created an issue Jenkins / JENKINS-61208 Read-only system - View admin monitors Issue Type: Story Assignee: Unassigned Components: core Created: 2020-02-24 17:02 Priority: Minor Reporter: Tim Jacomb Allow users with Jenkins.SYSTEM_READ permission to view admin monitors Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-61206) Add UI access for agent/ExtendedRead
Title: Message Title Tim Jacomb created an issue Jenkins / JENKINS-61206 Add UI access for agent/ExtendedRead Issue Type: Story Assignee: Unassigned Components: core Created: 2020-02-24 17:01 Priority: Minor Reporter: Tim Jacomb Agent/ExtendedRead currently only allows access via the API This should be extended to the UI, extended-read-permission-plugin should be updated to activate this permission as well Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-61205) Read-only system - Global security configuration
Title: Message Title Tim Jacomb created an issue Jenkins / JENKINS-61205 Read-only system - Global security configuration Issue Type: Story Assignee: Unassigned Components: core Created: 2020-02-24 16:59 Priority: Minor Reporter: Tim Jacomb Allow read-only access to the global security configuration page to users with Jenkins.SYSTEM_READ Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-61204) Read-only system - Global tool configuration
Title: Message Title Tim Jacomb created an issue Jenkins / JENKINS-61204 Read-only system - Global tool configuration Issue Type: Story Assignee: Tim Jacomb Components: core Created: 2020-02-24 16:45 Priority: Minor Reporter: Tim Jacomb Read-only view of Global tool configuration for Jenkins.SYSTEM_READ users Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-61203) Read-only system - Plugin manager
Title: Message Title Tim Jacomb created an issue Jenkins / JENKINS-61203 Read-only system - Plugin manager Issue Type: Story Assignee: Tim Jacomb Components: core Created: 2020-02-24 16:42 Priority: Minor Reporter: Tim Jacomb Allow access to Manage plugins sections to Jenkins.SYSTEM_READ users Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-61202) Read only view of job configuration page
Title: Message Title Tim Jacomb updated an issue Jenkins / JENKINS-61202 Read only view of job configuration page Change By: Tim Jacomb Labels: lts-candidate Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.204752.158256225.5519.1582562400223%40Atlassian.JIRA.
[JIRA] (JENKINS-61202) Read only view of job configuration page
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-61202 Read only view of job configuration page Change By: Daniel Beck Issue Type: Story Improvement Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.204752.158256225.5521.1582562400269%40Atlassian.JIRA.
[JIRA] (JENKINS-61202) Read only view of job configuration page
Title: Message Title Tim Jacomb assigned an issue to Tim Jacomb Jenkins / JENKINS-61202 Read only view of job configuration page Change By: Tim Jacomb Assignee: Tim Jacomb Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.204752.158256225.5518.1582562340050%40Atlassian.JIRA.
[JIRA] (JENKINS-61202) Read only view of job configuration page
Title: Message Title Tim Jacomb created an issue Jenkins / JENKINS-61202 Read only view of job configuration page Issue Type: Story Assignee: Unassigned Components: core Created: 2020-02-24 16:37 Priority: Minor Reporter: Tim Jacomb Make job/configure view look read only with the extended read permission Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-60998) Azure VM Agents is using incorrect subscription id
Title: Message Title Ali Allomani commented on JENKINS-60998 Re: Azure VM Agents is using incorrect subscription id Jie Shen maybe you can take a look into this ? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.204466.1580995914000.5504.1582561560327%40Atlassian.JIRA.
[JIRA] (JENKINS-47597) Jenkins UI wording for removing a GitHub-based multibranch Pipeline project is very misleading
Title: Message Title Mark Stosberg commented on JENKINS-47597 Re: Jenkins UI wording for removing a GitHub-based multibranch Pipeline project is very misleading I agree, the current wording sounds like it's going to delete your git repository. Yikes! If it's going to delete the Jenkins Pipeline, why not just call it "Pipeline" in the menu? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.186010.1508474112000.5506.1582561560402%40Atlassian.JIRA.
[JIRA] (JENKINS-61201) Read-only system - About jenkins
Title: Message Title Tim Jacomb created an issue Jenkins / JENKINS-61201 Read-only system - About jenkins Issue Type: Story Assignee: Unassigned Components: core Created: 2020-02-24 15:49 Priority: Minor Reporter: Tim Jacomb Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To
[JIRA] (JENKINS-61201) Read-only system - About jenkins
Title: Message Title Tim Jacomb assigned an issue to Tim Jacomb Jenkins / JENKINS-61201 Read-only system - About jenkins Change By: Tim Jacomb Assignee: Tim Jacomb Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.204750.1582559353000.5495.1582559400175%40Atlassian.JIRA.
[JIRA] (JENKINS-12548) Read-only system configuration browsing
Title: Message Title Tim Jacomb updated an issue Jenkins / JENKINS-12548 Read-only system configuration browsing Change By: Tim Jacomb Issue Type: New Feature Epic Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.142914.1327605395000.5491.1582559340731%40Atlassian.JIRA.
[JIRA] (JENKINS-61197) Running a job with a custom workspace set to eg. 'F:\' causes NullPointerException
Title: Message Title Oleg Nenashev commented on JENKINS-61197 Re: Running a job with a custom workspace set to eg. 'F:\' causes NullPointerException There is no recent changes in the codebase: https://github.com/jenkinsci/jenkins/blame/master/core/src/main/java/hudson/FilePath.java#L1327 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.204745.1582545957000.5493.1582559340754%40Atlassian.JIRA.
[JIRA] (JENKINS-61164) Configure Clouds - no credentials visible for vSphere Cloud
Title: Message Title Nick Jones updated JENKINS-61164 Jenkins / JENKINS-61164 Configure Clouds - no credentials visible for vSphere Cloud Change By: Nick Jones Status: Open Fixed but Unreleased Resolution: Duplicate Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.204698.1582196162000.5447.1582558320597%40Atlassian.JIRA.
[JIRA] (JENKINS-61198) Thresholds not reliable
Title: Message Title Simon Richter updated JENKINS-61198 Jenkins / JENKINS-61198 Thresholds not reliable Change By: Simon Richter Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.204746.1582552124000.5413.1582556880198%40Atlassian.JIRA.
[JIRA] (JENKINS-61198) Thresholds not reliable
Title: Message Title Simon Richter updated JENKINS-61198 Jenkins / JENKINS-61198 Thresholds not reliable Change By: Simon Richter Status: Open Fixed but Unreleased Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.204746.1582552124000.5411.1582556820283%40Atlassian.JIRA.
[JIRA] (JENKINS-61198) Thresholds not reliable
Title: Message Title Simon Richter commented on JENKINS-61198 Re: Thresholds not reliable Okay, that was me being stupid and interpreting "greater than" as "greater or equal". Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.204746.1582552124000.5409.1582556820252%40Atlassian.JIRA.
[JIRA] (JENKINS-61198) Thresholds not reliable
Title: Message Title Simon Richter commented on JENKINS-61198 Re: Thresholds not reliable Wait, am I being stupid? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.204746.1582552124000.5391.1582556040107%40Atlassian.JIRA.
[JIRA] (JENKINS-61198) Thresholds not reliable
Title: Message Title Simon Richter edited a comment on JENKINS-61198 Re: Thresholds not reliable Thresholds are "1", "1", empty, empty: !warn.png|thumbnail!With 1 failing test, I'd expect this to give me "unstable" Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.204746.1582552124000.5382.1582554780201%40Atlassian.JIRA.
[JIRA] (JENKINS-61200) Missing authentication when downloading Avatar
Title: Message Title
Jakub Bochenski created an issue
Jenkins / JENKINS-61200
Missing authentication when downloading Avatar
Issue Type:
Bug
Assignee:
Unassigned
Components:
bitbucket-branch-source-plugin
Created:
2020-02-24 14:30
Priority:
Major
Reporter:
Jakub Bochenski
I'm seeing those errors in the log, I expect the credentials are valid since other functions of the plugin work
Feb 24, 2020 2:27:18 PM INFO com.cloudbees.jenkins.plugins.bitbucket.BitbucketTeamMetadataAction$BitbucketAvatarCacheSource fetch
IOException: I/O error when accessing URL: /rest/api/1.0/projects/J4A/avatar.png
com.cloudbees.jenkins.plugins.bitbucket.api.BitbucketRequestException: HTTP request error. Status: 401: .
HttpResponseProxy{HTTP/1.1 401 [Server: nginx/1.6.2, Date: Mon, 24 Feb 2020 14:27:18 GMT, Content-Type: application/json;charset=UTF-8, Transfer-Encoding: chunked, Connection: keep-alive, X-AREQUESTID: @16SCIDTx987x473696093x3, X-ASEN: SEN-9755481, WWW-Authenticate: Basic realm="Atlassian Bitbucket", Vary: Accept-Encoding] org.apache.http.client.entity.DecompressingEntity@7fe95b62}
at com.cloudbees.jenkins.plugins.bitbucket.server.client.BitbucketServerAPIClient.getImageRequest(BitbucketServerAPIClient.java:877)
at com.cloudbees.jenkins.plugins.bitbucket.server.client.BitbucketServerAPIClient.getTeamAvatar(BitbucketServerAPIClient.java:728)
Caused: java.io.IOException: I/O error when accessing URL: /rest/api/1.0/projects/J4A/avatar.png
at com.cloudbees.jenkins.plugins.bitbucket.server.client.BitbucketServerAPIClient.getTeamAvatar(BitbucketServerAPIClient.java:733)
at com.cloudbees.jenkins.plugins.bitbucket.BitbucketTeamMetadataAction$BitbucketAvatarCacheSource.fetch(BitbucketTeamMetadataAction.java:80)
at
[JIRA] (JENKINS-61198) Thresholds not reliable
Title: Message Title Simon Richter commented on JENKINS-61198 Re: Thresholds not reliable Thresholds are "1", "1", empty, empty: Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.204746.1582552124000.5379.1582554660520%40Atlassian.JIRA.
[JIRA] (JENKINS-61198) Thresholds not reliable
Title: Message Title Simon Richter updated an issue Jenkins / JENKINS-61198 Thresholds not reliable Change By: Simon Richter Attachment: warn.png Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.204746.1582552124000.5377.1582554660397%40Atlassian.JIRA.
[JIRA] (JENKINS-61199) Job Configuration History Plugin doesn't seem to honor "Max number of days to keep history entries" for deleted jobs
Title: Message Title Martin Jost created an issue Jenkins / JENKINS-61199 Job Configuration History Plugin doesn't seem to honor "Max number of days to keep history entries" for deleted jobs Issue Type: Bug Assignee: Stefan Brausch Components: jobconfighistory-plugin Created: 2020-02-24 14:18 Environment: Jenkins 2.204.2 (newest LTS) Job Configuration History Plugin 2.24 (most recent) Java OpenJDK8U-jdk_x64_linux_hotspot_8u232b09 Running on Redhat 7 No container Labels: plugin Priority: Minor Reporter: Martin Jost I have configured the plugin as follow: Use different history directory than default:: [Empty] Max number of history entries to keep: 20 Max number of days to keep history entries: 365 Max number of history entries to show per page: [Empty] Configuration exclude file pattern: queue|nodeMonitors|UpdateCenter|global-build-stats Do not save duplicate history: ON * Save Maven module configuration changes: ON * Show build badges: Always Exclude users: [Empty] Now to my amazement, I found on the FS files like:
[JIRA] (JENKINS-61197) Running a job with a custom workspace set to eg. 'F:\' causes NullPointerException
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-61197 Running a job with a custom workspace set to eg. 'F:\' causes NullPointerException Change By: Oleg Nenashev Labels: regression Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.204745.1582545957000.5371.1582552980147%40Atlassian.JIRA.
[JIRA] (JENKINS-61030) Runtime results from UFT to Jenkins Console
Title: Message Title MANJU commented on JENKINS-61030 Re: Runtime results from UFT to Jenkins Console Anda Sorina Laakso yes we have created the Enhancement request : OCTCR17E389018 https://softwaresupport.softwaregrp.com/doc/KM03602415 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.204504.1581330691000.5369.1582552740100%40Atlassian.JIRA.
[JIRA] (JENKINS-61198) Thresholds not reliable
Title: Message Title Nikolas Falco commented on JENKINS-61198 Re: Thresholds not reliable As you can see from the logs the threadshold check is performed at the end. INFO: Starting to record. INFO: Processing BoostTest-1.x (default) INFO: [BoostTest-1.x (default)] - 7 test report file(s) were found with the pattern 'build/qa/**/*.boost-results.xml' relative to '/var/lib/jenkins-agent/workspace/linux-kicad-head' for the testing framework 'BoostTest-1.x (default)'. INFO: Processing JUnit INFO: [JUnit] - 6 test report file(s) were found with the pattern 'build/qa/*.xunit-results/*.xml' relative to '/var/lib/jenkins-agent/workspace/linux-kicad-head' for the testing framework 'JUnit'. INFO: Processing CTest-Version 3.x (default) INFO: [CTest-Version 3.x (default)] - 2 test report file(s) were found with the pattern 'build/Testing/**/*.xml' relative to '/var/lib/jenkins-agent/workspace/linux-kicad-head' for the testing framework 'CTest-Version 3.x (default)'. INFO: Check 'Failed Tests' threshold. INFO: Setting the build status to SUCCESS INFO: Stopping recording. How did you configure the threshold? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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-61198) Thresholds not reliable
Title: Message Title Simon Richter updated an issue Jenkins / JENKINS-61198 Thresholds not reliable Change By: Simon Richter We have a few jobs that use the xUnit plugin with multiple sources to collect results from multiple test frameworks. The build should be marked as unstable if there is a single test failure.In several builds, the build is marked as successful with multiple test failures. My suspicion is that thresholds are checked only for one of the sources, not all of them cumulatively.[Example build| [ https://jenkins.simonrichter.eu/job/linux-kicad-head/4211/] Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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-61198) Thresholds not reliable
Title: Message Title Simon Richter updated an issue Jenkins / JENKINS-61198 Thresholds not reliable Change By: Simon Richter We have a few jobs that use the xUnit plugin with multiple sources to collect results from multiple test frameworks. The build should be marked as unstable if there is a single test failure.In several builds, the build is marked as successful with multiple test failures. My suspicion is that thresholds are checked only for one of the sources, not all of them cumulatively.[ [ Example build ] |[https://jenkins.simonrichter.eu/job/linux-kicad-head/4211/] |https://jenkins.simonrichter.eu/job/linux-kicad-head/4211/] Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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-61198) Thresholds not reliable
Title: Message Title Simon Richter updated an issue Jenkins / JENKINS-61198 Thresholds not reliable Change By: Simon Richter We have a few jobs that use the xUnit plugin with multiple sources to collect results from multiple test frameworks. The build should be marked as unstable if there is a single test failure.In several builds, the build is marked as successful with multiple test failures. My suspicion is that thresholds are checked only for one of the sources, not all of them cumulatively.[ [ Example build] ( |[ https://jenkins.simonrichter.eu/job/linux-kicad-head/4211/ ) ]|https://jenkins.simonrichter.eu/job/linux-kicad-head/4211/] Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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-61198) Thresholds not reliable
Title: Message Title Simon Richter created an issue Jenkins / JENKINS-61198 Thresholds not reliable Issue Type: Bug Assignee: Nikolas Falco Components: xunit-plugin Created: 2020-02-24 13:48 Priority: Minor Reporter: Simon Richter We have a few jobs that use the xUnit plugin with multiple sources to collect results from multiple test frameworks. The build should be marked as unstable if there is a single test failure. In several builds, the build is marked as successful with multiple test failures. My suspicion is that thresholds are checked only for one of the sources, not all of them cumulatively. [Example build](https://jenkins.simonrichter.eu/job/linux-kicad-head/4211/) Add Comment
[JIRA] (JENKINS-57795) Orphaned EC2 instances after Jenkins restart
Title: Message Title Jakub Bochenski commented on JENKINS-57795 Re: Orphaned EC2 instances after Jenkins restart We are still seeing issues with spawning instances after restart. Do you plan to work on resolving this? FABRIZIO MANFREDIRaihaan Shouhell Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.199745.1559315049000.5353.1582550760205%40Atlassian.JIRA.
[JIRA] (JENKINS-60920) Update the Header and Breadcrumb styles
Title: Message Title Oleg Nenashev resolved as Fixed Jenkins / JENKINS-60920 Update the Header and Breadcrumb styles Change By: Oleg Nenashev Status: In Progress Resolved Resolution: Fixed Released As: Jenkins 2.222 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.204317.1580393533000.5347.1582548960489%40Atlassian.JIRA.
[JIRA] (JENKINS-60266) Add a Jenkins.CONFIGURE permission to be able to configure Jenkins without ADMINISTER
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-60266 Add a Jenkins.CONFIGURE permission to be able to configure Jenkins without ADMINISTER Change By: Oleg Nenashev Released As: Jenkins 2. 221 222 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.203254.1574682467000.5349.1582548960514%40Atlassian.JIRA.
[JIRA] (JENKINS-60966) Administrative monitors global configuration long and unordered
Title: Message Title Oleg Nenashev updated JENKINS-60966 Jenkins / JENKINS-60966 Administrative monitors global configuration long and unordered Change By: Oleg Nenashev Status: Fixed but Unreleased Resolved Released As: Jenkins 2.222 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.204429.158088555.5340.1582548900849%40Atlassian.JIRA.
[JIRA] (JENKINS-12548) Read-only system configuration browsing
Title: Message Title Oleg Nenashev commented on JENKINS-12548 Re: Read-only system configuration browsing Foundation bits were landed in https://jenkins.io/changelog/#v2.222 . Now we definitely need an EPIC Tim Jacomb Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.142914.1327605395000.5333.1582548900702%40Atlassian.JIRA.
[JIRA] (JENKINS-61121) Too many open files when using Resource root URL
Title: Message Title Oleg Nenashev updated JENKINS-61121 Jenkins / JENKINS-61121 Too many open files when using Resource root URL Change By: Oleg Nenashev Status: Fixed but Unreleased Resolved Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.204636.1582020729000.5343.1582548900905%40Atlassian.JIRA.
[JIRA] (JENKINS-40640) @Library not working with pipeline model
Title: Message Title Prabhu Shankar commented on JENKINS-40640 Re: @Library not working with pipeline model The issue is reproducible in Jenkins ver. 2.204.2 too, Is this really a duplicate for JENKINS-40642? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.177339.1482421375000.5329.1582548540192%40Atlassian.JIRA.
[JIRA] (JENKINS-40640) @Library not working with pipeline model
Title: Message Title Prabhu Shankar stopped work on JENKINS-40640 Change By: Prabhu Shankar Status: In Progress Open Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.177339.1482421375000.5325.1582548360507%40Atlassian.JIRA.
[JIRA] (JENKINS-40640) @Library not working with pipeline model
Title: Message Title Prabhu Shankar updated JENKINS-40640 Jenkins / JENKINS-40640 @Library not working with pipeline model Change By: Prabhu Shankar Status: In Review Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.177339.1482421375000.5322.1582548301177%40Atlassian.JIRA.
[JIRA] (JENKINS-40640) @Library not working with pipeline model
Title: Message Title Prabhu Shankar updated JENKINS-40640 Jenkins / JENKINS-40640 @Library not working with pipeline model Change By: Prabhu Shankar Resolution: Duplicate Status: Closed In Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.177339.1482421375000.5317.1582548300822%40Atlassian.JIRA.
[JIRA] (JENKINS-55106) Build stuck on final "exit 0"
Title: Message Title kredens edited a comment on JENKINS-55106 Re: Build stuck on final "exit 0" I don can 't see the issue anymore using v2.204.2 and newest set of BlueOcean plugins. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.196167.1544451681000.5286.1582548182073%40Atlassian.JIRA.
[JIRA] (JENKINS-55106) Build stuck on final "exit 0"
Title: Message Title kredens commented on JENKINS-55106 Re: Build stuck on final "exit 0" I don't see the issue anymore using v2.204.2 and newest set of BlueOcean plugins. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.196167.1544451681000.5284.1582548182040%40Atlassian.JIRA.
[JIRA] (JENKINS-61007) pipeline-model-definition is using findbugs without providing / depending on it
Title: Message Title Wadeck Follonier commented on JENKINS-61007 Re: pipeline-model-definition is using findbugs without providing / depending on it Updating to 2.220 solves the problem, at least locally Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.204477.1581032748000.5254.1582547460414%40Atlassian.JIRA.
[JIRA] (JENKINS-41037) Unabel to serialize mock because of ConcurrentModificationException
Title: Message Title Steve Clarke commented on JENKINS-41037 Re: Unabel to serialize mock because of ConcurrentModificationException I see exactly the same issue; [2020-02-23T12:22:16.287Z] java.util.ConcurrentModificationException [2020-02-23T12:22:16.287Z] at java.util.ArrayList$Itr.checkForComodification(ArrayList.java:909) [2020-02-23T12:22:16.287Z] at java.util.ArrayList$Itr.next(ArrayList.java:859) [2020-02-23T12:22:16.287Z] at com.thoughtworks.xstream.converters.collections.CollectionConverter.marshal(CollectionConverter.java:73) [2020-02-23T12:22:16.287Z] at com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:69) [2020-02-23T12:22:16.287Z] at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:58) [2020-02-23T12:22:16.287Z] at com.thoughtworks.xstream.core.AbstractReferenceMarshaller$1.convertAnother(AbstractReferenceMarshaller.java:84) [2020-02-23T12:22:16.287Z] at hudson.util.RobustReflectionConverter.marshallField(RobustReflectionConverter.java:263) [2020-02-23T12:22:16.287Z] at hudson.util.RobustReflectionConverter$2.writeField(RobustReflectionConverter.java:250) [2020-02-23T12:22:16.287Z] Caused: java.lang.RuntimeException: Failed to serialize org.jenkinsci.plugins.workflow.libs.LibrariesAction#libraries for class org.jenkinsci.plugins.workflow.libs.LibrariesAction [2020-02-23T12:22:16.288Z] at hudson.util.RobustReflectionConverter$2.writeField(RobustReflectionConverter.java:254) [2020-02-23T12:22:16.288Z] at hudson.util.RobustReflectionConverter$2.visit(RobustReflectionConverter.java:222) [2020-02-23T12:22:16.288Z] at com.thoughtworks.xstream.converters.reflection.PureJavaReflectionProvider.visitSerializableFields(PureJavaReflectionProvider.java:138) [2020-02-23T12:22:16.288Z] at hudson.util.RobustReflectionConverter.doMarshal(RobustReflectionConverter.java:208) [2020-02-23T12:22:16.288Z] at hudson.util.RobustReflectionConverter.marshal(RobustReflectionConverter.java:149) [2020-02-23T12:22:16.288Z] at com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:69) [2020-02-23T12:22:16.288Z] at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:58) [2020-02-23T12:22:16.288Z] at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:43) [2020-02-23T12:22:16.288Z] at com.thoughtworks.xstream.core.AbstractReferenceMarshaller$1.convertAnother(AbstractReferenceMarshaller.java:88) [2020-02-23T12:22:16.288Z] at com.thoughtworks.xstream.converters.collections.AbstractCollectionConverter.writeItem(AbstractCollectionConverter.java:64) [2020-02-23T12:22:16.288Z] at com.thoughtworks.xstream.converters.collections.CollectionConverter.marshal(CollectionConverter.java:74) [2020-02-23T12:22:16.288Z] at com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:69) [2020-02-23T12:22:16.288Z] at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:58) [2020-02-23T12:22:16.288Z] at com.thoughtworks.xstream.core.AbstractReferenceMarshaller$1.convertAnother(AbstractReferenceMarshaller.java:84) [2020-02-23T12:22:16.288Z] at hudson.util.RobustReflectionConverter.marshallField(RobustReflectionConverter.java:263) [2020-02-23T12:22:16.288Z] at hudson.util.RobustReflectionConverter$2.writeField(RobustReflectionConverter.java:250) [2020-02-23T12:22:16.288Z] Caused: java.lang.RuntimeException: Failed to serialize
[JIRA] (JENKINS-61197) Running a job with a custom workspace set to eg. 'F:\' causes NullPointerException
Title: Message Title Frank Schlottmann-Gödde updated an issue Jenkins / JENKINS-61197 Running a job with a custom workspace set to eg. 'F:\' causes NullPointerException Change By: Frank Schlottmann-Gödde After upgrading fom ver 2.211 to ver 2.221 jobs with a drive as custom workspace throw a NullPointerException immediately: *00:00:00.002* Running as SYSTEM *00:00:00.002* [EnvInject] - Loading node environment variables. *00:00:00.003* Baue auf Master in Arbeitsbereich F:\ *00:00:00.004* FATAL: null *00:00:00.005* java.lang.NullPointerException *00:00:00.005* at hudson.FilePath.sibling(FilePath.java:1327) *00:00:00.005* at hudson.slaves.WorkspaceList.tempDir(WorkspaceList.java:306) *00:00:00.005* at hudson.model.AbstractBuild.getEnvironment(AbstractBuild.java:868) *00:00:00.005* at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:852) *00:00:00.005* at hudson.scm.SCM.checkout(SCM.java:505) *00:00:00.005* at hudson.model.AbstractProject.checkout(AbstractProject.java:1206) *00:00:00.005* at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:574) *00:00:00.005* at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) *00:00:00.005* at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:499) *00:00:00.005* at hudson.model.Run.execute(Run.java:1856) *00:00:00.005* at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) *00:00:00.005* at hudson.model.ResourceController.execute(ResourceController.java:97) *00:00:00.005* at hudson.model.Executor.run(Executor.java:428) *00:00:00.005* ERROR: Build step failed with exception Add Comment
[JIRA] (JENKINS-61197) Running a job with a custom workspace set to eg. 'F:\' causes NullPointerException
Title: Message Title Frank Schlottmann-Gödde updated an issue Jenkins / JENKINS-61197 Running a job with a custom workspace set to eg. 'F:\' causes NullPointerException Change By: Frank Schlottmann-Gödde After upgrading fom ver 2.211 to ver 2.221 jobs with a drive as custom workspace throw a NullPointerException immediately: Running as SYSTEM[EnvInject] - Loading node environment variables.Baue auf Master in Arbeitsbereich F:\FATAL: nulljava.lang.NullPointerException at hudson.FilePath.sibling(FilePath.java:1327) at hudson.slaves.WorkspaceList.tempDir(WorkspaceList.java:306) at hudson.model.AbstractBuild.getEnvironment(AbstractBuild.java:868) at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:852) at hudson.scm.SCM.checkout(SCM.java:505) at hudson.model.AbstractProject.checkout(AbstractProject.java:1206) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:574) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:499) at hudson.model.Run.execute(Run.java:1856) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:428)ERROR: Build step failed with exception Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-61197) Running a job with a custom workspace set to eg. 'F:\' causes NullPointerException
Title: Message Title Frank Schlottmann-Gödde updated an issue Jenkins / JENKINS-61197 Running a job with a custom workspace set to eg. 'F:\' causes NullPointerException Change By: Frank Schlottmann-Gödde After upgrading fom ver 2.211 to ver 2.221 jobs with a drive as custom workspace throw a NullPointerException immediately: *00:00:00.002* Running as SYSTEM *00:00:00.002* [EnvInject] - Loading node environment variables. *00:00:00.003* Baue auf Master in Arbeitsbereich F:\ *00:00:00.004* FATAL: null *00:00:00.005* java.lang.NullPointerException *00:00:00.005* at hudson.FilePath.sibling(FilePath.java:1327) *00:00:00.005* at hudson.slaves.WorkspaceList.tempDir(WorkspaceList.java:306) *00:00:00.005* at hudson.model.AbstractBuild.getEnvironment(AbstractBuild.java:868) *00:00:00.005* at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:852) *00:00:00.005* at hudson.scm.SCM.checkout(SCM.java:505) *00:00:00.005* at hudson.model.AbstractProject.checkout(AbstractProject.java:1206) *00:00:00.005* at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:574) *00:00:00.005* at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) *00:00:00.005* at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:499) *00:00:00.005* at hudson.model.Run.execute(Run.java:1856) *00:00:00.005* at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) *00:00:00.005* at hudson.model.ResourceController.execute(ResourceController.java:97) *00:00:00.005* at hudson.model.Executor.run(Executor.java:428) *00:00:00.005* ERROR: Build step failed with exception Add Comment
[JIRA] (JENKINS-61197) Running a job with a custom workspace set to eg. 'F:\' causes NullPointerException
Title: Message Title Frank Schlottmann-Gödde created an issue Jenkins / JENKINS-61197 Running a job with a custom workspace set to eg. 'F:\' causes NullPointerException Issue Type: Bug Assignee: Unassigned Components: core Created: 2020-02-24 12:05 Environment: Jenkins ver 2.221, Windows SBS 2012 Priority: Major Reporter: Frank Schlottmann-Gödde After upgrading fom ver 2.211 to ver 2.221 jobs with a drive as custom workspace throw a NullPointerException immediately: 00:00:00.002 Running as SYSTEM*00:00:00.002* [EnvInject] - Loading node environment variables.00:00:00.003 Baue auf Master in Arbeitsbereich F:*00:00:00.004* FATAL: null*00:00:00.005* java.lang.NullPointerException*00:00:00.005* at hudson.FilePath.sibling(FilePath.java:1327)00:00:00.005 at hudson.slaves.WorkspaceList.tempDir(WorkspaceList.java:306)00:00:00.005 at hudson.model.AbstractBuild.getEnvironment(AbstractBuild.java:868)00:00:00.005 at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:852)00:00:00.005 at hudson.scm.SCM.checkout(SCM.java:505)00:00:00.005 at hudson.model.AbstractProject.checkout(AbstractProject.java:1206)00:00:00.005 at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:574)00:00:00.005 at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)00:00:00.005 at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:499)00:00:00.005 at hudson.model.Run.execute(Run.java:1856)00:00:00.005 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)00:00:00.005 at hudson.model.ResourceController.execute(ResourceController.java:97)00:00:00.005 at hudson.model.Executor.run(Executor.java:428)00:00:00.005 ERROR: Build step failed with exception
[JIRA] (JENKINS-61146) ec2-plugin occassional traceback
Title: Message Title Tobias Kahse commented on JENKINS-61146 Re: ec2-plugin occassional traceback I've experienced the same issue. It was caused by some of my builds not having a label because they have `agent any` defined in their pipeline. The PR https://github.com/jenkinsci/ec2-plugin/pull/431 solves this issue by ignoring queued builds without any label. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.204676.1582116605000.5240.1582545600211%40Atlassian.JIRA.
