[JIRA] (JENKINS-60684) Job shown twice and creates duplicate folder in Windows
Title: Message Title Geoff Bache created an issue Jenkins / JENKINS-60684 Job shown twice and creates duplicate folder in Windows Issue Type: Bug Assignee: Unassigned Components: core Created: 2020-01-08 07:36 Environment: Jenkins 2.204 Windows Server 2016 Java 1.8.0_144 Priority: Minor Reporter: Geoff Bache I have one Jenkins job that constantly shows up twice on the "All" tab in the main jobs view. The first link takes me to the job and shows the builds, the second shows the job as never having run. If I look under the "jobs" folder on the disk in Windows explorer it seems Jenkins has somehow managed to create two folders with the same name and same parent. The "extra" one contains the directory "builds" with an empty file "legacyIds" and a file "permalinks" containing only the text lastFailedBuild -1 lastSuccessfulBuild -1 If I rename or remove this folder and restart Jenkins, it is recreated with the same contents and the same behaviour in the Jenkins GUI. If I go to the "Manage Jenkins" tab, this job is also listed as having data in an old format, though I've been unable to work out what it is referring to, and whether this is a symptom or a cause of the above problem. We have many other Jenkins jobs that do not exhibit this behaviour. I wondered about folder permission but Jenkins seems to be able to write to the folder without difficulties when running the job, which works fine if you use the "correct version" of it. I realise this is probably not enough information to reproduce this but I'm mostly looking for advice on how to troubleshoot this further.
[JIRA] (JENKINS-60417) Print log if post processing has been skipped
Title: Message Title shubham srivastava commented on JENKINS-60417 Re: Print log if post processing has been skipped I just removed all the empty files from the directory whose name is matching with the regex and then the plugin works fine. if even a single empty file is present in the directory the complete post processing is skipped and logger output is not shown Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203478.1575970934000.4299.1578463260230%40Atlassian.JIRA.
[JIRA] (JENKINS-60683) Jenkins fails to launch S3-publisher plugin
Title: Message Title sean martin updated an issue Jenkins / JENKINS-60683 Jenkins fails to launch S3-publisher plugin Change By: sean martin !image-2020-01-08-11-04-02-406.png! Hope to help me 希望对我有帮助 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203927.1578452753000.4290.1578453420350%40Atlassian.JIRA.
[JIRA] (JENKINS-60683) Jenkins fails to launch S3-publisher plugin
Title: Message Title sean martin created an issue Jenkins / JENKINS-60683 Jenkins fails to launch S3-publisher plugin Issue Type: Bug Assignee: Alexander A Attachments: image-2020-01-08-11-04-02-406.png, image-2020-01-08-11-04-23-546.png Components: s3-plugin Created: 2020-01-08 03:05 Priority: Blocker Reporter: sean martin Hope to help me Add Comment
[JIRA] (JENKINS-59741) EditIssueStep in Jira Steps Plugin does not allow setting "notifyUsers" flag.
Title: Message Title Arjun Gopisetty started work on JENKINS-59741 Change By: Arjun Gopisetty Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202459.1570779665000.4281.1578451680444%40Atlassian.JIRA.
[JIRA] (JENKINS-59741) EditIssueStep in Jira Steps Plugin does not allow setting "notifyUsers" flag.
Title: Message Title Arjun Gopisetty stopped work on JENKINS-59741 Change By: Arjun Gopisetty Status: In Progress Open Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202459.1570779665000.4276.1578451020439%40Atlassian.JIRA.
[JIRA] (JENKINS-59741) EditIssueStep in Jira Steps Plugin does not allow setting "notifyUsers" flag.
Title: Message Title Arjun Gopisetty started work on JENKINS-59741 Change By: Arjun Gopisetty Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202459.1570779665000.4271.1578450540393%40Atlassian.JIRA.
[JIRA] (JENKINS-59300) p4-plugin sets client root to null with template workspaces
Title: Message Title David Hows updated an issue Jenkins / JENKINS-59300 p4-plugin sets client root to null with template workspaces Change By: David Hows Comment: So, i've just been bitten hard by this in or Prod environment.I'm not by any means fluent in Java, but it looks like the issue is proximally caused by the line you mentioned, but actually caused because the deepClone() is actually not a deep clone, but rather a shallow clone. My understanding is that this would make all the subobjects references to the original and any changes would be reflected in both.Consider the call to deepClone() [here|[https://github.com/jenkinsci/p4-plugin/blob/master/src/main/java/org/jenkinsci/plugins/p4/workspace/Workspace.java#L165]] it simply calls [clone()|https://docs.oracle.com/javase/7/docs/api/java/lang/Object.html] which per Javadoc is a shallow copy. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit
[JIRA] (JENKINS-37588) Multibranch pipeline does not allow quiet time or throttle
Title: Message Title vincenzo cerbone commented on JENKINS-37588 Re: Multibranch pipeline does not allow quiet time or throttle Successfully tested with Declarative (Jenkins 2.200) but had no luck to set it in Scripted fashion. As someone stated before, there's no way neither to get it generated with pipeline-syntax generator, nor trying something like this: properties([ pipelineTriggers([ [ $class: 'HudsonStartupTrigger', quietPeriod: '2' ] ]) ]) will produce: no known implementation of class hudson.triggers.Trigger is named HudsonStartupTrigger Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.173704.1471877153000.4216.1578441061154%40Atlassian.JIRA.
[JIRA] (JENKINS-60658) Jenkins ver. 2.204.1 missing org/joda/time/DateTime
Title: Message Title Daniel Foulkes updated JENKINS-60658 Jenkins / JENKINS-60658 Jenkins ver. 2.204.1 missing org/joda/time/DateTime Change By: Daniel Foulkes Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203900.1578346137000.4214.1578438720219%40Atlassian.JIRA.
[JIRA] (JENKINS-60658) Jenkins ver. 2.204.1 missing org/joda/time/DateTime
Title: Message Title Daniel Foulkes commented on JENKINS-60658 Re: Jenkins ver. 2.204.1 missing org/joda/time/DateTime I've found the issue, also there's clearly no one bothering to fix the travis build issue so I've sorted that too. It looks like there's a real lack of oversight on this plugin atm. for those stuck my repo is now working with Jenkins 2.2+ if needed my PR request can be found at: https://github.com/dfoulkes/delivery-pipeline-plugin Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203900.1578346137000.4212.1578438660126%40Atlassian.JIRA.
[JIRA] (JENKINS-59300) p4-plugin sets client root to null with template workspaces
Title: Message Title David Hows edited a comment on JENKINS-59300 Re: p4-plugin sets client root to null with template workspaces So, i've just been bitten hard by this in or Prod environment.I'm not by any means fluent in Java, but it looks like the issue is proximally caused by the line you mentioned, but actually caused because the deepClone() is actually not a deep clone, but rather a shallow clone. My understanding is that this would make all the subobjects references to the original and any changes would be reflected in both.Consider the call to deepClone() [here|[https://github.com/jenkinsci/p4-plugin/blob/master/src/main/java/org/jenkinsci/plugins/p4/workspace/Workspace.java#L165]] it simply calls [clone()|https://docs.oracle.com/javase/7/docs/api/java/lang/Object.html] ] which per Javadoc is a shallow copy. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201847.1568127629000.4209.1578438240549%40Atlassian.JIRA.
[JIRA] (JENKINS-59300) p4-plugin sets client root to null with template workspaces
Title: Message Title David Hows edited a comment on JENKINS-59300 Re: p4-plugin sets client root to null with template workspaces So, i've just been bitten hard by this in or Prod environment.I'm not by any means fluent in Java, but it looks like the issue is proximally caused by the line you mentioned, but actually caused because the deepClone() is actually not a deep clone, but rather a shallow clone. My understanding is that this would make all the subobjects references to the original and any changes would be reflected in both.Consider the call to deepClone() [here|[https://github.com/jenkinsci/p4-plugin/blob/master/src/main/java/org/jenkinsci/plugins/p4/workspace/Workspace.java#L165] ] it simply calls [clone()|https://docs.oracle.com/javase/7/docs/api/java/lang/Object.html]] which per Javadoc is a shallow copy. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201847.1568127629000.4207.1578438240485%40Atlassian.JIRA.
[JIRA] (JENKINS-59300) p4-plugin sets client root to null with template workspaces
Title: Message Title David Hows edited a comment on JENKINS-59300 Re: p4-plugin sets client root to null with template workspaces So, i've just been bitten hard by this in or Prod environment.I'm not by any means fluent in Java, but it looks like the issue is proximally caused by the line you mentioned, but actually caused because the deepClone() is actually not a deep clone, but rather a shallow clone. My understanding is that this would make all the subobjects references to the original and any changes would be reflected in both. Consider the call to deepClone() [here|[https://github.com/jenkinsci/p4-plugin/blob/master/src/main/java/org/jenkinsci/plugins/p4/workspace/Workspace.java#L165] ] it simply calls [clone()| [ https://docs.oracle.com/javase/7/docs/api/java/lang/Object.html]] which per Javadoc is a shallow copy. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201847.1568127629000.4204.1578438240421%40Atlassian.JIRA.
[JIRA] (JENKINS-59300) p4-plugin sets client root to null with template workspaces
Title: Message Title David Hows commented on JENKINS-59300 Re: p4-plugin sets client root to null with template workspaces So, i've just been bitten hard by this in or Prod environment. I'm not by any means fluent in Java, but it looks like the issue is proximally caused by the line you mentioned, but actually caused because the deepClone() is actually not a deep clone, but rather a shallow clone. Consider the call to deepClone() here it simply calls [clone()|https://docs.oracle.com/javase/7/docs/api/java/lang/Object.html] which per Javadoc is a shallow copy. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201847.1568127629000.4200.1578437760149%40Atlassian.JIRA.
[JIRA] (JENKINS-50772) Content type not set reasonably
Title: Message Title Jesse Glick assigned an issue to Jesse Glick Jenkins / JENKINS-50772 Content type not set reasonably Change By: Jesse Glick Assignee: Robin Verduijn Jesse Glick Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.189876.1523552257000.4198.1578437580454%40Atlassian.JIRA.
[JIRA] (JENKINS-60682) Improve scriptApproval ux
Title: Message Title Josh Soref created an issue Jenkins / JENKINS-60682 Improve scriptApproval ux Issue Type: Improvement Assignee: Unassigned Attachments: image-2020-01-07-16-33-07-031.png, image-2020-01-07-16-33-19-734.png Components: core Created: 2020-01-07 21:34 Priority: Minor Reporter: Josh Soref Current: Replacement: Add Comment
[JIRA] (JENKINS-60642) Bitbucket Server Integration plugin breaks Role-based Authorization config
Title: Message Title Jeff Thornsen commented on JENKINS-60642 Re: Bitbucket Server Integration plugin breaks Role-based Authorization config Same behavior when using Matrix-based security. The atlassian-bitbucket plugin seems to require all users to have global ** Job/Configure or Administrator permissions. JENKINS-60116 claims to fix this in 1.0.3 of the plugin, but it doesn't seem to actually be fixed. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203881.1578301129000.4187.1578432421098%40Atlassian.JIRA.
[JIRA] (JENKINS-59493) Must include region in s3 bucket URL; support for GovCloud
Title: Message Title Jesse Glick updated JENKINS-59493 Jenkins / JENKINS-59493 Must include region in s3 bucket URL; support for GovCloud Change By: Jesse Glick Status: In Review Fixed but Unreleased Resolution: Fixed Released As: 1.8 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202109.1569270343000.4184.1578430980236%40Atlassian.JIRA.
[JIRA] (JENKINS-59493) Must include region in s3 bucket URL; support for GovCloud
Title: Message Title Jesse Glick assigned an issue to Jesse Glick Jenkins / JENKINS-59493 Must include region in s3 bucket URL; support for GovCloud Change By: Jesse Glick Assignee: candrews Jesse Glick Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202109.1569270343000.4182.1578429840308%40Atlassian.JIRA.
[JIRA] (JENKINS-60648) java.lang.IllegalStateException: The super POM /org/apache/maven/model/pom-4.0.0.xml was not found, please verify the integrity of your Maven installation
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-60648 java.lang.IllegalStateException: The super POM /org/apache/maven/model/pom-4.0.0.xml was not found, please verify the integrity of your Maven installation Change By: Oleg Nenashev Labels: jenkins regression Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203890.1578328547000.4179.1578428700467%40Atlassian.JIRA.
[JIRA] (JENKINS-60641) IllegalArgumentException: No script is provided
Title: Message Title Oleg Nenashev commented on JENKINS-60641 Re: IllegalArgumentException: No script is provided 2.213 includes the fix FTR Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203880.157829510.4172.1578428520386%40Atlassian.JIRA.
[JIRA] (JENKINS-60116) Overall/Administer permission required to configure jobs
Title: Message Title Jeff Thornsen commented on JENKINS-60116 Re: Overall/Administer permission required to configure jobs This is still not fixed for me with atlassian-bitbucket-server-integration-plugin version 1.0.3. All users still require global Administrator or Job/Configure permissions to do anything inside of Folders. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202963.1573262524000.4170.1578427980222%40Atlassian.JIRA.
[JIRA] (JENKINS-60490) Job/Configure permission required to configure jobs
Title: Message Title Jeff Thornsen commented on JENKINS-60490 Re: Job/Configure permission required to configure jobs This is affecting my instance as well. It seems there is a bug or limitation in Atlassian's Jenkins-Bitbucket integration plugin that requires all users to have global Job/Configure permissions. Simply having permissions at the Folder Level isn't sufficient, and causes all kinds of weird behavior in the UI (like the configure page loading but half the buttons are non-operational, or getting the "Oops" page with the burning Jenkins logo). Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203579.1576451961000.4167.1578427500179%40Atlassian.JIRA.
[JIRA] (JENKINS-60680) NullPointerException after upgrading analysis model api
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-60680 NullPointerException after upgrading analysis model api Change By: Ulli Hafner Component/s: analysis-model Component/s: analysis-core-plugin Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203924.1578424869000.4162.1578426600277%40Atlassian.JIRA.
[JIRA] (JENKINS-60680) NullPointerException after upgrading analysis model api
Title: Message Title Ulli Hafner resolved as Fixed Jenkins / JENKINS-60680 NullPointerException after upgrading analysis model api Change By: Ulli Hafner Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203924.1578424869000.4164.1578426600315%40Atlassian.JIRA.
[JIRA] (JENKINS-60680) NullPointerException after upgrading analysis model api
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-60680 NullPointerException after upgrading analysis model api Change By: Ulli Hafner Environment: Jenkins 2.204.1Warnings NG 7.3 .0 Analysis Model API 7.0.3 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203924.1578424869000.4158.1578426540219%40Atlassian.JIRA.
[JIRA] (JENKINS-60680) NullPointerException after upgrading analysis model api
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-60680 NullPointerException after upgrading analysis model api Change By: Ulli Hafner Labels: NPE Released As: https://github.com/jenkinsci/analysis-model/releases/tag/analysis-model-7.0.4 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203924.1578424869000.4160.1578426540251%40Atlassian.JIRA.
[JIRA] (JENKINS-60415) Deleting project does not delete artifacts from S3
Title: Message Title Jesse Glick commented on JENKINS-60415 Re: Deleting project does not delete artifacts from S3 Could be considered a core bug in that JCloudsArtifactManager.delete ought to have been called for all the builds, but that would be inefficient anyway. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203473.1575952804000.4155.1578425520239%40Atlassian.JIRA.
[JIRA] (JENKINS-60681) LDAP Error
Title: Message Title Santiago Costa Diaz created an issue Jenkins / JENKINS-60681 LDAP Error Issue Type: Bug Assignee: Unassigned Components: ldap-plugin Created: 2020-01-07 19:31 Environment: PROD Priority: Blocker Reporter: Santiago Costa Diaz Stack trace org.springframework.dao.IncorrectResultSizeDataAccessException: Incorrect result size: expected 1, actual 2 at org.acegisecurity.ldap.LdapTemplate$3.doInDirContext(LdapTemplate.java:259) at org.acegisecurity.ldap.LdapTemplate.execute(LdapTemplate.java:126) at org.acegisecurity.ldap.LdapTemplate.searchForSingleEntry(LdapTemplate.java:246) at org.acegisecurity.ldap.search.FilterBasedLdapUserSearch.searchForUser(FilterBasedLdapUserSearch.java:119) at hudson.security.LDAPSecurityRealm$LDAPUserDetailsService.loadUserByUsername(LDAPSecurityRealm.java:1336) at hudson.security.LDAPSecurityRealm$LDAPUserDetailsService.loadUserByUsername(LDAPSecurityRealm.java:1273) at hudson.security.LDAPSecurityRealm$DescriptorImpl.validate(LDAPSecurityRealm.java:1747) at hudson.security.LDAPSecurityRealm$DescriptorImpl.doValidate(LDAPSecurityRealm.java:1617) at java.base/java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:710) at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:396) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:408) at org.kohsuke.stapler.interceptor.RequirePOST$Processor.invoke(RequirePOST.java:77) at org.kohsuke.stapler.PreInvokeInterceptedFunction.invoke(PreInvokeInterceptedFunction.java:26) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:212) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:145) at org.kohsuke.stapler.MetaClass$11.doDispatch(MetaClass.java:535) at
[JIRA] (JENKINS-59493) Must include region in s3 bucket URL; support for GovCloud
Title: Message Title Jesse Glick started work on JENKINS-59493 Change By: Jesse Glick Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202109.1569270343000.4151.1578425340383%40Atlassian.JIRA.
[JIRA] (JENKINS-59493) Must include region in s3 bucket URL; support for GovCloud
Title: Message Title Jesse Glick updated JENKINS-59493 Jenkins / JENKINS-59493 Must include region in s3 bucket URL; support for GovCloud Change By: Jesse Glick Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202109.1569270343000.4153.1578425340408%40Atlassian.JIRA.
[JIRA] (JENKINS-59493) Must include region in s3 bucket URL; support for GovCloud
Title: Message Title Jesse Glick assigned an issue to candrews Jenkins / JENKINS-59493 Must include region in s3 bucket URL; support for GovCloud Change By: Jesse Glick Assignee: candrews Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202109.1569270343000.4149.1578425340354%40Atlassian.JIRA.
[JIRA] (JENKINS-60667) Jobs hanging indefinitely on ec2 slaves
Title: Message Title Handi Gao updated an issue Jenkins / JENKINS-60667 Jobs hanging indefinitely on ec2 slaves Change By: Handi Gao Environment: Jenkins: 2.204.1 (base image: jenkinsci/blueocean:1.21.0)ec2 plugin: 1.47maven plugin: 3.4clone-workspace-scm plugin: 0.6htmlpublisher plugin: 1.21 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203910.1578354542000.4147.1578425160167%40Atlassian.JIRA.
[JIRA] (JENKINS-60680) NullPointerException after upgrading analysis model api
Title: Message Title Mohammad Sadegh Dehghan created an issue Jenkins / JENKINS-60680 NullPointerException after upgrading analysis model api Issue Type: Bug Assignee: Ulli Hafner Components: analysis-core-plugin Created: 2020-01-07 19:21 Environment: Jenkins 2.204.1 Warnings NG 7.3 Analysis Model API 7.0.3 Labels: NPE Priority: Major Reporter: Mohammad Sadegh Dehghan After Upgrading from Warning NG 6.0.4 and Analysis Model API 6.0.2 to latest versions, I got this exception: [Pipeline] recordIssues [Maven] Sleeping for 5 seconds due to JENKINS-32191...[Maven] Parsing console log (workspace: '/var/jenkins_home/build/workspace/project-test') [Java] Sleeping for 5 seconds due to JENKINS-32191...[Java] Parsing console log (workspace: '/var/jenkins_home/build/workspace/project-test')[Static Analysis] Attaching ResultAction with ID 'analysis' to run 'project-test #4690'. Error when executing always post condition: java.lang.NullPointerException at edu.hm.hafner.analysis.Report.addAll(Report.java:157) at edu.hm.hafner.analysis.Report.copyIssuesAndProperties(Report.java:586) at edu.hm.hafner.analysis.Report.addAll(Report.java:177) at io.jenkins.plugins.analysis.core.model.AnalysisResult.getIssues(AnalysisResult.java:411) at java.util.Optional.map(Optional.java:215) at io.jenkins.plugins.analysis.core.model.AnalysisHistory.getIssues(AnalysisHistory.java:139) at
[JIRA] (JENKINS-60667) Jobs hanging indefinitely on ec2 slaves
Title: Message Title Handi Gao updated an issue Jenkins / JENKINS-60667 Jobs hanging indefinitely on ec2 slaves Change By: Handi Gao Component/s: maven-plugin Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203910.1578354542000.4143.1578424860319%40Atlassian.JIRA.
[JIRA] (JENKINS-55017) Allow advanced configuration for other s3 providers
Title: Message Title Jesse Glick updated JENKINS-55017 Jenkins / JENKINS-55017 Allow advanced configuration for other s3 providers Change By: Jesse Glick Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196055.1543946313000.4141.1578424800934%40Atlassian.JIRA.
[JIRA] (JENKINS-55017) Allow advanced configuration for other s3 providers
Title: Message Title Jesse Glick started work on JENKINS-55017 Change By: Jesse Glick Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196055.1543946313000.4138.1578424800796%40Atlassian.JIRA.
[JIRA] (JENKINS-55017) Allow advanced configuration for other s3 providers
Title: Message Title Jesse Glick assigned an issue to Chris Tapley Jenkins / JENKINS-55017 Allow advanced configuration for other s3 providers Change By: Jesse Glick Assignee: Chris Tapley Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196055.1543946313000.4135.1578424800704%40Atlassian.JIRA.
[JIRA] (JENKINS-57566) Default security prohibits ResultAction's getResult
Title: Message Title Ulli Hafner resolved as Fixed Jenkins / JENKINS-57566 Default security prohibits ResultAction's getResult Change By: Ulli Hafner Status: In Progress Resolved Resolution: Fixed Released As: https://github.com/jenkinsci/warnings-ng-plugin/releases/tag/warnings-ng-7.3.0 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199480.1558369817000.4131.1578423060874%40Atlassian.JIRA.
[JIRA] (JENKINS-60679) java.lang.NoSuchMethodError: org.bouncycastle.asn1.DERNull.equals(Lorg/bouncycastle/asn1/ASN1Encodable;)Z
Title: Message Title Arnaud Lefebvre created an issue Jenkins / JENKINS-60679 java.lang.NoSuchMethodError: org.bouncycastle.asn1.DERNull.equals(Lorg/bouncycastle/asn1/ASN1Encodable;)Z Issue Type: Bug Assignee: Ivan Fernandez Calvo Components: saml-plugin Created: 2020-01-07 17:47 Environment: Jenkins 2.204.1 (LTS) Icedtea8 3.11.0 saml-plugin 1.1.4 bouncycastle-api 1.18 Priority: Major Reporter: Arnaud Lefebvre When logging in using SAML, jenkins will throw this error: java.lang.NoSuchMethodError: org.bouncycastle.asn1.DERNull.equals(Lorg/bouncycastle/asn1/ASN1Encodable;)Z at org.bouncycastle.operator.jcajce.OperatorHelper.getSignatureName(Unknown Source) at org.bouncycastle.operator.jcajce.OperatorHelper.createSignature(Unknown Source) at org.bouncycastle.operator.jcajce.JcaContentSignerBuilder.build(Unknown Source) at org.jenkinsci.plugins.saml.BundleKeyStore.generateCertificate(BundleKeyStore.java:279) at org.jenkinsci.plugins.saml.BundleKeyStore.createCertificateChain(BundleKeyStore.java:151) at org.jenkinsci.plugins.saml.BundleKeyStore.init(BundleKeyStore.java:113) at org.jenkinsci.plugins.saml.OpenSAMLWrapper.createSAML2Client(OpenSAMLWrapper.java:113) at org.jenkinsci.plugins.saml.SamlRedirectActionWrapper.process(SamlRedirectActionWrapper.java:45) at org.jenkinsci.plugins.saml.SamlRedirectActionWrapper.process(SamlRedirectActionWrapper.java:30) at org.jenkinsci.plugins.saml.OpenSAMLWrapper.get(OpenSAMLWrapper.java:64) at org.jenkinsci.plugins.saml.SamlSecurityRealm.doCommenceLogin(SamlSecurityRealm.java:257) at
[JIRA] (JENKINS-60537) Exception when using multiple labels on a pod template
Title: Message Title
Alexander Bodor edited a comment on JENKINS-60537
Re: Exception when using multiple labels on a pod template
Also affected by this at work, had to pin the plugin down to 1.22.0 for the time being, until this gets solved. Additional information: In versions 1.22.2, 1.22.3 and 1.22.4 (latest at the time of this writing) of the kubernetes plugin, we're getting a different error which might have also been introduced by this change (a bit of speculation on my side, but so it seems), so those newer versions are also unusable right now: {code:java}Jan 07, 2020 11:55:46 AM WARNING org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud provisionFailed to count the # of live instances on Kubernetesio.fabric8.kubernetes.client.KubernetesClientException: Failure executing: GET at: https://kubernetes.default.svc/api/v1/namespaces/edited-namespace/pods?labelSelector=jenkins%3Dslave%2Cjenkins%2Flabel%3Dkubernetes-tools-small%20agent. Message: found 'agent', expected: ',' or 'end of string'. Received status: Status(apiVersion=v1, code=400, details=null, kind=Status, message=found 'agent', expected: ',' or 'end of string', metadata=ListMeta(_continue=null, remainingItemCount=null, resourceVersion=null, selfLink=null, additionalProperties={}), reason=BadRequest, status=Failure, additionalProperties={}). at io.fabric8.kubernetes.client.dsl.base.OperationSupport.requestFailure(OperationSupport.java:510) at io.fabric8.kubernetes.client.dsl.base.OperationSupport.assertResponseCode(OperationSupport.java:449) at io.fabric8.kubernetes.client.dsl.base.OperationSupport.handleResponse(OperationSupport.java:413) at io.fabric8.kubernetes.client.dsl.base.OperationSupport.handleResponse(OperationSupport.java:372) at io.fabric8.kubernetes.client.dsl.base.OperationSupport.handleResponse(OperationSupport.java:354) at io.fabric8.kubernetes.client.dsl.base.BaseOperation.listRequestHelper(BaseOperation.java:153) at io.fabric8.kubernetes.client.dsl.base.BaseOperation.list(BaseOperation.java:620) at io.fabric8.kubernetes.client.dsl.base.BaseOperation.list(BaseOperation.java:69) at org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud.getActiveSlavePods(KubernetesCloud.java:608) at org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud.addProvisionedSlave(KubernetesCloud.java:593) at org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud.provision(KubernetesCloud.java:535) at io.jenkins.plugins.kubernetes.NoDelayProvisionerStrategy.apply(NoDelayProvisionerStrategy.java:64) at hudson.slaves.NodeProvisioner.update(NodeProvisioner.java:332) at hudson.slaves.NodeProvisioner.access$900(NodeProvisioner.java:63) at hudson.slaves.NodeProvisioner$NodeProvisionerInvoker.doRun(NodeProvisioner.java:819) at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:70) at jenkins.security.ImpersonatingScheduledExecutorService$1.run(ImpersonatingScheduledExecutorService.java:58) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) 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} K8s endpoint in AWS EKS 1.13 (if it matters): {code:java}Server Version: version.Info{Major:"1", Minor:"13+", GitVersion:"v1.13.12-eks-eb1860", GitCommit:"eb1860579253bb5bf83a5a03eb0330307ae26d18",
[JIRA] (JENKINS-60537) Exception when using multiple labels on a pod template
Title: Message Title
Alexander Bodor edited a comment on JENKINS-60537
Re: Exception when using multiple labels on a pod template
Also affected by this at work, had to pin the plugin down to 1.22.0 for the time being, until this gets solved. Additional information: In versions 1.22.2, 1.22.3 and 1.22.4 (latest at the time of this writing) of the kubernetes plugin, we're getting a different error which might have also been introduced by this change (a bit of speculation on my side, but so it seems), so those newer versions are also unusable right now: {code:java}Jan 07, 2020 11:55:46 AM WARNING org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud provisionFailed to count the # of live instances on Kubernetesio.fabric8.kubernetes.client.KubernetesClientException: Failure executing: GET at: https://kubernetes.default.svc/api/v1/namespaces/edited-namespace/pods?labelSelector=jenkins%3Dslave%2Cjenkins%2Flabel%3Dkubernetes-tools-small%20agent. Message: found 'agent', expected: ',' or 'end of string'. Received status: Status(apiVersion=v1, code=400, details=null, kind=Status, message=found 'agent', expected: ',' or 'end of string', metadata=ListMeta(_continue=null, remainingItemCount=null, resourceVersion=null, selfLink=null, additionalProperties={}), reason=BadRequest, status=Failure, additionalProperties={}). at io.fabric8.kubernetes.client.dsl.base.OperationSupport.requestFailure(OperationSupport.java:510) at io.fabric8.kubernetes.client.dsl.base.OperationSupport.assertResponseCode(OperationSupport.java:449) at io.fabric8.kubernetes.client.dsl.base.OperationSupport.handleResponse(OperationSupport.java:413) at io.fabric8.kubernetes.client.dsl.base.OperationSupport.handleResponse(OperationSupport.java:372) at io.fabric8.kubernetes.client.dsl.base.OperationSupport.handleResponse(OperationSupport.java:354) at io.fabric8.kubernetes.client.dsl.base.BaseOperation.listRequestHelper(BaseOperation.java:153) at io.fabric8.kubernetes.client.dsl.base.BaseOperation.list(BaseOperation.java:620) at io.fabric8.kubernetes.client.dsl.base.BaseOperation.list(BaseOperation.java:69) at org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud.getActiveSlavePods(KubernetesCloud.java:608) at org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud.addProvisionedSlave(KubernetesCloud.java:593) at org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud.provision(KubernetesCloud.java:535) at io.jenkins.plugins.kubernetes.NoDelayProvisionerStrategy.apply(NoDelayProvisionerStrategy.java:64) at hudson.slaves.NodeProvisioner.update(NodeProvisioner.java:332) at hudson.slaves.NodeProvisioner.access$900(NodeProvisioner.java:63) at hudson.slaves.NodeProvisioner$NodeProvisionerInvoker.doRun(NodeProvisioner.java:819) at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:70) at jenkins.security.ImpersonatingScheduledExecutorService$1.run(ImpersonatingScheduledExecutorService.java:58) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) 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} K8s endpoint in AWS EKS 1.13: {code:java}Server Version: version.Info{Major:"1", Minor:"13+", GitVersion:"v1.13.12-eks-eb1860", GitCommit:"eb1860579253bb5bf83a5a03eb0330307ae26d18",
[JIRA] (JENKINS-60537) Exception when using multiple labels on a pod template
Title: Message Title
Alexander Bodor edited a comment on JENKINS-60537
Re: Exception when using multiple labels on a pod template
Also affected by this at work, had to pin the plugin down to 1.22.0 for the time being, until this gets solved. Additional information: In versions 1.22.2, 1.22.3 and 1.22.4 (latest at the time of this writing) of the kubernetes plugin, we're getting a different error which might have also been introduced by this change (a bit of speculation on my side, but so it seems), so those newer versions are also unusable right now: {code:java}Jan 07, 2020 11:55:46 AM WARNING org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud provisionFailed to count the # of live instances on Kubernetesio.fabric8.kubernetes.client.KubernetesClientException: Failure executing: GET at: https://kubernetes.default.svc/api/v1/namespaces/edited-namespace/pods?labelSelector=jenkins%3Dslave%2Cjenkins%2Flabel%3Dkubernetes-tools-small%20agent. Message: found 'agent', expected: ',' or 'end of string'. Received status: Status(apiVersion=v1, code=400, details=null, kind=Status, message=found 'agent', expected: ',' or 'end of string', metadata=ListMeta(_continue=null, remainingItemCount=null, resourceVersion=null, selfLink=null, additionalProperties={}), reason=BadRequest, status=Failure, additionalProperties={}). at io.fabric8.kubernetes.client.dsl.base.OperationSupport.requestFailure(OperationSupport.java:510) at io.fabric8.kubernetes.client.dsl.base.OperationSupport.assertResponseCode(OperationSupport.java:449) at io.fabric8.kubernetes.client.dsl.base.OperationSupport.handleResponse(OperationSupport.java:413) at io.fabric8.kubernetes.client.dsl.base.OperationSupport.handleResponse(OperationSupport.java:372) at io.fabric8.kubernetes.client.dsl.base.OperationSupport.handleResponse(OperationSupport.java:354) at io.fabric8.kubernetes.client.dsl.base.BaseOperation.listRequestHelper(BaseOperation.java:153) at io.fabric8.kubernetes.client.dsl.base.BaseOperation.list(BaseOperation.java:620) at io.fabric8.kubernetes.client.dsl.base.BaseOperation.list(BaseOperation.java:69) at org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud.getActiveSlavePods(KubernetesCloud.java:608) at org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud.addProvisionedSlave(KubernetesCloud.java:593) at org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud.provision(KubernetesCloud.java:535) at io.jenkins.plugins.kubernetes.NoDelayProvisionerStrategy.apply(NoDelayProvisionerStrategy.java:64) at hudson.slaves.NodeProvisioner.update(NodeProvisioner.java:332) at hudson.slaves.NodeProvisioner.access$900(NodeProvisioner.java:63) at hudson.slaves.NodeProvisioner$NodeProvisionerInvoker.doRun(NodeProvisioner.java:819) at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:70) at jenkins.security.ImpersonatingScheduledExecutorService$1.run(ImpersonatingScheduledExecutorService.java:58) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) 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} K8s endpoint in AWS EKS 1.13 (if it matters) : {code:java}Server Version: version.Info{Major:"1", Minor:"13+", GitVersion:"v1.13.12-eks-eb1860", GitCommit:"eb1860579253bb5bf83a5a03eb0330307ae26d18",
[JIRA] (JENKINS-60537) Exception when using multiple labels on a pod template
Title: Message Title
Alexander Bodor commented on JENKINS-60537
Re: Exception when using multiple labels on a pod template
Also affected by this at work, had to pin the plugin down to 1.22.0 for the time being, until this gets solved. Additional information: In versions 1.22.2, 1.22.3 and 1.22.4 (latest at the time of this writing) of the kubernetes plugin, we're getting a different error which might have also been introduced by this change (a bit of speculation on my side, but so it seems), so those newer versions are also unusable right now:
Jan 07, 2020 11:55:46 AM WARNING org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud provision
Failed to count the # of live instances on Kubernetes
io.fabric8.kubernetes.client.KubernetesClientException: Failure executing: GET at: https://kubernetes.default.svc/api/v1/namespaces/edited-namespace/pods?labelSelector=jenkins%3Dslave%2Cjenkins%2Flabel%3Dkubernetes-tools-small%20agent. Message: found 'agent', expected: ',' or 'end of string'. Received status: Status(apiVersion=v1, code=400, details=null, kind=Status, message=found 'agent', expected: ',' or 'end of string', metadata=ListMeta(_continue=null, remainingItemCount=null, resourceVersion=null, selfLink=null, additionalProperties={}), reason=BadRequest, status=Failure, additionalProperties={}).
at io.fabric8.kubernetes.client.dsl.base.OperationSupport.requestFailure(OperationSupport.java:510)
at io.fabric8.kubernetes.client.dsl.base.OperationSupport.assertResponseCode(OperationSupport.java:449)
at io.fabric8.kubernetes.client.dsl.base.OperationSupport.handleResponse(OperationSupport.java:413)
at io.fabric8.kubernetes.client.dsl.base.OperationSupport.handleResponse(OperationSupport.java:372)
at io.fabric8.kubernetes.client.dsl.base.OperationSupport.handleResponse(OperationSupport.java:354)
at io.fabric8.kubernetes.client.dsl.base.BaseOperation.listRequestHelper(BaseOperation.java:153)
at io.fabric8.kubernetes.client.dsl.base.BaseOperation.list(BaseOperation.java:620)
at io.fabric8.kubernetes.client.dsl.base.BaseOperation.list(BaseOperation.java:69)
at org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud.getActiveSlavePods(KubernetesCloud.java:608)
at org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud.addProvisionedSlave(KubernetesCloud.java:593)
at org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud.provision(KubernetesCloud.java:535)
at io.jenkins.plugins.kubernetes.NoDelayProvisionerStrategy.apply(NoDelayProvisionerStrategy.java:64)
at hudson.slaves.NodeProvisioner.update(NodeProvisioner.java:332)
at hudson.slaves.NodeProvisioner.access$900(NodeProvisioner.java:63)
at hudson.slaves.NodeProvisioner$NodeProvisionerInvoker.doRun(NodeProvisioner.java:819)
at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:70)
at jenkins.security.ImpersonatingScheduledExecutorService$1.run(ImpersonatingScheduledExecutorService.java:58)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
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-60662) Update Jenkins Core Changelog Generator to support new labels
Title: Message Title Oleg Nenashev updated JENKINS-60662 Jenkins / JENKINS-60662 Update Jenkins Core Changelog Generator to support new labels Change By: Oleg Nenashev Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203904.157835026.4106.1578416280209%40Atlassian.JIRA.
[JIRA] (JENKINS-60663) Update Jenkins Changelog generator to inject authors for notable changes
Title: Message Title Oleg Nenashev resolved as Fixed Jenkins / JENKINS-60663 Update Jenkins Changelog generator to inject authors for notable changes Change By: Oleg Nenashev Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203906.1578350453000.4107.1578416280253%40Atlassian.JIRA.
[JIRA] (JENKINS-51550) docker.image.inside run after why do delete the container , which make me can not to deploy to a docker container
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-51550 docker.image.inside run after why do delete the container , which make me can not to deploy to a docker container Change By: Jesse Glick Component/s: pipeline Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.190936.1527280701000.4101.1578414720782%40Atlassian.JIRA.
[JIRA] (JENKINS-51550) docker.image.inside run after why do delete the container , which make me can not to deploy to a docker container
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-51550 docker.image.inside run after why do delete the container , which make me can not to deploy to a docker container Change By: Jesse Glick Issue Type: Bug New Feature Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.190936.1527280701000.4103.1578414720880%40Atlassian.JIRA.
[JIRA] (JENKINS-60677) Option to cancel builds when orphaning items
Title: Message Title Francisco Fernández assigned an issue to Unassigned Jenkins / JENKINS-60677 Option to cancel builds when orphaning items Change By: Francisco Fernández Assignee: Francisco Fernández Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203921.1578408271000.4097.1578414600205%40Atlassian.JIRA.
[JIRA] (JENKINS-60676) withDockerContainer Stop and delete containers after body execution
Title: Message Title Abdou KEITA commented on JENKINS-60676 Re: withDockerContainer Stop and delete containers after body execution Could you update https://issues.jenkins-ci.org/browse/JENKINS-51550 as well? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203919.1578396581000.4086.1578413280163%40Atlassian.JIRA.
[JIRA] (JENKINS-55348) Display Pull Request Name instead of ID in the UI
Title: Message Title Pay Bas commented on JENKINS-55348 Re: Display Pull Request Name instead of ID in the UI This is the Trait that I created. Working well. Going on holiday soon so a colleague of mine will probably finish it and create a PR. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196444.1545944269000.4080.1578413100739%40Atlassian.JIRA.
[JIRA] (JENKINS-55348) Display Pull Request Name instead of ID in the UI
Title: Message Title Pay Bas updated an issue Jenkins / JENKINS-55348 Display Pull Request Name instead of ID in the UI Change By: Pay Bas Attachment: Screenshot_2020-01-07 opp-release Config [Jenkins].png Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196444.1545944269000.4070.1578412920305%40Atlassian.JIRA.
[JIRA] (JENKINS-30413) Failed test age is incorrect if same test name exist in different package
Title: Message Title Stephen McCants edited a comment on JENKINS-30413 Re: Failed test age is incorrect if same test name exist in different package I'm seeing this problem on Jenkins 2.198 with JUnit plugin 1.28. Since there is a test case demonstrating the problem and a purposed proposed fix (along with 6 votes) could this ticket get a little attention to fix the problem? Thanks. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.165008.144198007.4054.1578411900590%40Atlassian.JIRA.
[JIRA] (JENKINS-56755) JUnit test report: Age and failedSince are wrong if test method names are not unique
Title: Message Title Stephen McCants commented on JENKINS-56755 Re: JUnit test report: Age and failedSince are wrong if test method names are not unique Yes, I just pinged that ticket requesting a little attention... I also voted for it since I just hit this problem myself. Hopefully it can be fixed easily with just a little attention. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198398.1553601185000.4051.1578411780149%40Atlassian.JIRA.
[JIRA] (JENKINS-56755) JUnit test report: Age and failedSince are wrong if test method names are not unique
Title: Message Title Lars commented on JENKINS-56755 Re: JUnit test report: Age and failedSince are wrong if test method names are not unique ... and is still not merged Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198398.1553601185000.4048.1578411661392%40Atlassian.JIRA.
[JIRA] (JENKINS-30413) Failed test age is incorrect if same test name exist in different package
Title: Message Title Stephen McCants commented on JENKINS-30413 Re: Failed test age is incorrect if same test name exist in different package I'm seeing this problem on Jenkins 2.198 with JUnit plugin 1.28. Since there is a test case demonstrating the problem and a purposed fix (along with 6 votes) could this ticket get a little attention to fix the problem? Thanks. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.165008.144198007.4033.1578411600290%40Atlassian.JIRA.
[JIRA] (JENKINS-30413) Failed test age is incorrect if same test name exist in different package
Title: Message Title Stephen McCants updated an issue Jenkins / JENKINS-30413 Failed test age is incorrect if same test name exist in different package Change By: Stephen McCants Environment: Jenkins-1.609.3 & 2.198 Junit-plugin 1.9 & 1.28 gtest to run test & produce xml results Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.165008.144198007.4023.1578411480416%40Atlassian.JIRA.
[JIRA] (JENKINS-60678) ComputerLauncher: Detection of AdoptOpenJDK 11 fails
Title: Message Title Martin Karing created an issue Jenkins / JENKINS-60678 ComputerLauncher: Detection of AdoptOpenJDK 11 fails Issue Type: Bug Assignee: Unassigned Components: core Created: 2020-01-07 15:35 Environment: Jenkins 2.209 Windows Server 2012 R2 AdoptOpenJDK 11 Priority: Minor Reporter: Martin Karing The ComputerLauncher.checkJavaVersion seems to have a problem when using Adopt OpenJDK 11 on Windows Server 2012 R2. The command line java -version produces the following output: openjdk version "11.0.5" 2019-10-15 OpenJDK Runtime Environment AdoptOpenJDK (build 11.0.5+10) OpenJDK 64-Bit Server VM AdoptOpenJDK (build 11.0.5+10, mixed mode) I am guessing the date behind the version could be the issue. Add
[JIRA] (JENKINS-56755) JUnit test report: Age and failedSince are wrong if test method names are not unique
Title: Message Title Stephen McCants commented on JENKINS-56755 Re: JUnit test report: Age and failedSince are wrong if test method names are not unique Seems like a duplicate of JENKINS-30413, which has a test case and purposed fix. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198398.1553601185000.4019.1578411300101%40Atlassian.JIRA.
[JIRA] (JENKINS-60426) All stages show up as UNSTABLE when one stage is unstable
Title: Message Title Nicholas Brown edited a comment on JENKINS-60426 Re: All stages show up as UNSTABLE when one stage is unstable Dupe of JenkinsJENKINS JENKINS -58783 ?Which was created as a result of: https://issues.jenkins-ci.org/browse/JENKINS-39203?focusedCommentId=372584#comment-372584 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203498.157599677.4003.1578409800511%40Atlassian.JIRA.
[JIRA] (JENKINS-60426) All stages show up as UNSTABLE when one stage is unstable
Title: Message Title Nicholas Brown commented on JENKINS-60426 Re: All stages show up as UNSTABLE when one stage is unstable Dupe of JenkinsJENKINS-58783 ? Which was created as a result of: https://issues.jenkins-ci.org/browse/JENKINS-39203?focusedCommentId=372584#comment-372584 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203498.157599677.4000.1578409800447%40Atlassian.JIRA.
[JIRA] (JENKINS-41662) Proceed button fails (investigate)
Title: Message Title Ted Sanders commented on JENKINS-41662 Re: Proceed button fails (investigate) I am experiencing the same problem with war: 2.190.3 and Blue Ocean 1.21.0 Pub-Sub "light" Bus 1.13 Rolling back to different plugin versions puts blue ocean into a worsened, unusable state. No screen output. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-60536) Jenkins job hangs in Jira call after git rev-list command
Title: Message Title
David France edited a comment on JENKINS-60536
Re: Jenkins job hangs in Jira call after git rev-list command
We've being seeing much the same problem stack that Kieran reported, trying to progress issues by a workflow action in Jira. We first became aware of the problem on 20/12/2019 .The locking thread :{noformat}" Handling GET /view/Pipelines/job/.../457/ from a.b.c.d : qtp64133603-15 AbstractBuild/index.jelly SubversionChangeLogSet/digest.jelly" #15 prio=5 os_prio=0 cpu=8985.66ms elapsed=5244.95s tid=0x64d07000 nid=0x1fdc waiting for monitor entry [0x665b7000] java.lang.Thread.State: BLOCKED (on object monitor)at org.apache.http.nio.reactor.ssl.SSLIOSession.close(SSLIOSession.java:605)- waiting to lock <0x8613f660> (a org.apache.http.nio.reactor.ssl.SSLIOSession)at org.apache.http.impl.nio.NHttpConnectionBase.close(NHttpConnectionBase.java:511)at org.apache.http.impl.nio.conn.CPoolEntry.closeConnection(CPoolEntry.java:75)at org.apache.http.impl.nio.conn.CPoolEntry.close(CPoolEntry.java:101)at org.apache.http.nio.pool.AbstractNIOConnPool.processPendingRequest(AbstractNIOConnPool.java:423)at org.apache.http.nio.pool.AbstractNIOConnPool.lease(AbstractNIOConnPool.java:280)at org.apache.http.impl.nio.conn.PoolingNHttpClientConnectionManager.requestConnection(PoolingNHttpClientConnectionManager.java:295)at org.apache.http.impl.nio.client.AbstractClientExchangeHandler.requestConnection(AbstractClientExchangeHandler.java:377)at org.apache.http.impl.nio.client.DefaultClientExchangeHandlerImpl.start(DefaultClientExchangeHandlerImpl.java:129)at org.apache.http.impl.nio.client.InternalHttpAsyncClient.execute(InternalHttpAsyncClient.java:141)at org.apache.http.impl.nio.client.CloseableHttpAsyncClient.execute(CloseableHttpAsyncClient.java:75)at org.apache.http.impl.nio.client.CloseableHttpAsyncClient.execute(CloseableHttpAsyncClient.java:108)at com.atlassian.httpclient.apache.httpcomponents.SettableFuturePromiseHttpPromiseAsyncClient.execute(SettableFuturePromiseHttpPromiseAsyncClient.java:36)at com.atlassian.httpclient.apache.httpcomponents.ApacheAsyncHttpClient.doExecute(ApacheAsyncHttpClient.java:417)at com.atlassian.httpclient.apache.httpcomponents.ApacheAsyncHttpClient.execute(ApacheAsyncHttpClient.java:364)at com.atlassian.httpclient.apache.httpcomponents.DefaultRequest$DefaultRequestBuilder.execute(DefaultRequest.java:297)at com.atlassian.jira.rest.client.internal.async.AtlassianHttpClientDecorator$AuthenticatedRequestBuilder.execute(AtlassianHttpClientDecorator.java:83)at com.atlassian.httpclient.apache.httpcomponents.DefaultRequest$DefaultRequestBuilder.get(DefaultRequest.java:253)at com.atlassian.jira.rest.client.internal.async.AbstractAsynchronousRestClient.getAndParse(AbstractAsynchronousRestClient.java:69)at com.atlassian.jira.rest.client.internal.async.AsynchronousIssueRestClient.getIssue(AsynchronousIssueRestClient.java:186)at com.atlassian.jira.rest.client.internal.async.AsynchronousIssueRestClient.getIssue(AsynchronousIssueRestClient.java:177)at hudson.plugins.jira.JiraRestService.getIssue(JiraRestService.java:154)at hudson.plugins.jira.JiraSession.getIssue(JiraSession.java:126)at hudson.plugins.jira.JiraSite.lambda$getIssue$0(JiraSite.java:878)at hudson.plugins.jira.JiraSite$$Lambda$303/0x2262d840.call(Unknown Source)at com.google.common.cache.LocalCache$LocalManualCache$1.load(LocalCache.java:4767)at
[JIRA] (JENKINS-6659) Record a change message along with the job change history
Title: Message Title Robin Schulz commented on JENKINS-6659 Re: Record a change message along with the job change history I'm currently working on this and the recent idea would be a sticky textbox next to the configure page (see picture). "Really mandatory" fields are not possible as far as I know, since the user may just ignore the red errors/ warnings and click S_ave_ nonetheless. It is possible to display an error/ warning depending on jch plugin configuration or to just always display it. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.136754.1275075929000.3970.1578409260361%40Atlassian.JIRA.
[JIRA] (JENKINS-60301) Cancel builds on new patch sets
Title: Message Title John V commented on JENKINS-60301 Re: Cancel builds on new patch sets I agree it would make more sense to have it in there, I've created JENKINS-60677. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203296.1574859139000.3954.1578408480258%40Atlassian.JIRA.
[JIRA] (JENKINS-60677) Option to cancel builds when orphaning items
Title: Message Title John V created an issue Jenkins / JENKINS-60677 Option to cancel builds when orphaning items Issue Type: New Feature Assignee: Francisco Fernández Components: cloudbees-folder-plugin Created: 2020-01-07 14:44 Priority: Major Reporter: John V It would be great to have the option to cancel builds when the orphaning is calculated. That is in DefaultOrphanedItemStrategy.java -> orphanedItems it checks whether it is currently building and skips the item (I would like to see that the build can be canceled). We are using the gerrit-code-review-plugin and having such an option would save us CPU resources when a new patch set is uploaded as the build result of the old patch set becomes obsolete once the new one is uploaded. Add Comment
[JIRA] (JENKINS-37579) image-gallery-plugin should support pipeline builds
Title: Message Title Cristian Ghita commented on JENKINS-37579 Re: image-gallery-plugin should support pipeline builds I would also need this plug-in available in pipelines. Currently I have some docker image running some UI tests and saving a screenshot on each failed test inside the container. I want to take those images out and have them displayed via this plug-in per build. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.173694.147181410.3941.1578407940397%40Atlassian.JIRA.
[JIRA] (JENKINS-60676) withDockerContainer Stop and delete containers after body execution
Title: Message Title Jesse Glick commented on JENKINS-60676 Re: withDockerContainer Stop and delete containers after body execution I am no longer maintaining this plugin, but if I were, I would recommend any such PR be rejected as an unnecessary complication. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203919.1578396581000.3938.1578407760161%40Atlassian.JIRA.
[JIRA] (JENKINS-60676) withDockerContainer Stop and delete containers after body execution
Title: Message Title Jesse Glick assigned an issue to Unassigned Jenkins / JENKINS-60676 withDockerContainer Stop and delete containers after body execution Change By: Jesse Glick Assignee: Jesse Glick Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203919.1578396581000.3936.1578407700388%40Atlassian.JIRA.
[JIRA] (JENKINS-55037) Allow configuration/filtering of detected Changes
Title: Message Title Luca Domenico Milanesio commented on JENKINS-55037 Re: Allow configuration/filtering of detected Changes Looks good, thanks again Peter van Zetten for raising this, I'll work on that for next release, it should be easy enough to do. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196079.1544027495000.3934.1578407100155%40Atlassian.JIRA.
[JIRA] (JENKINS-55037) Allow configuration/filtering of detected Changes
Title: Message Title Peter van Zetten commented on JENKINS-55037 Re: Allow configuration/filtering of detected Changes The env vars are good enough for now - we can handle the WIP/Private state and omit stages or shortcut the entire build. A trait to completely prevent the build job creation would be even better! Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196079.1544027495000.3932.1578406980105%40Atlassian.JIRA.
[JIRA] (JENKINS-60536) Jenkins job hangs in Jira call after git rev-list command
Title: Message Title
David France edited a comment on JENKINS-60536
Re: Jenkins job hangs in Jira call after git rev-list command
We've being seeing much the same problem stack that Kieran reported, trying to progress issues by a workflow action in Jira. We first became aware of the problem on 20/12/2019:{noformat}"Executor #1 for master : executing deployToUAT #1619" #647 daemon prio=5 os_prio=0 cpu=436.80ms elapsed=236.46s tid=0x62b92000 nid=0x2590 waiting on condition [0x6644d000] java.lang.Thread.State: WAITING (parking)at jdk.internal.misc.Unsafe.park(java.base@11.0.5/Native Method)- parking to wait for <0x83d46f58> (a java.util.concurrent.locks.ReentrantLock$NonfairSync)at java.util.concurrent.locks.LockSupport.park(java.base@11.0.5/LockSupport.java:194)at java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(java.base@11.0.5/AbstractQueuedSynchronizer.java:885)at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireQueued(java.base@11.0.5/AbstractQueuedSynchronizer.java:917)at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquire(java.base@11.0.5/AbstractQueuedSynchronizer.java:1240)at java.util.concurrent.locks.ReentrantLock.lock(java.base@11.0.5/ReentrantLock.java:267)at org.apache.http.nio.pool.AbstractNIOConnPool.lease(AbstractNIOConnPool.java:278)at org.apache.http.impl.nio.conn.PoolingNHttpClientConnectionManager.requestConnection(PoolingNHttpClientConnectionManager.java:295)at org.apache.http.impl.nio.client.AbstractClientExchangeHandler.requestConnection(AbstractClientExchangeHandler.java:377)at org.apache.http.impl.nio.client.DefaultClientExchangeHandlerImpl.start(DefaultClientExchangeHandlerImpl.java:129)at org.apache.http.impl.nio.client.InternalHttpAsyncClient.execute(InternalHttpAsyncClient.java:141)at org.apache.http.impl.nio.client.CloseableHttpAsyncClient.execute(CloseableHttpAsyncClient.java:75)at org.apache.http.impl.nio.client.CloseableHttpAsyncClient.execute(CloseableHttpAsyncClient.java:108)at com.atlassian.httpclient.apache.httpcomponents.SettableFuturePromiseHttpPromiseAsyncClient.execute(SettableFuturePromiseHttpPromiseAsyncClient.java:36)at com.atlassian.httpclient.apache.httpcomponents.ApacheAsyncHttpClient.doExecute(ApacheAsyncHttpClient.java:417)at com.atlassian.httpclient.apache.httpcomponents.ApacheAsyncHttpClient.execute(ApacheAsyncHttpClient.java:364)at com.atlassian.httpclient.apache.httpcomponents.DefaultRequest$DefaultRequestBuilder.execute(DefaultRequest.java:297)at com.atlassian.jira.rest.client.internal.async.AtlassianHttpClientDecorator$AuthenticatedRequestBuilder.execute(AtlassianHttpClientDecorator.java:83)at com.atlassian.httpclient.apache.httpcomponents.DefaultRequest$DefaultRequestBuilder.get(DefaultRequest.java:253)at com.atlassian.jira.rest.client.internal.async.AbstractAsynchronousRestClient.getAndParse(AbstractAsynchronousRestClient.java:69)at com.atlassian.jira.rest.client.internal.async.AsynchronousSearchRestClient.searchJqlImplGet(AsynchronousSearchRestClient.java:109)at com.atlassian.jira.rest.client.internal.async.AsynchronousSearchRestClient.searchJql(AsynchronousSearchRestClient.java:94)at hudson.plugins.jira.JiraRestService.getIssuesFromJqlSearch(JiraRestService.java:196)at hudson.plugins.jira.JiraSession.getIssuesFromJqlSearch(JiraSession.java:136)at hudson.plugins.jira.JiraSite.progressMatchingIssues(JiraSite.java:1043)at
[JIRA] (JENKINS-60630) Git plugin fails to replace parametrized value in scm checkout instead it is taking parameter variable as it is
Title: Message Title Mahantesh Hoolikatti edited a comment on JENKINS-60630 Re: Git plugin fails to replace parametrized value in scm checkout instead it is taking parameter variable as it is I am not switching from one branch to another branch. I am using git webhook and reading the webhook parameters like Branch name and commitId. I wanted to use the parameters values in GitScm so I am assigning them to variables and then using in GitScm but the variables are not replacing with values. (Parameter expansion is not working) Please find the attached screenshot for reference !Screenshot 2020-01-07 at 7.07.17 PM.png|thumbnail! Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203864.1578048105000.3921.1578406080281%40Atlassian.JIRA.
[JIRA] (JENKINS-60536) Jenkins job hangs in Jira call after git rev-list command
Title: Message Title
David France edited a comment on JENKINS-60536
Re: Jenkins job hangs in Jira call after git rev-list command
We've being seeing much the same problem stack that Kieran reported, trying to progress issues by a workflow action in Jira. We first became aware of the problem on 20/12/2019:{noformat}"Executor #1 for master : executing deployToUAT #1619" #647 daemon prio=5 os_prio=0 cpu=436.80ms elapsed=236.46s tid=0x62b92000 nid=0x2590 waiting on condition [0x6644d000] java.lang.Thread.State: WAITING (parking)at jdk.internal.misc.Unsafe.park(java.base@11.0.5/Native Method)- parking to wait for <0x83d46f58> (a java.util.concurrent.locks.ReentrantLock$NonfairSync)at java.util.concurrent.locks.LockSupport.park(java.base@11.0.5/LockSupport.java:194)at java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(java.base@11.0.5/AbstractQueuedSynchronizer.java:885)at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireQueued(java.base@11.0.5/AbstractQueuedSynchronizer.java:917)at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquire(java.base@11.0.5/AbstractQueuedSynchronizer.java:1240)at java.util.concurrent.locks.ReentrantLock.lock(java.base@11.0.5/ReentrantLock.java:267)at org.apache.http.nio.pool.AbstractNIOConnPool.lease(AbstractNIOConnPool.java:278)at org.apache.http.impl.nio.conn.PoolingNHttpClientConnectionManager.requestConnection(PoolingNHttpClientConnectionManager.java:295)at org.apache.http.impl.nio.client.AbstractClientExchangeHandler.requestConnection(AbstractClientExchangeHandler.java:377)at org.apache.http.impl.nio.client.DefaultClientExchangeHandlerImpl.start(DefaultClientExchangeHandlerImpl.java:129)at org.apache.http.impl.nio.client.InternalHttpAsyncClient.execute(InternalHttpAsyncClient.java:141)at org.apache.http.impl.nio.client.CloseableHttpAsyncClient.execute(CloseableHttpAsyncClient.java:75)at org.apache.http.impl.nio.client.CloseableHttpAsyncClient.execute(CloseableHttpAsyncClient.java:108)at com.atlassian.httpclient.apache.httpcomponents.SettableFuturePromiseHttpPromiseAsyncClient.execute(SettableFuturePromiseHttpPromiseAsyncClient.java:36)at com.atlassian.httpclient.apache.httpcomponents.ApacheAsyncHttpClient.doExecute(ApacheAsyncHttpClient.java:417)at com.atlassian.httpclient.apache.httpcomponents.ApacheAsyncHttpClient.execute(ApacheAsyncHttpClient.java:364)at com.atlassian.httpclient.apache.httpcomponents.DefaultRequest$DefaultRequestBuilder.execute(DefaultRequest.java:297)at com.atlassian.jira.rest.client.internal.async.AtlassianHttpClientDecorator$AuthenticatedRequestBuilder.execute(AtlassianHttpClientDecorator.java:83)at com.atlassian.httpclient.apache.httpcomponents.DefaultRequest$DefaultRequestBuilder.get(DefaultRequest.java:253)at com.atlassian.jira.rest.client.internal.async.AbstractAsynchronousRestClient.getAndParse(AbstractAsynchronousRestClient.java:69)at com.atlassian.jira.rest.client.internal.async.AsynchronousSearchRestClient.searchJqlImplGet(AsynchronousSearchRestClient.java:109)at com.atlassian.jira.rest.client.internal.async.AsynchronousSearchRestClient.searchJql(AsynchronousSearchRestClient.java:94)at hudson.plugins.jira.JiraRestService.getIssuesFromJqlSearch(JiraRestService.java:196)at hudson.plugins.jira.JiraSession.getIssuesFromJqlSearch(JiraSession.java:136)at hudson.plugins.jira.JiraSite.progressMatchingIssues(JiraSite.java:1043)at
[JIRA] (JENKINS-60536) Jenkins job hangs in Jira call after git rev-list command
Title: Message Title
David France edited a comment on JENKINS-60536
Re: Jenkins job hangs in Jira call after git rev-list command
We've being seeing much the same problem stack that Kieran reported, trying to progress issues by a workflow action in Jira. We first became aware of the problem on 20/12/2019:{noformat}"Executor #1 for master : executing deployToUAT #1619" #647 daemon prio=5 os_prio=0 cpu=436.80ms elapsed=236.46s tid=0x62b92000 nid=0x2590 waiting on condition [0x6644d000] java.lang.Thread.State: WAITING (parking)at jdk.internal.misc.Unsafe.park(java.base@11.0.5/Native Method)- parking to wait for <0x83d46f58> (a java.util.concurrent.locks.ReentrantLock$NonfairSync)at java.util.concurrent.locks.LockSupport.park(java.base@11.0.5/LockSupport.java:194)at java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(java.base@11.0.5/AbstractQueuedSynchronizer.java:885)at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireQueued(java.base@11.0.5/AbstractQueuedSynchronizer.java:917)at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquire(java.base@11.0.5/AbstractQueuedSynchronizer.java:1240)at java.util.concurrent.locks.ReentrantLock.lock(java.base@11.0.5/ReentrantLock.java:267)at org.apache.http.nio.pool.AbstractNIOConnPool.lease(AbstractNIOConnPool.java:278)at org.apache.http.impl.nio.conn.PoolingNHttpClientConnectionManager.requestConnection(PoolingNHttpClientConnectionManager.java:295)at org.apache.http.impl.nio.client.AbstractClientExchangeHandler.requestConnection(AbstractClientExchangeHandler.java:377)at org.apache.http.impl.nio.client.DefaultClientExchangeHandlerImpl.start(DefaultClientExchangeHandlerImpl.java:129)at org.apache.http.impl.nio.client.InternalHttpAsyncClient.execute(InternalHttpAsyncClient.java:141)at org.apache.http.impl.nio.client.CloseableHttpAsyncClient.execute(CloseableHttpAsyncClient.java:75)at org.apache.http.impl.nio.client.CloseableHttpAsyncClient.execute(CloseableHttpAsyncClient.java:108)at com.atlassian.httpclient.apache.httpcomponents.SettableFuturePromiseHttpPromiseAsyncClient.execute(SettableFuturePromiseHttpPromiseAsyncClient.java:36)at com.atlassian.httpclient.apache.httpcomponents.ApacheAsyncHttpClient.doExecute(ApacheAsyncHttpClient.java:417)at com.atlassian.httpclient.apache.httpcomponents.ApacheAsyncHttpClient.execute(ApacheAsyncHttpClient.java:364)at com.atlassian.httpclient.apache.httpcomponents.DefaultRequest$DefaultRequestBuilder.execute(DefaultRequest.java:297)at com.atlassian.jira.rest.client.internal.async.AtlassianHttpClientDecorator$AuthenticatedRequestBuilder.execute(AtlassianHttpClientDecorator.java:83)at com.atlassian.httpclient.apache.httpcomponents.DefaultRequest$DefaultRequestBuilder.get(DefaultRequest.java:253)at com.atlassian.jira.rest.client.internal.async.AbstractAsynchronousRestClient.getAndParse(AbstractAsynchronousRestClient.java:69)at com.atlassian.jira.rest.client.internal.async.AsynchronousSearchRestClient.searchJqlImplGet(AsynchronousSearchRestClient.java:109)at com.atlassian.jira.rest.client.internal.async.AsynchronousSearchRestClient.searchJql(AsynchronousSearchRestClient.java:94)at hudson.plugins.jira.JiraRestService.getIssuesFromJqlSearch(JiraRestService.java:196)at hudson.plugins.jira.JiraSession.getIssuesFromJqlSearch(JiraSession.java:136)at hudson.plugins.jira.JiraSite.progressMatchingIssues(JiraSite.java:1043)at
[JIRA] (JENKINS-60536) Jenkins job hangs in Jira call after git rev-list command
Title: Message Title
David France edited a comment on JENKINS-60536
Re: Jenkins job hangs in Jira call after git rev-list command
We've being seeing much the same problem stack that Kieran reported, trying to progress issues by a workflow action in Jira. We first became aware of the problem on 20/12/2019:{noformat}"Executor #1 for master : executing deployToUAT #1619" #647 daemon prio=5 os_prio=0 cpu=436.80ms elapsed=236.46s tid=0x62b92000 nid=0x2590 waiting on condition [0x6644d000] java.lang.Thread.State: WAITING (parking)at jdk.internal.misc.Unsafe.park(java.base@11.0.5/Native Method)- parking to wait for <0x83d46f58> (a java.util.concurrent.locks.ReentrantLock$NonfairSync)at java.util.concurrent.locks.LockSupport.park(java.base@11.0.5/LockSupport.java:194)at java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(java.base@11.0.5/AbstractQueuedSynchronizer.java:885)at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireQueued(java.base@11.0.5/AbstractQueuedSynchronizer.java:917)at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquire(java.base@11.0.5/AbstractQueuedSynchronizer.java:1240)at java.util.concurrent.locks.ReentrantLock.lock(java.base@11.0.5/ReentrantLock.java:267)at org.apache.http.nio.pool.AbstractNIOConnPool.lease(AbstractNIOConnPool.java:278)at org.apache.http.impl.nio.conn.PoolingNHttpClientConnectionManager.requestConnection(PoolingNHttpClientConnectionManager.java:295)at org.apache.http.impl.nio.client.AbstractClientExchangeHandler.requestConnection(AbstractClientExchangeHandler.java:377)at org.apache.http.impl.nio.client.DefaultClientExchangeHandlerImpl.start(DefaultClientExchangeHandlerImpl.java:129)at org.apache.http.impl.nio.client.InternalHttpAsyncClient.execute(InternalHttpAsyncClient.java:141)at org.apache.http.impl.nio.client.CloseableHttpAsyncClient.execute(CloseableHttpAsyncClient.java:75)at org.apache.http.impl.nio.client.CloseableHttpAsyncClient.execute(CloseableHttpAsyncClient.java:108)at com.atlassian.httpclient.apache.httpcomponents.SettableFuturePromiseHttpPromiseAsyncClient.execute(SettableFuturePromiseHttpPromiseAsyncClient.java:36)at com.atlassian.httpclient.apache.httpcomponents.ApacheAsyncHttpClient.doExecute(ApacheAsyncHttpClient.java:417)at com.atlassian.httpclient.apache.httpcomponents.ApacheAsyncHttpClient.execute(ApacheAsyncHttpClient.java:364)at com.atlassian.httpclient.apache.httpcomponents.DefaultRequest$DefaultRequestBuilder.execute(DefaultRequest.java:297)at com.atlassian.jira.rest.client.internal.async.AtlassianHttpClientDecorator$AuthenticatedRequestBuilder.execute(AtlassianHttpClientDecorator.java:83)at com.atlassian.httpclient.apache.httpcomponents.DefaultRequest$DefaultRequestBuilder.get(DefaultRequest.java:253)at com.atlassian.jira.rest.client.internal.async.AbstractAsynchronousRestClient.getAndParse(AbstractAsynchronousRestClient.java:69)at com.atlassian.jira.rest.client.internal.async.AsynchronousSearchRestClient.searchJqlImplGet(AsynchronousSearchRestClient.java:109)at com.atlassian.jira.rest.client.internal.async.AsynchronousSearchRestClient.searchJql(AsynchronousSearchRestClient.java:94)at hudson.plugins.jira.JiraRestService.getIssuesFromJqlSearch(JiraRestService.java:196)at hudson.plugins.jira.JiraSession.getIssuesFromJqlSearch(JiraSession.java:136)at hudson.plugins.jira.JiraSite.progressMatchingIssues(JiraSite.java:1043)at
[JIRA] (JENKINS-37984) org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script
Title: Message Title Richard Olsson edited a comment on JENKINS-37984 Re: org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script Hi,My config & setup:- [Jenkins ver. 2.190.3- Declarative pipelines- Pipeline jobs with groovy pipeline script of 591 lines and 39 jobs to build are failing with "General error during class generation: Method code too large!" (Files with 396 lines are fine)|http://sw-jenkins-m.infinera.com/] I've a Job DSL logic in place reading configuration files to create "pipeline code" (+ jobs and so on...) that are stored in variables in the Job DSL groovy scripts. And they are then used when creating the Jenkins pipeline jobs.So, the pipeline code are created "on the fly" with Job DSL groovy scripts.In the repo I do have a pipeline code TEMPLATE file. So, read that into the Job DSL groovy code and then do some edit/replacing and store the final pipeline code in an internal variable. So, the pipeline code are only stored in groovy variables, not in any file. So, they can not be handled as static files. This infrastructure works very well in other pipeline setups with less number of Jenkins jobs and pipeline code lines. This issue came as a surprise for me when creating this new setup with bigger pipelines. :-| h3. What to do? I've seen references to [https://jenkins.io/doc/book/pipeline/shared-libraries/#defining-declarative-pipelines].But I doubt that I can update any code in files in the shared libraries from Job DSL groovy code...?Anyone, have any suggestion, or is the only way to split into more pipeline jobs and pipeline code files?I don't want to make any big changes to the Job DSL logic that's already in place and works fine for other smaller setups! Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-37984) org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script
Title: Message Title Richard Olsson commented on JENKINS-37984 Re: org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script Hi, My config & setup: - [Jenkins ver. 2.190.3 Declarative pipelines Pipeline jobs with groovy pipeline script of 591 lines and 39 jobs to build are failing with "General error during class generation: Method code too large!" (Files with 396 lines are fine)|http://sw-jenkins-m.infinera.com/] I've a Job DSL logic in place reading configuration files to create "pipeline code" (+ jobs and so on...) that are stored in variables in the Job DSL groovy scripts. And they are then used when creating the Jenkins pipeline jobs. So, the pipeline code are created "on the fly" with Job DSL groovy scripts. In the repo I do have a pipeline code TEMPLATE file. So, read that into the Job DSL groovy code and then do some edit/replacing and store the final pipeline code in an internal variable. So, the pipeline code are only stored in groovy variables, not in any file. So, they can not be handled as static files. This infrastructure works very well in other pipeline setups with less number of Jenkins jobs and pipeline code lines. This issue came as a surprise for me when creating this new setup with bigger pipelines. :-| I've seen references to https://jenkins.io/doc/book/pipeline/shared-libraries/#defining-declarative-pipelines. But I doubt that I can update any code in files in the shared libraries from Job DSL groovy code...? Anyone, have any suggestion, or is the only way to split into more pipeline jobs and pipeline code files? I don't want to make any big changes to the Job DSL logic that's already in place and works fine for other smaller setups! Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-60676) withDockerContainer Stop and delete containers after body execution
Title: Message Title Abdou KEITA commented on JENKINS-60676 Re: withDockerContainer Stop and delete containers after body execution I will open a new PR then! And i will let you review it! Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203919.1578396581000.3743.1578405180139%40Atlassian.JIRA.
[JIRA] (JENKINS-60536) Jenkins job hangs in Jira call after git rev-list command
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-60536 Jenkins job hangs in Jira call after git rev-list command Change By: Mark Waite Summary: Jenkins job hangs in Jira call after git rev-list command Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203639.1576745651000.3736.1578404760320%40Atlassian.JIRA.
[JIRA] (JENKINS-60676) withDockerContainer Stop and delete containers after body execution
Title: Message Title Abdou KEITA updated JENKINS-60676 Jenkins / JENKINS-60676 withDockerContainer Stop and delete containers after body execution Change By: Abdou KEITA Resolution: Won't Do Status: Resolved In Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203919.1578396581000.3734.1578404520432%40Atlassian.JIRA.
[JIRA] (JENKINS-60676) withDockerContainer Stop and delete containers after body execution
Title: Message Title Abdou KEITA updated an issue Jenkins / JENKINS-60676 withDockerContainer Stop and delete containers after body execution Change By: Abdou KEITA Hello Jesse, withDockerContainer stop stops containers and delete deletes them after the end of the block .Could you have a look on how to make it optional? Thank you in advance! -- Abdou -- Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203919.1578396581000.3732.1578404520399%40Atlassian.JIRA.
[JIRA] (JENKINS-60630) Git plugin fails to replace parametrized value in scm checkout instead it is taking parameter variable as it is
Title: Message Title Mahantesh Hoolikatti edited a comment on JENKINS-60630 Re: Git plugin fails to replace parametrized value in scm checkout instead it is taking parameter variable as it is I am not switching from one branch to another branch. I am using git webhook and reading the webhook parameters like Branch name and commitId. I wanted to use the parameters values in GitScm so I am assigning them to variables and then using in GitScm but the variables are not replacing with values. Please find the attached screenshot for reference !Screenshot 2020-01-07 at 7.07.17 PM.png|thumbnail! Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203864.1578048105000.3727.1578404400164%40Atlassian.JIRA.
[JIRA] (JENKINS-60630) Git plugin fails to replace parametrized value in scm checkout instead it is taking parameter variable as it is
Title: Message Title Mahantesh Hoolikatti updated an issue Jenkins / JENKINS-60630 Git plugin fails to replace parametrized value in scm checkout instead it is taking parameter variable as it is Change By: Mahantesh Hoolikatti Attachment: Screenshot 2020-01-07 at 7.07.17 PM.png Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203864.1578048105000.3725.1578404340253%40Atlassian.JIRA.
[JIRA] (JENKINS-60630) Git plugin fails to replace parametrized value in scm checkout instead it is taking parameter variable as it is
Title: Message Title Mahantesh Hoolikatti commented on JENKINS-60630 Re: Git plugin fails to replace parametrized value in scm checkout instead it is taking parameter variable as it is I am not switching from one branch to another branch. I am using git webhook and reading the webhook parameters like Branch name and commitId. I wanted to use the parameters values in GitScm so I am assigning them to variables and then using in GitScm but the variables are not replacing with values. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203864.1578048105000.3723.1578404280119%40Atlassian.JIRA.
[JIRA] (JENKINS-60536) Jenkins job hangs after git rev-list command
Title: Message Title
David France edited a comment on JENKINS-60536
Re: Jenkins job hangs after git rev-list command
We've being seeing much the same problem stack that Kieran reported, trying to progress issues by a workflow action in Jira. We first became aware of the problem on 20/12/2019:{noformat}"Executor #1 for master : executing deployToUAT #1619" #647 daemon prio=5 os_prio=0 cpu=436.80ms elapsed=236.46s tid=0x62b92000 nid=0x2590 waiting on condition [0x6644d000] java.lang.Thread.State: WAITING (parking)at jdk.internal.misc.Unsafe.park(java.base@11.0.5/Native Method)- parking to wait for <0x83d46f58> (a java.util.concurrent.locks.ReentrantLock$NonfairSync)at java.util.concurrent.locks.LockSupport.park(java.base@11.0.5/LockSupport.java:194)at java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(java.base@11.0.5/AbstractQueuedSynchronizer.java:885)at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireQueued(java.base@11.0.5/AbstractQueuedSynchronizer.java:917)at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquire(java.base@11.0.5/AbstractQueuedSynchronizer.java:1240)at java.util.concurrent.locks.ReentrantLock.lock(java.base@11.0.5/ReentrantLock.java:267)at org.apache.http.nio.pool.AbstractNIOConnPool.lease(AbstractNIOConnPool.java:278)at org.apache.http.impl.nio.conn.PoolingNHttpClientConnectionManager.requestConnection(PoolingNHttpClientConnectionManager.java:295)at org.apache.http.impl.nio.client.AbstractClientExchangeHandler.requestConnection(AbstractClientExchangeHandler.java:377)at org.apache.http.impl.nio.client.DefaultClientExchangeHandlerImpl.start(DefaultClientExchangeHandlerImpl.java:129)at org.apache.http.impl.nio.client.InternalHttpAsyncClient.execute(InternalHttpAsyncClient.java:141)at org.apache.http.impl.nio.client.CloseableHttpAsyncClient.execute(CloseableHttpAsyncClient.java:75)at org.apache.http.impl.nio.client.CloseableHttpAsyncClient.execute(CloseableHttpAsyncClient.java:108)at com.atlassian.httpclient.apache.httpcomponents.SettableFuturePromiseHttpPromiseAsyncClient.execute(SettableFuturePromiseHttpPromiseAsyncClient.java:36)at com.atlassian.httpclient.apache.httpcomponents.ApacheAsyncHttpClient.doExecute(ApacheAsyncHttpClient.java:417)at com.atlassian.httpclient.apache.httpcomponents.ApacheAsyncHttpClient.execute(ApacheAsyncHttpClient.java:364)at com.atlassian.httpclient.apache.httpcomponents.DefaultRequest$DefaultRequestBuilder.execute(DefaultRequest.java:297)at com.atlassian.jira.rest.client.internal.async.AtlassianHttpClientDecorator$AuthenticatedRequestBuilder.execute(AtlassianHttpClientDecorator.java:83)at com.atlassian.httpclient.apache.httpcomponents.DefaultRequest$DefaultRequestBuilder.get(DefaultRequest.java:253)at com.atlassian.jira.rest.client.internal.async.AbstractAsynchronousRestClient.getAndParse(AbstractAsynchronousRestClient.java:69)at com.atlassian.jira.rest.client.internal.async.AsynchronousSearchRestClient.searchJqlImplGet(AsynchronousSearchRestClient.java:109)at com.atlassian.jira.rest.client.internal.async.AsynchronousSearchRestClient.searchJql(AsynchronousSearchRestClient.java:94)at hudson.plugins.jira.JiraRestService.getIssuesFromJqlSearch(JiraRestService.java:196)at hudson.plugins.jira.JiraSession.getIssuesFromJqlSearch(JiraSession.java:136)at hudson.plugins.jira.JiraSite.progressMatchingIssues(JiraSite.java:1043)at
[JIRA] (JENKINS-60676) withDockerContainer Stop and delete containers after body execution
Title: Message Title Jesse Glick resolved as Won't Do If you want specialized behavior, simply do not use this plugin—use for example sh 'docker run whatever' Jenkins / JENKINS-60676 withDockerContainer Stop and delete containers after body execution Change By: Jesse Glick Status: Open Resolved Resolution: Won't Do Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-60536) Jenkins job hangs after git rev-list command
Title: Message Title David France commented on JENKINS-60536 Re: Jenkins job hangs after git rev-list command We've being seeing much the same problem stack that Kieran reported, trying to progress issues by a workflow action in Jira. We first became aware of the problem on 20/12/2019: "Executor #1 for master : executing deployToUAT #1619" #647 daemon prio=5 os_prio=0 cpu=436.80ms elapsed=236.46s tid=0x6 2b92000 nid=0x2590 waiting on condition [0x6644d000] java.lang.Thread.State: WAITING (parking) at jdk.internal.misc.Unsafe.park(java.base@11.0.5/Native Method) - parking to wait for <0x83d46f58> (a java.util.concurrent.locks.ReentrantLock$NonfairSync) at java.util.concurrent.locks.LockSupport.park(java.base@11.0.5/LockSupport.java:194) at java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(java.base@11.0.5/AbstractQueuedSynchronizer.j ava:885) at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireQueued(java.base@11.0.5/AbstractQueuedSynchronizer.java:917)at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquire(java.base@11.0.5/AbstractQueuedSynchronizer.java:1240) at java.util.concurrent.locks.ReentrantLock.lock(java.base@11.0.5/ReentrantLock.java:267) at org.apache.http.nio.pool.AbstractNIOConnPool.lease(AbstractNIOConnPool.java:278) at org.apache.http.impl.nio.conn.PoolingNHttpClientConnectionManager.requestConnection(PoolingNHttpClientConnectionManager.j ava:295) at org.apache.http.impl.nio.client.AbstractClientExchangeHandler.requestConnection(AbstractClientExchangeHandler.java:377) at org.apache.http.impl.nio.client.DefaultClientExchangeHandlerImpl.start(DefaultClientExchangeHandlerImpl.java:129) at org.apache.http.impl.nio.client.InternalHttpAsyncClient.execute(InternalHttpAsyncClient.java:141) at org.apache.http.impl.nio.client.CloseableHttpAsyncClient.execute(CloseableHttpAsyncClient.java:75) at org.apache.http.impl.nio.client.CloseableHttpAsyncClient.execute(CloseableHttpAsyncClient.java:108) at com.atlassian.httpclient.apache.httpcomponents.SettableFuturePromiseHttpPromiseAsyncClient.execute(SettableFuturePromiseH ttpPromiseAsyncClient.java:36) at com.atlassian.httpclient.apache.httpcomponents.ApacheAsyncHttpClient.doExecute(ApacheAsyncHttpClient.java:417) at com.atlassian.httpclient.apache.httpcomponents.ApacheAsyncHttpClient.execute(ApacheAsyncHttpClient.java:364) at com.atlassian.httpclient.apache.httpcomponents.DefaultRequest$DefaultRequestBuilder.execute(DefaultRequest.java:297) at com.atlassian.jira.rest.client.internal.async.AtlassianHttpClientDecorator$AuthenticatedRequestBuilder.execute(AtlassianH ttpClientDecorator.java:83) at com.atlassian.httpclient.apache.httpcomponents.DefaultRequest$DefaultRequestBuilder.get(DefaultRequest.java:253) at com.atlassian.jira.rest.client.internal.async.AbstractAsynchronousRestClient.getAndParse(AbstractAsynchronousRestClient.j ava:69) at com.atlassian.jira.rest.client.internal.async.AsynchronousSearchRestClient.searchJqlImplGet(AsynchronousSearchRestClient. java:109) at com.atlassian.jira.rest.client.internal.async.AsynchronousSearchRestClient.searchJql(AsynchronousSearchRestClient.java:94 ) at hudson.plugins.jira.JiraRestService.getIssuesFromJqlSearch(JiraRestService.java:196) at
[JIRA] (JENKINS-60676) withDockerContainer Stop and delete containers after body execution
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-60676 withDockerContainer Stop and delete containers after body execution Change By: Jesse Glick Component/s: docker-plugin Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203919.1578396581000.3670.1578403561121%40Atlassian.JIRA.
[JIRA] (JENKINS-60652) plugin breaks jenkins without a connection to AWS
Title: Message Title Dominik Bartholdi commented on JENKINS-60652 Re: plugin breaks jenkins without a connection to AWS maybe its worth breaking this issue up into multiple, meaning: fix the low hanging fruits. After all, I think a plugin should never make jenkins unusable just because it is installed but not configured and not used. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203894.157833410.3633.1578400260248%40Atlassian.JIRA.
[JIRA] (JENKINS-60330) EC2 number of instances capped at 1 even though Instance Cap is greater
Title: Message Title George Cimpoies updated JENKINS-60330 Jenkins / JENKINS-60330 EC2 number of instances capped at 1 even though Instance Cap is greater Change By: George Cimpoies Status: Fixed but Unreleased Resolved Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203341.1575031121000.3631.1578399060586%40Atlassian.JIRA.
[JIRA] (JENKINS-60330) EC2 number of instances capped at 1 even though Instance Cap is greater
Title: Message Title George Cimpoies updated JENKINS-60330 Although AMI instance cap was set to 10, global instance cap was set to 1 Jenkins / JENKINS-60330 EC2 number of instances capped at 1 even though Instance Cap is greater Change By: George Cimpoies Status: Open Fixed but Unreleased Assignee: FABRIZIO MANFREDI George Cimpoies Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-60676) withDockerContainer Stop and delete containers after body execution
Title: Message Title Abdou KEITA created an issue Jenkins / JENKINS-60676 withDockerContainer Stop and delete containers after body execution Issue Type: New Feature Assignee: Jesse Glick Components: docker-plugin, docker-workflow-plugin Created: 2020-01-07 11:29 Priority: Minor Reporter: Abdou KEITA Hello Jesse, withDockerContainer stop containers and delete them. Could you have a look on how to make it optional? Thank you in advance! -Abdou- Add Comment This message was sent by
[JIRA] (JENKINS-60676) withDockerContainer Stop and delete containers after body execution
Title: Message Title Abdou KEITA updated an issue Jenkins / JENKINS-60676 withDockerContainer Stop and delete containers after body execution Change By: Abdou KEITA Priority: Minor Major Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203919.1578396581000.3619.1578396601361%40Atlassian.JIRA.
[JIRA] (JENKINS-51550) docker.image.inside run after why do delete the container , which make me can not to deploy to a docker container
Title: Message Title Abdou KEITA commented on JENKINS-51550 Re: docker.image.inside run after why do delete the container , which make me can not to deploy to a docker container Hello, How could we redefine withDockerContainer to add new options to not stop and not remove containers ? Thank you in advance ! -Abdou- Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.190936.1527280701000.3610.1578395760130%40Atlassian.JIRA.
[JIRA] (JENKINS-60675) An automated ant build called from Jenkins fails
Title: Message Title Karl Wirth commented on JENKINS-60675 Re: An automated ant build called from Jenkins fails Hi Peeush Trikha - From the console log I cannot see what is not working. Can you add extra debugging to the script to show where it is failing. Is it possible that you are expecting variables to be present that are not? For example maybe add 'p4 set' to the script to display what P4PORT, P4USER and P4CLIENT are in use. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203918.1578391928000.3602.1578395640238%40Atlassian.JIRA.
[JIRA] (JENKINS-60652) plugin breaks jenkins without a connection to AWS
Title: Message Title Dominik Bartholdi commented on JENKINS-60652 Re: plugin breaks jenkins without a connection to AWS Thanks for the info - I have my setup similar to yours (with CloudFormation, JasC), but until now, the Jenkins Docker Image I create also used to work on my local env (my mac) - but now this unfortunately is not the case anymore and its harder to do some first local testing of the image. The most important part for me right now is your first part "Listing credentials" - this effectively hinders my workflow right now. I don't know the internals of the credential providers, but from a users point of view: I have a job configured e.g. a pipeline and the only thing to reference credentials are by a string-id. For me as a pipeline admin, I don't care which provider actually holds the credentials. If it is not found by any of the providers, it should throw an exception. So there is no way for me to say that I want this credentials retrieved rather from AWS and not from the internal jenkins provider. Saying this, I don't understand why a provider should throw an exception if it can't resolve credentials for a given ID (unless the credentials framework swallows the exceptions and interprets it as a "NotFound" to hand over to the next provider installed until one can resolve it). Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit
[JIRA] (JENKINS-6659) Record a change message along with the job change history
Title: Message Title Robin Schulz updated an issue Jenkins / JENKINS-6659 Record a change message along with the job change history Change By: Robin Schulz Attachment: image-2020-01-07-12-06-44-451.png Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.136754.1275075929000.3581.1578395220748%40Atlassian.JIRA.
[JIRA] (JENKINS-60652) plugin breaks jenkins without a connection to AWS
Title: Message Title Chris Kilding commented on JENKINS-60652 Re: plugin breaks jenkins without a connection to AWS This will take time to work out, so in the meantime if you're wondering how we make this work at our place... We manage our AWS accounts almost entirely with Terraform We use either immutable infrastructure tools (AMI builders, Docker etc plus Jenkins Configuration As Code) or configuration management tools (Puppet etc) to provision servers, so while we try to support manual plugin configuration through the Global Configuration Web UI, it's not a code path we actively use ourselves. We have non-production AWS accounts where we can test all infrastructure changes before rolling them out to production. This combination of things probably meant we were able to catch misconfiguration bugs in the credential provider before the bugs ever got near our production Jenkins. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203894.157833410.3573.1578395040122%40Atlassian.JIRA.
