[JIRA] (JENKINS-59457) all pipeline job failed after upgrade security script plugin
Title: Message Title Dennis Tran created an issue Jenkins / JENKINS-59457 all pipeline job failed after upgrade security script plugin Issue Type: Bug Assignee: Andrew Bayer Components: script-security-plugin Created: 2019-09-20 05:02 Environment: Jenkins in Ubuntu version 2.164.2 Script security plugin 1.64 Priority: Minor Reporter: Dennis Tran After upgrading secript security plugin from version 1.57 to 1.64, all my pipeline jobs have been failed with some error: org.jenkinsci.plugins.workflow.steps.MissingContextVariableException: Required context class hudson.FilePath is missingorg.jenkinsci.plugins.workflow.steps.MissingContextVariableException: Required context class hudson.FilePath is missingPerhaps you forgot to surround the code with a step that provides this, such as: node, dockerNode at org.jenkinsci.plugins.workflow.steps.StepDescriptor.checkContextAvailability(StepDescriptor.java:266) or Groovy.lang.MissingPropertyException: No such property: buildUser for class: WorkflowScriptGroovy.lang.MissingPropertyException: No such property: buildUser for class: WorkflowScript at org.codehaus.groovy.runtime.ScriptBytecodeAdapter.unwrap(ScriptBytecodeAdapter.java:53) at org.codehaus.groovy.runtime.ScriptBytecodeAdapter.getProperty(ScriptBytecodeAdapter.java:458) at
[JIRA] (JENKINS-59456) Parameterized Remote Trigger Plugin Invalid character found in the request target, Square Brackets need encoding
Title: Message Title Gary Yao created an issue Jenkins / JENKINS-59456 Parameterized Remote Trigger Plugin Invalid character found in the request target, Square Brackets need encoding Issue Type: Bug Assignee: KaiHsiang Chang Components: parameterized-remote-trigger-plugin Created: 2019-09-20 04:44 Environment: Jenkins ver. 2.176.3 Plugin Parameterized-Remote-Trigger:3.0.9 Priority: Minor Reporter: Gary Yao A good explanation found in https://programmer.help/blogs/characters-are-defined-in-rfc-7230-and-rfc-3986.html Our remote Jenkins runs inside Tomcat, after Tomcat upgraded, Jobs can not be triggerred remotely anymore. We used a hacky workaround which temporarily solved this issue by simply replace [ with %5B and ] with %5D in remoteJobUrl in src/main/java/org/jenkinsci/plugins/ParameterizedRemoteTrigger/RemoteBuildConfiguration.java Add Comment
[JIRA] (JENKINS-59455) CheckFilterTest failing on environment.txt
Title: Message Title Allan BURDAJEWICZ commented on JENKINS-59455 Re: CheckFilterTest failing on environment.txt I have noticed that: 1) Environment Variables is actually not using a filtered content: https://github.com/jenkinsci/support-core-plugin/blob/support-core-2.61/src/main/java/com/cloudbees/jenkins/support/impl/EnvironmentVariables.java#L54-L85 2) Environment Variable component is using a cache: https://github.com/jenkinsci/support-core-plugin/blob/support-core-2.61/src/main/java/com/cloudbees/jenkins/support/impl/EnvironmentVariables.java#L87-L90 It is my understanding that this test relies on the Environment Variables content to be filtered ? When I use a PrefilteredContent instead of the a PrintedContent and filter the entire line, it fix the text for me locally. Removing the cache however has no effect. Maybe Ramon Leon knows what is going on ? 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.202048.1568948997000.1476.1568949300067%40Atlassian.JIRA.
[JIRA] (JENKINS-59455) CheckFilterTest failing on environment.txt
Title: Message Title Allan BURDAJEWICZ assigned an issue to Allan BURDAJEWICZ Jenkins / JENKINS-59455 CheckFilterTest failing on environment.txt Change By: Allan BURDAJEWICZ Assignee: Emilio Escobar Allan BURDAJEWICZ Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202048.1568948997000.1474.1568949060336%40Atlassian.JIRA.
[JIRA] (JENKINS-59455) CheckFilterTest failing on environment.txt
Title: Message Title Allan BURDAJEWICZ assigned an issue to Unassigned Jenkins / JENKINS-59455 CheckFilterTest failing on environment.txt Change By: Allan BURDAJEWICZ Assignee: Allan BURDAJEWICZ Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202048.1568948997000.1475.1568949060353%40Atlassian.JIRA.
[JIRA] (JENKINS-59455) CheckFilterTest failing on environment.txt
Title: Message Title Allan BURDAJEWICZ created an issue Jenkins / JENKINS-59455 CheckFilterTest failing on environment.txt Issue Type: Bug Assignee: Emilio Escobar Components: support-core-plugin Created: 2019-09-20 03:09 Environment: support-core Priority: Major Reporter: Allan BURDAJEWICZ The CheckFilterTest is failing with the following issues: === Starting checkFilterTest(com.cloudbees.jenkins.support.CheckFilterTest) 0.067 [id=14] INFO o.jvnet.hudson.test.WarExploder#explode: Picking up existing exploded jenkins.war at /Users/allan/Projects/dohbedoh/jenkins-plugins/support-core-plugin/target/jenkins-for-test 0.388 [id=14] INFO o.jvnet.hudson.test.JenkinsRule#createWebServer: Running on http://localhost:54708/jenkins/ 1.934 [id=24] INFO jenkins.InitReactorRunner$1#onAttained: Started initialization 2.377 [id=35] WARNING hudson.ClassicPluginStrategy#createClassJarFromWebInfClasses: Created /var/folders/m7/lghwdpdx70d6454dsp825bxcgn/T/jenkins2715125141041055036/async-http-client/WEB-INF/lib/classes.jar; update plugin to a version created with a newer harness 3.017 [id=37] INFO jenkins.InitReactorRunner$1#onAttained: Listed all plugins 5.225 [id=30] INFO jenkins.InitReactorRunner$1#onAttained: Prepared all plugins 5.245 [id=31] INFO jenkins.InitReactorRunner$1#onAttained: Started all plugins 5.248 [id=27] INFO jenkins.InitReactorRunner$1#onAttained: Augmented all extensions 6.204 [id=26] INFO jenkins.InitReactorRunner$1#onAttained: Loaded all jobs 6.417 [id=22] INFO jenkins.InitReactorRunner$1#onAttained: Completed initialization 6.436 [id=52]
[JIRA] (JENKINS-59454) Increase Advisor bundle generation delay to 30mins
Title: Message Title Owen Wood created an issue Jenkins / JENKINS-59454 Increase Advisor bundle generation delay to 30mins Issue Type: Task Assignee: Owen Wood Components: cloudbees-jenkins-advisor-plugin Created: 2019-09-20 01:36 Priority: Minor Reporter: Owen Wood To give the support-core plugin enough time to generate a bundle first. See also https://github.com/jenkinsci/support-core-plugin/pull/191 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-59308) Cobertura Code coverage all reports are showing in similar
Title: Message Title Amila Gunathilake updated an issue Jenkins / JENKINS-59308 Cobertura Code coverage all reports are showing in similar Change By: Amila Gunathilake Priority: Minor Blocker 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.201856.1568169015000.1462.1568941680287%40Atlassian.JIRA.
[JIRA] (JENKINS-59288) Not able to connect to RobotFramework-SikuliLibrary
Title: Message Title Anthony Le updated JENKINS-59288 XVFB was the solution. Sikuli requires a frame buffer to allow the connection. If you run a Jenkins build that involves Robot Framework with the Sikuli Library, then XVFB will resolve connection issues. Jenkins / JENKINS-59288 Not able to connect to RobotFramework-SikuliLibrary Change By: Anthony Le Status: Open Fixed but Unreleased Assignee: Jan Niklas Hasse Anthony Le Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-59453) Cleanup plugin dependencies / Move to BOM
Title: Message Title Owen Wood updated an issue Jenkins / JENKINS-59453 Cleanup plugin dependencies / Move to BOM Change By: Owen Wood We moved to using [ https://github.com/jenkinsci/bom ] as part of https://issues.jenkins-ci.org/browse/JENKINS-59320 We still have dependencies explicitly declaring versions, which could be managed by the BOM.This task is for cleaning up those dependencies. 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.202044.1568928952000.1452.1568929140206%40Atlassian.JIRA.
[JIRA] (JENKINS-59453) Cleanup plugin dependencies / Move to BOM
Title: Message Title Owen Wood created an issue Jenkins / JENKINS-59453 Cleanup plugin dependencies / Move to BOM Issue Type: Task Assignee: Owen Wood Components: support-core-plugin Created: 2019-09-19 21:35 Priority: Minor Reporter: Owen Wood We moved to using https://github.com/jenkinsci/bom as part of https://issues.jenkins-ci.org/browse/JENKINS-59320 We still have dependencies explicitly declaring versions, which could be managed by the BOM. This task is for cleaning up those dependencies. Add Comment
[JIRA] (JENKINS-56249) userContent *zip* (all files in zip) stopped working at 2.164
Title: Message Title Jeff Thompson commented on JENKINS-56249 Re: userContent *zip* (all files in zip) stopped working at 2.164 And which of those use cases involve userContent, as described in the OP? 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.197816.1550852223000.1444.1568928840198%40Atlassian.JIRA.
[JIRA] (JENKINS-59320) Support plugin should log all running jobs when bundle is generated
Title: Message Title Owen Wood updated JENKINS-59320 Will release as part of 2.62 Jenkins / JENKINS-59320 Support plugin should log all running jobs when bundle is generated Change By: Owen Wood Status: In Review Resolved Resolution: Done 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-59320) Support plugin should log all running jobs when bundle is generated
Title: Message Title Owen Wood edited a comment on JENKINS-59320 Re: Support plugin should log all running jobs when bundle is generated https://github.com/jenkinsci/support-core-plugin/pull/ 188 189 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.201871.1568228336000.1440.1568928660220%40Atlassian.JIRA.
[JIRA] (JENKINS-56249) userContent *zip* (all files in zip) stopped working at 2.164
Title: Message Title Jeff Thompson commented on JENKINS-56249 Re: userContent *zip* (all files in zip) stopped working at 2.164 Arjo Poldervaart, could you clarify some of your use cases for symlinks? How do you use them? Where do they link from and to? Do they link from inside a workspace to somewhere else on the system? Anyone else, please respond also, about your need for symlink support. I'm especially interested in how your symlink use works with zip files, as featured in the OP. Zip files generated by Jenkins do not contain symlinks but may resolve the symlink to the target and include all of that. One scenario, described in JENKINS-56114, involves a master or agent which resides in a path containing a symlink at the root or somewhere else higher in the path. 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.197816.1550852223000.1431.1568927340340%40Atlassian.JIRA.
[JIRA] (JENKINS-59452) Support JIRA sites that uses a personal certificate during authentication
Title: Message Title
Frank Refol updated an issue
Jenkins / JENKINS-59452
Support JIRA sites that uses a personal certificate during authentication
Change By:
Frank Refol
In our firms Jira instance, we have to use a personal certificate (PKCS#12) in order to open the page. After I am authenticated the page is shown where I can now interface with Jira such as logging into it with my regular username and password. Currently this is not possible using Jira plugin or any Jira plugin for that matter. The Jenkns server that I am using this on is a Windows machine. I've tried installing the personal certificate in that server in the service account that the Jenkins service is running as. I also tried adding the personal certificate in the JRE's certificate store (cacert). Albeit, I had to convert it first. I also tested that I can access Jira using the browser in the Jenkins server logged in as the Jenkins service account.In the Jenkins Configuration Jira plugin settings, when I try to validate the settings, I get the following exception stack (note I've obfuscated irrelevant text): { noformat quote } Caused by: org.apache.http.ProtocolException: Not a valid protocol version: You are not allowed to access this resource. For support please email: helpd...@sxx.com or call (xxx) xxx-Caused by: org.apache.http.ProtocolException: Not a valid protocol version: You are not allowed to access this resource. For support please email: helpd...@strozfriedberg.com or call (212) 981-2662 at org.apache.http.impl.nio.codecs.AbstractMessageParser.parse(AbstractMessageParser.java:209) at org.apache.http.impl.nio.DefaultNHttpClientConnection.consumeInput(DefaultNHttpClientConnection.java:245) at org.apache.http.impl.nio.client.InternalIODispatch.onInputReady(InternalIODispatch.java:81) at org.apache.http.impl.nio.client.InternalIODispatch.onInputReady(InternalIODispatch.java:39) at org.apache.http.impl.nio.reactor.AbstractIODispatch.inputReady(AbstractIODispatch.java:121) at org.apache.http.impl.nio.reactor.BaseIOReactor.readable(BaseIOReactor.java:162) at org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvent(AbstractIOReactor.java:337) at org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvents(AbstractIOReactor.java:315) at org.apache.http.impl.nio.reactor.AbstractIOReactor.execute(AbstractIOReactor.java:276) at org.apache.http.impl.nio.reactor.BaseIOReactor.execute(BaseIOReactor.java:104) at org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor$Worker.run(AbstractMultiworkerIOReactor.java:588) { noformat quote }
[JIRA] (JENKINS-59452) Support JIRA sites that uses a personal certificate during authentication
Title: Message Title
Frank Refol updated an issue
Jenkins / JENKINS-59452
Support JIRA sites that uses a personal certificate during authentication
Change By:
Frank Refol
In our firms Jira instance, we have to use a personal certificate (PKCS#12) in order to open the page. After I am authenticated the page is shown where I can now interface with Jira such as logging into it with my regular username and password. Currently this is not possible using Jira plugin or any Jira plugin for that matter. The Jenkns server that I am using this on is a Windows machine. I've tried installing the personal certificate in that server in the service account that the Jenkins service is running as. I also tried adding the personal certificate in the JRE's certificate store (cacert). Albeit, I had to convert it first. I also tested that I can access Jira using the browser in the Jenkins server logged in as the Jenkins service account.In the Jenkins Configuration Jira plugin settings, when I try to validate the settings, I get the following exception stack (note I've obfuscated irrelevant text): {quote}Caused by: org.apache.http.ProtocolException: Not a valid protocol version: You are not allowed to access this resource. For support please email: helpdesk xxx @ sxx xx .com or call (xxx) xxx- Caused Caused by: org.apache.http.ProtocolException: Not a valid protocol version: You are not allowed to access this resource. For support please email: helpdesk xxx @ strozfriedberg .com or call ( 212 xxx ) 981 xxx - 2662 at org.apache.http.impl.nio.codecs.AbstractMessageParser.parse(AbstractMessageParser.java:209) at org.apache.http.impl.nio.DefaultNHttpClientConnection.consumeInput(DefaultNHttpClientConnection.java:245) at org.apache.http.impl.nio.client.InternalIODispatch.onInputReady(InternalIODispatch.java:81) at org.apache.http.impl.nio.client.InternalIODispatch.onInputReady(InternalIODispatch.java:39) at org.apache.http.impl.nio.reactor.AbstractIODispatch.inputReady(AbstractIODispatch.java:121) at org.apache.http.impl.nio.reactor.BaseIOReactor.readable(BaseIOReactor.java:162) at org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvent(AbstractIOReactor.java:337) at org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvents(AbstractIOReactor.java:315) at org.apache.http.impl.nio.reactor.AbstractIOReactor.execute(AbstractIOReactor.java:276) at org.apache.http.impl.nio.reactor.BaseIOReactor.execute(BaseIOReactor.java:104) at org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor$Worker.run(AbstractMultiworkerIOReactor.java:588){quote}
[JIRA] (JENKINS-59452) Support JIRA sites that uses a personal certificate during authentication
Title: Message Title
Frank Refol updated an issue
Jenkins / JENKINS-59452
Support JIRA sites that uses a personal certificate during authentication
Change By:
Frank Refol
Component/s:
jira-steps-plugin
In our firms Jira instance, we have to use a personal certificate (PKCS#12) in order to open the page. After I am authenticated the page is shown where I can now interface with Jira such as logging into it with my regular username and password. Currently this is not possible using Jira plugin or any Jira plugin for that matter. The Jenkns server that I am using this on is a Windows machine. I've tried installing the personal certificate in that server in the service account that the Jenkins service is running as. I also tried adding the personal certificate in the JRE's certificate store (cacert). Albeit, I had to convert it first. I also tested that I can access Jira using the browser in the Jenkins server logged in as the Jenkins service account. In the Jenkins Configuration Jira plugin settings, when I try to validate the settings, I get the following exception stack (note I've obfuscated irrelevant text):{noformat}Caused by: org.apache.http.ProtocolException: Not a valid protocol version: You are not allowed to access this resource. For support please email: helpd...@sxx.com or call (xxx) xxx-Caused by: org.apache.http.ProtocolException: Not a valid protocol version: You are not allowed to access this resource. For support please email: helpd...@strozfriedberg.com or call (212) 981-2662 at org.apache.http.impl.nio.codecs.AbstractMessageParser.parse(AbstractMessageParser.java:209) at org.apache.http.impl.nio.DefaultNHttpClientConnection.consumeInput(DefaultNHttpClientConnection.java:245) at org.apache.http.impl.nio.client.InternalIODispatch.onInputReady(InternalIODispatch.java:81) at org.apache.http.impl.nio.client.InternalIODispatch.onInputReady(InternalIODispatch.java:39) at org.apache.http.impl.nio.reactor.AbstractIODispatch.inputReady(AbstractIODispatch.java:121) at org.apache.http.impl.nio.reactor.BaseIOReactor.readable(BaseIOReactor.java:162) at org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvent(AbstractIOReactor.java:337) at org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvents(AbstractIOReactor.java:315) at org.apache.http.impl.nio.reactor.AbstractIOReactor.execute(AbstractIOReactor.java:276) at org.apache.http.impl.nio.reactor.BaseIOReactor.execute(BaseIOReactor.java:104) at org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor$Worker.run(AbstractMultiworkerIOReactor.java:588) {noformat}
[JIRA] (JENKINS-59452) Support JIRA sites that uses a personal certificate during authentication
Title: Message Title Frank Refol created an issue Jenkins / JENKINS-59452 Support JIRA sites that uses a personal certificate during authentication Issue Type: Improvement Assignee: Dan Alvizu Components: jira-ext-plugin, jira-plugin, jira-trigger-plugin Created: 2019-09-19 20:23 Priority: Major Reporter: Frank Refol In our firms Jira instance, we have to use a personal certificate (PKCS#12) in order to open the page. After I am authenticated the page is shown where I can now interface with Jira such as logging into it with my regular username and password. Currently this is not possible using Jira plugin or any Jira plugin for that matter. The Jenkns server that I am using this on is a Windows machine. I've tried installing the personal certificate in that server in the service account that the Jenkins service is running as. I also tried adding the personal certificate in the JRE's certificate store (cacert). Albeit, I had to convert it first. I also tested that I can access Jira using the browser in the Jenkins server logged in as the Jenkins service account. Add Comment
[JIRA] (JENKINS-59204) NPE when trying to use claim plugin after upgrading to jenkins 2.191
Title: Message Title Kevin Werner commented on JENKINS-59204 Re: NPE when trying to use claim plugin after upgrading to jenkins 2.191 Hit this as well on 2.176.3. Downgraded to 1.20 (the downgrade version offered on the Plugins page) and things work again. 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.201470.1566815964000.1405.1568923740383%40Atlassian.JIRA.
[JIRA] (JENKINS-59451) Possibly unclosed file handlers in slave to master security admin whitelist rule and in agen standard output swapper
Title: Message Title Stefan Spieker created an issue Jenkins / JENKINS-59451 Possibly unclosed file handlers in slave to master security admin whitelist rule and in agen standard output swapper Issue Type: Bug Assignee: Stefan Spieker Components: core Created: 2019-09-19 19:51 Environment: jenkins 2.195 Priority: Minor Reporter: Stefan Spieker Possibly unclosed file handlers in slave to master security admin whitelist rule and in agen standard output swapper Add Comment
[JIRA] (JENKINS-59451) Possibly unclosed file handlers in slave to master security admin whitelist rule and in agen standard output swapper
Title: Message Title Stefan Spieker started work on JENKINS-59451 Change By: Stefan Spieker 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.202037.1568922668000.1401.1568922720276%40Atlassian.JIRA.
[JIRA] (JENKINS-54683) Pods entering error state due to ConnectionRefusalException: Unknown client name
Title: Message Title ipleten commented on JENKINS-54683 Re: Pods entering error state due to ConnectionRefusalException: Unknown client name We have exact the same problem. 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.195475.1542484359000.1388.1568922600332%40Atlassian.JIRA.
[JIRA] (JENKINS-58430) Publishing two fitnesse xml files with same test name confuses the results
Title: Message Title jaruzafa updated JENKINS-58430 Fixed on fitnesse-plugin 1.30 Jenkins / JENKINS-58430 Publishing two fitnesse xml files with same test name confuses the results Change By: jaruzafa 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.200559.1562773241000.1386.1568921340264%40Atlassian.JIRA.
[JIRA] (JENKINS-58923) Cannot browse result of tests when publishing several fitnesse result files on Windows
Title: Message Title jaruzafa updated JENKINS-58923 Fixed on fitnesse-plugin 1.30 Jenkins / JENKINS-58923 Cannot browse result of tests when publishing several fitnesse result files on Windows Change By: jaruzafa 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.201266.1565782125000.1384.1568921280171%40Atlassian.JIRA.
[JIRA] (JENKINS-58923) Cannot browse result of tests when publishing several fitnesse result files on Windows
Title: Message Title jaruzafa updated JENKINS-58923 Jenkins / JENKINS-58923 Cannot browse result of tests when publishing several fitnesse result files on Windows Change By: jaruzafa Status: In Progress Fixed but Unreleased 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.201266.1565782125000.1382.1568919660338%40Atlassian.JIRA.
[JIRA] (JENKINS-58923) Cannot browse result of tests when publishing several fitnesse result files on Windows
Title: Message Title jaruzafa started work on JENKINS-58923 Change By: jaruzafa 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.201266.1565782125000.1380.1568919660257%40Atlassian.JIRA.
[JIRA] (JENKINS-59145) After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI
Title: Message Title Jacek Kowalski commented on JENKINS-59145 Re: After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI The problem occurs when Jenkins switches from rendering configuration fields directly (in the source of /job/.../configure) to requesting them via AJAX (/$stapler/bound/.../render). I do not know what conditions must be met in order for this to happen (>160 plugins?). Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201579.156710687.1373.1568918820278%40Atlassian.JIRA.
[JIRA] (JENKINS-59450) Test cases are missing randomly in measurement "testcase_point" from jenkins builds
Title: Message Title vikash srivastava updated an issue Jenkins / JENKINS-59450 Test cases are missing randomly in measurement "testcase_point" from jenkins builds Change By: vikash srivastava Randomly see the entire suite test cases missing in test case point after a build. As you can see in the csv attached, the last build for this test case is #5760 , however the latest build that we ran in jenkin is #5986 for which others suits have data. 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.202036.1568915919000.1371.1568916240167%40Atlassian.JIRA.
[JIRA] (JENKINS-59450) Test cases are missing randomly in measurement "testcase_point" from jenkins builds
Title: Message Title vikash srivastava updated an issue Jenkins / JENKINS-59450 Test cases are missing randomly in measurement "testcase_point" from jenkins builds Change By: vikash srivastava Attachment: jenkinsbuildinfo_jenkinsbuildinfo.csv 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.202036.1568915919000.1369.1568916120140%40Atlassian.JIRA.
[JIRA] (JENKINS-59450) Test cases are missing randomly in measurement "testcase_point" from jenkins builds
Title: Message Title vikash srivastava updated an issue Jenkins / JENKINS-59450 Test cases are missing randomly in measurement "testcase_point" from jenkins builds Change By: vikash srivastava Randomly see the entire suite test cases missing in test case point after a 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.202036.1568915919000.1367.1568916060220%40Atlassian.JIRA.
[JIRA] (JENKINS-59450) Test cases are missing randomly in measurement "testcase_point" from jenkins builds
Title: Message Title vikash srivastava created an issue Jenkins / JENKINS-59450 Test cases are missing randomly in measurement "testcase_point" from jenkins builds Issue Type: Bug Assignee: Aleksi Simell Components: influxdb-plugin Created: 2019-09-19 17:58 Environment: influx db version:1.20 Jenkins ver. 2.156 Priority: Minor Reporter: vikash srivastava Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-54249) GitHub Commit Status Setter - Cannot retrieve Git metadata
Title: Message Title Mark Waite commented on JENKINS-54249 Re: GitHub Commit Status Setter - Cannot retrieve Git metadata If you have a publicly available plugin that explicitly depends on git plugin 4.0.0-rc (and not on earlier released versions), then the plugin maintainer needs to be notified that 4.0.0-rc is a dead and removed release. 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.194891.1540467307000.1299.1568907720876%40Atlassian.JIRA.
[JIRA] (JENKINS-54249) GitHub Commit Status Setter - Cannot retrieve Git metadata
Title: Message Title Alan Lee commented on JENKINS-54249 Re: GitHub Commit Status Setter - Cannot retrieve Git metadata Mark Waite Thanks for a comprehensive summary of the issue. I think what I need is the last paragraph. Will try it out. 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.194891.1540467307000.1251.1568906700639%40Atlassian.JIRA.
[JIRA] (JENKINS-59397) iOS upload timeout for large size of app
Title: Message Title david huang commented on JENKINS-59397 Re: iOS upload timeout for large size of app it worked. Creating an upload resource. Create upload resource successful. Uploading app to resource. Upload app to resource successful. Committing resource. Committing resource successful. Distributing resource. Distributing resource successful. 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.201954.1568661479000.1248.1568906280200%40Atlassian.JIRA.
[JIRA] (JENKINS-59449) ATH Test error plugins.GradlePluginTest.run_gradle_script_build_scan_link
Title: Message Title rsandell created an issue Jenkins / JENKINS-59449 ATH Test error plugins.GradlePluginTest.run_gradle_script_build_scan_link Issue Type: Bug Assignee: Stefan Wolf Components: gradle-plugin Created: 2019-09-19 15:06 Environment: ATH java-8-firefox-4 gradle-plugin 1.33 Jenkins 2.176.3 Priority: Major Reporter: rsandell Error Message Unable to locate By.partialLinkText: Gradle Build Scan in http://127.0.0.1:56288/job/deadly_height/1/ Stacktrace org.openqa.selenium.NoSuchElementException: Unable to locate By.partialLinkText: Gradle Build Scan in http://127.0.0.1:56288/job/deadly_height/1/ at org.jenkinsci.test.acceptance.po.CapybaraPortingLayerImpl.find(CapybaraPortingLayerImpl.java:203) at plugins.GradlePluginTest.run_gradle_script_build_scan_link(GradlePluginTest.java:137) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47) at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) at org.jenkinsci.test.acceptance.junit.WithPlugins$RuleImpl$1.evaluate(WithPlugins.java:164) at org.jenkinsci.test.acceptance.junit.Since$RuleImpl$1.evaluate(Since.java:49) at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55) at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55) at
[JIRA] (JENKINS-59448) Distinct jenkins userids for same AD user
Title: Message Title Jaguar Lakatos created an issue Jenkins / JENKINS-59448 Distinct jenkins userids for same AD user Issue Type: Bug Assignee: Félix Belzunce Arcos Components: active-directory-plugin Created: 2019-09-19 15:03 Environment: Jenkins version 2.195 Active directory plugin version 2.16 Priority: Minor Reporter: Jaguar Lakatos Jenkins creates distinct user ids for the same active directory user, based on login name format. Users can use either "domainName\userName" or "userName@domainName" format for authentication. Jenkins should check the identity before creates new user id for the same user with different login format. Add Comment
[JIRA] (JENKINS-59161) ERROR: 530 Authentication required
Title: Message Title
Andrii Petrenko edited a comment on JENKINS-59161
Re: ERROR: 530 Authentication required
[https://pastebin.com/sp2Rtm1g]Jira is breaking the output. and another one with startls enabled: [https://pastebin.com/uWQtWDBS]arguments: {noformat}--env JAVA_OPTS="-Xmx4096m -Dmail.debug=true -Dmail.smtp.starttls.enable=true" {noformat}
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.201598.1567204978000.1233.1568905380268%40Atlassian.JIRA.
[JIRA] (JENKINS-59447) Bitbucket plugin is not triggering the job(s) when ssh and https have different hostnames
Title: Message Title
Torsten Reinhard updated an issue
Jenkins / JENKINS-59447
Bitbucket plugin is not triggering the job(s) when ssh and https have different hostnames
Change By:
Torsten Reinhard
+Bitbucket is not triggering matching jobs.+The log statements in Jenkins are showing this after pushing to ci-test.git Repo: {code:java}...Considering candidate job xx-freestyle-triggered-by-bitbucketSep 19, 2019 11:31:49 AM FINE com.cloudbees.jenkins.plugins.BitbucketJobProbeConsidering to poke xx-freestyle-triggered-by-bitbucketSep 19, 2019 11:31:49 AM FINE com.cloudbees.jenkins.plugins.BitbucketJobProberepo scheme: sshSep 19, 2019 11:31:49 AM FINE com.cloudbees.jenkins.plugins.BitbucketJobProbeTrying to match ssh://g...@git.mygroup.net:7999/scopecom/ci-test.git<-->https://atc.mygroup.net/scopecom/ci-test Sep 19, 2019 11:31:49 AM FINE com.cloudbees.jenkins.plugins.BitbucketJobProbexx-freestyle-triggered-by-bitbucket SCM doesnt match remote repo {1}Sep 19, 2019 11:31:49 AM FINE com.cloudbees.jenkins.plugins.BitbucketJobProbeConsidering candidate job xx-pipeline-triggered-by-bitbucketSep 19, 2019 11:31:49 AM FINE com.cloudbees.jenkins.plugins.BitbucketJobProbeConsidering to poke xx-pipeline-triggered-by-bitbucket...Sep 19, 2019 11:31:49 AM FINE com.cloudbees.jenkins.plugins.BitbucketJobProberepo scheme: sshSep 19, 2019 11:31:49 AM FINE com.cloudbees.jenkins.plugins.BitbucketJobProbeTrying to match ssh://g...@git.mygroup.net:7999/scopecom/ci-test.git<-->https://atc.mygroup.net/scopecom/ci-test Sep 19, 2019 11:31:49 AM FINE com.cloudbees.jenkins.plugins.BitbucketJobProbexx-pipeline-triggered-by-bitbucket SCM doesnt match remote repo {1}...{code}I´ve already merged https://github.com/jenkinsci/bitbucket-plugin/pull/59 - but I still have an issue caused by different hostnames. In our setup we have * ssh://git.mygroup.net:7999/../project/repo.git and * https://atc.mygroup.net/project/repo.gitThe final check is comparing the hostname(s) - and the project/repo paths. I dont know why they the Bitbucket team decided for different hostnames for the same thing - but I need an "official" solution to be able to use this plugin.One idea could be to add some global configuration, where hostname equivilents may be defined (in a map for example)So I would add there git.mygroup.net == atc.mygroup.net - and the Another idea would be to add a checkbox like "ignore hostname, compare project/repo only".The plugin will should consider this alternativeNames alternatives - and perform the comparison accordingly .
[JIRA] (JENKINS-26708) Deleting a Job does not fire the RunListener.onDeleted event for its Runs
Title: Message Title Zangdaarr Mortpartout commented on JENKINS-26708 Re: Deleting a Job does not fire the RunListener.onDeleted event for its Runs Hi guys, This bug is open this 2015 and is MAJOR, could you please work on 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.160382.1422620208000.1216.1568904300319%40Atlassian.JIRA.
[JIRA] (JENKINS-59161) ERROR: 530 Authentication required
Title: Message Title Andrii Petrenko commented on JENKINS-59161 Re: ERROR: 530 Authentication required https://pastebin.com/sp2Rtm1g Jira is breaking the output. 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.201598.1567204978000.1210.1568904180892%40Atlassian.JIRA.
[JIRA] (JENKINS-57328) Should not use secret name as credential ID
Title: Message Title
Ankur Patel commented on JENKINS-57328
Re: Should not use secret name as credential ID
For my case, I am using a Helm Chart to deploy Jenkins and its naming standard prefixes the secret names with the chart name. (ex: '{chartName}-{credname}'.) I've resolved to modify the secret template and use the name as written to get around this, so breaking convention to workaround it. Another issue is that, Kubernetes naming convention doesn't allow mixed-case names. So credential names are forced to follow the same convention. ("lower case alphanumeric characters, -, and .") Not a terrible issue, just forced to update all the pipelines. So this change would afford a good deal of flexibility.
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.199101.1557040941000.1213.1568904180926%40Atlassian.JIRA.
[JIRA] (JENKINS-59388) Broken formatting for Boolean parameters
Title: Message Title Igor Rondarev updated an issue Jenkins / JENKINS-59388 Broken formatting for Boolean parameters Change By: Igor Rondarev Starting from some Jenkins release in this year (cannot remember exactly, but seems that it first occured in winter/spring 2019), boolean parameters description title started to display not left-hand side (as it was before), but right to boolean check mark. It looks not quite logical, so i doubt it's feature and not a bug. It affects both Freestyle and Pipeline projects. 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.201944.1568631629000.1199.1568903160068%40Atlassian.JIRA.
[JIRA] (JENKINS-55787) Switch labels from entry to checkbox
Title: Message Title Igor Rondarev edited a comment on JENKINS-55787 Re: Switch labels from entry to checkbox Josh, i'm terrbily sorry, but don't you think that this decision is a bit premature? I agree with Adrian Adrien that currently all job parameters looks like a table that's easy to watch and use, and 'jumping' to the right side at boolean parameters is, to be honest, not very easy to read (also from the same UX point of view, we get empty gap at the left side where label originally was; i've even created a bug report (JENKINS-59388) and have rewritten several jobs in our organization from 'booleanParam' to 'choice' with 'true'/'false' values before i found this ticket). Probably it would be better to make it configurable or add another type (e.g. BooleanLabel) with UI you propose. 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.197176.1548453513000.1196.1568903040277%40Atlassian.JIRA.
[JIRA] (JENKINS-59388) Broken formatting for Boolean parameters
Title: Message Title Igor Rondarev updated an issue Jenkins / JENKINS-59388 Broken formatting for Boolean parameters Change By: Igor Rondarev Starting from some Jenkins release in this year (cannot remember exactly, but seems that it first occured in winter/spring 2019), boolean parameters description started to display nor not left-hand side (as it was before), but right to boolean check mark. It looks not quite logical, so i doubt it's feature and not a bug. It affects both Freestyle and Pipeline projects. 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.201944.1568631629000.1194.1568902620067%40Atlassian.JIRA.
[JIRA] (JENKINS-55787) Switch labels from entry to checkbox
Title: Message Title Igor Rondarev edited a comment on JENKINS-55787 Re: Switch labels from entry to checkbox Josh, i'm terrbily sorry, but don't you think that this decision is a bit premature? I agree with Adrian that currently all job parameters looks like a table that's easy to watch and use, and 'jumping' to the right side at boolean parameters is, to be honest, not very easy to read (also from the same UX point of view, we get empty gap at the left side where label originally was; i've even created a bug report (JENKINS-59388) and have rewritten several jobs in out our organization from 'booleanParam' to 'choice' with 'true'/'false' values before i found this ticket). Probably it would be better to make it configurable or add another type (e.g. BooleanLabel) with UI you propose. 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.197176.1548453513000.1191.1568901780272%40Atlassian.JIRA.
[JIRA] (JENKINS-59447) Bitbucket plugin is not triggering the job(s) when ssh and https have different hostnames
Title: Message Title
Torsten Reinhard created an issue
Jenkins / JENKINS-59447
Bitbucket plugin is not triggering the job(s) when ssh and https have different hostnames
Issue Type:
New Feature
Assignee:
Unassigned
Components:
bitbucket-plugin
Created:
2019-09-19 13:58
Environment:
Jenkins-2.176.3 Bitbucket Plugin 1.1.11 (latest) Bitbucket Server 5.8.2
Priority:
Minor
Reporter:
Torsten Reinhard
Bitbucket is not triggering matching jobs. The log statements in Jenkins are showing
...
Considering candidate job xx-freestyle-triggered-by-bitbucket
Sep 19, 2019 11:31:49 AM FINE com.cloudbees.jenkins.plugins.BitbucketJobProbeConsidering to poke xx-freestyle-triggered-by-bitbucket
Sep 19, 2019 11:31:49 AM FINE com.cloudbees.jenkins.plugins.BitbucketJobProberepo scheme: ssh
Sep 19, 2019 11:31:49 AM FINE com.cloudbees.jenkins.plugins.BitbucketJobProbeTrying to match ssh://g...@git.mygroup.net:7999/scopecom/ci-test.git<-->https://atc.mygroup.net/scopecom/ci-test
Sep 19, 2019 11:31:49 AM FINE com.cloudbees.jenkins.plugins.BitbucketJobProbexx-freestyle-triggered-by-bitbucket SCM doesnt match remote repo {1}
Sep 19, 2019 11:31:49 AM FINE com.cloudbees.jenkins.plugins.BitbucketJobProbeConsidering candidate job xx-pipeline-triggered-by-bitbucket
Sep 19, 2019 11:31:49 AM FINE com.cloudbees.jenkins.plugins.BitbucketJobProbeConsidering to poke xx-pipeline-triggered-by-bitbucket
...
Sep 19, 2019 11:31:49 AM FINE com.cloudbees.jenkins.plugins.BitbucketJobProberepo scheme: ssh
Sep 19, 2019 11:31:49 AM FINE com.cloudbees.jenkins.plugins.BitbucketJobProbeTrying to match
[JIRA] (JENKINS-55787) Switch labels from entry to checkbox
Title: Message Title Igor Rondarev edited a comment on JENKINS-55787 Re: Switch labels from entry to checkbox Josh, i'm terrbily sorry, but don't you think that this decision is a bit premature? I agree with Adrian that currently all job parameters looks like a table that's easy to watch and use, and 'jumping' to the right side at boolean parameters is, to be honest, not very convenient easy to read (also from the same UX point of view, we get empty gap at the left side where label originally was; i've even created a bug report (JENKINS-59388) and have rewritten several jobs in out organization from 'booleanParam' to 'choice' with 'true'/'false' values before i found this ticket). Probably it would be better to make it configurable or add another type (e.g. BooleanLabel) with UI you propose. 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.197176.1548453513000.1186.1568901420163%40Atlassian.JIRA.
[JIRA] (JENKINS-55787) Switch labels from entry to checkbox
Title: Message Title Igor Rondarev commented on JENKINS-55787 Re: Switch labels from entry to checkbox I've also read JENKINS-56109 story and in common i agree that these 'name'/'value' tables look a bit old-fashioned, and a gap between label and checkbox isn't good too (especially when it's large), but now we've got 'mix' of styles. 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.197176.1548453513000.1184.1568901360200%40Atlassian.JIRA.
[JIRA] (JENKINS-59336) Git plugin version 4.0.0-rc failed to load
Title: Message Title Mark Waite edited a comment on JENKINS-59336 Re: Git plugin version 4.0.0-rc failed to load The git client plugin 3.0.0-rc is a pre-release version of git client plugin 3.0.0. It was inadvertently released into the Jenkins community for about 10 days and was then removed from the Jenkins update center.The same mistake happened with git plugin 4.0.0-rc. Both are pre-release versions that were intended for test installations, not for production use. They were both removed from the update center about 10 days after they were released.You have a few choices to resolve the [security issue|https://jenkins.io/security/advisory/2019-09-12/] in git client plugin 3.0.0-rc.# Install git plugin 3.12.1 and git client plugin 2.8.5 from the Jenkins update center# Upload [git plugin 3.12.1|https:// repo updates .jenkins-ci.org/ releases download / org/jenkins-ci/ plugins/git/3.12.1/git -3 . 12.1. hpi] and [git client plugin 2.8. 5 6 |https:// repo updates .jenkins-ci.org/ releases download / org/jenkins-ci/ plugins/git-client/2.8. 5 6 /git-client -2 . 8.5. hpi] into your Jenkins server from the "*Advanced*" tab of the "*Manage Plugins*" page inside "*Manage Jenkins*" # Install git plugin 4.0.0-beta11 and git client plugin 3.0.0-beta11 from the [Jenkins experimental update center|https://jenkins.io/doc/developer/publishing/releasing-experimental-updates/#using-the-experimental-update-center]# Upload [git plugin 4.0.0-beta11|https://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/git/4.0.0-beta11/git-4.0.0-beta11.hpi] and [git client plugin 3.0.0-beta11|https://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/git-client/3.0.0-beta11/git-client-3.0.0-beta11.hpi] into your Jenkins server from the "*Advanced*" tab of the "*Manage Plugins*" page inside "*Manage Jenkins*" If you choose git plugin 3.12.1, you are choosing the released git plugin and the most stable.If you choose git plugin 4.0.0-beta11, you are choosing the most recent pre-release git plugin with more bug fixes than are available in git plugin 3.12.1. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-59446) Write technical guideline to write stable ATH
Title: Message Title Antonio Muñiz created an issue Jenkins / JENKINS-59446 Write technical guideline to write stable ATH Issue Type: Improvement Assignee: Antonio Muñiz Components: acceptance-test-harness Created: 2019-09-19 13:53 Priority: Major Reporter: Antonio Muñiz There are a few tips to write stable non-flaky ATH. Put those in a readme and review if the other thousand md files in the repo still make sense. Add Comment This message was sent by Atlassian Jira
[JIRA] (JENKINS-59388) Broken formatting for Boolean parameters
Title: Message Title Igor Rondarev edited a comment on JENKINS-59388 Re: Broken formatting for Boolean parameters Related to JENKINS- 56109 and JENKINS- 55787 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.201944.1568631629000.1177.1568901060063%40Atlassian.JIRA.
[JIRA] (JENKINS-59161) ERROR: 530 Authentication required
Title: Message Title Joe Tavin commented on JENKINS-59161 Re: ERROR: 530 Authentication required Resolved this by downgrading to v1.2.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.201598.1567204978000.1168.1568901000442%40Atlassian.JIRA.
[JIRA] (JENKINS-59388) Broken formatting for Boolean parameters
Title: Message Title Igor Rondarev commented on JENKINS-59388 Re: Broken formatting for Boolean parameters Related to JENKINS-55787 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.201944.1568631629000.1165.1568900580057%40Atlassian.JIRA.
[JIRA] (JENKINS-55787) Switch labels from entry to checkbox
Title: Message Title Igor Rondarev commented on JENKINS-55787 Re: Switch labels from entry to checkbox Josh, i'm terrbily sorry, but don't you think that this decision is a bit premature? I agree with Adrian that currently all job parameters looks like a table that's easy to watch and use, and 'jumping' to the right side at boolean parameters is, to be honest, not very convenient (also from the same UX point of view, we get empty gap at the left side where label originally was; i've even created a bug report (JENKINS-59388) and have rewritten several jobs in out organization from 'booleanParam' to 'choice' with 'true'/'false' values before i found this ticket). Probably it would be better to make it configurable or add another type (e.g. BooleanLabel) with UI you propose. 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.197176.1548453513000.1162.1568900400216%40Atlassian.JIRA.
[JIRA] (JENKINS-59090) Micro Focus UFT Jenkins plugin is marking build status as "FAILURE" even when builds are passing
Title: Message Title Sandeep Yadav commented on JENKINS-59090 Re: Micro Focus UFT Jenkins plugin is marking build status as "FAILURE" even when builds are passing Our other jobs have similar time outs and this happens only when a particular build encounters a failure. From this instance onwards, all future builds are marked as failed. 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.201510.1566845071000.1159.1568899800156%40Atlassian.JIRA.
[JIRA] (JENKINS-36544) Allow setting environment variables for dynamic ec2 slaves
Title: Message Title Marco Andries commented on JENKINS-36544 Re: Allow setting environment variables for dynamic ec2 slaves We would also benefit greatly by this. We're blocked and asked the following question to reach a work around: https://stackoverflow.com/questions/58006452/issue-setting-jenkins-environment-variables-on-ec2-fleet 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.172564.1468000478000.1148.1568898840985%40Atlassian.JIRA.
[JIRA] (JENKINS-59445) Continuous Multi Job Configuration
Title: Message Title Ashish Donde created an issue Jenkins / JENKINS-59445 Continuous Multi Job Configuration Issue Type: Task Assignee: Unassigned Components: multijob-plugin Created: 2019-09-19 12:43 Priority: Major Reporter: Ashish Donde Hello, I have 2 jobs that run on a Jenkins slave - AutoIT MoveMouse The first job has to run 4 times a day (eg. 8 AM, 12 PM, 6 PM, 9 PM) MouseMove is a script that runs on the slave machine to keep it alive and prevent it from locking. MouseMove has to run continuously between these 4 jobs every 10 mins. Also I have to make sure that both the jobs never overlap each other i.e. MoveMouse should run every 10 mins between two runs of AutoIT. I have downloaded Multi Job Plugin and also created a multi job but I am not sure how can I achieve the above requirement. Any thoughts? Can this be achieved by writing a groovy code? Add Comment
[JIRA] (JENKINS-59412) Clarify that build history does not include pipeline stages
Title: Message Title Jesse Glick started work on JENKINS-59412 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.201973.1568739433000.1142.1568896321017%40Atlassian.JIRA.
[JIRA] (JENKINS-59412) Clarify that build history does not include pipeline stages
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-59412 Clarify that build history does not include pipeline stages Change By: Jesse Glick Labels: ux 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.201973.1568739433000.1140.1568896320985%40Atlassian.JIRA.
[JIRA] (JENKINS-59412) Clarify that build history does not include pipeline stages
Title: Message Title Jesse Glick updated JENKINS-59412 Jenkins / JENKINS-59412 Clarify that build history does not include pipeline stages 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.201973.1568739433000.1144.1568896321071%40Atlassian.JIRA.
[JIRA] (JENKINS-58301) Kubernetes Plugin Repeated Socket Ping Timeout Exceptions
Title: Message Title Lee McClintock updated an issue Jenkins / JENKINS-58301 Kubernetes Plugin Repeated Socket Ping Timeout Exceptions Change By: Lee McClintock I often get issues like this:java.net.SocketTimeoutException: sent ping but didn't receive pong within 1000ms (after 330 successful ping/pongs)One single issue breaks the entire task and makes it hard to even cancel the task. Should this not be retried rather than break execution? Our Jenkins will run longer running tasks as well. Any single task breaking stop in the middle is a real issue, and I don't see why one network issue after 330 successful ones (in this case) is such a big issue. I set the timeout (both Connection and Read) in the settings of the Kubernetes Plugin as well, but it still only has a timeout of one second. x 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
[JIRA] (JENKINS-57158) Pipeline is green but shows red in stage view
Title: Message Title Jon Sten commented on JENKINS-57158 Re: Pipeline is green but shows red in stage view A user ran into the same problem. I did some quick debugging and it the problem is not on the client side. The rest API call incorrectly reports back failure. On the server side I found that calling RunExt.createNew() provides a RunExt with correct status, while RunExt.create() returns a cached RunExt with its status set to failure. I have no idea how that RunExt with incorrect status ended up in the cache. Would be interesting to know it it was had failure status when initially created or had success as initial result but the field was altered by some other code. No one knows... 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.198908.1556031734000.1122.1568893680278%40Atlassian.JIRA.
[JIRA] (JENKINS-18576) Add throughput column to performance plugin charts
Title: Message Title Anton Babchenko commented on JENKINS-18576 Re: Add throughput column to performance plugin charts Hi! Do you have any updates? I'm waiting for this feature for almost a year. Are you ok? Do you need some help? 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.149883.1372759075000.1115.1568893380336%40Atlassian.JIRA.
[JIRA] (JENKINS-56827) Performance center - Jenkins Integration job run issue
Title: Message Title Daniel Danan commented on JENKINS-56827 Re: Performance center - Jenkins Integration job run issue Hi Raj, I am Daniel, the developer of this plugin. Unfortunately the error is not clear. Could you please review Jenkins logs and see if you can find the full stack of the exception in there. if you do, please share it with me. Also try to review the logs of the PC server that you are trying to access from Jenkins and see if there are exception reported at the time the request is performed. regards, Daniel 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.198484.1554097754000.1119.1568893380417%40Atlassian.JIRA.
[JIRA] (JENKINS-59416) getting NullReferenceException still job is marked as success
Title: Message Title Anda Sorina Laakso commented on JENKINS-59416 Re: getting NullReferenceException still job is marked as success I want to know what version of the plugin are you using. Thank you. 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.201978.1568780076000.1112.1568893140433%40Atlassian.JIRA.
[JIRA] (JENKINS-57795) Orphaned EC2 instances after Jenkins restart
Title: Message Title cedric lecoz commented on JENKINS-57795 Re: Orphaned EC2 instances after Jenkins restart Hi Raihaan Shouhell, Using the 1.46-rc1050.43f9773eed95 plugin, I reproduced the issue when starting a new EC2 after the previous one was terminated, see attached log start_fresh_1.46-rc1050.43f9773eed95.txt. (what I believe was fixed in PR-397). Issue from a stopped slave has not yet been reproduced. BR, Cedric. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199745.1559315049000.1108.1568892780555%40Atlassian.JIRA.
[JIRA] (JENKINS-57795) Orphaned EC2 instances after Jenkins restart
Title: Message Title cedric lecoz updated an issue Jenkins / JENKINS-57795 Orphaned EC2 instances after Jenkins restart Change By: cedric lecoz Attachment: start_fresh_1.46-rc1050.43f9773eed95.txt Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199745.1559315049000.1103.1568892780419%40Atlassian.JIRA.
[JIRA] (JENKINS-59161) ERROR: 530 Authentication required
Title: Message Title
Joe Tavin edited a comment on JENKINS-59161
Re: ERROR: 530 Authentication required
Experiencing same issue with mailer plugin *v1.2.7* . emails not getting sent. Using Amazon SES as SMTP server, emails not getting sent.When using *{{mail}}* keyword in Pipeline , getting error {code:java}com.sun.mail.smtp.SMTPSendFailedException: 530 Authentication required{code} Test emails via "Test configuration" do work though..
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.201598.1567204978000.1093.1568891700361%40Atlassian.JIRA.
[JIRA] (JENKINS-59161) ERROR: 530 Authentication required
Title: Message Title
Joe Tavin edited a comment on JENKINS-59161
Re: ERROR: 530 Authentication required
Experiencing same issue with *v1.2.7* . emails not getting sent. Using Amazon SES as SMTP server, using * { {mail}}* keyword in Pipeline{ code:java}com.sun.mail.smtp.SMTPSendFailedException: 530 Authentication required{code}
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.201598.1567204978000.1083.1568891521571%40Atlassian.JIRA.
[JIRA] (JENKINS-59161) ERROR: 530 Authentication required
Title: Message Title
Joe Tavin edited a comment on JENKINS-59161
Re: ERROR: 530 Authentication required
having Experiencing same issue and with *v1.2.7* emails not getting sent.{code:java}com.sun.mail.smtp.SMTPSendFailedException: 530 Authentication required{code}
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.201598.1567204978000.1073.1568891400325%40Atlassian.JIRA.
[JIRA] (JENKINS-59161) ERROR: 530 Authentication required
Title: Message Title Joe Tavin commented on JENKINS-59161 Re: ERROR: 530 Authentication required having same issue and emails not getting sent. com.sun.mail.smtp.SMTPSendFailedException: 530 Authentication required 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.201598.1567204978000.1063.1568891220543%40Atlassian.JIRA.
[JIRA] (JENKINS-59444) Please respect build strategy "Skip initial build on first branch indexing"
Title: Message Title Christian Ciach closed an issue as Not A Defect Jenkins / JENKINS-59444 Please respect build strategy "Skip initial build on first branch indexing" Change By: Christian Ciach Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202029.1568889065000.1060.1568890980388%40Atlassian.JIRA.
[JIRA] (JENKINS-59444) Please respect build strategy "Skip initial build on first branch indexing"
Title: Message Title Christian Ciach commented on JENKINS-59444 Re: Please respect build strategy "Skip initial build on first branch indexing" It was actually a bad configuration. For future readers, please see the corrected configuration attached. 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.202029.1568889065000.1058.1568890861047%40Atlassian.JIRA.
[JIRA] (JENKINS-59444) Please respect build strategy "Skip initial build on first branch indexing"
Title: Message Title Christian Ciach updated an issue Jenkins / JENKINS-59444 Please respect build strategy "Skip initial build on first branch indexing" Change By: Christian Ciach Attachment: corrected_skip_initial_build.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.202029.1568889065000.1056.1568890800256%40Atlassian.JIRA.
[JIRA] (JENKINS-59327) No credentials specified Multibranch Pipeline - Branch script
Title: Message Title Mark Waite edited a comment on JENKINS-59327 Re: No credentials specified Multibranch Pipeline - Branch script You said: > bq. If I want to avoid failure with git credentials I have to specify credentials in multibranch configuration.That is correct. A multibranch job must be able to discover the branches which contain a Jenkinsfile. If the repository is secured (private), then the multibranch job must know the credentials to read that repository. Without the credentials, the multibranch job cannot discover branches in a secured (private) repository.Later you said: > bq. Which is pointless because I specified credentials in the Jenkins file (branch script named master on the previous script) and it should use that one from "nested" job.If the multibranch Pipeline does not have the credentials, it cannot read the Jenkinsfile. 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.201878.1568271976000.1054.1568890140500%40Atlassian.JIRA.
[JIRA] (JENKINS-59327) No credentials specified Multibranch Pipeline - Branch script
Title: Message Title Mark Waite commented on JENKINS-59327 Re: No credentials specified Multibranch Pipeline - Branch script You said: > If I want to avoid failure with git credentials I have to specify credentials in multibranch configuration. That is correct. A multibranch job must be able to discover the branches which contain a Jenkinsfile. If the repository is secured (private), then the multibranch job must know the credentials to read that repository. Without the credentials, the multibranch job cannot discover branches in a secured (private) repository. Later you said: > Which is pointless because I specified credentials in the Jenkins file (branch script named master on the previous script) and it should use that one from "nested" job. If the multibranch Pipeline does not have the credentials, it cannot read the Jenkinsfile. 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.201878.1568271976000.1052.1568890140365%40Atlassian.JIRA.
[JIRA] (JENKINS-59387) Failed to connect to repository : Command "C:\Program Files\Git\cmd\git.exe ls-remote -h — my Repository URL HEAD"
Title: Message Title Mark Waite updated JENKINS-59387 Jenkins / JENKINS-59387 Failed to connect to repository : Command "C:\Program Files\Git\cmd\git.exe ls-remote -h — my Repository URL HEAD" Change By: Mark Waite Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201943.1568630962000.1049.1568889720752%40Atlassian.JIRA.
[JIRA] (JENKINS-59387) Failed to connect to repository : Command "C:\Program Files\Git\cmd\git.exe ls-remote -h — my Repository URL HEAD"
Title: Message Title Mark Waite commented on JENKINS-59387 Re: Failed to connect to repository : Command "C:\Program Files\Git\cmd\git.exe ls-remote -h — my Repository URL HEAD" The git client plugin documentation recommends that you disable the credential manager that git for Windows offers to install by default. The Windows credential manager is a great help for interactive users. It can be a great distraction for automation use cases like Jenkins. Please don't use the bug tracker to request help. The user mailing list and the chat system are better places to request help with configuration problems. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201943.1568630962000.1044.1568889720645%40Atlassian.JIRA.
[JIRA] (JENKINS-59387) Failed to connect to repository : Command "C:\Program Files\Git\cmd\git.exe ls-remote -h — my Repository URL HEAD"
Title: Message Title Mark Waite updated JENKINS-59387 Jenkins / JENKINS-59387 Failed to connect to repository : Command "C:\Program Files\Git\cmd\git.exe ls-remote -h — my Repository URL HEAD" Change By: Mark Waite Status: Open Fixed but Unreleased Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201943.1568630962000.1047.1568889720693%40Atlassian.JIRA.
[JIRA] (JENKINS-59444) Please respect build strategy "Skip initial build on first branch indexing"
Title: Message Title Christian Ciach commented on JENKINS-59444 Re: Please respect build strategy "Skip initial build on first branch indexing" Actually, maybe I am doing it wrong. See here: JENKINS-58254 I will try out the workaround there and will update this issue accordingly. 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.202029.1568889065000.1041.1568889180118%40Atlassian.JIRA.
[JIRA] (JENKINS-59444) Please respect build strategy "Skip initial build on first branch indexing"
Title: Message Title Christian Ciach created an issue Jenkins / JENKINS-59444 Please respect build strategy "Skip initial build on first branch indexing" Issue Type: Bug Assignee: Parichay Barpanda Attachments: skip_initial_build.png Components: gitlab-branch-source-plugin Created: 2019-09-19 10:31 Environment: Gitlab-Branch-Source 1.3.0 Basic Branch Build Strategies Plugin 1.3.2 Jenkins 2.195 OpenJDK 11.0.4 CentOS 7 Priority: Minor Reporter: Christian Ciach Hi and thank you again for this great plugin! We are using the "Basic Branch Build Strategies Plugin" to configure which branches to automatically build on changes. I think this is a core plugin by now, but I am not completely sure about that. As you can see from the screenshot attached, there is a build strategy called "Skip initial build on first branch indexing" that is very important for us. We have a whole lot of Branches and Tags and it really hurts the jenkins when all of these clog the build queue when first importing Gitlab projects using your fine plugin. Unfortunately it seems like "Gitlab-Branch-Source" plugin doesn't honor the setting "Skip initial build on first branch indexing". Every time the plugin finds a new gitlab project, the build queue immediately fills up with hundreds of branches and tags.
[JIRA] (JENKINS-56307) Create a NodeProvisioner.Strategy for Kubernetes plugin to reduce provisioning time
Title: Message Title Vincent Latombe updated JENKINS-56307 Jenkins / JENKINS-56307 Create a NodeProvisioner.Strategy for Kubernetes plugin to reduce provisioning time Change By: Vincent Latombe 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.197887.1551263076000.1030.1568889061741%40Atlassian.JIRA.
[JIRA] (JENKINS-56307) Create a NodeProvisioner.Strategy for Kubernetes plugin to reduce provisioning time
Title: Message Title Vincent Latombe started work on JENKINS-56307 Change By: Vincent Latombe 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.197887.1551263076000.1027.1568889061705%40Atlassian.JIRA.
[JIRA] (JENKINS-54249) GitHub Commit Status Setter - Cannot retrieve Git metadata
Title: Message Title Mark Waite commented on JENKINS-54249 Re: GitHub Commit Status Setter - Cannot retrieve Git metadata Alan Lee the latest release of the GitHub plugin (1.29.3) depends on git plugin 3.4.0 or newer. The GitHub plugin expects the git plugin to write BuildData. All releases of git plugin 3.x write BuildData. Git plugin 4.0.0-beta10 (pre-release delivered July 5, 2019) and git plugin 4.0.0-beta11 (pre-release delivered Sep 13, 2019) write BuildData. Git plugin 4.0.0-rc (pre-release delivered Jan 30, 2019) does not write BuildData. Git plugin 4.0.0-rc was a failed attempt to resolve the memory bloat caused by the git plugin (JENKINS-19022). The attempt introduced too many incompatibilities and had to be reverted. My sincere apologies that I released git plugin 4.0.0-rc. The poor choice of version string caused it to appear in the Jenkins update center rather than in the Jenkins experimental update center. If you are running git plugin 4.0.0-rc and cannot downgrade, then I assume that means some plugin in your installation has declared a dependency on git plugin 4.0.0-rc. That plugin needs to be updated to not depend on git plugin 4.0.0-rc. The BuildData related changes in git plugin 4.0.0-rc are not included in git plugin 4.0.0-beta10 and are not included in git plugin 4.0.0-beta11 and will not be included in the final release of git plugin 4.0.0. The git plugin 4.0.0-rc release was a terrible mistake that I made which delivered pre-release code to the production Jenkins update center. The git plugin 4.0.0-rc release was also the clear proof that the API changes proposed in git plugin 4.0.0 pre-releases introduced too much incompatibility for other plugins that use the BuildData provided by the git plugin. If you cannot downgrade because an installed plugin has an explicit dependency on 4.0.0-rc, then you should still be able to upgrade to git plugin 4.0.0-beta11 from the experimental upgrade center. However, if one of your installed plugins truly has a dependency on git plugin 4.0.0-rc, it seems likely that the reason it depends on git plugin 4.0.0-rc is because it is using the API changes that were included in git plugin 4.0.0-rc. Those API changes are not available in newer pre-releases of git plugin 4.0.0 like git plugin 4.0.0-beta10 and git plugin 4.0.0-beta11. In summary, if you cannot downgrade because one of your plugins explicitly depends on git plugin 4.0.0-rc, then that plugin must be changed to not depend on git plugin 4.0.0-rc. If you cannot downgrade for some other reason, then you can likely upgrade to git client plugin 3.0.0-beta11 and git plugin 4.0.0-beta11. Add Comment
[JIRA] (JENKINS-59443) Kubernetes plugin volumeMount turns backslashes to forward slashes
Title: Message Title Jan Lindstam created an issue Jenkins / JENKINS-59443 Kubernetes plugin volumeMount turns backslashes to forward slashes Issue Type: Bug Assignee: Unassigned Components: kubernetes-plugin Created: 2019-09-19 10:03 Labels: Windows volumes Priority: Minor Reporter: Jan Lindstam Having successfully configured a Windows server jnlp image and able to run builds on it, now then trying to add ability to use the slave for building docker images. Problem is this: if i define a HostPath volume in the configuration Ui with following values ( both fields same value) : \\.\pipe\docker_engine \\.\pipe\docker_engine the outcome is Error: Error response from daemon: invalid volume specification: '\\.\pipe\docker_engine:c://./pipe/docker_engine' reason for this is that in volumemount the backslashes have turned direction. Hosts portion of volume is correct: volumeMounts: - mountPath: //./pipe/docker_engine name: volume-0 ... volumes: - hostPath: path: \\.\pipe\docker_engine Now if i take the pod yaml out, modify the mountpaths forward slashes to backslashes, and run it in with kubectl, the pod starts successfully. Assuming
[JIRA] (JENKINS-56307) Create a NodeProvisioner.Strategy for Kubernetes plugin to reduce provisioning time
Title: Message Title runze xia commented on JENKINS-56307 Re: Create a NodeProvisioner.Strategy for Kubernetes plugin to reduce provisioning time Mikaël Barbero have created PR, If you could help review and some tests will be very nice https://github.com/jenkinsci/kubernetes-plugin/pull/598 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.197887.1551263076000.971.1568887200483%40Atlassian.JIRA.
[JIRA] (JENKINS-59442) NoClassDefFoundError of application classes during test
Title: Message Title Oliver Gondža commented on JENKINS-59442 Re: NoClassDefFoundError of application classes during test This is really a topic for https://groups.google.com/forum/#!forum/jenkinsci-dev. Also, make sure to attach the code and more details on what are you doing so someone can assist you. 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.202027.1568884729000.959.1568886960147%40Atlassian.JIRA.
[JIRA] (JENKINS-59410) any dependency to spring is causing version conflict between shared libraries and jdk-tools plugin spring 2.5X
Title: Message Title tigran mnatsakanyan commented on JENKINS-59410 Re: any dependency to spring is causing version conflict between shared libraries and jdk-tools plugin spring 2.5X I had a chat with Carlos Sanchez in k8s slack, and very good advice was to go ahead and shade conflicting dependencies with https://maven.apache.org/plugins/maven-shade-plugin or any other plugin supporting shading. That solution worked. I am leaving the issue open to check if there are more fundamental solutions available, which does not require recompiling to renaming conflicting classes for the confused classloader. Because it's not always your own code appears as a dependency to add a build plugin to it but could be someone else's jar file. 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.201970.1568735892000.957.1568885400141%40Atlassian.JIRA.
[JIRA] (JENKINS-56307) Create a NodeProvisioner.Strategy for Kubernetes plugin to reduce provisioning time
Title: Message Title Mikaël Barbero commented on JENKINS-56307 Re: Create a NodeProvisioner.Strategy for Kubernetes plugin to reduce provisioning time runze xia awesome! Let me know if/how I can help! 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.197887.1551263076000.948.1568885220308%40Atlassian.JIRA.
[JIRA] (JENKINS-56307) Create a NodeProvisioner.Strategy for Kubernetes plugin to reduce provisioning time
Title: Message Title runze xia commented on JENKINS-56307 Re: Create a NodeProvisioner.Strategy for Kubernetes plugin to reduce provisioning time Mikaël Barbero yes I have started 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.197887.1551263076000.939.1568885160256%40Atlassian.JIRA.
[JIRA] (JENKINS-56307) Create a NodeProvisioner.Strategy for Kubernetes plugin to reduce provisioning time
Title: Message Title Mikaël Barbero commented on JENKINS-56307 Re: Create a NodeProvisioner.Strategy for Kubernetes plugin to reduce provisioning time It looks like it would be a very good fit. Thanks for sharing. Are you starting the backport of the EC2 no-delay strategy to the Kubernetes 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.197887.1551263076000.930.1568885040666%40Atlassian.JIRA.
[JIRA] (JENKINS-57012) Allow folder scope credential for Jira connection
Title: Message Title Mathieu Delrocq edited a comment on JENKINS-57012 Re: Allow folder scope credential for Jira connection The PR is still in review and I don't have much times to work on it for the moment... I will continu as soon as possible.And I will need to do somes rework on my solution to keep binary compatibility.I hope to work on it next month. 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.198713.1555344179000.928.1568884920144%40Atlassian.JIRA.
[JIRA] (JENKINS-57012) Allow folder scope credential for Jira connection
Title: Message Title Mathieu Delrocq edited a comment on JENKINS-57012 Re: Allow folder scope credential for Jira connection The PR is still in review and I don't have much times to work on it for the moment... I will continu as soon as possible. Maybe And I will need to do somes rework on my solution to keep binary compatibility.I hope to work on it next month. 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.198713.1555344179000.925.1568884860156%40Atlassian.JIRA.
[JIRA] (JENKINS-57012) Allow folder scope credential for Jira connection
Title: Message Title Mathieu Delrocq commented on JENKINS-57012 Re: Allow folder scope credential for Jira connection The PR is still in review and I don't have much times to work on it for the moment... I will continu as soon as possible. Maybe I will need to do somes rework on my solution to keep binary compatibility. I hope to work on it next month. 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.198713.1555344179000.920.1568884800247%40Atlassian.JIRA.
[JIRA] (JENKINS-59442) NoClassDefFoundError of application classes during test
Title: Message Title Theodore Chaikalis updated an issue Jenkins / JENKINS-59442 NoClassDefFoundError of application classes during test Change By: Theodore Chaikalis Summary: NoClassDefFoundError of one of my application classes during test 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.202027.1568884729000.922.1568884800274%40Atlassian.JIRA.
[JIRA] (JENKINS-59442) NoClassDefFoundError of one of my classes during test
Title: Message Title Theodore Chaikalis created an issue Jenkins / JENKINS-59442 NoClassDefFoundError of one of my classes during test Issue Type: Bug Assignee: Oliver Gondža Components: jenkins-test-harness Created: 2019-09-19 09:18 Environment: Jenkins ver. 2.150 awt.toolkit sun.awt.X11.XToolkit buildInfoConfig.propertiesFile /var/jenkins_home/workspace/deploy-proddev10-batch-consumers@tmp/artifactory/buildInfo1022248419511780205.properties executable-war /usr/share/jenkins/jenkins.war file.encoding UTF-8 file.encoding.pkg sun.io file.separator / guice.disable.misplaced.annotation.check true java.awt.graphicsenv sun.awt.X11GraphicsEnvironment java.awt.headless true java.awt.printerjob sun.print.PSPrinterJob java.class.path /usr/share/jenkins/jenkins.war java.class.version 52.0 java.endorsed.dirs /usr/lib/jvm/java-8-openjdk-amd64/jre/lib/endorsed java.ext.dirs /usr/lib/jvm/java-8-openjdk-amd64/jre/lib/ext:/usr/java/packages/lib/ext java.home /usr/lib/jvm/java-8-openjdk-amd64/jre java.io.tmpdir /tmp java.library.path /usr/java/packages/lib/amd64:/usr/lib/x86_64-linux-gnu/jni:/lib/x86_64-linux-gnu:/usr/lib/x86_64-linux-gnu:/usr/lib/jni:/lib:/usr/lib java.runtime.name OpenJDK Runtime Environment java.runtime.version 1.8.0_131-8u131-b11-1~bpo8+1-b11 java.specification.name Java Platform API Specification java.specification.vendor Oracle Corporation java.specification.version 1.8 java.vendor Oracle Corporation java.vendor.url http://java.oracle.com/ java.vendor.url.bug http://bugreport.sun.com/bugreport/ java.version 1.8.0_131 java.vm.info mixed mode java.vm.name OpenJDK 64-Bit Server VM java.vm.specification.name Java Virtual Machine Specification java.vm.specification.vendor Oracle Corporation java.vm.specification.version 1.8 java.vm.vendor Oracle Corporation java.vm.version 25.131-b11 javamelody.About Monitoring https://wiki.jenkins-ci.org/display/JENKINS/Monitoring javamelody.analytics-id UA-1335263-7 javamelody.csrf-protection-enabled true javamelody.custom-reports Jenkins Info,About Monitoring javamelody.gzip-compression-disabled true javamelody.http-transform-pattern /\d+/|(?<=/static/|/adjuncts/|/bound/)[\w\-]+|(?<=/ws/|/user/|/testReport/|/javadoc/|/site/|/violations/file/|/cobertura/).+|(?<=/job/).+(?=/descriptorByName/) javamelody.Jenkins Info /systemInfo javamelody.maven-repositories /var/jenkins_home/.m2/repository,http://repo1.maven.org/maven2,http://repo.jenkins-ci.org/public javamelody.no-database true javamelody.storage-directory //var/jenkins_home/monitoring javamelody.system-actions-enabled true jetty.git.hash
[JIRA] (JENKINS-56307) Create a NodeProvisioner.Strategy for Kubernetes plugin to reduce provisioning time
Title: Message Title runze xia assigned an issue to runze xia Jenkins / JENKINS-56307 Create a NodeProvisioner.Strategy for Kubernetes plugin to reduce provisioning time Change By: runze xia Assignee: runze xia 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.197887.1551263076000.898.1568884380294%40Atlassian.JIRA.
[JIRA] (JENKINS-59441) Jenkins can't reach update json despite browser load it correctly
Title: Message Title Bartlomiej Chrabaszcz updated an issue Jenkins / JENKINS-59441 Jenkins can't reach update json despite browser load it correctly Change By: Bartlomiej Chrabaszcz 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.202026.1568879688000.896.1568883780100%40Atlassian.JIRA.
[JIRA] (JENKINS-56307) Create a NodeProvisioner.Strategy for Kubernetes plugin to reduce provisioning time
Title: Message Title runze xia commented on JENKINS-56307 Re: Create a NodeProvisioner.Strategy for Kubernetes plugin to reduce provisioning time https://github.com/jenkinsci/ec2-plugin/blob/master/src/main/java/hudson/plugins/ec2/NoDelayProvisionerStrategy.java I think the strategy in the ec2 plugin is very valuable. 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.197887.1551263076000.888.1568883360412%40Atlassian.JIRA.
