[JIRA] (JENKINS-56976) WAIT ERROR even though when JESINTERFACELEVEL is 2
Title: Message Title Alexander Shcherbakov edited a comment on JENKINS-56976 Re: WAIT ERROR even though when JESINTERFACELEVEL is 2 Just in cae case , the code may be found in separate branch at GitHub. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56976) WAIT ERROR even though when JESINTERFACELEVEL is 2
Title: Message Title Alexander Shcherbakov commented on JENKINS-56976 Re: WAIT ERROR even though when JESINTERFACELEVEL is 2 Just in cae, the code may be found in separate branch at GitHub. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56976) WAIT ERROR even though when JESINTERFACELEVEL is 2
Title: Message Title bharath kumar commented on JENKINS-56976 Re: WAIT ERROR even though when JESINTERFACELEVEL is 2 thanks Alexander, i will ask my admin to install the new debug version Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39343) Persistent search/overviews/filtered views
Title: Message Title Craig Rodrigues commented on JENKINS-39343 Re: Persistent search/overviews/filtered views Reinhold Füreder I disagree. I work in a team where users (not just admins) need to get an overview of lots of jobs. The Blue Ocean overview is definitely not as good as the Classic UI for this. I'm facing this same issues as Sverre Moe. Those are all very good issues that you raise. If you haven't done so already, I recommend going to the https://gitter.im/jenkinsci/blueocean-plugin gitter channel and raise the issues you have there. It looks like Blue Ocean is not resourced as much as it was when the project was originally started, but there are are a few devs working on it, and they do monitor that channel. If you have time, you may also want to give it a try and try to understand the code and submit fixes I've started going that. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56976) WAIT ERROR even though when JESINTERFACELEVEL is 2
Title: Message Title Alexander Shcherbakov updated JENKINS-56976 Jenkins / JENKINS-56976 WAIT ERROR even though when JESINTERFACELEVEL is 2 Change By: Alexander Shcherbakov Status: In Review Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39343) Persistent search/overviews/filtered views
Title: Message Title Reinhold Füreder commented on JENKINS-39343 Re: Persistent search/overviews/filtered views Naive food for thoughts: Jenkins admins have to use Classic UI anyways, and that is OK. By contrast Jenkins users (= developers) can/shall use nice/modern/new Blue Ocean UI for everything the need (so failure notifications always link primarily to BO) and they do NOT need the overview (like Jenkins admins)? So I can perfectly live with this issue being closed – of course assuming that (Cloud Bees) Jenkins development resources are then spent on more vital things like the following https://issues.jenkins-ci.org/browse/JENKINS-44869 https://issues.jenkins-ci.org/browse/JENKINS-47286 https://issues.jenkins-ci.org/browse/JENKINS-46715 https://issues.jenkins-ci.org/browse/JENKINS-46521 https://issues.jenkins-ci.org/browse/JENKINS-39203 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47286) Support skipping stages in scripted pipelines for nice visualization in blue ocean and classic UI stage view
Title: Message Title
Reinhold Füreder commented on JENKINS-47286
Re: Support skipping stages in scripted pipelines for nice visualization in blue ocean and classic UI stage view
While I am not sure if this is the correct/perfect/recommended place for this question, it admittedly fits to this issue and I can actually give you a little hint My approach for this is to have a skipableStage step in my shared Jenkins pipeline library that wraps the default/standard stage step, so the usage is almost like normally:
...
acmeSharedLibrary.skipableStage("stage name") {
... // normal stage implementation
}
...
... and the steps implementation in pseudo code is:
stage(stageName) {
if (currentBuild.result) {
echo "Skipping stage '${stageName}' due to build result '${currentBuild.result}'..."
Result result = Result.fromString(currentBuild.result)
markStageSkippedForResult(stageName, result) // via the aformentioned workaround
} else {
body() // which is the closure block of this "skippableStage"
}
}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
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.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56981) VM failed to provision when use Pool Retention Strategy
Title: Message Title Jie Shen commented on JENKINS-56981 Re: VM failed to provision when use Pool Retention Strategy Hi di wang, do you mean no VM could be created successfully with your settings? I just check it in my environment, it seems to work well for me. Your log is just for clean up action, could you please provide the reason for its failed deployment? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54776) Node stays suspended after node is started
Title: Message Title Jie Shen commented on JENKINS-54776 Re: Node stays suspended after node is started Hi All, I could provide a preview build which will force reconnect and may mitigate the issue. I cannot make sure it will work for every cases since this problem is hard to reproduce. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56972) limit number of concurrent provissioning vm's
Title: Message Title Jie Shen commented on JENKINS-56972 Re: limit number of concurrent provissioning vm's Make sense. I will check how to achieve this feature. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56969) Unable to connect to slave via ssh
Title: Message Title Nicketa Kumar commented on JENKINS-56969 Re: Unable to connect to slave via ssh It is .PEM. This is the type of key being generated by aws. Also as you can see in log, the error is "Caused by: java.io.IOException: PEM problem: it is of unknown type" which means jenkins is unable to read it as per my understanding. The second issue is, if I try Host Key Verification Strategy as Manually trusted key Verification Strategy, then there is a bug in jenkins. you can see here bug-screenshot.JPG Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56988) Unable to connect to GCE using plugin via ssh
Title: Message Title Rukeith Tseng created an issue Jenkins / JENKINS-56988 Unable to connect to GCE using plugin via ssh Issue Type: Bug Assignee: Evan Brown Components: google-compute-engine-plugin Created: 2019-04-12 02:47 Environment: Jenkins v2.150.3 google-compute-engine-plugin v3.0.0 Labels: plugin slave Priority: Minor Reporter: Rukeith Tseng I use the plugin to create a slave node on GCE, but the node is always offline. I saw the log is below. SSH cannot connect to GCE. just before slave jenkins-slave-916wdt gets launched ... executing pre-launch scripts ... Apr 12, 2019 2:31:47 AM null FINEST: Instance jenkins-slave-916wdt is running and ready... Apr 12, 2019 2:31:47 AM null INFO: Launching instance: jenkins-slave-916wdt Apr 12, 2019 2:31:54 AM null INFO: bootstrap Apr 12, 2019 2:31:54 AM null INFO: Getting keypair... Apr 12, 2019 2:31:54 AM null INFO: Using autogenerated keypair Apr 12, 2019 2:31:54 AM null INFO: Authenticating as jenkins Apr 12, 2019 2:31:55 AM null INFO: Connecting to 35.229.250.191 on port 22, with timeout 1. Apr 12, 2019 2:31:56 AM null INFO: Failed to connect via ssh: There was a problem while connecting to 35.229.250.191:22 Apr 12, 2019 2:31:56 AM null INFO: Waiting for SSH to come up. Sleeping 5. Apr 12, 2019 2:32:01 AM null INFO: Connecting to 35.229.250.191 on port 22, with timeout 1. Apr 12, 2019 2:32:01 AM null INFO: Failed to
[JIRA] (JENKINS-53017) Jenkins slave can't connect via ssh to GCE instance
Title: Message Title Rukeith Tseng commented on JENKINS-53017 Re: Jenkins slave can't connect via ssh to GCE instance Why this issue been closed. Is it been solved? How to solve it? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39343) Persistent search/overviews/filtered views
Title: Message Title Craig Rodrigues commented on JENKINS-39343 Re: Persistent search/overviews/filtered views I agree with @Sverre and others. The Blue Ocean UI for displaying hundreds of pipelines is worse than the Classic UI. If Blue Ocean had the ability to navigate through folders, that would be an improvement. Also, if Blue Ocean supported views, that would be an improvement. When you have hundreds of jobs, displaying everything in a flat namespace view, and requiring the user to search in order to filter the display of pipelines is not convenient. This gap in the UI/UX of Blue Ocean is one reason I constantly toggle back to the Classic UI. In the Classic UI, I make extensive use of folders and views to organize hundreds if Jenkins jobs. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56981) VM failed to provision when use Pool Retention Strategy
Title: Message Title Azure DevOps assigned an issue to Jie Shen Jenkins / JENKINS-56981 VM failed to provision when use Pool Retention Strategy Change By: Azure DevOps Assignee: Azure DevOps Jie Shen Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56981) VM failed to provision when use Pool Retention Strategy
Title: Message Title Azure DevOps started work on JENKINS-56981 Change By: Azure DevOps Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56972) limit number of concurrent provissioning vm's
Title: Message Title Azure DevOps started work on JENKINS-56972 Change By: Azure DevOps Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56972) limit number of concurrent provissioning vm's
Title: Message Title Azure DevOps assigned an issue to Jie Shen Jenkins / JENKINS-56972 limit number of concurrent provissioning vm's Change By: Azure DevOps Assignee: Azure DevOps Jie Shen Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39343) Persistent search/overviews/filtered views
Title: Message Title Michael Neale edited a comment on JENKINS-39343 Re: Persistent search/overviews/filtered views I opened this quiet a few years ago thinking it was a good idea. The searches add the search text to the urls - which are book markable (which is how people use it today). So the idea was so take these bookmarks and somehow install them in the app. I don't see that happening this way now though, so will close this. if/when anyone wants to have a crack at this - feel free to grab it. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39343) Persistent search/overviews/filtered views
Title: Message Title Michael Neale closed an issue as Postponed Jenkins / JENKINS-39343 Persistent search/overviews/filtered views Change By: Michael Neale Status: Open Closed Resolution: Postponed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39343) Persistent search/overviews/filtered views
Title: Message Title Michael Neale commented on JENKINS-39343 Re: Persistent search/overviews/filtered views I opened this quiet a few years ago thinking it was a good idea. The searches add the search text to the urls - which are book markable (which is how people use it today). So the idea was so take these bookmarks and somehow install them in the app. I don't see that happening this way now though, so will close this. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55560) stashing a symlink to a directory resolves the symlink instead of stashing it
Title: Message Title Aakash Sudhanwa commented on JENKINS-55560 Re: stashing a symlink to a directory resolves the symlink instead of stashing it Hi any time line on when this will be part of a Jenkins Release ? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-27911) Install unlimited strength JCE policy files together with JDK (optionally & automatically)
Title: Message Title Ronnie Zhou resolved as Not A Defect Closed per suggested. Jenkins / JENKINS-27911 Install unlimited strength JCE policy files together with JDK (optionally & automatically) Change By: Ronnie Zhou Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-27911) Install unlimited strength JCE policy files together with JDK (optionally & automatically)
Title: Message Title Mike Duigou commented on JENKINS-27911 Re: Install unlimited strength JCE policy files together with JDK (optionally & automatically) This issue can probably be closed since it is not an issue for 9 and later and 8u161 and later. The unlimited strength policy file is no longer needed. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56986) Deadlock on EC2 resources and build queue
Title: Message Title
Sam Gleske updated an issue
Jenkins / JENKINS-56986
Deadlock on EC2 resources and build queue
Change By:
Sam Gleske
This is either the same as or is related to JENKINS-53858. Feel free to close this as a duplicate and re-open JENKINS-53858 if it is the same.h2. EnvironmentI'm using a slightly modified version of the EC2 plugin specifically https://github.com/sgleske-ias/ec2-plugin/tree/ias-internal-2 ; it was built from EC2 plugin 1.42-SNAPSHOT before 1.42 was released - but after https://github.com/jenkinsci/ec2-plugin/commit/2f3a04a2d3ce0e51a755792b9d03b4fff4ebe9b3 was merged. So my custom version includes the deadlock fix for JENKINS-53858. - (CORRECTION my version did not include the fix from JENKINS-53858) h2. Deadlock behaviorDuring the deadlock the web UI was responsive. The deadlock blocked:* New items being queued (such as build events submitted through webhooks).* Autoscaling provisioning of new EC2 agents was blocked.* I was not able to delete the 1 EC2 agent that was provisioned but marked as offline because it was deadlocked.There was a "jenkins.util.Timer \[#8\]" thread in which most actions in my Jenkins instance were blocked. This was for the cloud provisioner. Most items that were blocked work blocked by this thread. "jenkins.util.Timer \[#8\]" thread was blocked by "jenkins.util.Timer \[#5\]" thread"jenkins.util.Timer \[#5\]" thread was blocked by waiting on "jenkins.util.Timer \[#8\]" and visa versa.h2. My hypothesisI believe they were blocked by the combination of the Queue lock and the EC2Cloud lock. Each needed both and was waiting on the other.h2. jenkins.util.Timer \[#8\] Thread Dump{noformat}jenkins.util.Timer [#8] at hudson.plugins.ec2.EC2Cloud.connect()Lcom/amazonaws/services/ec2/AmazonEC2; (EC2Cloud.java:748) at hudson.plugins.ec2.CloudHelper.getInstance(Ljava/lang/String;Lhudson/plugins/ec2/EC2Cloud;)Lcom/amazonaws/services/ec2/model/Instance; (CloudHelper.java:47) at hudson.plugins.ec2.CloudHelper.getInstanceWithRetry(Ljava/lang/String;Lhudson/plugins/ec2/EC2Cloud;)Lcom/amazonaws/services/ec2/model/Instance; (CloudHelper.java:25) at hudson.plugins.ec2.EC2Computer.getState()Lhudson/plugins/ec2/InstanceState; (EC2Computer.java:127) at hudson.plugins.ec2.EC2RetentionStrategy.internalCheck(Lhudson/plugins/ec2/EC2Computer;)J (EC2RetentionStrategy.java:112) at hudson.plugins.ec2.EC2RetentionStrategy.check(Lhudson/plugins/ec2/EC2Computer;)J (EC2RetentionStrategy.java:90) at hudson.plugins.ec2.EC2RetentionStrategy.check(Lhudson/model/Computer;)J (EC2RetentionStrategy.java:48) at hudson.slaves.ComputerRetentionWork$1.run()V (ComputerRetentionWork.java:72) at hudson.model.Queue._withLock(Ljava/lang/Runnable;)V (Queue.java:1381) at hudson.model.Queue.withLock(Ljava/lang/Runnable;)V (Queue.java:1258) at hudson.slaves.ComputerRetentionWork.doRun()V (ComputerRetentionWork.java:63) at hudson.triggers.SafeTimerTask.run()V (SafeTimerTask.java:72) at jenkins.security.ImpersonatingScheduledExecutorService$1.run()V
[JIRA] (JENKINS-53858) Deadlock on EC2 resources
Title: Message Title Sam Gleske commented on JENKINS-53858 Re: Deadlock on EC2 resources False alarm. I closed my issue as a duplicate because I realized my version did not include the deadlock fix. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56986) Deadlock on EC2 resources and build queue
Title: Message Title Sam Gleske closed an issue as Duplicate I misspoke. My compiled plugin does not include the deadlock fix. Jenkins / JENKINS-56986 Deadlock on EC2 resources and build queue Change By: Sam Gleske Status: Open Closed Resolution: Duplicate Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56986) Deadlock on EC2 resources and build queue
Title: Message Title
Sam Gleske updated an issue
Jenkins / JENKINS-56986
Deadlock on EC2 resources and build queue
Change By:
Sam Gleske
This is either the same as or is related to JENKINS-53858. Feel free to close this as a duplicate and re-open JENKINS-53858 if it is the same. h2. EnvironmentI'm using a slightly modified version of the EC2 plugin specifically [ https://github.com/sgleske-ias/ec2-plugin/tree/ias-internal- 1] 2 ; it was built from EC2 plugin 1.42-SNAPSHOT before 1.42 was released but after [ https://github.com/jenkinsci/ec2-plugin/commit/2f3a04a2d3ce0e51a755792b9d03b4fff4ebe9b3 ] was merged. So my custom version includes the deadlock fix for JENKINS-53858. h2. Deadlock behaviorDuring the deadlock the web UI was responsive. The deadlock blocked: * New items being queued (such as build events submitted through webhooks and other kinds of triggers ). * Autoscaling provisioning of new EC2 agents was blocked. * I was not able to delete the 1 EC2 agent that was provisioned but marked as offline because it was deadlocked.There was a * "jenkins.util.Timer \ [#8 \ ]" * thread in which most actions in my Jenkins instance were blocked. This was for the cloud provisioner. Most items that were blocked work blocked by this thread. * "jenkins.util.Timer \ [#8 \ ]" * thread was blocked by * "jenkins.util.Timer \ [#5 \ ]" * thread * "jenkins.util.Timer \ [#5 \ ]" * thread was blocked by waiting on * "jenkins.util.Timer \ [#8 \ ]" * and visa versa. h2. My hypothesisI believe they were blocked by the combination of the Queue lock and the EC2Cloud lock. Each needed both and was waiting on the other. h2. jenkins.util.Timer \ [#8 \ ] Thread Dump {noformat}jenkins.util.Timer [#8] at hudson.plugins.ec2.EC2Cloud.connect()Lcom/amazonaws/services/ec2/AmazonEC2; (EC2Cloud.java:748) at hudson.plugins.ec2.CloudHelper.getInstance(Ljava/lang/String;Lhudson/plugins/ec2/EC2Cloud;)Lcom/amazonaws/services/ec2/model/Instance; (CloudHelper.java:47) at hudson.plugins.ec2.CloudHelper.getInstanceWithRetry(Ljava/lang/String;Lhudson/plugins/ec2/EC2Cloud;)Lcom/amazonaws/services/ec2/model/Instance; (CloudHelper.java:25) at hudson.plugins.ec2.EC2Computer.getState()Lhudson/plugins/ec2/InstanceState; (EC2Computer.java:127) at hudson.plugins.ec2.EC2RetentionStrategy.internalCheck(Lhudson/plugins/ec2/EC2Computer;)J (EC2RetentionStrategy.java:112) at hudson.plugins.ec2.EC2RetentionStrategy.check(Lhudson/plugins/ec2/EC2Computer;)J (EC2RetentionStrategy.java:90) at hudson.plugins.ec2.EC2RetentionStrategy.check(Lhudson/model/Computer;)J (EC2RetentionStrategy.java:48) at hudson.slaves.ComputerRetentionWork$1.run()V (ComputerRetentionWork.java:72) at hudson.model.Queue._withLock(Ljava/lang/Runnable;)V (Queue.java:1381) at hudson.model.Queue.withLock(Ljava/lang/Runnable;)V (Queue.java:1258) at hudson.slaves.ComputerRetentionWork.doRun()V (ComputerRetentionWork.java:63) at hudson.triggers.SafeTimerTask.run()V (SafeTimerTask.java:72) at
[JIRA] (JENKINS-56987) Jira Atlassian API Changes for GDPR
Title: Message Title Olivier Lamy updated an issue Jenkins / JENKINS-56987 Jira Atlassian API Changes for GDPR Change By: Olivier Lamy see changes [https://developer.atlassian.com/cloud/jira/platform/api-changes-for-user-privacy-announcement/] Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56987) Atlassian Jira API Changes for GDPR
Title: Message Title Olivier Lamy updated an issue Jenkins / JENKINS-56987 Atlassian Jira API Changes for GDPR Change By: Olivier Lamy Summary: Jira Atlassian Jira API Changes for GDPR Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56987) Jira Atlassian API Changes for GDPR
Title: Message Title Olivier Lamy created an issue Jenkins / JENKINS-56987 Jira Atlassian API Changes for GDPR Issue Type: Task Assignee: Unassigned Components: jira-plugin Created: 2019-04-11 23:38 Priority: Minor Reporter: Olivier Lamy Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56986) Deadlock on EC2 resources and build queue
Title: Message Title
Sam Gleske updated an issue
Jenkins / JENKINS-56986
Deadlock on EC2 resources and build queue
Change By:
Sam Gleske
This is either the same as or is related to JENKINS-53858. Feel free to close this as a duplicate and re-open JENKINS-53858 if it is the same. h2. EnvironmentI'm using a slightly modified version of the EC2 plugin specifically [ https://github.com/sgleske-ias/ec2-plugin/tree/ias-internal-1 ] ; it was built from EC2 plugin 1.42-SNAPSHOT before 1.42 was released but after [ https://github.com/jenkinsci/ec2-plugin/commit/2f3a04a2d3ce0e51a755792b9d03b4fff4ebe9b3 ] was merged. So my custom version includes the deadlock fix for JENKINS-53858. h2. Deadlock behaviorDuring the deadlock the web UI was responsive. The deadlock blocked: * New items being queued (such as build events submitted through webhooks and other kinds of triggers).* Autoscaling provisioning of new EC2 agents was blocked.* I was not able to delete the 1 EC2 agent that was provisioned but marked as offline because it was deadlocked.There was a * "jenkins.util.Timer \ [#8 \ ]" * thread in which most actions in my Jenkins instance were blocked. This was for the cloud provisioner. Most items that were blocked work blocked by this thread. * "jenkins.util.Timer \ [#8 \ ]" * thread was blocked by * "jenkins.util.Timer \ [#5 \ ]" * thread * "jenkins.util.Timer \ [#5 \ ]" * thread was blocked by waiting on * "jenkins.util.Timer \ [#8 \ ]" * and visa versa. h2. My hypothesisI believe they were blocked by the combination of the Queue lock and the EC2Cloud lock. Each needed both and was waiting on the other. h2. jenkins.util.Timer \ [#8 \ ] Thread Dump {noformat}jenkins.util.Timer [#8] at hudson.plugins.ec2.EC2Cloud.connect()Lcom/amazonaws/services/ec2/AmazonEC2; (EC2Cloud.java:748) at hudson.plugins.ec2.CloudHelper.getInstance(Ljava/lang/String;Lhudson/plugins/ec2/EC2Cloud;)Lcom/amazonaws/services/ec2/model/Instance; (CloudHelper.java:47) at hudson.plugins.ec2.CloudHelper.getInstanceWithRetry(Ljava/lang/String;Lhudson/plugins/ec2/EC2Cloud;)Lcom/amazonaws/services/ec2/model/Instance; (CloudHelper.java:25) at hudson.plugins.ec2.EC2Computer.getState()Lhudson/plugins/ec2/InstanceState; (EC2Computer.java:127) at hudson.plugins.ec2.EC2RetentionStrategy.internalCheck(Lhudson/plugins/ec2/EC2Computer;)J (EC2RetentionStrategy.java:112) at hudson.plugins.ec2.EC2RetentionStrategy.check(Lhudson/plugins/ec2/EC2Computer;)J (EC2RetentionStrategy.java:90) at hudson.plugins.ec2.EC2RetentionStrategy.check(Lhudson/model/Computer;)J (EC2RetentionStrategy.java:48) at hudson.slaves.ComputerRetentionWork$1.run()V (ComputerRetentionWork.java:72) at hudson.model.Queue._withLock(Ljava/lang/Runnable;)V (Queue.java:1381) at hudson.model.Queue.withLock(Ljava/lang/Runnable;)V (Queue.java:1258) at hudson.slaves.ComputerRetentionWork.doRun()V (ComputerRetentionWork.java:63) at hudson.triggers.SafeTimerTask.run()V (SafeTimerTask.java:72) at
[JIRA] (JENKINS-56986) Deadlock on EC2 resources and build queue
Title: Message Title
Sam Gleske updated an issue
Jenkins / JENKINS-56986
Deadlock on EC2 resources and build queue
Change By:
Sam Gleske
This is either the same as or is related to JENKINS-53858. Feel free to close this as a duplicate and re-open JENKINS-53858 if it is the same.h2. EnvironmentI'm using a slightly modified version of the EC2 plugin specifically https://github.com/sgleske-ias/ec2-plugin/tree/ias-internal-1 ; it was built from EC2 plugin 1.42-SNAPSHOT before 1.42 was released but after https://github.com/jenkinsci/ec2-plugin/commit/2f3a04a2d3ce0e51a755792b9d03b4fff4ebe9b3 was merged. So my custom version includes the deadlock fix for JENKINS-53858.h2. Deadlock behaviorDuring the deadlock the web UI was responsive. The deadlock blocked:* New items being queued (such as build events submitted through webhooks and other kinds of triggers ).* Autoscaling provisioning of new EC2 agents was blocked.* I was not able to delete the 1 EC2 agent that was provisioned but marked as offline because it was deadlocked.There was a "jenkins.util.Timer \[#8\]" thread in which most actions in my Jenkins instance were blocked. This was for the cloud provisioner. Most items that were blocked work blocked by this thread. "jenkins.util.Timer \[#8\]" thread was blocked by "jenkins.util.Timer \[#5\]" thread"jenkins.util.Timer \[#5\]" thread was blocked by waiting on "jenkins.util.Timer \[#8\]" and visa versa.h2. My hypothesisI believe they were blocked by the combination of the Queue lock and the EC2Cloud lock. Each needed both and was waiting on the other.h2. jenkins.util.Timer \[#8\] Thread Dump{noformat}jenkins.util.Timer [#8] at hudson.plugins.ec2.EC2Cloud.connect()Lcom/amazonaws/services/ec2/AmazonEC2; (EC2Cloud.java:748) at hudson.plugins.ec2.CloudHelper.getInstance(Ljava/lang/String;Lhudson/plugins/ec2/EC2Cloud;)Lcom/amazonaws/services/ec2/model/Instance; (CloudHelper.java:47) at hudson.plugins.ec2.CloudHelper.getInstanceWithRetry(Ljava/lang/String;Lhudson/plugins/ec2/EC2Cloud;)Lcom/amazonaws/services/ec2/model/Instance; (CloudHelper.java:25) at hudson.plugins.ec2.EC2Computer.getState()Lhudson/plugins/ec2/InstanceState; (EC2Computer.java:127) at hudson.plugins.ec2.EC2RetentionStrategy.internalCheck(Lhudson/plugins/ec2/EC2Computer;)J (EC2RetentionStrategy.java:112) at hudson.plugins.ec2.EC2RetentionStrategy.check(Lhudson/plugins/ec2/EC2Computer;)J (EC2RetentionStrategy.java:90) at hudson.plugins.ec2.EC2RetentionStrategy.check(Lhudson/model/Computer;)J (EC2RetentionStrategy.java:48) at hudson.slaves.ComputerRetentionWork$1.run()V (ComputerRetentionWork.java:72) at hudson.model.Queue._withLock(Ljava/lang/Runnable;)V (Queue.java:1381) at hudson.model.Queue.withLock(Ljava/lang/Runnable;)V (Queue.java:1258) at hudson.slaves.ComputerRetentionWork.doRun()V (ComputerRetentionWork.java:63) at hudson.triggers.SafeTimerTask.run()V (SafeTimerTask.java:72) at jenkins.security.ImpersonatingScheduledExecutorService$1.run()V (ImpersonatingScheduledExecutorService.java:58) at
[JIRA] (JENKINS-53858) Deadlock on EC2 resources
Title: Message Title Sam Gleske commented on JENKINS-53858 Re: Deadlock on EC2 resources Either this bug still exists or maybe I'm experiencing a slightly different bug but similar. Just in case, I filed a new issue with debug details in JENKINS-56986. If you feel mine is a duplicate feel free to close my issue and re-open this issue. I have populated new details (I think after reading comments). Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56986) Deadlock on EC2 resources and build queue
Title: Message Title
Sam Gleske updated an issue
Jenkins / JENKINS-56986
Deadlock on EC2 resources and build queue
Change By:
Sam Gleske
This is either the same as or is related to JENKINS-53858. Feel free to close this as a duplicate and re-open JENKINS-53858 if it is the same.h2. EnvironmentI'm using a slightly modified version of the EC2 plugin specifically https://github.com/sgleske-ias/ec2-plugin/tree/ias-internal-1 ; it was built from EC2 plugin 1.42-SNAPSHOT before 1.42 was released but after https://github.com/jenkinsci/ec2-plugin/commit/2f3a04a2d3ce0e51a755792b9d03b4fff4ebe9b3 was merged. So my custom version includes the deadlock fix for JENKINS-53858.h2. Deadlock behaviorDuring the deadlock the web UI was responsive. The deadlock blocked:* New items being queued (such as build events submitted through webhooks).* Autoscaling provisioning of new EC2 agents was blocked.* I was not able to delete the 1 EC2 agent that was provisioned but marked as offline because it was deadlocked.There was a "jenkins.util.Timer \ [#8 \ ]" thread in which most actions in my Jenkins instance were blocked. This was for the cloud provisioner. Most items that were blocked work blocked by this thread. "jenkins.util.Timer \ [#8 \ ]" thread was blocked by "jenkins.util.Timer \ [#5 \ ]" thread"jenkins.util.Timer \ [#5 \ ]" thread was blocked by waiting on "jenkins.util.Timer \ [# 5 8\ ]" and visa versa. h2. My hypothesisI believe they were blocked by the combination of the Queue lock and the EC2Cloud lock. Each needed both and was waiting on the other.h2. jenkins.util.Timer \[#8\] Thread Dump{noformat}jenkins.util.Timer [#8] at hudson.plugins.ec2.EC2Cloud.connect()Lcom/amazonaws/services/ec2/AmazonEC2; (EC2Cloud.java:748) at hudson.plugins.ec2.CloudHelper.getInstance(Ljava/lang/String;Lhudson/plugins/ec2/EC2Cloud;)Lcom/amazonaws/services/ec2/model/Instance; (CloudHelper.java:47) at hudson.plugins.ec2.CloudHelper.getInstanceWithRetry(Ljava/lang/String;Lhudson/plugins/ec2/EC2Cloud;)Lcom/amazonaws/services/ec2/model/Instance; (CloudHelper.java:25) at hudson.plugins.ec2.EC2Computer.getState()Lhudson/plugins/ec2/InstanceState; (EC2Computer.java:127) at hudson.plugins.ec2.EC2RetentionStrategy.internalCheck(Lhudson/plugins/ec2/EC2Computer;)J (EC2RetentionStrategy.java:112) at hudson.plugins.ec2.EC2RetentionStrategy.check(Lhudson/plugins/ec2/EC2Computer;)J (EC2RetentionStrategy.java:90) at hudson.plugins.ec2.EC2RetentionStrategy.check(Lhudson/model/Computer;)J (EC2RetentionStrategy.java:48) at hudson.slaves.ComputerRetentionWork$1.run()V (ComputerRetentionWork.java:72) at hudson.model.Queue._withLock(Ljava/lang/Runnable;)V (Queue.java:1381) at hudson.model.Queue.withLock(Ljava/lang/Runnable;)V (Queue.java:1258) at hudson.slaves.ComputerRetentionWork.doRun()V (ComputerRetentionWork.java:63) at hudson.triggers.SafeTimerTask.run()V (SafeTimerTask.java:72) at jenkins.security.ImpersonatingScheduledExecutorService$1.run()V (ImpersonatingScheduledExecutorService.java:58) at
[JIRA] (JENKINS-56986) Deadlock on EC2 resources and build queue
Title: Message Title Sam Gleske created an issue Jenkins / JENKINS-56986 Deadlock on EC2 resources and build queue Issue Type: Bug Assignee: FABRIZIO MANFREDI Components: ec2-plugin Created: 2019-04-11 23:21 Environment: Jenkins version 2.150.2 ace-editor 1.1 ansicolor 0.6.2 antisamy-markup-formatter 1.5 apache-httpcomponents-client-4-api 4.5.5-3.0 authentication-tokens 1.3 aws-credentials 1.24 aws-java-sdk 1.11.457 badge 1.7 basic-branch-build-strategies 1.1.1 blueocean 1.10.2 blueocean-autofavorite 1.2.3 blueocean-bitbucket-pipeline 1.10.2 blueocean-commons 1.10.2 blueocean-config 1.10.2 blueocean-core-js 1.10.2 blueocean-dashboard 1.10.2 blueocean-display-url 2.2.0 blueocean-events 1.10.2 blueocean-git-pipeline 1.10.2 blueocean-github-pipeline 1.10.2 blueocean-i18n 1.10.2 blueocean-jira 1.10.2 blueocean-jwt 1.10.2 blueocean-personalization 1.10.2 blueocean-pipeline-api-impl 1.10.2 blueocean-pipeline-editor 1.10.2 blueocean-pipeline-scm-api 1.10.2 blueocean-rest 1.10.2 blueocean-rest-impl 1.10.2 blueocean-web 1.10.2 bouncycastle-api 2.17 branch-api 2.1.2 cloudbees-bitbucket-branch-source 2.4.1 cloudbees-folder 6.7 cobertura 1.13 code-coverage-api 1.0.7 command-launcher 1.3 config-file-provider 3.5 credentials 2.1.18 credentials-binding 1.17 dashboard-view 2.10 display-url-api 2.3.0 docker-commons 1.13 docker-workflow 1.17 durable-task 1.29 ec2 1.42-SNAPSHOT (private-2daf3555-samgleske) email-ext 2.63 embeddable-build-status 1.9 favorite 2.3.2 git 3.9.3 git-client 2.7.6 git-server 1.7 github 1.29.3 github-api 1.95 github-autostatus 3.2 github-branch-source 2.4.2 github-oauth 0.31 groovy 2.1 groovy-postbuild 2.4.3 handlebars 1.1.1 handy-uri-templates-2-api 2.1.6-1.0 htmlpublisher 1.18 jackson2-api 2.9.8 javadoc 1.4 jdk-tool 1.2 jenkins-design-language 1.10.2 jira 3.0.5 jira-steps 1.4.4 job-dsl 1.71 job-restrictions 0.8 jquery-detached 1.2.1 jsch 0.1.55 junit 1.27 lockable-resources 2.4 mailer 1.23 mask-passwords 2.12.0 matrix-auth 2.3 matrix-project 1.13 maven-plugin 3.2 mercurial 2.5 momentjs 1.1.1 node-iterator-api 1.5.0 pipeline-build-step 2.7 pipeline-github 2.1 pipeline-githubnotify-step 1.0.4 pipeline-graph-analysis 1.9 pipeline-input-step 2.9 pipeline-milestone-step 1.3.1 pipeline-model-api 1.3.4.1 pipeline-model-declarative-agent 1.1.1 pipeline-model-definition 1.3.4.1 pipeline-model-extensions 1.3.4.1 pipeline-multibranch-defaults 2.0 pipeline-rest-api 2.10 pipeline-stage-step 2.3 pipeline-stage-tags-metadata 1.3.4.1 pipeline-stage-view 2.10 plain-credentials 1.5 pubsub-light 1.12
[JIRA] (JENKINS-56967) Jenkins Pipeline parallel checkout fails on ECS slave
Title: Message Title Mark Waite updated JENKINS-56967 Jenkins / JENKINS-56967 Jenkins Pipeline parallel checkout fails on ECS slave Change By: Mark Waite Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56967) Jenkins Pipeline parallel checkout fails on ECS slave
Title: Message Title Mark Waite edited a comment on JENKINS-56967 Re: Jenkins Pipeline parallel checkout fails on ECS slave It seems likely that the agent where you are executing the checkout does not have command line git installed. Either that, or there is some issue which is preventing the command line git process from creating an empty repository. Those both are likely configuration issues rather than bugs in the git plugin.I've marked this as "Resolved" and "Not a defect" on the assumption that it is a configuration issue. There are so many running copies of the git plugin in AWS environments that I will be quiet quite shocked if this is a bug in the git plugin. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56967) Jenkins Pipeline parallel checkout fails on ECS slave
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-56967 Jenkins Pipeline parallel checkout fails on ECS slave Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56967) Jenkins Pipeline parallel checkout fails on ECS slave
Title: Message Title Mark Waite updated JENKINS-56967 It seems likely that the agent where you are executing the checkout does not have command line git installed. Either that, or there is some issue which is preventing the command line git process from creating an empty repository. Those both are likely configuration issues rather than bugs in the git plugin. I've marked this as "Resolved" and "Not a defect" on the assumption that it is a configuration issue. There are so many running copies of the git plugin in AWS environments that I will be quiet shocked if this is a bug in the git plugin. Jenkins / JENKINS-56967 Jenkins Pipeline parallel checkout fails on ECS slave Change By: Mark Waite Status: Open Fixed but Unreleased Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and
[JIRA] (JENKINS-56967) Jenkins Pipeline parallel checkout fails on ECS slave
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-56967 Jenkins Pipeline parallel checkout fails on ECS slave Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-27911) Install unlimited strength JCE policy files together with JDK (optionally & automatically)
Title: Message Title Ronnie Zhou commented on JENKINS-27911 Re: Install unlimited strength JCE policy files together with JDK (optionally & automatically) The installer allows to execute shell / batch command for a customized installation. Have you tried this option? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56688) pipeline-syntax Global Variables params.get doesn't work
Title: Message Title Devin Nusbaum commented on JENKINS-56688 Re: pipeline-syntax Global Variables params.get doesn't work Map.getOrDefault(Object, Object) is now whitelisted by default in Script Security 1.57. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56688) pipeline-syntax Global Variables params.get doesn't work
Title: Message Title Devin Nusbaum updated an issue Jenkins / JENKINS-56688 pipeline-syntax Global Variables params.get doesn't work Change By: Devin Nusbaum Released As: workflow-cps 2.66 , script-security 1.57 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56976) WAIT ERROR even though when JESINTERFACELEVEL is 2
Title: Message Title Alexander Shcherbakov updated an issue Jenkins / JENKINS-56976 WAIT ERROR even though when JESINTERFACELEVEL is 2 Change By: Alexander Shcherbakov Attachment: zos-connector-2.2.1-SNAPSHOT.hpi Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56976) WAIT ERROR even though when JESINTERFACELEVEL is 2
Title: Message Title Alexander Shcherbakov commented on JENKINS-56976 Re: WAIT ERROR even though when JESINTERFACELEVEL is 2 Kindly try new version and attach the resulting job log. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56976) WAIT ERROR even though when JESINTERFACELEVEL is 2
Title: Message Title Alexander Shcherbakov updated JENKINS-56976 Jenkins / JENKINS-56976 WAIT ERROR even though when JESINTERFACELEVEL is 2 Change By: Alexander Shcherbakov Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56688) pipeline-syntax Global Variables params.get doesn't work
Title: Message Title Devin Nusbaum updated JENKINS-56688 The updated documentation was just released in version 2.66 of Pipeline: Groovy Plugin. I will try to release Script Security shortly to get the update that adds the new recommendation to the default whitelist. Jenkins / JENKINS-56688 pipeline-syntax Global Variables params.get doesn't work Change By: Devin Nusbaum Status: Fixed but Unreleased Resolved Released As: workflow-cps 2.66 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41791) Build cannot be resumed if parallel was used with Kubernetes plugin
Title: Message Title Devin Nusbaum updated JENKINS-41791 A fix for this issue was just released in version 2.66 of Pipeline: Groovy Plugin. Jenkins / JENKINS-41791 Build cannot be resumed if parallel was used with Kubernetes plugin Change By: Devin Nusbaum Status: Fixed but Unreleased Resolved Released As: workflow-cps 2.66 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56985) Jenkins is exposing credentials when no build steps but post build steps
Title: Message Title Alfred Wong created an issue Jenkins / JENKINS-56985 Jenkins is exposing credentials when no build steps but post build steps Issue Type: Bug Assignee: Unassigned Components: credentials-binding-plugin, credentials-plugin Created: 2019-04-11 20:33 Environment: Jenkins 2.164.2, credentials-plugin 2.1.18 credentials-binding-plugin 1.18 Labels: plugin Priority: Blocker Reporter: Alfred Wong While looking at console logs, in our case, it failed to delete the workspace and go to post build steps and run a command that contains credentials, the console logs expose the credentials instead of using . I created a job that use credentials binding and no build steps but only post build step, in the post build step, I echo the credentials and it exposed them. It looks like any time when no actual build steps is run, the credentials are not hidden.
[JIRA] (JENKINS-47896) Jenkins core classes should implement SerializableOnlyOverRemoting
Title: Message Title Jesse Glick assigned an issue to Jesse Glick Jenkins / JENKINS-47896 Jenkins core classes should implement SerializableOnlyOverRemoting Change By: Jesse Glick Assignee: Jesse Glick Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47896) Jenkins core classes should implement SerializableOnlyOverRemoting
Title: Message Title Jesse Glick assigned an issue to Jesse Glick Jenkins / JENKINS-47896 Jenkins core classes should implement SerializableOnlyOverRemoting Change By: Jesse Glick Assignee: Jesse Glick Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47896) Jenkins core classes should implement SerializableOnlyOverRemoting
Title: Message Title Jesse Glick started work on JENKINS-47896 Change By: Jesse Glick Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47896) Jenkins core classes should implement SerializableOnlyOverRemoting
Title: Message Title Jesse Glick updated JENKINS-47896 Jenkins / JENKINS-47896 Jenkins core classes should implement SerializableOnlyOverRemoting Change By: Jesse Glick Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41827) JenkinsRule mode to use realistic class loading
Title: Message Title Jesse Glick commented on JENKINS-41827 Re: JenkinsRule mode to use realistic class loading I suspect Arquillian would be much more trouble than it is worth, since Jenkins uses only a little bit of the Servlet system and then has its own big complex module system completely outside of that. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54992) Terrifying message makes me think Jenkins will delete my github repo
Title: Message Title Liam Newman commented on JENKINS-54992 Re: Terrifying message makes me think Jenkins will delete my github repo Also, not this same issue manifests in the GitHub Organization Pipeline:This looks like we're going to delete an Organization not the GitHub Organization Pipeline. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54992) Terrifying message makes me think Jenkins will delete my github repo
Title: Message Title Liam Newman updated an issue Jenkins / JENKINS-54992 Terrifying message makes me think Jenkins will delete my github repo Change By: Liam Newman Attachment: Screen Shot 2019-04-11 at 12.45.33 PM.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41827) JenkinsRule mode to use realistic class loading
Title: Message Title Matt Sicker commented on JENKINS-41827 Re: JenkinsRule mode to use realistic class loading Perhaps consider Arquillian as a framework for that? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54992) Terrifying message makes me think Jenkins will delete my github repo
Title: Message Title Liam Newman commented on JENKINS-54992 Re: Terrifying message makes me think Jenkins will delete my github repo Interesting point: This is only an issue for the GitHub branch source. No other currently implemented source has this problem. All others display this way: This is because no other branch source includes a pronoun, or related implementation changes introduced with JENKINS-38987 - https://github.com/jenkinsci/github-branch-source-plugin/commit/c0557dd3fa8b53e0ff52d315424cebd8fdfd61d9#diff-3f936a67918affedec628eae019f97f3 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54992) Terrifying message makes me think Jenkins will delete my github repo
Title: Message Title Liam Newman updated an issue Jenkins / JENKINS-54992 Terrifying message makes me think Jenkins will delete my github repo Change By: Liam Newman Attachment: Screen Shot 2019-04-11 at 12.03.39 PM.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56984) Basic Branch 1.3 thows AbstractMethodError not Fully Backwards Compatible
Title: Message Title chirs damour updated an issue Jenkins / JENKINS-56984 Basic Branch 1.3 thows AbstractMethodError not Fully Backwards Compatible Change By: chirs damour Environment: Jenkins ver. 2.150.1branch-api-plugin 2.4basic build strategies 1.3 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56984) Basic Branch 1.3 thows AbstractMethodError not Fully Backwards Compatible
Title: Message Title
chirs damour updated an issue
Jenkins / JENKINS-56984
Basic Branch 1.3 thows AbstractMethodError not Fully Backwards Compatible
Change By:
chirs damour
first mentioned in JENKINS-38522I was asked to assign to [~fbelzunc] by [~stephenconnolly]after upgrading to 1.3 i started getting this in my logs{code:java} SCMEventListener.onSCMHeadEvent(SCMHeadEvent) jenkins.branch.MultiBranchProject$SCMEventListenerImpl@1cf8cddc propagated an exceptionjava.lang.AbstractMethodError: jenkins.branch.BranchBuildStrategy.isAutomaticBuild(Ljenkins/scm/api/SCMSource;Ljenkins/scm/api/SCMHead;Ljenkins/scm/api/SCMRevision;Ljenkins/scm/api/SCMRevision;Lhudson/model/TaskListener;)Z at jenkins.branch.buildstrategies.basic.AllBranchBuildStrategyImpl.isAutomaticBuild(AllBranchBuildStrategyImpl.java:77) at jenkins.branch.BranchBuildStrategy.automaticBuild(BranchBuildStrategy.java:190) at jenkins.branch.MultiBranchProject.isAutomaticBuild(MultiBranchProject.java:2231) at jenkins.branch.MultiBranchProject.access$1200(MultiBranchProject.java:125) at jenkins.branch.MultiBranchProject$SCMHeadObserverImpl.observe(MultiBranchProject.java:2076) at jenkins.scm.api.SCMHeadObserver$Wrapped.observe(SCMHeadObserver.java:638) at jenkins.scm.api.SCMHeadEvent$Validated.observe(SCMHeadEvent.java:295) at jenkins.scm.api.trait.SCMSourceRequest.process(SCMSourceRequest.java:357) at jenkins.scm.api.trait.SCMSourceRequest.process(SCMSourceRequest.java:249) at org.jenkinsci.plugins.github_branch_source.GitHubSCMSource.retrieve(GitHubSCMSource.java:917) at jenkins.scm.api.SCMSource._retrieve(SCMSource.java:373) at jenkins.scm.api.SCMSource.fetch(SCMSource.java:327) at jenkins.branch.MultiBranchProject$SCMEventListenerImpl.processHeadUpdate(MultiBranchProject.java:1576) at jenkins.branch.MultiBranchProject$SCMEventListenerImpl.onSCMHeadEvent(MultiBranchProject.java:1177) at jenkins.scm.api.SCMHeadEvent$DispatcherImpl.fire(SCMHeadEvent.java:246) at jenkins.scm.api.SCMHeadEvent$DispatcherImpl.fire(SCMHeadEvent.java:229) at jenkins.scm.api.SCMEvent$Dispatcher.run(SCMEvent.java:479) at jenkins.security.ImpersonatingScheduledExecutorService$1.run(ImpersonatingScheduledExecutorService.java:58) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) {code} the issue is the all/none/any wrapper strategies now assume any wrapped strategy implements the new interface method...however older plugin will NOT implement such a method.Could add another interface inbetween, or use reflection, or try catch to make this all
[JIRA] (JENKINS-38552) Multibranch pipeline (re)creation intelligence
Title: Message Title chirs damour commented on JENKINS-38552 Re: Multibranch pipeline (re)creation intelligence JENKINS-56984 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56984) Basic Branch 1.3 thows AbstractMethodError not Fully Backwards Compatible
Title: Message Title chirs damour updated an issue Jenkins / JENKINS-56984 Basic Branch 1.3 thows AbstractMethodError not Fully Backwards Compatible Change By: chirs damour Summary: Basic Branch 1.3 thows AbstractMethodError not Fully Backwards Compatible Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56984) Basic Branch 1.3 not Fully Backwards Compatible
Title: Message Title chirs damour created an issue Jenkins / JENKINS-56984 Basic Branch 1.3 not Fully Backwards Compatible Issue Type: Bug Assignee: Félix Belzunce Arcos Components: basic-branch-build-strategies-plugin, branch-api-plugin Created: 2019-04-11 19:09 Priority: Major Reporter: chirs damour first mentioned in JENKINS-38522 I was asked to assign to Félix Belzunce Arcos by Stephen Connolly after upgrading to 1.3 i started getting this in my logs SCMEventListener.onSCMHeadEvent(SCMHeadEvent) jenkins.branch.MultiBranchProject$SCMEventListenerImpl@1cf8cddc propagated an exception java.lang.AbstractMethodError: jenkins.branch.BranchBuildStrategy.isAutomaticBuild(Ljenkins/scm/api/SCMSource;Ljenkins/scm/api/SCMHead;Ljenkins/scm/api/SCMRevision;Ljenkins/scm/api/SCMRevision;Lhudson/model/TaskListener;)Z at jenkins.branch.buildstrategies.basic.AllBranchBuildStrategyImpl.isAutomaticBuild(AllBranchBuildStrategyImpl.java:77) at jenkins.branch.BranchBuildStrategy.automaticBuild(BranchBuildStrategy.java:190) at jenkins.branch.MultiBranchProject.isAutomaticBuild(MultiBranchProject.java:2231) at jenkins.branch.MultiBranchProject.access$1200(MultiBranchProject.java:125) at jenkins.branch.MultiBranchProject$SCMHeadObserverImpl.observe(MultiBranchProject.java:2076) at jenkins.scm.api.SCMHeadObserver$Wrapped.observe(SCMHeadObserver.java:638) at jenkins.scm.api.SCMHeadEvent$Validated.observe(SCMHeadEvent.java:295) at jenkins.scm.api.trait.SCMSourceRequest.process(SCMSourceRequest.java:357) at jenkins.scm.api.trait.SCMSourceRequest.process(SCMSourceRequest.java:249) at org.jenkinsci.plugins.github_branch_source.GitHubSCMSource.retrieve(GitHubSCMSource.java:917) at jenkins.scm.api.SCMSource._retrieve(SCMSource.java:373) at jenkins.scm.api.SCMSource.fetch(SCMSource.java:327) at
[JIRA] (JENKINS-45308) unclassified field java.io.File text
Title: Message Title Jesse Glick commented on JENKINS-45308 Re: unclassified field java.io.File text You cannot approve an “unclassified” signature because it has not been, well, classified. Errors about “unclassified” signatures represent bugs in the sandbox code. Please report them as distinct issues with complete, minimal steps to reproduce from scratch. Please use the users’ list for help or advice with other matters. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56983) stageFlowNodes never marked as IN_PROGRESS
Title: Message Title Rickard Dybeck created an issue Jenkins / JENKINS-56983 stageFlowNodes never marked as IN_PROGRESS Issue Type: Bug Assignee: Sam Van Oort Components: pipeline-stage-view-plugin Created: 2019-04-11 18:28 Environment: Jenkins 2.164.1 LTS Pipeline Stage View Plugin 2.10 Priority: Minor Reporter: Rickard Dybeck When iterating all nodes for a particular job under the `wfapi`, all currently running stageFlowNodes have status "SUCCESS". Basically what I'm seeing is the topmost entry in `/wfapi` has "status": "IN_PROGRESS", and under stages it'll aslo have "status": "IN_PROGRESS". But hitting the api under the "self" link for the stage (for example `execution/node/17/wfapi/describe`) the response has "status": "IN_PROGRESS", but all stageFlowNodes are "SUCCESS". If the execution of one of them fails, it'll change from SUCCESS to FAILED. This makes it a bit tricky to figure out which of these stageFlowNodes is the one actually marking the stage as "IN_PROGRESS". Add Comment
[JIRA] (JENKINS-56858) unable to load plugins
Title: Message Title Yufen Kuo commented on JENKINS-56858 Re: unable to load plugins $ /usr/local/git/jenkinsfile-runner/app/target/appassembler/bin/jenkinsfile-runner -Djenkins.version=2.164.1 -p /var/jenkins_home/plugins -f /var/jenkins_home/foo "-Djenkins.version=2.164.1" is not a valid option Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56874) Log4j2.xml file in the plugin causes unexpected errors
Title: Message Title Timothy Klopotoski commented on JENKINS-56874 Re: Log4j2.xml file in the plugin causes unexpected errors Agreed, definitely something weird going on here. Indeed, our master instance is running inside docker. Having trouble coming up with a reason why it wouldn't be able to write to userContent. I am able to create a file on the host in the userContent dir and see the file through the Jenkins web UI. I can also accomplish the same from within the container (e.g. docker exec -it jenkins /bin/bash -c "touch /var/jenkins_home/userContent/timski" – can see `timski` in the web UI). Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56982) Close the connection while restarting to avoid tests hung
Title: Message Title Ramon Leon commented on JENKINS-56982 Re: Close the connection while restarting to avoid tests hung PR with the fix: https://github.com/jenkinsci/acceptance-test-harness/pull/502 So far so good, but it was not easy. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56982) Close the connection while restarting to avoid tests hung
Title: Message Title Ramon Leon updated JENKINS-56982 Jenkins / JENKINS-56982 Close the connection while restarting to avoid tests hung Change By: Ramon Leon Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56982) Close the connection while restarting to avoid tests hung
Title: Message Title Ramon Leon started work on JENKINS-56982 Change By: Ramon Leon Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56492) [ATH] Fix Javadoc failures on Java11
Title: Message Title Ramon Leon updated JENKINS-56492 Jenkins / JENKINS-56492 [ATH] Fix Javadoc failures on Java11 Change By: Ramon Leon Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56982) Close the connection while restarting to avoid tests hung
Title: Message Title Ramon Leon created an issue Jenkins / JENKINS-56982 Close the connection while restarting to avoid tests hung Issue Type: Bug Assignee: Ramon Leon Components: acceptance-test-harness Created: 2019-04-11 16:17 Labels: test hang stalled stuck Priority: Major Reporter: Ramon Leon We have experienced some tests getting hung/stalled/stuck (for searches ) during the execution of the ATHs. The symptom is very different tests hold in every execution and the build doesn't finish. After a lot of analysis, I've found out that it's because of the connection used for testing if Jenkins is ready not being closed. This issue may impact a lot of people, a lot of tests with very different symptoms. If you have a test restarting Jenkins in your ATH test and your tests don't finish getting hung in very different tests, perhaps you are facing this issue. Add Comment
[JIRA] (JENKINS-56890) IOException: "cannot find current thread"
Title: Message Title William F commented on JENKINS-56890 Re: IOException: "cannot find current thread" looking at the class methods where "threads" (a TreeMap) is accessed: https://github.com/jenkinsci/workflow-cps-plugin/blob/master/src/main/java/org/jenkinsci/plugins/workflow/cps/CpsThreadGroup.java#L176-L195 I see that there is an attempt to ensure that all "put" calls are executed within the same thread – but AFAICT there is no such logic for "get". Given that TreeMap is NOT a thread-safe class, if calls to "threads.put" and "threads.get" are interleaved, it is entirely possible to get "null" when invoking "get" for a key that has been "put" in another thread. Even without interleaved execution, I believe it would be possible to get such behavior simply via invoking "put" and "get" in different threads without any synchronization constructs, in terms of the Java Memory Model (but my own memory regarding the JMM is pretty hazy). In other words, from a glance, it really just looks like "threads" is being manipulated in a non-threadsafe manner. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56980) Daylight savings window at 0 2 * * *, observed in Jenkins 2.89.2
Title: Message Title
Joseph Kesselman updated an issue
Jenkins / JENKINS-56980
Daylight savings window at 0 2 * * *, observed in Jenkins 2.89.2
Change By:
Joseph Kesselman
This spring, we had a job scheduled to trigger at 2AM ("0 2 * * *") fail to execute the morning of the EST/DST switch-over. Our suspicion is that the skip from 01:59 to 03:00 provoked this problem. (Which might also mean that jobs scheduled in that window would run twice the night of the autumn switch-over.)A trivial workaround would to schedule for 01:59 (or, for paranoia's sake, 01:58). But standard scheduler logic Really Should Not be vulnerable to this.Admittedly we're still running Jenkins 2.89.2 (our own fault; we haven't found time to resolve some compatability issues with newer releases), so this may have been fixed Long Ago. Apologies if so. "Better to speak up and risk being thought a fool, than to remain silent and remove all doubt."
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
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.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56980) Daylight savings window at 0 2 * * *, observed in Jenkins 2.89.2
Title: Message Title
Joseph Kesselman updated an issue
Jenkins / JENKINS-56980
Daylight savings window at 0 2 * * *, observed in Jenkins 2.89.2
Change By:
Joseph Kesselman
Environment:
This spring, we had a job scheduled to trigger at 2AM ("0 2 * * *") fail to execute the morning of the EST/DST switch-over. Our suspicion is that the skip from 01:59 to 03:00 provoked this problem. (Which might also mean that jobs scheduled in that window would run twice the night of the autumn switch-over.)A trivial workaround would to schedule for 01:59 (or, for paranoia's sake, 01:58). But standard scheduler logic Really Should Not be vulnerable to this.Admittedly we're still running Jenkins 2.89.2 (our own fault; we haven't found time to resolve some compatability issues with newer releases), so this may have been fixed Long Ago. Apologies if so. "Better to speak up and risk being thought a fool, than to remain silent and remove all doubt."
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
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.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56981) VM failed to provision when use Pool Retention Strategy
Title: Message Title di wang created an issue Jenkins / JENKINS-56981 VM failed to provision when use Pool Retention Strategy Issue Type: Bug Assignee: Azure DevOps Components: azure-vm-agents-plugin Created: 2019-04-11 15:58 Environment: Jenkins 2.150.1 Azure VM Agents 0.9.0 [root@pkrvmv9zkwan3x3 centos]# cat /etc/*release CentOS Linux release 7.6.1810 (Core) NAME="CentOS Linux" VERSION="7 (Core)" ID="centos" ID_LIKE="rhel fedora" VERSION_ID="7" PRETTY_NAME="CentOS Linux 7 (Core)" ANSI_COLOR="0;31" CPE_NAME="cpe:/o:centos:centos:7" HOME_URL="https://www.centos.org/" BUG_REPORT_URL="https://bugs.centos.org/" CENTOS_MANTISBT_PROJECT="CentOS-7" CENTOS_MANTISBT_PROJECT_VERSION="7" REDHAT_SUPPORT_PRODUCT="centos" REDHAT_SUPPORT_PRODUCT_VERSION="7" CentOS Linux release 7.6.1810 (Core) CentOS Linux release 7.6.1810 (Core) Priority: Major Reporter: di wang When use pool retention strategy, most times VMs are failed to provision. If use the same template settings, only change retention strategy to Idle retention strategy, then all vms can provisioned successfully(100%). Retention time in hour: 24 Pool Size: 1 Only a few times, VMs can be provisioned successfully with pool retention strategy. Node ProvisioningActivity for Azure-Test/jenkins-… java.lang.Exception: Node ProvisioningActivity for Azure-Test/jenkins-test/null (229415501) has lost. Mark as failure at com.microsoft.azure.vmagent.AzureVMAgentCleanUpTask.cleanCloudStatistics(AzureVMAgentCleanUpTask.java:604) at com.microsoft.azure.vmagent.AzureVMAgentCleanUpTask.clean(AzureVMAgentCleanUpTask.java:622) at
[JIRA] (JENKINS-56980) Daylight savings window at 0 2 * * *, observed in Jenkins 2.89.2
Title: Message Title
Joseph Kesselman created an issue
Jenkins / JENKINS-56980
Daylight savings window at 0 2 * * *, observed in Jenkins 2.89.2
Issue Type:
Bug
Assignee:
Unassigned
Components:
core
Created:
2019-04-11 15:51
Environment:
This spring, we had a job scheduled to trigger at 2AM ("0 2 * * *") fail to execute the morning of the EST/DST switch-over. Our suspicion is that the skip from 01:59 to 03:00 provoked this problem. (Which might also mean that jobs scheduled in that window would run twice the night of the autumn switch-over.) A trivial workaround would to schedule for 01:59 (or, for paranoia's sake, 01:58). But standard scheduler logic Really Should Not be vulnerable to this. Admittedly we're still running Jenkins 2.89.2 (our own fault; we haven't found time to resolve some compatability issues with newer releases), so this may have been fixed Long Ago. Apologies if so. "Better to speak up and risk being thought a fool, than to remain silent and remove all doubt."
Priority:
Minor
Reporter:
Joseph Kesselman
Add Comment
[JIRA] (JENKINS-56975) writeMavenPom / java.lang.ClassCastException when adding a new plugin
Title: Message Title fr33ky _ updated an issue Jenkins / JENKINS-56975 writeMavenPom / java.lang.ClassCastException when adding a new plugin Change By: fr33ky _ Summary: writeMavenPom / java.lang.ClassCastException when adding a new plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56979) Add ability to configure the xvnc command line from inside a pipeline script
Title: Message Title
Vincent Massol created an issue
Jenkins / JENKINS-56979
Add ability to configure the xvnc command line from inside a pipeline script
Issue Type:
Improvement
Assignee:
Levon Saldamli
Components:
xvnc-plugin
Created:
2019-04-11 15:40
Environment:
Right now it's possible to configure the xvnc plugin in the jenkins configuration but it doesn't seem possible to do so when using the plugin in a pipeline script (all you can configure is takeScreenshot and authority). See https://github.com/jenkinsci/xvnc-plugin/blob/master/src/main/java/hudson/plugins/xvnc/Xvnc.java#L93 It would be nice to be able to control the command line when using it, with something like: {code} wrap([$class: 'Xvnc', cmd = 'vncserver :$DISPLAY_NUMBER -nolisten tcp -geometry 1280x1024']) { ... } {code}
Priority:
Minor
Reporter:
Vincent Massol
Add Comment
[JIRA] (JENKINS-56979) Add ability to configure the xvnc command line from inside a pipeline script
Title: Message Title
Vincent Massol updated an issue
Jenkins / JENKINS-56979
Add ability to configure the xvnc command line from inside a pipeline script
Change By:
Vincent Massol
Right now it's possible to configure the xvnc plugin in the jenkins configuration but it doesn't seem possible to do so when using the plugin in a pipeline script (all you can configure is takeScreenshot and authority).See https://github.com/jenkinsci/xvnc-plugin/blob/master/src/main/java/hudson/plugins/xvnc/Xvnc.java#L93It would be nice to be able to control the command line when using it, with something like:{code}wrap([$class: 'Xvnc', cmd = 'vncserver :$DISPLAY_NUMBER -nolisten tcp -geometry 1280x1024']) {...}{code}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
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.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56979) Add ability to configure the xvnc command line from inside a pipeline script
Title: Message Title
Vincent Massol updated an issue
Jenkins / JENKINS-56979
Add ability to configure the xvnc command line from inside a pipeline script
Change By:
Vincent Massol
Environment:
Right now it's possible to configure the xvnc plugin in the jenkins configuration but it doesn't seem possible to do so when using the plugin in a pipeline script (all you can configure is takeScreenshot and authority).See https://github.com/jenkinsci/xvnc-plugin/blob/master/src/main/java/hudson/plugins/xvnc/Xvnc.java#L93It would be nice to be able to control the command line when using it, with something like:{code}wrap([$class: 'Xvnc', cmd = 'vncserver :$DISPLAY_NUMBER -nolisten tcp -geometry 1280x1024']) {...}{code}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
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.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56976) WAIT ERROR even though when JESINTERFACELEVEL is 2
Title: Message Title Alexander Shcherbakov started work on JENKINS-56976 Change By: Alexander Shcherbakov Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50394) Branch Indexing fails with MissingObjectException
Title: Message Title rsandell updated JENKINS-50394 Jenkins / JENKINS-50394 Branch Indexing fails with MissingObjectException Change By: rsandell Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56978) The pipeline status sometimes not appear in output
Title: Message Title Shurik Gefter created an issue Jenkins / JENKINS-56978 The pipeline status sometimes not appear in output Issue Type: Bug Assignee: Unassigned Components: jenkinsfile-runner Created: 2019-04-11 15:12 Priority: Minor Reporter: Shurik Gefter I run the same Jenkinfile via docker and sometimes the status of pipeline not present in output "Finished: FAILURE" Add Comment
[JIRA] (JENKINS-56846) filesystem scm load stuck in jenkinfile-runner
Title: Message Title
Shurik Gefter commented on JENKINS-56846
Re: filesystem scm load stuck in jenkinfile-runner
I found WA. Before I call the library command I manually create the /tmp/jenkinsfileRunner.tmp/jfr408537468992298463.run/workspace/job@libs folder and copy files to there. After it my jenkinsfile run successfully via docker.
stage('Load Library') {
steps {
sh "echo 'WA - when running via docker the load library stuck, do the preparation manually'"
sh "mkdir -p ${WORKSPACE}/../job@libs/"
sh "rm -rf /workspace/my_shared_library/.git"
sh "cp -r /workspace/my_shared_library ${WORKSPACE}/../job@libs"
library identifier: 'my_shared_library@main',
retriever: legacySCM(
filesystem(clearWorkspace: false, copyHidden: false, path: '/workspace/my_shared_library'))
}
}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
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.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56969) Unable to connect to slave via ssh
Title: Message Title Matt Sicker commented on JENKINS-56969 Re: Unable to connect to slave via ssh What key type is your private key? I do recall seeing some Trilead classes removed from Jenkins not that long ago, so it's possible you found a regression. There was also an upgrade for JSch which disabled some insecure key types and parameters, though I don't believe that's used in any of the plugins you listed. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56977) Input "ChoiceParameterDefinition" with same name make the UI bug (select wrong choice when clicked)
Title: Message Title
Sylvain TARGONSKI created an issue
Jenkins / JENKINS-56977
Input "ChoiceParameterDefinition" with same name make the UI bug (select wrong choice when clicked)
Issue Type:
Bug
Assignee:
Unassigned
Attachments:
2019-04-11 16_55_39-jenkins _ ec2_test _ master _ #43.png
Components:
blueocean-plugin
Created:
2019-04-11 14:58
Environment:
Jenkins 2.170 BlueOcean 1.14
Priority:
Minor
Reporter:
Sylvain TARGONSKI
I'm using BlueOcean with declarative Pipelines. In one of my pipeline there is a step which executes a Jenkins "script" in which there is a jenkins "input" using parameter type "ChoiceParameterDefinition". It reads the choices from a variable which contains multiple lines :
steps {
script {
def userInput = input(
id: 'userInput', message: "mytest",
parameters: [
[$class: 'ChoiceParameterDefinition', choices: "${VAR_1}", name: 'config']
])
VAR_2 = "${userInput}"
}
}
When there are choices composed of the exact same string, the UI bugs. The user is prompted with a choice list but when he clicks on the first choice it selects the second one and vice versa. I came accross this bug when I was doing some testings with the same string in each line of the variable. I'm not sure there
[JIRA] (JENKINS-56975) java.lang.ClassCastException when adding a new plugin
Title: Message Title
fr33ky _ updated an issue
Jenkins / JENKINS-56975
java.lang.ClassCastException when adding a new plugin
Change By:
fr33ky _
Trying to add a plugin to a pom, we are facing the following exception when writeMavenPom() is called:{code:java} java.lang.ClassCastException: org.apache.maven.model.Plugin cannot be cast to org.apache.maven.model.Plugin at org.apache.maven.model.io.xpp3.MavenXpp3Writer.writeBuild(MavenXpp3Writer.java:343) at org.apache.maven.model.io.xpp3.MavenXpp3Writer.writeModel(MavenXpp3Writer.java:1134) at org.apache.maven.model.io.xpp3.MavenXpp3Writer.write(MavenXpp3Writer.java:134) at org.jenkinsci.plugins.pipeline.utility.steps.maven.WriteMavenPomStep$Execution.run(WriteMavenPomStep.java:160) at org.jenkinsci.plugins.pipeline.utility.steps.maven.WriteMavenPomStep$Execution.run(WriteMavenPomStep.java:130) at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748){code}Code that reproduces the problem:{code:groovy}import org.apache.maven.model.PluginwriteFile file: 'pom.xml', text: '4.0.0'def myPom = readMavenPom()myPom.getBuild().getPlugins().add(new Plugin())writeMavenPom(myPom){code} Many thanks for your help and this plugin!
Add Comment
[JIRA] (JENKINS-56976) WAIT ERROR even though when JESINTERFACELEVEL is 2
Title: Message Title bharath kumar created an issue Jenkins / JENKINS-56976 WAIT ERROR even though when JESINTERFACELEVEL is 2 Issue Type: Bug Assignee: Alexander Shcherbakov Attachments: log.txt Components: zos-connector-plugin Created: 2019-04-11 14:32 Environment: Linux , oracle JDK, zos connector plugin 2.2.0 Priority: Major Reporter: bharath kumar My JESINTERFACELEVEL is 2, when executing jenkins freestyle or scripted job to submit JCL after unchecking the JESINTERFACELEVEL=1 option , the console output holds up with 'submitted job' step and after the wait time is over , multiple entries of JOBLOG is seen in console output and the job fails with "ERROR : z/OS job failed with WAIT-ERROR" Add Comment
[JIRA] (JENKINS-56966) Azure Deployment of .NET Package Folder has some files with 0 size
Title: Message Title Josh Chiancone edited a comment on JENKINS-56966 Re: Azure Deployment of .NET Package Folder has some files with 0 size I can provide sections of build logs or additional information, if you need specific information. I'd rather not attach the full pipeline log, though.! image screenshot - 2019-04-11-10-22-58-877 1 .png |thumbnail ! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56966) Azure Deployment of .NET Package Folder has some files with 0 size
Title: Message Title Josh Chiancone updated an issue Jenkins / JENKINS-56966 Azure Deployment of .NET Package Folder has some files with 0 size Change By: Josh Chiancone Attachment: screenshot-1.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56890) IOException: "cannot find current thread"
Title: Message Title Jon B commented on JENKINS-56890 Re: IOException: "cannot find current thread" I just had a build fail with this problem java.io.IOException: cannot find current thread at org.jenkinsci.plugins.workflow.cps.CpsStepContext.doGet(CpsStepContext.java:300) at org.jenkinsci.plugins.workflow.cps.CpsBodySubContext.doGet(CpsBodySubContext.java:88) at org.jenkinsci.plugins.workflow.support.DefaultStepContext.get(DefaultStepContext.java:67) at org.jenkinsci.plugins.credentialsbinding.impl.BindingStep$Callback.finished(BindingStep.java:254) at org.jenkinsci.plugins.credentialsbinding.impl.BindingStep$Execution2$Callback2.finished(BindingStep.java:162) at org.jenkinsci.plugins.workflow.steps.GeneralNonBlockingStepExecution$TailCall.lambda$onSuccess$0(GeneralNonBlockingStepExecution.java:140) at org.jenkinsci.plugins.workflow.steps.GeneralNonBlockingStepExecution.lambda$run$0(GeneralNonBlockingStepExecution.java:77) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) Finished: FAILURE Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47286) Support skipping stages in scripted pipelines for nice visualization in blue ocean and classic UI stage view
Title: Message Title
Mihai Dinu edited a comment on JENKINS-47286
Re: Support skipping stages in scripted pipelines for nice visualization in blue ocean and classic UI stage view
There's a nice post here: **[https://comquent.de/en/skipped-stages-in-jenkins-scripted-pipeline/] that describes how to use the [https://github.com/comquent/imperative-when] workaround. I have a related question though: is it possible to show the stages that follow a failed stage as skipped (or failed)? My use case is something like this{code:java}node {try {stage('Will fail') {sh 'exit 1'}stage('Some operations') {echo 'This stage should run when previous stage is successful'echo 'Should be skipped or failed when previous stage fails'}} catch (err) {echo "Print the error from the first stage $err"}finally {stage('Post build') {echo 'Always do some cleanup ops'}}}{code} The problem that I'm facing is that any stage from my pipeline can fail and I want all my downstream stages to be skipped, except the post build one. When a stage fails, it is caught in the `catch` *_catch_* block and so all downstream stages are ignored, ruining the pipeline stage view from the job UI. Any possible solutions for this?
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
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.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56974) Unable to mention branch name in trigger option
Title: Message Title Ethashamuddin Mohammed commented on JENKINS-56974 Re: Unable to mention branch name in trigger option I came across this known issue, but it is different issue https://github.com/jenkinsci/gitlab-plugin/issues/606 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47286) Support skipping stages in scripted pipelines for nice visualization in blue ocean and classic UI stage view
Title: Message Title
Mihai Dinu commented on JENKINS-47286
Re: Support skipping stages in scripted pipelines for nice visualization in blue ocean and classic UI stage view
There's a nice post here: **https://comquent.de/en/skipped-stages-in-jenkins-scripted-pipeline/ that describes how to use the https://github.com/comquent/imperative-when workaround. I have a related question though: is it possible to show the stages that follow a failed stage as skipped (or failed)? My use case is something like this
node {
try {
stage('Will fail') {
sh 'exit 1'
}
stage('Some operations') {
echo 'This stage should run when previous stage is successful'
echo 'Should be skipped or failed when previous stage fails'
}
}
catch (err) {
echo "Print the error from the first stage $err"
}
finally {
stage('Post build') {
echo 'Always do some cleanup ops'
}
}
}
The problem that I'm facing is that any stage from my pipeline can fail and I want all my downstream stages to be skipped, except the post build one. When a stage fails, it is caught in the `catch` block and so all downstream stages are ignored, ruining the pipeline stage view from the job UI. Any possible solutions for this?
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
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.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56966) Azure Deployment of .NET Package Folder has some files with 0 size
Title: Message Title Josh Chiancone updated an issue Jenkins / JENKINS-56966 Azure Deployment of .NET Package Folder has some files with 0 size Change By: Josh Chiancone Attachment: image-2019-04-11-10-22-58-877.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56975) java.lang.ClassCastException when adding a new plugin
Title: Message Title fr33ky _ created an issue Jenkins / JENKINS-56975 java.lang.ClassCastException when adding a new plugin Issue Type: Bug Assignee: rsandell Components: pipeline-utility-steps-plugin Created: 2019-04-11 14:25 Environment: Jenkins 2.164.1 Pipeline Utility Steps 2.3.0 Priority: Minor Reporter: fr33ky _ Trying to add a plugin to a pom, we are facing the following exception when writeMavenPom() is called: java.lang.ClassCastException: org.apache.maven.model.Plugin cannot be cast to org.apache.maven.model.Plugin at org.apache.maven.model.io.xpp3.MavenXpp3Writer.writeBuild(MavenXpp3Writer.java:343) at org.apache.maven.model.io.xpp3.MavenXpp3Writer.writeModel(MavenXpp3Writer.java:1134) at org.apache.maven.model.io.xpp3.MavenXpp3Writer.write(MavenXpp3Writer.java:134) at org.jenkinsci.plugins.pipeline.utility.steps.maven.WriteMavenPomStep$Execution.run(WriteMavenPomStep.java:160) at org.jenkinsci.plugins.pipeline.utility.steps.maven.WriteMavenPomStep$Execution.run(WriteMavenPomStep.java:130) at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748)
[JIRA] (JENKINS-56966) Azure Deployment of .NET Package Folder has some files with 0 size
Title: Message Title Josh Chiancone updated an issue Jenkins / JENKINS-56966 Azure Deployment of .NET Package Folder has some files with 0 size Change By: Josh Chiancone Attachment: image-2019-04-11-10-22-58-877.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. For more options, visit https://groups.google.com/d/optout.
