[JIRA] (JENKINS-58565) Jenkins build not grabbing hptoolslauncher
Title: Message Title Evelyn augustin updated an issue Jenkins / JENKINS-58565 Jenkins build not grabbing hptoolslauncher Change By: Evelyn augustin I'm trying to run my build in jenkins, and it uses a slave node(windows), and this is the error i get, where you can see it doesn't get the HpToolsLauncher.exe and straight away fails: [Office365connector] No webhooks to notify[EnvInject] - Loading node environment variables.Building remotely on [slave-USNT01142|http://uslx1019:8080/computer/slave-USNT01142] (ALM POC) in workspace C:\Jenkins\workspace\ALM TestBuild step 'Execute Micro Focus functional tests from Micro Focus ALM' changed build result to FAILURERecording test resultsRunResultRecorder: didn't find any test results to record[Office365connector] No webhooks to notifyFinished: FAILURE As you can see, But when i run it on a master(linux) it could get the build doesn't grab exe :[ALM Test] $ "/apps/ jenkins_slave .jenkins /workspace/ALM Test/HpToolsLauncher.exe" -paramfile props18072019222131451.txt Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit
[JIRA] (JENKINS-44361) Jenkins CLI does not follow redirect correctly
Title: Message Title Allan BURDAJEWICZ commented on JENKINS-44361 Re: Jenkins CLI does not follow redirect correctly I have seen a similar issue with the install-plugin command recently, In Jenkins 2.186. See https://issues.jenkins-ci.org/browse/JENKINS-29065. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.182171.1495179974000.15919.1563512700212%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-29065) CLI install plugin jobs-dsl fails
Title: Message Title
Allan BURDAJEWICZ edited a comment on JENKINS-29065
Re: CLI install plugin jobs-dsl fails
[~danielbeck] Maybe this could be reopen. Or maybe this is related to https://issues.jenkins-ci.org/browse/JENKINS-44361 ? The issue with the HTTP / HTTPS redirect is corrupting the file when downloading using the CLI.If I use {{wget https://updates.jenkins.io/download/plugins/groovy/2.2/groovy.hpi}} and then do a {{sha1sum groovy.jpi}} I can see the right sha {{85af4e8de47e981d3bf22adaf0c7f5747b991d83}}.If I use the Jenkins CLI to install from {{https://updates.jenkins.io}}, it succeeds:{code}java -jar jenkins-cli.jar -logger FINE -s http://cje.example.com:8081 -auth admin:admin install-plugin https://updates.jenkins.io/download/plugins/groovy/2.2/groovy.hpi Jul 19, 2019 2:34:09 PM org.apache.sshd.common.util.security.SecurityUtils registerFINE: register(BC) not registered - enabled=true, supported=falseJul 19, 2019 2:34:09 PM org.apache.sshd.common.util.security.AbstractSecurityProviderRegistrar getOrCreateProviderINFO: getOrCreateProvider(EdDSA) created instance of net.i2p.crypto.eddsa.EdDSASecurityProviderJul 19, 2019 2:34:09 PM hudson.cli.CLI _mainFINE: using connection mode HTTPJul 19, 2019 2:34:09 PM hudson.cli.CLI plainHttpConnectionFINE: Trying to connect to http://allan.oss.com:8081/ via plain protocol over HTTPJul 19, 2019 2:34:09 PM hudson.cli.FullDuplexHttpStream FINE: establishing download sideJul 19, 2019 2:34:09 PM hudson.cli.FullDuplexHttpStream FINE: established download sideJul 19, 2019 2:34:09 PM hudson.cli.FullDuplexHttpStream FINE: establishing upload sideJul 19, 2019 2:34:09 PM hudson.cli.FullDuplexHttpStream FINE: established upload sideInstalling a plugin from https://updates.jenkins.io/download/plugins/groovy/2.2/groovy.hpi{code}*but the sha of the {{$JENKINS_HOME/plugins/groovy.hpi}} is wrong {{7c5e3f4ae6540474cf24bd4cb3ece2d31e701965}}*. The file contains the HTTP response:{code}302 FoundFoundThe document has moved here.{code}This will break Jenkins startup on the next restart.If I use the Jenkins CLI to install from {{http://updates.jenkins.io}}, it succeeds:{code}java -jar jenkins-cli.jar -logger FINE -s http://cje.example.com:8081 -auth admin:admin install-plugin https://updates.jenkins.io/download/plugins/groovy/2.2/groovy.hpi Jul 19, 2019 2:34:09 PM org.apache.sshd.common.util.security.SecurityUtils registerFINE: register(BC) not registered - enabled=true, supported=falseJul 19, 2019 2:34:09 PM org.apache.sshd.common.util.security.AbstractSecurityProviderRegistrar getOrCreateProviderINFO: getOrCreateProvider(EdDSA) created instance of net.i2p.crypto.eddsa.EdDSASecurityProviderJul 19, 2019 2:34:09 PM hudson.cli.CLI _mainFINE: using connection mode HTTPJul 19, 2019 2:34:09 PM hudson.cli.CLI plainHttpConnectionFINE: Trying to connect to http://allan.oss.com:8081/ via plain protocol over HTTPJul 19, 2019 2:34:09 PM hudson.cli.FullDuplexHttpStream FINE: establishing download sideJul 19, 2019 2:34:09 PM hudson.cli.FullDuplexHttpStream FINE: established download sideJul 19, 2019 2:34:09 PM hudson.cli.FullDuplexHttpStream FINE: establishing upload sideJul 19, 2019 2:34:09 PM hudson.cli.FullDuplexHttpStream FINE: established upload sideInstalling a plugin from https://updates.jenkins.io/download/plugins/groovy/2.2/groovy.hpi{code}And the sha of the {{$JENKINS_HOME/plugins/groovy.hpi}} is correct {{85af4e8de47e981d3bf22adaf0c7f5747b991d83}}*Note that it works for the update site at {{jenkins-updates.cloudbees.com/}} whether you use {{http}} or {{https}}
[JIRA] (JENKINS-29065) CLI install plugin jobs-dsl fails
Title: Message Title
Allan BURDAJEWICZ edited a comment on JENKINS-29065
Re: CLI install plugin jobs-dsl fails
[~danielbeck] The issue with the HTTP / HTTPS redirect is corrupting the file when downloading using the CLI.If I use {{wget https://updates.jenkins.io/download/plugins/groovy/2.2/groovy.hpi}} and then do a {{sha1sum groovy.jpi}} I can see the right sha {{85af4e8de47e981d3bf22adaf0c7f5747b991d83}}.If I use the Jenkins CLI to install from {{https://updates.jenkins.io}}, it succeeds:{code}java -jar jenkins-cli.jar -logger FINE -s http://cje.example.com:8081 -auth admin:admin install-plugin https://updates.jenkins.io/download/plugins/groovy/2.2/groovy.hpi Jul 19, 2019 2:34:09 PM org.apache.sshd.common.util.security.SecurityUtils registerFINE: register(BC) not registered - enabled=true, supported=falseJul 19, 2019 2:34:09 PM org.apache.sshd.common.util.security.AbstractSecurityProviderRegistrar getOrCreateProviderINFO: getOrCreateProvider(EdDSA) created instance of net.i2p.crypto.eddsa.EdDSASecurityProviderJul 19, 2019 2:34:09 PM hudson.cli.CLI _mainFINE: using connection mode HTTPJul 19, 2019 2:34:09 PM hudson.cli.CLI plainHttpConnectionFINE: Trying to connect to http://allan.oss.com:8081/ via plain protocol over HTTPJul 19, 2019 2:34:09 PM hudson.cli.FullDuplexHttpStream FINE: establishing download sideJul 19, 2019 2:34:09 PM hudson.cli.FullDuplexHttpStream FINE: established download sideJul 19, 2019 2:34:09 PM hudson.cli.FullDuplexHttpStream FINE: establishing upload sideJul 19, 2019 2:34:09 PM hudson.cli.FullDuplexHttpStream FINE: established upload sideInstalling a plugin from https://updates.jenkins.io/download/plugins/groovy/2.2/groovy.hpi{code}*but the sha of the {{$JENKINS_HOME/plugins/groovy.hpi}} is wrong {{7c5e3f4ae6540474cf24bd4cb3ece2d31e701965}}*. The file contains the HTTP response:{code}302 FoundFoundThe document has moved here.{code} This will break Jenkins startup on the next restart.If I use the Jenkins CLI to install from {{http://updates.jenkins.io}}, it succeeds:{code}java -jar jenkins-cli.jar -logger FINE -s http://cje.example.com:8081 -auth admin:admin install-plugin https://updates.jenkins.io/download/plugins/groovy/2.2/groovy.hpi Jul 19, 2019 2:34:09 PM org.apache.sshd.common.util.security.SecurityUtils registerFINE: register(BC) not registered - enabled=true, supported=falseJul 19, 2019 2:34:09 PM org.apache.sshd.common.util.security.AbstractSecurityProviderRegistrar getOrCreateProviderINFO: getOrCreateProvider(EdDSA) created instance of net.i2p.crypto.eddsa.EdDSASecurityProviderJul 19, 2019 2:34:09 PM hudson.cli.CLI _mainFINE: using connection mode HTTPJul 19, 2019 2:34:09 PM hudson.cli.CLI plainHttpConnectionFINE: Trying to connect to http://allan.oss.com:8081/ via plain protocol over HTTPJul 19, 2019 2:34:09 PM hudson.cli.FullDuplexHttpStream FINE: establishing download sideJul 19, 2019 2:34:09 PM hudson.cli.FullDuplexHttpStream FINE: established download sideJul 19, 2019 2:34:09 PM hudson.cli.FullDuplexHttpStream FINE: establishing upload sideJul 19, 2019 2:34:09 PM hudson.cli.FullDuplexHttpStream FINE: established upload sideInstalling a plugin from https://updates.jenkins.io/download/plugins/groovy/2.2/groovy.hpi{code}And the sha of the {{$JENKINS_HOME/plugins/groovy.hpi}} is correct {{85af4e8de47e981d3bf22adaf0c7f5747b991d83}}*Note that it works for the update site at {{jenkins-updates.cloudbees.com/}} whether you use {{http}} or {{https}}
[JIRA] (JENKINS-29065) CLI install plugin jobs-dsl fails
Title: Message Title Allan BURDAJEWICZ commented on JENKINS-29065 Re: CLI install plugin jobs-dsl fails Daniel Beck The issue with the HTTP / HTTPS redirect is corrupting the file when downloading using the CLI. If I use wget https://updates.jenkins.io/download/plugins/groovy/2.2/groovy.hpi and then do a sha1sum groovy.jpi I can see the right sha 85af4e8de47e981d3bf22adaf0c7f5747b991d83. If I use the Jenkins CLI to install from https://updates.jenkins.io, it succeeds: java -jar jenkins-cli.jar -logger FINE -s http://cje.example.com:8081 -auth admin:admin install-plugin https://updates.jenkins.io/download/plugins/groovy/2.2/groovy.hpi Jul 19, 2019 2:34:09 PM org.apache.sshd.common.util.security.SecurityUtils register FINE: register(BC) not registered - enabled=true, supported=false Jul 19, 2019 2:34:09 PM org.apache.sshd.common.util.security.AbstractSecurityProviderRegistrar getOrCreateProvider INFO: getOrCreateProvider(EdDSA) created instance of net.i2p.crypto.eddsa.EdDSASecurityProvider Jul 19, 2019 2:34:09 PM hudson.cli.CLI _main FINE: using connection mode HTTP Jul 19, 2019 2:34:09 PM hudson.cli.CLI plainHttpConnection FINE: Trying to connect to http://allan.oss.com:8081/ via plain protocol over HTTP Jul 19, 2019 2:34:09 PM hudson.cli.FullDuplexHttpStream FINE: establishing download side Jul 19, 2019 2:34:09 PM hudson.cli.FullDuplexHttpStream FINE: established download side Jul 19, 2019 2:34:09 PM hudson.cli.FullDuplexHttpStream FINE: establishing upload side Jul 19, 2019 2:34:09 PM hudson.cli.FullDuplexHttpStream FINE: established upload side Installing a plugin from https://updates.jenkins.io/download/plugins/groovy/2.2/groovy.hpi but the sha of the $JENKINS_HOME/plugins/groovy.hpi is wrong 7c5e3f4ae6540474cf24bd4cb3ece2d31e701965. This will break Jenkins startup on the next restart. If I use the Jenkins CLI to install from http://updates.jenkins.io, it succeeds: java -jar jenkins-cli.jar -logger FINE -s http://cje.example.com:8081 -auth admin:admin install-plugin https://updates.jenkins.io/download/plugins/groovy/2.2/groovy.hpi Jul 19, 2019 2:34:09 PM org.apache.sshd.common.util.security.SecurityUtils register FINE: register(BC) not registered - enabled=true, supported=false Jul 19, 2019 2:34:09 PM org.apache.sshd.common.util.security.AbstractSecurityProviderRegistrar getOrCreateProvider INFO: getOrCreateProvider(EdDSA) created instance of net.i2p.crypto.eddsa.EdDSASecurityProvider Jul 19, 2019 2:34:09 PM hudson.cli.CLI _main FINE: using connection mode HTTP Jul 19, 2019 2:34:09 PM hudson.cli.CLI plainHttpConnection FINE: Trying to connect to http://allan.oss.com:8081/ via plain protocol over HTTP Jul 19, 2019 2:34:09 PM hudson.cli.FullDuplexHttpStream FINE: establishing download side Jul 19, 2019 2:34:09 PM hudson.cli.FullDuplexHttpStream FINE: established download side Jul 19, 2019 2:34:09 PM hudson.cli.FullDuplexHttpStream FINE: establishing upload side Jul 19, 2019 2:34:09 PM hudson.cli.FullDuplexHttpStream FINE: established upload side Installing a plugin from https://updates.jenkins.io/download/plugins/groovy/2.2/groovy.hpi
[JIRA] (JENKINS-46858) Comma separated parameters doesn't limit jobs
Title: Message Title Peter Wiseman commented on JENKINS-46858 Re: Comma separated parameters doesn't limit jobs I successfully tested with space delimiters. Note you can't use "space and comma". It needs to be space only. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.185214.1505320984000.15895.1563507720426%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58324) HTML report do not show from Jenkins page (html error 404 on page js file)
Title: Message Title Richard Bywater resolved as Not A Defect Jenkins / JENKINS-58324 HTML report do not show from Jenkins page (html error 404 on page js file) Change By: Richard Bywater Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200432.1562163785000.15892.1563506100435%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58324) HTML report do not show from Jenkins page (html error 404 on page js file)
Title: Message Title Richard Bywater commented on JENKINS-58324 Re: HTML report do not show from Jenkins page (html error 404 on page js file) Hi Ante Kevrić - sorry for the delay but I think I have found the issue is not with the HTML Publisher plugin but with the _javascript_ that is included with the RPT output. Basically it looks like when the page loads, it looks to see if the page is being served up using the file:// type protocol (which it would be when looking at locally from the zip) or if "force offline" is enabled (I have no idea how that gets set as it seems to the a RPT _javascript_ thing). If one of these conditions is true, it goes into some kind of offline mode and works with no issues. If those conditions aren't met however, it attempts to fetch stuff from "/analytics" and when that fails it appears to stop processing and just give you a blank screen. Obviously it will never be able to get the "/analytics" endpoint on Jenkins. Only thing I can think of is to find out, if you don't know already, how to force the offline mode to be set and then it will work perfectly. (I tested by taking the ZIP file contents and publishing that to HTML Publisher, and then manually debugging the _javascript_ and forcing offline and it showed with no issues within Jenkins). Going to close this issue for now but please feel free to comment if new information comes to hand. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200432.1562163785000.15890.1563506100399%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58565) Jenkins build not grabbing hptoolslauncher
Title: Message Title Evelyn augustin created an issue Jenkins / JENKINS-58565 Jenkins build not grabbing hptoolslauncher Issue Type: Bug Assignee: Daniel Gront Components: hp-application-automation-tools-plugin Created: 2019-07-19 03:08 Priority: Minor Reporter: Evelyn augustin [Office365connector] No webhooks to notify [EnvInject] - Loading node environment variables. Building remotely on slave-USNT01142 (ALM POC) in workspace C:\Jenkins\workspace\ALM Test Build step 'Execute Micro Focus functional tests from Micro Focus ALM' changed build result to FAILURE Recording test results RunResultRecorder: didn't find any test results to record [Office365connector] No webhooks to notify Finished: FAILURE As you can see, the build doesn't grab: [ALM Test] $ "/apps/jenkins_slave/workspace/ALM Test/HpToolsLauncher.exe" -paramfile props18072019222131451.txt Add Comment
[JIRA] (JENKINS-58157) "delete build" button is to long
Title: Message Title Aakash Kanvinde started work on JENKINS-58157 Change By: Aakash Kanvinde Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200205.1561341295000.15884.1563503400231%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57333) Move macOS keychain information from "Configure System" to "Credentials".
Title: Message Title Kazuhide Takahashi assigned an issue to Kazuhide Takahashi Jenkins / JENKINS-57333 Move macOS keychain information from "Configure System" to "Credentials". Change By: Kazuhide Takahashi Assignee: Kazuhide Takahashi Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199107.1557107892000.15882.1563498780117%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58237) dSYMs not generated in version 2.0.11
Title: Message Title Kazuhide Takahashi assigned an issue to Kazuhide Takahashi Jenkins / JENKINS-58237 dSYMs not generated in version 2.0.11 Change By: Kazuhide Takahashi Assignee: Kazuhide Takahashi Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200298.156162958.15880.1563498600242%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58559) Incrementals URL missing plugin name
Title: Message Title Natasha Stopa commented on JENKINS-58559 Re: Incrementals URL missing plugin name Fixed in https://github.com/jenkinsci/plugin-installation-manager-tool/pull/43 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200709.1563467344000.15874.1563495360322%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58556) Comments on same line as plugin info cause invalid URL
Title: Message Title Natasha Stopa commented on JENKINS-58556 Re: Comments on same line as plugin info cause invalid URL Fixed in https://github.com/jenkinsci/plugin-installation-manager-tool/pull/43 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200706.1563466609000.15876.1563495360381%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58549) Would be nice to have a --version command line option
Title: Message Title Natasha Stopa commented on JENKINS-58549 Re: Would be nice to have a --version command line option Fixed in https://github.com/jenkinsci/plugin-installation-manager-tool/pull/43 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200699.1563453076000.15878.1563495360533%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58559) Incrementals URL missing plugin name
Title: Message Title
Alex Earl updated an issue
Jenkins / JENKINS-58559
Incrementals URL missing plugin name
Change By:
Alex Earl
With the following line in a plugins.txt file:{code}workflow-support:incrementals;org.jenkins-ci.plugins.workflow;2.19-rc289.d09828a05a74{code}The following URL is being used for the plugin download:https://repo.jenkins-ci.org/incrementals/org/jenkins-ci/plugins/workflow/2.19-rc289.d09828a05a74/workflow-support-2.19-rc289.d09828a05a74.hpiThe actual URL should be:https://repo.jenkins-ci.org/incrementals/org/jenkins-ci/plugins/workflow/*workflow-support*/2.19-rc289.d09828a05a74/workflow-support-2.19-rc289.d09828a05a74.hpiThe workflow-support is missing from after the groupId /artifactId info.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200709.1563467344000.15869.1563493620160%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58544) Implement HTTP client retries
Title: Message Title Lenin Raj Rajasekaran started work on JENKINS-58544 Change By: Lenin Raj Rajasekaran Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200694.1563448453000.15867.1563493260145%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58416) Support sending deployment information to Jira
Title: Message Title Lenin Raj Rajasekaran started work on JENKINS-58416 Change By: Lenin Raj Rajasekaran Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200543.1562720583000.15861.1563493200514%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58416) Support sending deployment information to Jira
Title: Message Title Lenin Raj Rajasekaran updated JENKINS-58416 Jenkins / JENKINS-58416 Support sending deployment information to Jira Change By: Lenin Raj Rajasekaran Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200543.1562720583000.15863.1563493200564%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58416) Support sending deployment information to Jira
Title: Message Title Lenin Raj Rajasekaran updated JENKINS-58416 Jenkins / JENKINS-58416 Support sending deployment information to Jira Change By: Lenin Raj Rajasekaran Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200543.1562720583000.15865.1563493200589%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58549) Would be nice to have a --version command line option
Title: Message Title Natasha Stopa started work on JENKINS-58549 Change By: Natasha Stopa Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200699.1563453076000.15859.1563492660176%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-25462) Failed to extract workspace.tar.gz when cloning workspace
Title: Message Title Guillaume Egles commented on JENKINS-25462 Re: Failed to extract workspace.tar.gz when cloning workspace Yep, I see the same issue. So frustrating as is it so intermittent! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.159027.1415231889000.15852.1563491580425%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-24138) Archived file names can change when moved from slave to master
Title: Message Title Kim Abbott commented on JENKINS-24138 Re: Archived file names can change when moved from slave to master I too am still having this issue. Running with: Jenkins 2.176.1 Copy Artifact Plugin 1.42.1 Master Linux Slave Windows 8 Server File pulls from repo onto Windows slave with correct filename, but when archived back to master the ™ gets garbled. So the rest of my deploy steps fail because I now have a file with an invalid filename. Its unclear if any changes from 2014 were ever implemented? Even version 1.9.0 is pretty dated, so seems like core is due to update and update dependencies? I don't know of any workaround at this point. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.156612.1407335439000.15845.1563489780213%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58564) Blue Ocean visualization should indicate parallel stages killed with fastFail
Title: Message Title leemeador created an issue Jenkins / JENKINS-58564 Blue Ocean visualization should indicate parallel stages killed with fastFail Issue Type: Improvement Assignee: Unassigned Components: blueocean-plugin Created: 2019-07-18 22:12 Environment: 2.164 Priority: Minor Reporter: leemeador When you have a parallel section, and one of the parallel stages fails, and you have fail fast set, All the other parallel stages (that haven't completed) show a message "sending interrupt ..." in the log when they are killed. It would be nice if the visualization let it be easy to see which of the parallel stages died on their own and which were killed because a different on died. Let's say the little circle turns grey. Then you could easily see which one has the log you need to look at to see why it failed. I suspect there is some complexity if two stages fail around the same time and then tell each other to die. Maybe this case can't easily be handled. Even if not, it is my opinion that solving the case where only one failed on its own would be useful. Maybe its as simple as putting that grey circle up if the log for that parallel stage has a message about "sending interrupt..." though I doubt that's the real indicator. (If there were two to fail at the same time there would be too many grey circles.)
[JIRA] (JENKINS-58501) Metaprogramming with InvokerHelper and MethodMissing triggers CPS MisMatch log
Title: Message Title Steven Terrana commented on JENKINS-58501 Re: Metaprogramming with InvokerHelper and MethodMissing triggers CPS MisMatch log Hey @jglick, i attempted a patch at this in groovy-cps and opened a PR. https://github.com/cloudbees/groovy-cps/pull/99 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200641.1563219069000.15842.1563485400262%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55981) Execute Scripts on Matrix steps are performed after email is sent
Title: Message Title Alex Earl commented on JENKINS-55981 Re: Execute Scripts on Matrix steps are performed after email is sent There really isn't a way to specify that certain post-build steps will execute in any specific order. This is not something that email-ext can control. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197393.1549390098000.15838.1563484860101%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56311) github-coverage-reporter-plugin missing pipeline instructions
Title: Message Title Jack Newcombe resolved as Fixed Jenkins / JENKINS-56311 github-coverage-reporter-plugin missing pipeline instructions Change By: Jack Newcombe Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197879.1551213782000.15807.1563484020881%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56311) github-coverage-reporter-plugin missing pipeline instructions
Title: Message Title Jack Newcombe commented on JENKINS-56311 Re: github-coverage-reporter-plugin missing pipeline instructions The above PR has now been merged. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197879.1551213782000.15801.1563484020507%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55388) multibranch pipeline deleting history and building unexpectedly
Title: Message Title Sudheer Gundanna edited a comment on JENKINS-55388 Re: multibranch pipeline deleting history and building unexpectedly This happened again today [July-18-2019]for me. Master branch all previous builds were removed and started building from #1. Is there any resolution for this issue? this is so frustrating. It has happened 5 times before.Jenkins version we are using is 2.164.2 GitHub plugin: 1.29.4 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196496.1546519053000.15745.1563480420221%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55388) multibranch pipeline deleting history and building unexpectedly
Title: Message Title Sudheer Gundanna commented on JENKINS-55388 Re: multibranch pipeline deleting history and building unexpectedly This happened again today [July-18-2019]for me. Master branch all previous builds were removed and started building from #1. Is there any resolution for this issue? this is so frustrating. It has happened 5 times before. Jenkins version we are using is 2.164.2 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196496.1546519053000.15736.1563480060358%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54121) Renaming jobs casue Jenkins crash
Title: Message Title
Alexey Grigorov edited a comment on JENKINS-54121
Re: Renaming jobs casue Jenkins crash
Hi [~danielbeck]I have same issue, jenkins 2.176.1, user tried to rename a folder containing 2 millions filesjenkins heap of 31 Gb become full and jenkins died in gc trace is { noformat code:java }"Handling POST /job/Avolin/job/Tradebeam/job/GTM-2/confirmRename from 10.212.255.245 : qtp1254526270-61611" #61611 prio=5 os_prio=0 tid=0x7f60801c6800 nid=0x3ee0 runnable [0x7f601d863000]"Handling POST /job/Avolin/job/Tradebeam/job/GTM-2/confirmRename from 10.212.255.245 : qtp1254526270-61611" #61611 prio=5 os_prio=0 tid=0x7f60801c6800 nid=0x3ee0 runnable [0x7f601d863000] java.lang.Thread.State: RUNNABLE at java.util.HashMap.putVal(HashMap.java:631) at java.util.HashMap.put(HashMap.java:612) at org.apache.tools.ant.util.LinkedHashtable.put(LinkedHashtable.java:110) - locked <0x7f624dfde3e0> (a org.apache.tools.ant.util.LinkedHashtable) at org.apache.tools.ant.taskdefs.Copy.buildMap(Copy.java:788) at org.apache.tools.ant.taskdefs.Copy.scan(Copy.java:735) at org.apache.tools.ant.taskdefs.Copy.iterateOverBaseDirs(Copy.java:660) at org.apache.tools.ant.taskdefs.Copy.execute(Copy.java:559) at hudson.model.AbstractItem.renameTo(AbstractItem.java:423) - locked <0x7f621d7a18f8> (a com.cloudbees.hudson.plugins.folder.Folder) - locked <0x7f6216b530b0> (a com.cloudbees.hudson.plugins.folder.Folder) at com.cloudbees.hudson.plugins.folder.AbstractFolder.renameTo(AbstractFolder.java:1305) at hudson.model.AbstractItem.doConfirmRename(AbstractItem.java:264) at java.lang.invoke.LambdaForm$DMH/769287236.invokeVirtual_LL_L(LambdaForm$DMH) at java.lang.invoke.LambdaForm$BMH/1605795346.reinvoke(LambdaForm$BMH) at java.lang.invoke.LambdaForm$MH/21979174.invoker(LambdaForm$MH) at java.lang.invoke.LambdaForm$MH/29329.invokeExact_MT(LambdaForm$MH) at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627) at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:396) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:408) at org.kohsuke.stapler.interceptor.RequirePOST$Processor.invoke(RequirePOST.java:77) at org.kohsuke.stapler.PreInvokeInterceptedFunction.invoke(PreInvokeInterceptedFunction.java:26) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:212) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:145) at org.kohsuke.stapler.MetaClass$11.doDispatch(MetaClass.java:535) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878) { noformat code }here is a shot from MAT , report archive attached!image-2019-07-18-22-42-26-771.png!
Add Comment
[JIRA] (JENKINS-54121) Renaming jobs casue Jenkins crash
Title: Message Title Alexey Grigorov commented on JENKINS-54121 Re: Renaming jobs casue Jenkins crash Hi Daniel Beck I have same issue, jenkins 2.176.1, user tried to rename a folder containing 2 millions files jenkins heap of 31 Gb become full and jenkins died in gc trace is "Handling POST /job/Avolin/job/Tradebeam/job/GTM-2/confirmRename from 10.212.255.245 : qtp1254526270-61611" #61611 prio=5 os_prio=0 tid=0x7f60801c6800 nid=0x3ee0 runnable [0x7f601d863000]"Handling POST /job/Avolin/job/Tradebeam/job/GTM-2/confirmRename from 10.212.255.245 : qtp1254526270-61611" #61611 prio=5 os_prio=0 tid=0x7f60801c6800 nid=0x3ee0 runnable [0x7f601d863000] java.lang.Thread.State: RUNNABLE at java.util.HashMap.putVal(HashMap.java:631) at java.util.HashMap.put(HashMap.java:612) at org.apache.tools.ant.util.LinkedHashtable.put(LinkedHashtable.java:110) - locked <0x7f624dfde3e0> (a org.apache.tools.ant.util.LinkedHashtable) at org.apache.tools.ant.taskdefs.Copy.buildMap(Copy.java:788) at org.apache.tools.ant.taskdefs.Copy.scan(Copy.java:735) at org.apache.tools.ant.taskdefs.Copy.iterateOverBaseDirs(Copy.java:660) at org.apache.tools.ant.taskdefs.Copy.execute(Copy.java:559) at hudson.model.AbstractItem.renameTo(AbstractItem.java:423) - locked <0x7f621d7a18f8> (a com.cloudbees.hudson.plugins.folder.Folder) - locked <0x7f6216b530b0> (a com.cloudbees.hudson.plugins.folder.Folder) at com.cloudbees.hudson.plugins.folder.AbstractFolder.renameTo(AbstractFolder.java:1305) at hudson.model.AbstractItem.doConfirmRename(AbstractItem.java:264) at java.lang.invoke.LambdaForm$DMH/769287236.invokeVirtual_LL_L(LambdaForm$DMH) at java.lang.invoke.LambdaForm$BMH/1605795346.reinvoke(LambdaForm$BMH) at java.lang.invoke.LambdaForm$MH/21979174.invoker(LambdaForm$MH) at java.lang.invoke.LambdaForm$MH/29329.invokeExact_MT(LambdaForm$MH) at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627) at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:396) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:408) at org.kohsuke.stapler.interceptor.RequirePOST$Processor.invoke(RequirePOST.java:77) at org.kohsuke.stapler.PreInvokeInterceptedFunction.invoke(PreInvokeInterceptedFunction.java:26) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:212) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:145) at org.kohsuke.stapler.MetaClass$11.doDispatch(MetaClass.java:535) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878) here is a shot from MAT , report archive attached
[JIRA] (JENKINS-54121) Renaming jobs casue Jenkins crash
Title: Message Title Alexey Grigorov reopened an issue Jenkins / JENKINS-54121 Renaming jobs casue Jenkins crash Change By: Alexey Grigorov Resolution: Incomplete Status: Closed Reopened Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194748.1539771324000.15730.1563479280346%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54121) Renaming jobs casue Jenkins crash
Title: Message Title Alexey Grigorov updated an issue Jenkins / JENKINS-54121 Renaming jobs casue Jenkins crash Change By: Alexey Grigorov Attachment: heapdump07-18-19_12_36_Leak_Suspects.zip Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194748.1539771324000.15724.1563479160169%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58563) Restrict Pipeline submitter from deploying to Dev
Title: Message Title SRIKANTH RAVIPATI updated an issue Jenkins / JENKINS-58563 Restrict Pipeline submitter from deploying to Dev Change By: SRIKANTH RAVIPATI Component/s: pipeline Component/s: parameterized-trigger-plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200713.1563478551000.15722.1563478980220%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54121) Renaming jobs casue Jenkins crash
Title: Message Title Alexey Grigorov updated an issue Jenkins / JENKINS-54121 Renaming jobs casue Jenkins crash Change By: Alexey Grigorov Attachment: image-2019-07-18-22-42-26-771.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194748.1539771324000.15721.1563478980205%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58563) Restrict Pipeline submitter from deploying to Dev
Title: Message Title SRIKANTH RAVIPATI commented on JENKINS-58563 Re: Restrict Pipeline submitter from deploying to Dev If a user4 logs in to jenkins and try to build this pipeline the step should through an error saying user cancelled as user4 is not defined in the submitter parameter. how do i make this work? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200713.1563478551000.15718.1563478920117%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58563) Restrict Pipeline submitter from deploying to Dev
Title: Message Title
SRIKANTH RAVIPATI updated an issue
Jenkins / JENKINS-58563
Restrict Pipeline submitter from deploying to Dev
Change By:
SRIKANTH RAVIPATI
stage('ApprovalStep'){stage('ApprovalStep'){ when{ _expression_ \{ BRANCH_NAME == 'master' } } steps{ script{ def IS_APPROVED = input( message: "Approve Deployment?" ok: "Deploy" submitter: "user1,user2,user3" parameters [ string(name: 'IS_APPROVED', defaultValue: 'Deploy', description: 'Deploy to master?') ] if((params.Selected_Env)=='master') { echo 'Production' echo " workspace ${PWD}" sh "${run_cmd} ${run_cmd_option} ${run_cmd_option_mule} -P arm -Dmule.version=${run_mule_version_prod_01_val} -Dtarget=${run_target_prod_01} -Dtarget.type=${run_target_value_01} -Dusername=${deploy_un} -Dpassword=${deploy_un_pwd} -Denvironment=Prod" } ) if (IS_APPROVED != 'Deploy') { currentBuild.result = "ABORTED" error "User cancelled" } } } }
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received
[JIRA] (JENKINS-58563) Restrict Pipeline submitter from deploying to Dev
Title: Message Title SRIKANTH RAVIPATI created an issue Jenkins / JENKINS-58563 Restrict Pipeline submitter from deploying to Dev Issue Type: Task Assignee: Unassigned Components: parameterized-trigger-plugin Created: 2019-07-18 19:35 Environment: Dev Priority: Minor Reporter: SRIKANTH RAVIPATI Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-57848) Jenkins Multipipeline jobs discards old builds and starts from build one
Title: Message Title Sudheer Gundanna commented on JENKINS-57848 Re: Jenkins Multipipeline jobs discards old builds and starts from build one This issue happened again. Jenkins master automatically removed all the history and artifacts from master branch and retriggered the build and set it to build number 1. Jenkins version: 2.164.2 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199806.1559671112000.15706.1563477480047%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58562) Support I3EN instance type
Title: Message Title kathir kalimuthu updated an issue Jenkins / JENKINS-58562 Support I3EN instance type Change By: kathir kalimuthu Issue Type: Task Improvement Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200712.1563477028000.15705.1563477060188%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58562) Support I3EN instance type
Title: Message Title kathir kalimuthu created an issue Jenkins / JENKINS-58562 Support I3EN instance type Issue Type: Task Assignee: Unassigned Components: ec2-plugin Created: 2019-07-18 19:10 Labels: jenkins ec2-plugin i3en AWS Priority: Major Reporter: kathir kalimuthu Not possible to launch I3EN instances that is launched few months ago. Add Comment
[JIRA] (JENKINS-58561) Seeing issue when i tried to push an image to ECR using docker pipeline plugin
Title: Message Title
rama golla updated an issue
Jenkins / JENKINS-58561
Seeing issue when i tried to push an image to ECR using docker pipeline plugin
Change By:
rama golla
Docker pipeline version:1.17Below is the code i am using in jenkins file``` withDockerRegistry(credentialsId: 'ecr:us-west-2:devecrcredentials', url: 'https://xx.dkr.ecr.us-west-2.amazonaws.com') { sh """ echo "Delete old docker images in ECR" aws ecr batch-delete-image --region us-west-2 --profile nonprod --repository-name media_dev --debug --image-ids "\$(aws ecr list-images --region us-west-2 --repository-name media_dev --profile nonprod --query 'imageIds[*]' --output json)" || true docker tag ${PROJECT_NAME}_${PROJECT_ENV}_${BUILD_NUMBER}:${VERSION} ${ECR_REPO_DEV}:${VERSION}_${PROJECT_ENV} docker push ${ECR_REPO_DEV}:${VERSION}_${PROJECT_ENV} """ } } ``` getting below error but this error is on and off meaning sometimes build is getting successful without below error ``` java.net.SocketException: Connection reset at java.net.SocketInputStream.read(SocketInputStream.java:210) at java.net.SocketInputStream.read(SocketInputStream.java:141) at sun.security.ssl.InputRecord.readFully(InputRecord.java:465) at sun.security.ssl.InputRecord.read(InputRecord.java:503) at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:983) at sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1385) at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1413) at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1397) at org.apache.http.conn.ssl.SSLConnectionSocketFactory.createLayeredSocket(SSLConnectionSocketFactory.java:396) at org.apache.http.conn.ssl.SSLConnectionSocketFactory.connectSocket(SSLConnectionSocketFactory.java:355) at com.amazonaws.http.conn.ssl.SdkTLSSocketFactory.connectSocket(SdkTLSSocketFactory.java:142) at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:142) at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:373) at sun.reflect.GeneratedMethodAccessor3949.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at com.amazonaws.http.conn.ClientConnectionManagerFactory$Handler.invoke(ClientConnectionManagerFactory.java:76) at com.amazonaws.http.conn.$Proxy143.connect(Unknown Source) at org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:381) at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:237) at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:185) at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:185) at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:83) at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:56) at
[JIRA] (JENKINS-58561) Seeing issue when i tried to push an image to ECR using docker pipeline plugin
Title: Message Title
rama golla updated an issue
Jenkins / JENKINS-58561
Seeing issue when i tried to push an image to ECR using docker pipeline plugin
Change By:
rama golla
Docker pipeline version:1.17Below is the code i am using in jenkins file```withDockerRegistry(credentialsId: 'ecr:us-west-2:devecrcredentials', url: 'https:// 757289378104 xx .dkr.ecr.us-west-2.amazonaws.com') {sh """echo "Delete old docker images in ECR"aws ecr batch-delete-image --region us-west-2 --profile nonprod --repository-name media_dev --debug --image-ids "\$(aws ecr list-images --region us-west-2 --repository-name media_dev --profile nonprod --query 'imageIds[*]' --output json)" || true docker tag ${PROJECT_NAME}_${PROJECT_ENV}_${BUILD_NUMBER}:${VERSION} ${ECR_REPO_DEV}:${VERSION}_${PROJECT_ENV} docker push ${ECR_REPO_DEV}:${VERSION}_${PROJECT_ENV}"""}}``` getting below error```java.net.SocketException: Connection reset at java.net.SocketInputStream.read(SocketInputStream.java:210) at java.net.SocketInputStream.read(SocketInputStream.java:141) at sun.security.ssl.InputRecord.readFully(InputRecord.java:465) at sun.security.ssl.InputRecord.read(InputRecord.java:503) at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:983) at sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1385) at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1413) at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1397) at org.apache.http.conn.ssl.SSLConnectionSocketFactory.createLayeredSocket(SSLConnectionSocketFactory.java:396) at org.apache.http.conn.ssl.SSLConnectionSocketFactory.connectSocket(SSLConnectionSocketFactory.java:355) at com.amazonaws.http.conn.ssl.SdkTLSSocketFactory.connectSocket(SdkTLSSocketFactory.java:142) at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:142) at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:373) at sun.reflect.GeneratedMethodAccessor3949.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at com.amazonaws.http.conn.ClientConnectionManagerFactory$Handler.invoke(ClientConnectionManagerFactory.java:76) at com.amazonaws.http.conn.$Proxy143.connect(Unknown Source) at org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:381) at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:237) at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:185) at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:185) at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:83) at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:56) at com.amazonaws.http.apache.client.impl.SdkHttpClient.execute(SdkHttpClient.java:72) at
[JIRA] (JENKINS-58561) Seeing issue when i tried to push an image to ECR using docker pipeline plugin
Title: Message Title
rama golla created an issue
Jenkins / JENKINS-58561
Seeing issue when i tried to push an image to ECR using docker pipeline plugin
Issue Type:
Task
Assignee:
Nicolas De Loof
Attachments:
error.PNG
Components:
docker-plugin
Created:
2019-07-18 17:58
Priority:
Major
Reporter:
rama golla
Docker pipeline version:1.17 Below is the code i am using in jenkins file ``` withDockerRegistry(credentialsId: 'ecr:us-west-2:devecrcredentials', url: 'https://757289378104.dkr.ecr.us-west-2.amazonaws.com') { sh """ echo "Delete old docker images in ECR" aws ecr batch-delete-image --region us-west-2 --profile nonprod --repository-name media_dev --debug --image-ids "\$(aws ecr list-images --region us-west-2 --repository-name media_dev --profile nonprod --query 'imageIds[*]' --output json)" || true docker tag ${PROJECT_NAME}${PROJECT_ENV}${BUILD_NUMBER}:${VERSION} ${ECR_REPO_DEV}:${VERSION}_${PROJECT_ENV} docker push ${ECR_REPO_DEV}:${VERSION}_${PROJECT_ENV} """ } } ``` getting below error ``` java.net.SocketException: Connection reset at java.net.SocketInputStream.read(SocketInputStream.java:210) at java.net.SocketInputStream.read(SocketInputStream.java:141) at sun.security.ssl.InputRecord.readFully(InputRecord.java:465) at sun.security.ssl.InputRecord.read(InputRecord.java:503) at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:983) at sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1385) at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1413) at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1397) at org.apache.http.conn.ssl.SSLConnectionSocketFactory.createLayeredSocket(SSLConnectionSocketFactory.java:396) at
[JIRA] (JENKINS-58560) deleting "other view" of an "Other Views Filter" results in "no such vertex in graph" exception
Title: Message Title Chris Burroughs created an issue Jenkins / JENKINS-58560 deleting "other view" of an "Other Views Filter" results in "no such vertex in graph" exception Issue Type: Bug Assignee: Sven Schoenung Components: view-job-filters-plugin Created: 2019-07-18 17:52 Environment: view-job-filters:2.1.1 Reproduced with both Jenkins 2.176.2 and master (59cd46988074a6796988dba7971e8746ce3cfb79) Priority: Minor Reporter: Chris Burroughs Create a view with any name (I called it "another-view-with-a" in the stack trace below).. For example, it could be a view that lists a single job"A". Create another view with "Other Views Filter" excluding the above view (In my example called "not-A") Delete the first view Viewing the 2nd view now results in "An error occurred when retrieving jobs for this view. Please consult the Jenkins logs for details.". The only method I found to get out of this situation was to stop jenkins and manually edit config.xml. Stack trace 019-07-18 17:40:18.765+ [id=10] WARNING h.ExpressionFactory2$JexlExpression#evaluate: Caught exception evaluating: it.items in /view/not-A/. Reason: java.lang.reflect.InvocationTargetException java.lang.IllegalArgumentException: no such vertex in graph: another-view-with-a at
[JIRA] (JENKINS-58339) Support new types of credentials
Title: Message Title Mathew Peterson edited a comment on JENKINS-58339 Re: Support new types of credentials Hello,I first wanted to say thank you for putting this plugin together.Secondly, this implementation is different than how we have tried to solve this so, maybe my suggestion is incompatible.We are using a very crude method to handle pulling secrets from AWS Secrets Manager and creating the Jenkins Credentials for them. Our solution is to create a file ( ` " init.groovy.d/credential-x.groovy ` " ) which executes aws cli command to retrieve the secret value for the supplied secret ARN. This file is generated from an Ansible template where we pass in the credential name and ARN, such that there exists one file per credential. In Ansible we have different templates for the different credential implementations, e.g. ` " AWSCredentialsImpl ` " , ` " StringCredentialsImpl ` " , ` " BasicSSHUserPrivateKey ` " , etc. The downside to this is that the secret is only updated once Jenkins reboots or the script gets ran manual via Script Console or similar. To restate, we have a specific ARN mapped to a specific Credential Implementation.Again, I know this is somewhat at odds to this plugin implementation but I think it could be beneficial to allow the end user to create the mappings of ARN and then have a schema for each Implementation. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200452.1562229894000.15676.1563470940133%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58501) Metaprogramming with InvokerHelper and MethodMissing triggers CPS MisMatch log
Title: Message Title Jesse Glick commented on JENKINS-58501 Re: Metaprogramming with InvokerHelper and MethodMissing triggers CPS MisMatch log With workflow-cps #306, probably falls on me or Devin Nusbaum to play with a groovy-cps patch that would resolve the issue. One thing I should have done initially, but neglected to, was write unit tests in groovy-cps for this. Quicker to iterate than the full functional tests in workflow-cps, though we need at least some of those as well, since “things happen” when a library is being used in a complex context. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200641.1563219069000.15608.1563469380176%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53767) Offer plugin management tooling
Title: Message Title Jesse Glick commented on JENKINS-53767 Re: Offer plugin management tooling JENKINS-47498 might be a better input source, as the list of plugins would actually be mechanically vetted, not merely the latest on offer. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194275.1537882941000.15594.1563468670743%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58339) Support new types of credentials
Title: Message Title Mathew Peterson commented on JENKINS-58339 Re: Support new types of credentials Hello, I first wanted to say thank you for putting this plugin together. Secondly, this implementation is different than how we have tried to solve this so, maybe my suggestion is incompatible. We are using a very crude method to handle pulling secrets from AWS Secrets Manager and creating the Jenkins Credentials for them. Our solution is to create a file (`init.groovy.d/credential-x.groovy`) which executes aws cli command to retrieve the secret value for the supplied secret ARN. This file is generated from an Ansible template where we pass in the credential name and ARN, such that there exists one file per credential. In Ansible we have different templates for the different credential implementations, e.g. `AWSCredentialsImpl`, `StringCredentialsImpl`, `BasicSSHUserPrivateKey`, etc. The downside to this is that the secret is only updated once Jenkins reboots or the script gets ran manual via Script Console or similar. To restate, we have a specific ARN mapped to a specific Credential Implementation. Again, I know this is somewhat at odds to this plugin implementation but I think it could be beneficial to allow the end user to create the mappings of ARN and then have a schema for each Implementation. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200452.1562229894000.15590.1563468600120%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58558) Show "Run build steps in a container" from Kubernetes plugin
Title: Message Title Edimar Cardoso commented on JENKINS-58558 Re: Show "Run build steps in a container" from Kubernetes plugin PR https://github.com/jenkinsci/blueocean-plugin/pull/2009 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200708.1563467237000.15588.1563467520043%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58559) Incrementals URL missing plugin name
Title: Message Title Alex Earl created an issue Jenkins / JENKINS-58559 Incrementals URL missing plugin name Issue Type: Bug Assignee: Natasha Stopa Components: plugin-installation-manager-tool Created: 2019-07-18 16:29 Priority: Minor Reporter: Alex Earl With the following line in a plugins.txt file: workflow-support:incrementals;org.jenkins-ci.plugins.workflow;2.19-rc289.d09828a05a74 The following URL is being used for the plugin download: https://repo.jenkins-ci.org/incrementals/org/jenkins-ci/plugins/workflow/2.19-rc289.d09828a05a74/workflow-support-2.19-rc289.d09828a05a74.hpi The actual URL should be: https://repo.jenkins-ci.org/incrementals/org/jenkins-ci/plugins/workflow/*workflow-support*/2.19-rc289.d09828a05a74/workflow-support-2.19-rc289.d09828a05a74.hpi The workflow-support is missing from after the groupId/artifactId info. Add Comment
[JIRA] (JENKINS-51254) Incrementalify plugin archetypes
Title: Message Title Jesse Glick resolved as Duplicate Jenkins / JENKINS-51254 Incrementalify plugin archetypes Change By: Jesse Glick Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.190579.1525984033000.15584.1563467280261%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58558) Show "Run build steps in a container" from Kubernetes plugin
Title: Message Title Edimar Cardoso updated an issue Jenkins / JENKINS-58558 Show "Run build steps in a container" from Kubernetes plugin Change By: Edimar Cardoso Attachment: Screenshot from 2019-07-18 12-12-31.png Attachment: Screenshot from 2019-07-18 12-12-16.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200708.1563467237000.15585.1563467280273%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58558) Show "Run build steps in a container" from Kubernetes plugin
Title: Message Title
Edimar Cardoso created an issue
Jenkins / JENKINS-58558
Show "Run build steps in a container" from Kubernetes plugin
Issue Type:
New Feature
Assignee:
Unassigned
Attachments:
Screenshot from 2019-07-18 12-12-16.png, Screenshot from 2019-07-18 12-12-31.png
Components:
blueocean-pipeline-editor-plugin
Created:
2019-07-18 16:27
Priority:
Minor
Reporter:
Edimar Cardoso
Show "Run build steps in a container" from Kubernetes plugin
stage('Run maven') {
steps {
sh 'set'
sh 'test -f /usr/bin/mvn' // checking backwards compatibility
sh "echo OUTSIDE_CONTAINER_ENV_VAR = ${CONTAINER_ENV_VAR}"
container('maven') {
sh 'echo INSIDE_CONTAINER_ENV_VAR = ${CONTAINER_ENV_VAR}'
sh 'mvn -version'
}
}
}
Example: https://github.com/jenkinsci/kubernetes-plugin/blob/master/src/test/resources/org/csanchez/jenkins/plugins/kubernetes/pipeline/declarative.groovy
[JIRA] (JENKINS-58557) Separate @jenkinsci-specific archetype
Title: Message Title Jesse Glick created an issue Jenkins / JENKINS-58557 Separate @jenkinsci-specific archetype Issue Type: New Feature Assignee: Unassigned Components: archetypes Created: 2019-07-18 16:26 Priority: Major Reporter: Jesse Glick Split empty-plugin into a truly generic one (no scm section or url); and then add a new (empty) archetype specifically for @jenkinsci-hosted plugins where we can preconfigure things like scm ur → wiki.jenkins.io, plus whatever new metadata might get added in JENKINS-45740 Release Drafter Dependabot (esp. if JENKINS-47498 pans out) Incrementals (JEP-305) img.shields.io badges to follow current best practices. Add Comment
[JIRA] (JENKINS-52946) Attempt to (de-)serialize anonymous class org.jenkinsci.plugins.envinject.EnvInjectComputerListener$2
Title: Message Title Amol Bhatia updated an issue Jenkins / JENKINS-52946 Attempt to (de-)serialize anonymous class org.jenkinsci.plugins.envinject.EnvInjectComputerListener$2 Change By: Amol Bhatia Comment: [~tgd0n0hue] Can you please share your old slave.jar file with me? I do not have any backup and the fix by [~jsoref] is still in unreleased state. Is there any other workaround, I can use for this issue meanwhile? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.192918.1533767555000.15568.1563467040561%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58556) Comments on same line as plugin info cause invalid URL
Title: Message Title Alex Earl created an issue Jenkins / JENKINS-58556 Comments on same line as plugin info cause invalid URL Issue Type: Bug Assignee: Natasha Stopa Components: plugin-installation-manager-tool Created: 2019-07-18 16:16 Priority: Minor Reporter: Alex Earl A plugin file with something like this: filesystem_scm:experimental # comment at the end Causes the tool to try to download from the following URL: https://updates.jenkins.io/download/plugins/filesystem_scm-plugin/experimental#commentattheend/filesystem_scm-plugin.hpi You can see the #commentattheend that gets included in the URL. Add Comment
[JIRA] (JENKINS-57154) Regression in github-oauth-plugin 0.32 breaks /configureSecurity page
Title: Message Title Christian Höltje commented on JENKINS-57154 Re: Regression in github-oauth-plugin 0.32 breaks /configureSecurity page Doing some googling... The has_recent_activity=1 cookie seems to be coming from GitHub. I suspect that the cookie parser being used by Jenkins is broken. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198903.1556022985000.15523.1563465120902%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58450) CHANGE_FORK doesn't point to the user/repo when the fork name differs from the upstream name
Title: Message Title Liam Newman updated an issue Jenkins / JENKINS-58450 CHANGE_FORK doesn't point to the user/repo when the fork name differs from the upstream name Change By: Liam Newman Summary: CHANGE_FORK doesn't point out to the user/repo when the fork name differs from the upstream name Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200582.156287771.15520.1563464160373%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57154) Regression in github-oauth-plugin 0.32 breaks /configureSecurity page
Title: Message Title Christian Höltje commented on JENKINS-57154 Re: Regression in github-oauth-plugin 0.32 breaks /configureSecurity page I have the same issue. To reproduce: Goto $JENKINS_URL/manage Goto $JENKINS_URL/configureSecurity Press "Reload" or click the "Configure Global Security" and you get a traceback saying anonymous doesn't have the right permissions. If you get the "Retry with POST" page and you look at the networking console, you'll see that it actually re-logged you in by visiting github and coming back. That's why the POST got converted to a GET. As above, I get these log entries everytime: Jul 18, 2019 11:20:33 AM hudson.util.Secret toString WARNING: Use of toString() on hudson.util.Secret from java.lang.String.valueOf(String.java:2994). Prefer getPlainText() or getEncryptedValue() depending your needs. see https://jenkins.io/redirect/hudson.util.Secret/ Jul 18, 2019 11:20:34 AM org.apache.http.client.protocol.ResponseProcessCookies processCookies WARNING: Invalid cookie header: "Set-Cookie: has_recent_activity=1; path=/; expires=Thu, 18 Jul 2019 16:20:34 -". Invalid 'expires' attribute: Thu, 18 Jul 2019 16:20:34 - This is the full traceback mentioned above: org.apache.commons.jelly.JellyTagException: jar:file:/var/lib/jenkins/war/WEB-INF/lib/jenkins-core-2.176.2.jar!/lib/layout/view.jelly:39:20: anonymous is missing the Overall/Administer permission at org.apache.commons.jelly.impl.TagScript.handleException(TagScript.java:726) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:281) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120) at org.kohsuke.stapler.jelly.groovy.JellyBuilder.doInvokeMethod(JellyBuilder.java:276) at org.kohsuke.stapler.jelly.groovy.Namespace$ProxyImpl.invoke(Namespace.java:92) at com.sun.proxy.$Proxy108.layout(Unknown Source) at lib.LayoutTagLib$layout.call(Unknown Source) at hudson.security.GlobalSecurityConfiguration.index.run(index.groovy:15) at org.kohsuke.stapler.jelly.groovy.GroovierJellyScript.run(GroovierJellyScript.java:74) at org.kohsuke.stapler.jelly.groovy.GroovierJellyScript.run(GroovierJellyScript.java:62) at org.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:63) at org.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:53) at org.kohsuke.stapler.jelly.ScriptInvoker.execute(ScriptInvoker.java:56) at org.kohsuke.stapler.jelly.ScriptInvoker.execute(ScriptInvoker.java:43) at
[JIRA] (JENKINS-58555) Ansible Plugin CredentialsID Overriden by ansible_ssh_key variable
Title: Message Title
Dimas Rizky updated an issue
Jenkins / JENKINS-58555
Ansible Plugin CredentialsID Overriden by ansible_ssh_key variable
Change By:
Dimas Rizky
So, in my private ansible repository, I have define `all` variables in each inventory group_vars. In those `all` group_vars I defined `ansible_ssh_key` to keys to other directory in same repository. Since I save it up on my git repo I'm not uploading my key files content, there's only placeholder for it, and to use it I manually copy the key content to the ansible controller after I clone the repositoryThe problem comes when I use jenkins to run my playbook, since I'm using k8s jenkins plugin, the executor will only spawned whenever the jobs get queued, and before I can ran my playbook, I have to clone my ansible repository. Which means the executor will only have my cloned ansible repository with `empty placeholder key` file. Since ansible plugin is providing `credentialsId` for the ssh access, I think it should just go fine, because the provided credentials will be used instead of my self declared `ansible_ssh_key`. But i was wrong, the key that is being used is the one I define on `ansible_ssh_key` variables.My question is, is this expected behaviour ? Or there's something that I missing here ? Pls pardon me with my long explanation just to ask such simple question. Thanks gentlementThis is how I invoke the stage to clone & run the playbook : { {pipeline{ code:java } } pipeline { { agent \ { label 'Jenkins-slave' } }} {{ stages { }} {{ stage('Clone Ansible'){ }} {{ steps { }} {{ echo 'Cloning Ansible to ansible' }} {{ git changelog: false, credentialsId: 'buildbot-pk', poll: false, url: 'g...@github.com:myrepo/ansible.git' }}{{}} {{ } }} {{ } }} {{ stage('Run Ansible'){ }} {{ steps { }}{{}}{{}} {{ ansiblePlaybook colorized: true, credentialsId: 'root-production', disableHostKeyChecking: true, inventory: 'myinventory', playbook: 'myplaybook.yml', tags: 'mytag' }} {{ } }} {{ } }} {{ } }} } { { code } }}
Add Comment
[JIRA] (JENKINS-58555) Ansible Plugin CredentialsID Overriden by ansible_ssh_key variable
Title: Message Title
Dimas Rizky updated an issue
Jenkins / JENKINS-58555
Ansible Plugin CredentialsID Overriden by ansible_ssh_key variable
Change By:
Dimas Rizky
So, in my private ansible repository, I have define `all` variables in each inventory group_vars. In those `all` group_vars I defined `ansible_ssh_key` to keys to other directory in same repository. Since I save it up on my git repo I'm not uploading my key files content, there's only placeholder for it, and to use it I manually copy the key content to the ansible controller after I clone the repositoryThe problem comes when I use jenkins to run my playbook, since I'm using k8s jenkins plugin, the executor will only spawned whenever the jobs get queued, and before I can ran my playbook, I have to clone my ansible repository. Which means the executor will only have my cloned ansible repository with `empty placeholder key` file. Since ansible plugin is providing `credentialsId` for the ssh access, I think it should just go fine, because the provided credentials will be used instead of my self declared `ansible_ssh_key`. But i was wrong, the key that is being used is the one I define on `ansible_ssh_key` variables.My question is, is this expected behaviour ? Or there's something that I missing here ? Pls pardon me with my long explanation just to ask such simple question. Thanks gentlementThis is how I invoke the stage to clone & run the playbook : {code:java}pipeline{agent { label 'Jenkins-slave' }stages {stage('Clone Ansible'){steps {echo 'Cloning Ansible to ansible'git changelog: false, credentialsId: 'buildbot-pk', poll: false, url: 'g...@github.com:myrepo/ansible.git'}}stage('Run Ansible'){steps {ansiblePlaybook colorized: true, credentialsId: 'root-production', disableHostKeyChecking: true, inventory: 'myinventory', playbook: 'myplaybook.yml', tags: 'mytag'}}}}{code}
Add Comment
[JIRA] (JENKINS-58555) Ansible Plugin CredentialsID Overriden by ansible_ssh_key variable
Title: Message Title
Dimas Rizky updated an issue
Jenkins / JENKINS-58555
Ansible Plugin CredentialsID Overriden by ansible_ssh_key variable
Change By:
Dimas Rizky
So, in my private ansible repository, I have define `all` variables in each inventory group_vars. In those `all` group_vars I defined `ansible_ssh_key` to keys to other directory in same repository. Since I save it up on my git repo I'm not uploading my key files content, there's only placeholder for it, and to use it I manually copy the key content to the ansible controller after I clone the repositoryThe problem comes when I use jenkins to run my playbook, since I'm using k8s jenkins plugin, the executor will only spawned whenever the jobs get queued, and before I can ran my playbook, I have to clone my ansible repository. Which means the executor will only have my cloned ansible repository with `empty placeholder key` file. Since ansible plugin is providing `credentialsId` for the ssh access, I think it should just go fine, because the provided credentials will be used instead of my self declared `ansible_ssh_key`. But i was wrong, the key that is being used is the one I define on `ansible_ssh_key` variables. My question is, * is this expected behaviour * ? Or there's something that I missing here ? Pls pardon me with my long explanation just to ask such simple question. Thanks gentlement This is how I invoke the stage to clone & run the playbook :{code:java}pipeline{agent { label 'Jenkins-slave' }stages {stage('Clone Ansible'){steps {echo 'Cloning Ansible to ansible'git changelog: false, credentialsId: 'buildbot-pk', poll: false, url: 'g...@github.com:myrepo/ansible.git'}}stage('Run Ansible'){steps {ansiblePlaybook colorized: true, credentialsId: 'root-production', disableHostKeyChecking: true, inventory: 'myinventory', playbook: 'myplaybook.yml', tags: 'mytag'}}}}{code}
Add Comment
[JIRA] (JENKINS-58555) Ansible Plugin CredentialsID Overriden by ansible_ssh_key variable
Title: Message Title
Dimas Rizky created an issue
Jenkins / JENKINS-58555
Ansible Plugin CredentialsID Overriden by ansible_ssh_key variable
Issue Type:
Bug
Assignee:
Jean-Christophe Sirot
Components:
ansible-plugin
Created:
2019-07-18 15:18
Environment:
Jenkins v2.185 running on jenkins-kubernetes-plugin Ansible Plugin v1.0
Priority:
Minor
Reporter:
Dimas Rizky
So, in my private ansible repository, I have define `all` variables in each inventory group_vars. In those `all` group_vars I defined `ansible_ssh_key` to keys to other directory in same repository. Since I save it up on my git repo I'm not uploading my key files content, there's only placeholder for it, and to use it I manually copy the key content to the ansible controller after I clone the repository The problem comes when I use jenkins to run my playbook, since I'm using k8s jenkins plugin, the executor will only spawned whenever the jobs get queued, and before I can ran my playbook, I have to clone my ansible repository. Which means the executor will only have my cloned ansible repository with `empty placeholder key` file. Since ansible plugin is providing `credentialsId` for the ssh access, I think it should just go fine, because the provided credentials will be used instead of my self declared `ansible_ssh_key`. But i was wrong, the key that is being used is the one I define on `ansible_ssh_key` variables. My question is, is this expected behaviour ? Or there's something that I missing here ? Pls pardon me with my long explanation just to ask such simple question. Thanks gentlement This is how I invoke the stage to clone & run the playbook : pipeline{ {{ agent { label 'Jenkins-slave' }}} stages { stage('Clone Ansible'){ steps { echo 'Cloning Ansible to ansible' git
[JIRA] (JENKINS-32996) Jenkins use different RTC Build Toolkit path as the one set in system configure
Title: Message Title Lakshmi Narasimhan Vaikuntam resolved as Not A Defect Given that valid build toolkit is required on the master, not only for builds but also for polling, I am resolving this bug as not a defect. Please note that polling happens only on master. Therefore a valid build toolkit is needed for all configurations for polling to work except snapshot which doesn't support polling. Jenkins / JENKINS-32996 Jenkins use different RTC Build Toolkit path as the one set in system configure Change By: Lakshmi Narasimhan Vaikuntam Status: Reopened Resolved Assignee: Lakshmi Narasimhan Vaikuntam Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed
[JIRA] (JENKINS-58159) 0 warnings found when parsing from file using IAR parser
Title: Message Title Jonathan Delizy commented on JENKINS-58159 Re: 0 warnings found when parsing from file using IAR parser Ulli Hafner You're right, changing the reportEncoding to UTF_16LE fixed it. Thanks a lot for your help. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200209.1561366965000.15468.1563462540398%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53486) email-ext fails when CasC attempts to set smtpHost
Title: Message Title Alex Earl commented on JENKINS-53486 Re: email-ext fails when CasC attempts to set smtpHost Yes, please file a separate issue. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.193954.1536546047000.15462.1563462540269%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58506) Redirect to root url determined from request
Title: Message Title Michael Rush commented on JENKINS-58506 Re: Redirect to root url determined from request Ah, ok. That makes sense. Thanks Vincent! Sorry for the misinformation in my comment. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200649.1563261173000.15459.1563462420269%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58448) History only seems to be pointing to the current build when using Warnings NG jenkin plugin and pipeline
Title: Message Title Ankush Pandit commented on JENKINS-58448 Re: History only seems to be pointing to the current build when using Warnings NG jenkin plugin and pipeline O that make sense. That did fix it. Thanks for your help on this! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200581.1562870523000.15457.1563461880536%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43802) Shared Library using folder-scoped credential fails to authenticate
Title: Message Title Jesse Glick updated JENKINS-43802 Jenkins / JENKINS-43802 Shared Library using folder-scoped credential fails to authenticate Change By: Jesse Glick Status: In Review Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.181318.1493051062000.15429.1563461761773%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57712) Allow entering search path for git blame
Title: Message Title Ulli Hafner commented on JENKINS-57712 Re: Allow entering search path for git blame I'm not sure if a better solution for JENKINS-57260 would be to record the Git repositories of a build and use that information later on. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199653.1559042804000.15424.1563460861494%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57712) Allow entering search path for git blame
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-57712 Allow entering search path for git blame Change By: Ulli Hafner Component/s: git-forensics-plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199653.1559042804000.15426.1563460861677%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57260) git blame fails for out-of-tree builds
Title: Message Title
Ulli Hafner commented on JENKINS-57260
Re: git blame fails for out-of-tree builds
You need to execute the warnings step within the dir('src') block. Otherwise the warnings plugin has no information about the storage of your source files.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199025.1556641885000.15420.1563460620119%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58143) Periodically finish in: Exec Failure: HTTP 401, Status: 401 - Unauthorized
Title: Message Title Jesse Glick commented on JENKINS-58143 Re: Periodically finish in: Exec Failure: HTTP 401, Status: 401 - Unauthorized Discussed in kubernetes #548. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200188.1561129406000.15417.1563460500112%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57556) Path should be stored relative to workspace
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-57556 Path should be stored relative to workspace Change By: Ulli Hafner Issue Type: Bug Improvement Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199467.1558350085000.15415.1563460440093%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57854) With "Warnings Plugin Native Format" tool, the expected input xml is not consistent with the exported xml
Title: Message Title Ulli Hafner resolved as Incomplete Jenkins / JENKINS-57854 With "Warnings Plugin Native Format" tool, the expected input xml is not consistent with the exported xml Change By: Ulli Hafner Status: Open Resolved Resolution: Incomplete Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199813.1559715209000.15414.1563460200249%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58159) 0 warnings found when parsing from file using IAR parser
Title: Message Title Ulli Hafner resolved as Not A Defect Seems that this is an encoding problem, your shell is exporting with UTF_16LE. See https://github.com/jenkinsci/analysis-model/commit/9c551b1ad555f3d482f10aa4ec9d56dcaa843ae2. Jenkins / JENKINS-58159 0 warnings found when parsing from file using IAR parser Change By: Ulli Hafner Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200209.1561366965000.15412.1563460140142%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58554) Workflow parse exception with new approach for unstable stages
Title: Message Title Radek Antoniuk commented on JENKINS-58554 Re: Workflow parse exception with new approach for unstable stages Got it, thanks! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200704.1563458988000.15410.1563459600092%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58554) Workflow parse exception with new approach for unstable stages
Title: Message Title
Devin Nusbaum commented on JENKINS-58554
Re: Workflow parse exception with new approach for unstable stages
Radek Antoniuk try/catch is raw Groovy, you cannot use it in Declarative outside of a script block. Use the warnError or catchError step instead of unstable, as in the first example here:
stage ('Tests: EN'){
steps{
warnError('Tests failed!') {
sh 'HOME=$(pwd) bundle && HOME=$(pwd) LOCALE=en BROWSER=chrome-headless-nogpu cucumber --format json --out reports/en.json'
}
}
}
I will try to update the blog post to explicitly mention that the try/catch example only applies for scripted Pipelines.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200704.1563458988000.15406.1563459361031%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58554) Workflow parse exception with new approach for unstable stages
Title: Message Title Devin Nusbaum closed an issue as Not A Defect Jenkins / JENKINS-58554 Workflow parse exception with new approach for unstable stages Change By: Devin Nusbaum Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200704.1563458988000.15408.1563459361401%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58554) Workflow parse exception with new approach for unstable stages
Title: Message Title Radek Antoniuk commented on JENKINS-58554 Re: Workflow parse exception with new approach for unstable stages Devin Nusbaum any if I'm doing anything wrong in the Declarative definition? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200704.1563458988000.15404.1563459060050%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58554) Workflow parse exception with new approach for unstable stages
Title: Message Title
Radek Antoniuk created an issue
Jenkins / JENKINS-58554
Workflow parse exception with new approach for unstable stages
Issue Type:
Bug
Assignee:
Unassigned
Components:
pipeline
Created:
2019-07-18 14:09
Environment:
Jenkins 2.176.1
Priority:
Minor
Reporter:
Radek Antoniuk
I am following https://jenkins.io/blog/2019/07/05/jenkins-pipeline-stage-result-visualization-improvements/ blogpost to use the new try/catch approach:
stages {
stage ('Tests: EN'){
steps{
try {
sh 'HOME=$(pwd) bundle && HOME=$(pwd) LOCALE=en BROWSER=chrome-headless-nogpu cucumber --format json --out reports/en.json'
}
catch (ex) {
unstable('Tests failed!')
}
}
}
for marking the results unstable but I'm getting:
org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed:
WorkflowScript: 21: Expected a step @ line 21, column 13.
try {
^
WorkflowScript: 32: Expected a step @ line 32, column 13.
try{
^
WorkflowScript: 43: Expected a step @ line 43, column 13.
try{
^
3 errors
at org.codehaus.groovy.control.ErrorCollector.failIfErrors(ErrorCollector.java:310)
at
[JIRA] (JENKINS-58552) .split('.') method works incorrect
Title: Message Title
gek commented on JENKINS-58552
Re: .split('.') method works incorrect
Oh, workaround was to use double backslashes:
script {
RC_FILES = '4,5,6'
println RC_FILES.getClass()
VERSION_TAIL_0 = '1.2.3'
println VERSION_TAIL_0.getClass()
ARRAY01 = RC_FILES.split(",")
ARRAY02 = VERSION_TAIL_0.split('\\.')
ARRAY01.each {
println("$it")
}
ARRAY02.each {
println("$it")
}
}
it was two wasted hours of my life...
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200702.1563458305000.15402.1563458940116%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58167) Add option to not store affected files
Title: Message Title Ulli Hafner assigned an issue to Unassigned Jenkins / JENKINS-58167 Add option to not store affected files Change By: Ulli Hafner Labels: help-wanted newbie-friendly Assignee: Ulli Hafner Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200218.1561384768000.15400.1563458880107%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58383) Disable aggregated analysis results
Title: Message Title Ulli Hafner assigned an issue to Unassigned Jenkins / JENKINS-58383 Disable aggregated analysis results Change By: Ulli Hafner Labels: help-wanted newbie-friendly Assignee: Ulli Hafner Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200507.1562597544000.15398.1563458820115%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58448) History only seems to be pointing to the current build when using Warnings NG jenkin plugin and pipeline
Title: Message Title Ulli Hafner resolved as Not A Defect Jenkins / JENKINS-58448 History only seems to be pointing to the current build when using Warnings NG jenkin plugin and pipeline Change By: Ulli Hafner Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200581.1562870523000.15396.1563458522187%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58553) NullPointerException - getDefaultParameterValue: [ EMPTY_JOB_NAME ] Unexpected error!
Title: Message Title Dilyan Angelov created an issue Jenkins / JENKINS-58553 NullPointerException - getDefaultParameterValue: [ EMPTY_JOB_NAME ] Unexpected error! Issue Type: Bug Assignee: Boguslaw Klimas Components: git-parameter-plugin Created: 2019-07-18 14:01 Environment: OS: CentOS 7 Jenkins ver: 2.186 Plugins ver: git 4.0.0-rc git-client 3.0.0-rc git-parameter 0.9.11 git-server 1.7 Labels: plugin jenkins git Priority: Minor Reporter: Dilyan Angelov Hello, I receive the following error every hour (12:05:00, 13:05:00 etc.) in jenkins.log: jenkins.log 2019-07-18 13:05:00.949+ [id=161] SEVERE n.u.l.h.p.g.GitParameterDefinition#getDefaultParameterValue: [ EMPTY_JOB_NAME ] Unexpected error! java.lang.NullPointerException at net.uaznia.lukanus.hudson.plugins.gitparameter.jobs.JobWrapperFactory.createJobWrapper(JobWrapperFactory.java:15) at net.uaznia.lukanus.hudson.plugins.gitparameter.GitParameterDefinition$DescriptorImpl.doFillValueItems(GitParameterDefinition.java:603) at net.uaznia.lukanus.hudson.plugins.gitparameter.GitParameterDefinition.getDefaultParameterValue(GitParameterDefinition.java:151) at hudson.plugins.git.util.GitUtils.addEnvironmentContributingActionsValues(GitUtils.java:329) at hudson.plugins.git.util.GitUtils.getPollEnvironment(GitUtils.java:306) at hudson.plugins.git.GitSCM.compareRemoteRevisionWithImpl(GitSCM.java:693) at hudson.plugins.git.GitSCM.compareRemoteRevisionWith(GitSCM.java:668) at hudson.scm.SCM.compareRemoteRevisionWith(SCM.java:400) at hudson.scm.SCM.poll(SCM.java:417) at
[JIRA] (JENKINS-58448) History only seems to be pointing to the current build when using Warnings NG jenkin plugin and pipeline
Title: Message Title Ulli Hafner commented on JENKINS-58448 Re: History only seems to be pointing to the current build when using Warnings NG jenkin plugin and pipeline I think I found the problem. In your pipeline you use a variable ID (using the system time). This is wrong you need to use the same ID for all builds, then the results will be correctly mapped. It is clear, if you change the ID in every build then you will never found a sequence of matching builds. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200581.1562870523000.15392.1563458522091%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58552) .split('.') method works incorrect
Title: Message Title
gek created an issue
Jenkins / JENKINS-58552
.split('.') method works incorrect
Issue Type:
Bug
Assignee:
vjuranek
Components:
groovy-plugin, pipeline
Created:
2019-07-18 13:58
Environment:
Jenkins 2.164.1 Pipeline:groovy 2.70
Priority:
Minor
Reporter:
gek
Hello! When i use .slit() method with '.' as delimiter, it's work incorrectly. If i use any other char, like ',' - it's work as expected, but not with '.' Problem code:
script {
RC_FILES = '4,5,6'
println RC_FILES.getClass()
VERSION_TAIL_0 = '1.2.3'
println VERSION_TAIL_0.getClass()
ARRAY01 = RC_FILES.split(",")
ARRAY02 = VERSION_TAIL_0.split('.')
ARRAY01.each {
println("$it")
}
ARRAY02.each {
println("$it")
}
}
Expected output:
[Pipeline] echo
class java.lang.String
[Pipeline] echo
class java.lang.String
[Pipeline] echo
4
[Pipeline] echo
5
[Pipeline] echo
6
[Pipeline] echo
1
[Pipeline] echo
2
[Pipeline] echo
3
Current output:
[Pipeline]
[JIRA] (JENKINS-58551) Add support for Chinese Lunar calendar
Title: Message Title Jack Shen updated an issue Jenkins / JENKINS-58551 Add support for Chinese Lunar calendar Change By: Jack Shen Sprint: GSoC 2019. Coding Phase 2 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200701.1563457668000.15388.1563457980225%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58303) GSoC 2019: Working Hours GSoC 2019 Phase 2
Title: Message Title Jeff Pearce updated an issue Jenkins / JENKINS-58303 GSoC 2019: Working Hours GSoC 2019 Phase 2 Change By: Jeff Pearce Epic Name: GSoC 2019: Working Hours GSoC 2019 Phase 3 2 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200411.1562083067000.15386.1563457920129%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58303) GSoC 2019: Working Hours GSoC 2019 Phase 2
Title: Message Title Jeff Pearce updated an issue Jenkins / JENKINS-58303 GSoC 2019: Working Hours GSoC 2019 Phase 2 Change By: Jeff Pearce Epic Name: GSoC 2019: Working Hours GSoC 2019 Phase 2 3 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200411.1562083067000.15385.1563457920099%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58551) Add support for Chinese Lunar calendar
Title: Message Title Jeff Pearce updated an issue Jenkins / JENKINS-58551 Add support for Chinese Lunar calendar Change By: Jeff Pearce We've settled on using Jollyday for determining holidays, but it doesn't have support for the Chinese lunar calendar, and they've been trying for two years to land a PR that would include it.Separately, I'll try to get that PR to land, but in the meantime, we'll just add support in the plugin, since it's unlikely Jollyday will merge that PR before the end of GSoC Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200701.1563457668000.15384.1563457860106%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58551) Add support for Chinese Lunar calendar
Title: Message Title Jeff Pearce created an issue Jenkins / JENKINS-58551 Add support for Chinese Lunar calendar Issue Type: Task Assignee: Jack Shen Components: working-hours-plugin Created: 2019-07-18 13:47 Labels: gsoc-2019 Priority: Minor Reporter: Jeff Pearce Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To
[JIRA] (JENKINS-56292) Job launching parameterized build on other project fails
Title: Message Title Tom Weeks commented on JENKINS-56292 Re: Job launching parameterized build on other project fails can reproduce on 2.167 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197871.1551195199000.15382.1563457680213%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58402) On Windows slaves, any call of dependency check tool results in "The input line is too long" error
Title: Message Title Kelly Hickel edited a comment on JENKINS-58402 Re: On Windows slaves, any call of dependency check tool results in "The input line is too long" error I did a bit of digging, and the problem is the set CLASSPATH in dependency-check.bat, which seems to be the cause of this problem reported against Dependency-Check [[https://github.com/jeremylong/DependencyCheck/issues/2062]].In my windows jenkins agent, the path to the tool BASEDIR is 135 characters, so the fully expanded CLASSPATH value would be 10841 characters, the longest command line for modern windows is 8191.I'll add this info to that ticket as well, not sure the best way to solve it, although for Java 9, that may be to use a manifest jar file. I should have pointed out that you don't need a windows machine to see this, you could just add "echo $CLASSPATH | wc -c" to dependency-check.sh, after CLASSPATH is set. If the length is over 8191, then it won't work on windows. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200527.1562668975000.15377.1563457440261%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57443) .plus() method works incorrect
Title: Message Title gek commented on JENKINS-57443 Re: .plus() method works incorrect Any feedback? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199256.155781424.15374.1563457320123%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58363) Add backend API for fetching date presets.
Title: Message Title Jack Shen updated JENKINS-58363 Jenkins / JENKINS-58363 Add backend API for fetching date presets. Change By: Jack Shen Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200478.1562338782000.15372.1563457200129%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38638) Allow build step and post build steps to differ from templates in EZ-templates plugin
Title: Message Title Juan Navarro commented on JENKINS-38638 Re: Allow build step and post build steps to differ from templates in EZ-templates plugin I was just googling for this feature and arrived here. What I don't see in these comments is a reason for not having the whole "Build" section in the "Features exempted from templating" area. This would be a good starting compromise, it should be really easy to add (just like there is already exemptions for job parameters, build triggers, etc.) and would have allowed using this plugin at all when the build steps must differ between jobs. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.175029.147526884.15366.1563457020246%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
