[JIRA] (JENKINS-59831) update JsonPath from 0.5.5 to 2.4.0
Title: Message Title Kemal Soysal commented on JENKINS-59831 Re: update JsonPath from 0.5.5 to 2.4.0 it would definitely make sense to interactively show the results of the json patterns on the given url... Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202566.1571343899000.12838.1571722800260%40Atlassian.JIRA.
[JIRA] (JENKINS-59876) Github orgnization commit trigger to build pipeline is not working through scm polling
Title: Message Title Kishore Babu Kavuru created an issue Jenkins / JENKINS-59876 Github orgnization commit trigger to build pipeline is not working through scm polling Issue Type: Bug Assignee: Mark Waite Components: git-plugin, github-api-plugin Created: 2019-10-22 05:29 Environment: windows jenkins 2.190 Priority: Critical Reporter: Kishore Babu Kavuru Commit trigger to Pipeline job using github-webhook is not working. 503- response in the hook. Add Comment
[JIRA] (JENKINS-59802) Changing access token credential causes 404 - Not Found error
Title: Message Title Kristy Hughes commented on JENKINS-59802 Re: Changing access token credential causes 404 - Not Found error This will be fixed in the next release (atlassian-bitbucket-server-integration-1.0-beta-2) Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202532.1571228005000.12833.1571716380132%40Atlassian.JIRA.
[JIRA] (JENKINS-59802) Changing access token credential causes 404 - Not Found error
Title: Message Title Kristy Hughes updated JENKINS-59802 Jenkins / JENKINS-59802 Changing access token credential causes 404 - Not Found error Change By: Kristy Hughes Status: In Review Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202532.1571228005000.12831.1571716320270%40Atlassian.JIRA.
[JIRA] (JENKINS-54044) Replay page "NOT FOUND" for branch
Title: Message Title Bogdan Ilchyshyn commented on JENKINS-54044 Re: Replay page "NOT FOUND" for branch To make it even worse, autorefresh feature replaces "%2F" in the original URL with "/". This causes any open build page for a branch like this to land at the Not Found page in some time. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194659.1539332795000.12829.1571715240132%40Atlassian.JIRA.
[JIRA] (JENKINS-59802) Changing access token credential causes 404 - Not Found error
Title: Message Title Kristy Hughes started work on JENKINS-59802 Change By: Kristy Hughes Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202532.1571228005000.12825.1571713680722%40Atlassian.JIRA.
[JIRA] (JENKINS-59802) Changing access token credential causes 404 - Not Found error
Title: Message Title Kristy Hughes updated JENKINS-59802 Jenkins / JENKINS-59802 Changing access token credential causes 404 - Not Found error Change By: Kristy Hughes Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202532.1571228005000.12827.1571713680799%40Atlassian.JIRA.
[JIRA] (JENKINS-59722) Old scm-api included in Jenkins LTS war file
Title: Message Title
Friedrich Clausen updated an issue
Jenkins / JENKINS-59722
Old scm-api included in Jenkins LTS war file
Change By:
Friedrich Clausen
We use the Jenkins WAR file as a - test rule - Job DSL to XML generator to locally verify our Job DSL prior to generating jobs on real instances. As part of this a Jenkins instance is started from the war archive obtained via the dependency "org.jenkins-ci.main:jenkins-war:2.190.1". This is, currently, the same as the war file fetched via [http://mirrors.jenkins.io/war-stable/latest/jenkins.war.]When starting up this war file the following warning is shown {noformat}java.io.IOException: Jenkins Git plugin version 3.12.1 failed to load. - SCM API Plugin version 2.4.1 is older than required. To fix, install version 2.6.3 or later.at hudson.PluginWrapper.resolvePluginDependencies(PluginWrapper.java:922)at hudson.PluginManager$2$1$1.run(PluginManager.java:545)at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169)at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:296)at jenkins.model.Jenkins$5.runTask(Jenkins.java:1118)at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:214)at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117)at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)at java.lang.Thread.run(Thread.java:748){noformat}After some investigation it appears that scm-api is bundled in the war file atWEB-INF/detached-plugins/scm-api.hpiThis is the 2.4.1 version it is complaining about. Can this be updated to one that works with the latest stable Jenkins?
Add Comment
[JIRA] (JENKINS-59722) Old scm-api included in Jenkins war file
Title: Message Title Friedrich Clausen updated an issue Jenkins / JENKINS-59722 Old scm-api included in Jenkins war file Change By: Friedrich Clausen Summary: Old scm-api included in Jenkins LTS war file Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202437.1570680992000.12821.1571713200345%40Atlassian.JIRA.
[JIRA] (JENKINS-59722) Old scm-api included in Jenkins LTS war file
Title: Message Title Friedrich Clausen reopened an issue I don't believe our usage is unsupported; I'll include some details. We are using gradle-jenkins-jobdsl-plugin to generate Job XML from Job DSL files. To do this gradle-jenkins-jobdsl-plugin will start an actual Jenkins instance using the war file. It is possible to include extra plugins using the "jenkinsPlugin" Gradle dependency configuration (see "How does it work" in link above). What we have been seeing is that, if any plugin specified in "jenkinsPlugins" depends on a plugin bundled in the Jenkins core war file then it'll use that even if a newer one is specified in "jenkinsPlugins". In the case of "Git" depending on "scm-api", it uses the bundled one that is too old. Even if we specify a newer scm-api in the "jenkinsPlugin" configuration. Reproducible Project I have created a small example project that illustrates this issue: https://github.com/ftclausen/JENKINS-59722 See README.md for how to trigger. Jenkins / JENKINS-59722 Old scm-api included in Jenkins LTS war file Change By: Friedrich Clausen Resolution: Not A Defect Status: Closed Reopened Add Comment
[JIRA] (JENKINS-59804) Support Multibranch Pipelines
Title: Message Title Daniel Kjellin assigned an issue to Unassigned Jenkins / JENKINS-59804 Support Multibranch Pipelines Change By: Daniel Kjellin Assignee: Kristy Hughes Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202534.1571228736000.12810.1571710320292%40Atlassian.JIRA.
[JIRA] (JENKINS-59578) Changing server configuration does not update SCM configuration
Title: Message Title Daniel Kjellin assigned an issue to Unassigned Jenkins / JENKINS-59578 Changing server configuration does not update SCM configuration Change By: Daniel Kjellin Assignee: Atlassian Bitbucket Server Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202218.1569821377000.12812.1571710320320%40Atlassian.JIRA.
[JIRA] (JENKINS-59869) OWASP Dependency-Check Plugin v5.2.2 declarative pipeline java not recognized
Title: Message Title Steve Springett commented on JENKINS-59869 Re: OWASP Dependency-Check Plugin v5.2.2 declarative pipeline java not recognized The Jenkins plugin simply calls dependency-check.bat (or .sh). Nothing more. The error contains everything you need to fix it. It's likely a path issue in that java is not in the path. Take a look at bin/dependency-check.bat and see what the script is trying to do. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202611.1571668367000.12807.1571707680148%40Atlassian.JIRA.
[JIRA] (JENKINS-59826) Error launching agent into second cloud
Title: Message Title Carlos Sanchez commented on JENKINS-59826 Re: Error launching agent into second cloud you are nesting two podTemplates, you can't do that to launch a pod. It creates a pod template in jenkins, not launch a new pod you should create a new job for the tests and call it, instead of using podTemplate again Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202561.157132511.12804.1571695200142%40Atlassian.JIRA.
[JIRA] (JENKINS-43353) Ability to abort all previous running builds
Title: Message Title Brandon Squizzato commented on JENKINS-43353 Re: Ability to abort all previous running builds Kamil Magomedov Build #1 would define milestone(1) Build #2 would define milestone(1) and milestone(2) Build #3 would define milestone(2) and milestone(3) Build #4 would define milestone(3) and milestone(4) and so on ... Every time a build runs, it is passing the highest milestone of the previous build. This causes the previous build to abort. From https://jenkins.io/doc/pipeline/steps/pipeline-milestone-step/ – > The milestone step forces all builds to go through in order, so an older build will never be allowed pass a milestone (it is aborted) if a newer build already passed it. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.180501.1491336786000.12788.1571693520680%40Atlassian.JIRA.
[JIRA] (JENKINS-59844) Process Launcher shouldn't throw ArrayIndexOutOfBoundException on empty command
Title: Message Title Dishit Devasia commented on JENKINS-59844 Re: Process Launcher shouldn't throw ArrayIndexOutOfBoundException on empty command Sure go ahead Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202579.1571403818000.12784.1571692380153%40Atlassian.JIRA.
[JIRA] (JENKINS-59866) Octane Cucumber test reporter plugin fails previous passed build after Jenkins restarts
Title: Message Title Minh Tran updated an issue Jenkins / JENKINS-59866 Octane Cucumber test reporter plugin fails previous passed build after Jenkins restarts Change By: Minh Tran Hi,I am currently having issue with "Octane Cucumber test reporter" plugin which could be reproduced as below steps:Steps: # Create a Maven project using cucumber framework and "com.hpe.alm.octane.OctaneGherkinFormatter:target\\gherkin-results \\ ManualRunnerTest_OctaneGherkinResults.xml" plugin. # Create a freestyle Jenkins job for above maven project and add the "Octane Cucumber test reporter" and "Publish Thucydides Test Reports" to Post-build Actions. # Create an Octane pipeline job that links to Jenkins job above. # Build the job and ensure the result is passed. # Validate the HTML report is published in Jenkins and ManualRunnerTest_OctaneGherkinResults.xml is generated in Jenkins workspace\target\gherkin-results. # Restart JenkinsExpected: * Job status is still passed. * HTML Report is still accessible.Actual: * Job status is turned to failed. * HTML Report is inaccessible removed .Please see attached the screenshots of the job status before and after Jenkins restart, console output log, and octane pipeline status. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-59860) Migrate to Github for documentation
Title: Message Title Mez Pahlan updated JENKINS-59860 Jenkins / JENKINS-59860 Migrate to Github for documentation Change By: Mez Pahlan Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202598.1571584911000.12780.157169197%40Atlassian.JIRA.
[JIRA] (JENKINS-59875) Git-client plugin version 2.8.6 breaks authentication on Windows box
Title: Message Title Mark Waite resolved as Won't Fix Jenkins / JENKINS-59875 Git-client plugin version 2.8.6 breaks authentication on Windows box Change By: Mark Waite Status: Open Resolved Resolution: Won't Fix Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202617.157168445.12779.1571688540195%40Atlassian.JIRA.
[JIRA] (JENKINS-59875) Git-client plugin version 2.8.6 breaks authentication on Windows box
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-59875 Git-client plugin version 2.8.6 breaks authentication on Windows box Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202617.157168445.12777.1571688480220%40Atlassian.JIRA.
[JIRA] (JENKINS-58344) Add support of project-level credentials management
Title: Message Title Rick Clephas commented on JENKINS-58344 Re: Add support of project-level credentials management Christoph Papke no unfortunately I haven't found a workaround besides the obvious: Giving the users Role1 Asking users with Role1 to manage the credentials Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200458.1562247469000.12767.1571687940261%40Atlassian.JIRA.
[JIRA] (JENKINS-58344) Add support of project-level credentials management
Title: Message Title Oleg Nenashev commented on JENKINS-58344 Re: Add support of project-level credentials management What can I do is to update Role Strategy to prevent confusion. If you feel it would help, please create a ticket Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200458.1562247469000.12763.1571687222364%40Atlassian.JIRA.
[JIRA] (JENKINS-58344) User with only project level create credentials permission can't create credentials
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-58344 User with only project level create credentials permission can't create credentials Change By: Oleg Nenashev Issue Type: Bug New Feature Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200458.1562247469000.12751.1571687040618%40Atlassian.JIRA.
[JIRA] (JENKINS-58344) User with only project level create credentials permission can't create credentials
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-58344 User with only project level create credentials permission can't create credentials Change By: Oleg Nenashev Component/s: role-strategy-plugin Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200458.1562247469000.12755.1571687100435%40Atlassian.JIRA.
[JIRA] (JENKINS-58344) Add support of project-level credentials management
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-58344 Add support of project-level credentials management Change By: Oleg Nenashev Summary: User with only Add support of project - level create credentials permission can't create credentials management Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200458.1562247469000.12760.1571687100512%40Atlassian.JIRA.
[JIRA] (JENKINS-58344) User with only project level create credentials permission can't create credentials
Title: Message Title Oleg Nenashev commented on JENKINS-58344 Re: User with only project level create credentials permission can't create credentials Sorry, I missed the notification and did not triage this issue. I doubt it is a bug, there is no "project level credentials permissions" in Credentials Plugin. Role Strategy just does not know whether there could be ones, and hence it offers the entire category. I will convert it to a feature request to credentials plugin. There is just no feature which is expected here Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200458.1562247469000.12749.1571687040542%40Atlassian.JIRA.
[JIRA] (JENKINS-58344) User with only project level create credentials permission can't create credentials
Title: Message Title Oleg Nenashev assigned an issue to Unassigned Jenkins / JENKINS-58344 User with only project level create credentials permission can't create credentials Change By: Oleg Nenashev Assignee: Oleg Nenashev Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200458.1562247469000.12758.1571687100482%40Atlassian.JIRA.
[JIRA] (JENKINS-59875) Git-client plugin version 2.8.6 breaks authentication on Windows box
Title: Message Title
Mark Waite updated an issue
Jenkins / JENKINS-59875
Git-client plugin version 2.8.6 breaks authentication on Windows box
Change By:
Mark Waite
When running with git-client plugin 2.8.6 we get the following error in the build log {noformat} Running as SYSTEM [EnvInject] - Loading node environment variables. Building remotely on BUILDAGENT (tool_nuget tool_powershell swarm role_generators team_development tool_msbuild tool_git) in workspace C:\ops\jenkins\workspace\testproduct12---b4eb99a4 [WS-CLEANUP] Deleting project workspace... [WS-CLEANUP] Deferred wipeout is used... using credential sandboxuser Cloning the remote Git repository Cloning repository [http://tfshostname:8080/tfs/projectcollection/sandbox/_git/testproduct123] > C:\Program Files\Git\cmd\git.exe init C:\ops\jenkins\workspace\testproduct12---b4eb99a4 # timeout=10 Fetching upstream changes from [http://tfshostname:8080/tfs/projectcollection/sandbox/_git/testproduct123] > C:\Program Files\Git\cmd\git.exe --version # timeout=10 using GIT_ASKPASS to set credentials User to access the sandbox project and the repos inside it. > C:\Program Files\Git\cmd\git.exe fetch --tags --progress -- [http://tfshostname:8080/tfs/projectcollection/sandbox/_git/testproduct123] +refs/heads/*:refs/remotes/origin/* ERROR: Error cloning remote repo 'origin' hudson.plugins.git.GitException: Command "C:\Program Files\Git\cmd\git.exe fetch --tags --progress -- [http://tfshostname:8080/tfs/projectcollection/sandbox/_git/testproduct123] +refs/heads/*:refs/remotes/origin/*" returned status code 128: stdout: stderr: fatal: Authentication failed for '[http://tfshostname:8080/tfs/projectcollection/sandbox/_git/testproduct123/]' at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2172) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1864) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$500(CliGitAPIImpl.java:78) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:545) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$2.execute(CliGitAPIImpl.java:758) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:153) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:146) at hudson.remoting.UserRequest.perform(UserRequest.java:212) at hudson.remoting.UserRequest.perform(UserRequest.java:54) at hudson.remoting.Request$2.run(Request.java:369) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at
[JIRA] (JENKINS-59875) Git-client plugin version 2.8.6 breaks authentication on Windows box
Title: Message Title
Mark Waite updated an issue
Jenkins / JENKINS-59875
Git-client plugin version 2.8.6 breaks authentication on Windows box
Change By:
Mark Waite
When running with git-client plugin 2.8.6 we get the following error in the build log {noformat} Running as SYSTEM [EnvInject] - Loading node environment variables. Building remotely on BUILDAGENT (tool_nuget tool_powershell swarm role_generators team_development tool_msbuild tool_git) in workspace C:\ops\jenkins\workspace\testproduct12---b4eb99a4 [WS-CLEANUP] Deleting project workspace... [WS-CLEANUP] Deferred wipeout is used... using credential sandboxuser Cloning the remote Git repository Cloning repository [http://tfshostname:8080/tfs/projectcollection/sandbox/_git/testproduct123] > C:\Program Files\Git\cmd\git.exe init C:\ops\jenkins\workspace\testproduct12---b4eb99a4 # timeout=10 Fetching upstream changes from [http://tfshostname:8080/tfs/projectcollection/sandbox/_git/testproduct123] > C:\Program Files\Git\cmd\git.exe --version # timeout=10 using GIT_ASKPASS to set credentials User to access the sandbox project and the repos inside it. > C:\Program Files\Git\cmd\git.exe fetch --tags --progress -- [http://tfshostname:8080/tfs/projectcollection/sandbox/_git/testproduct123] +refs/heads/*:refs/remotes/origin/* ERROR: Error cloning remote repo 'origin' hudson.plugins.git.GitException: Command "C:\Program Files\Git\cmd\git.exe fetch --tags --progress -- [http://tfshostname:8080/tfs/projectcollection/sandbox/_git/testproduct123] +refs/heads/*:refs/remotes/origin/*" returned status code 128: stdout: stderr: fatal: Authentication failed for '[http://tfshostname:8080/tfs/projectcollection/sandbox/_git/testproduct123/]' at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2172) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1864) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$500(CliGitAPIImpl.java:78) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:545) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$2.execute(CliGitAPIImpl.java:758) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:153) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:146) at hudson.remoting.UserRequest.perform(UserRequest.java:212) at hudson.remoting.UserRequest.perform(UserRequest.java:54) at hudson.remoting.Request$2.run(Request.java:369) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at
[JIRA] (JENKINS-59875) Git-client plugin version 2.8.6 breaks authentication on Windows box
Title: Message Title
Mark Waite updated an issue
Jenkins / JENKINS-59875
Git-client plugin version 2.8.6 breaks authentication on Windows box
Change By:
Mark Waite
When running with git-client plugin 2.8.6 we get the following error in the build log {noformat} Running as SYSTEM [EnvInject] - Loading node environment variables. Building remotely on BUILDAGENT (tool_nuget tool_powershell swarm role_generators team_development tool_msbuild tool_git) in workspace C:\ops\jenkins\workspace\testproduct12---b4eb99a4 [WS-CLEANUP] Deleting project workspace... [WS-CLEANUP] Deferred wipeout is used... using credential sandboxuser Cloning the remote Git repository Cloning repository [http://tfshostname:8080/tfs/projectcollection/sandbox/_git/testproduct123] > C:\Program Files\Git\cmd\git.exe init C:\ops\jenkins\workspace\testproduct12---b4eb99a4 # timeout=10 Fetching upstream changes from [http://tfshostname:8080/tfs/projectcollection/sandbox/_git/testproduct123] > C:\Program Files\Git\cmd\git.exe --version # timeout=10 using GIT_ASKPASS to set credentials User to access the sandbox project and the repos inside it. > C:\Program Files\Git\cmd\git.exe fetch --tags --progress -- [http://tfshostname:8080/tfs/projectcollection/sandbox/_git/testproduct123] +refs/heads/*:refs/remotes/origin/* ERROR: Error cloning remote repo 'origin' hudson.plugins.git.GitException: Command "C:\Program Files\Git\cmd\git.exe fetch --tags --progress -- [http://tfshostname:8080/tfs/projectcollection/sandbox/_git/testproduct123] +refs/heads/*:refs/remotes/origin/*" returned status code 128: stdout: stderr: fatal: Authentication failed for '[http://tfshostname:8080/tfs/projectcollection/sandbox/_git/testproduct123/]' at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2172) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1864) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$500(CliGitAPIImpl.java:78) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:545) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$2.execute(CliGitAPIImpl.java:758) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:153) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:146) at hudson.remoting.UserRequest.perform(UserRequest.java:212) at hudson.remoting.UserRequest.perform(UserRequest.java:54) at hudson.remoting.Request$2.run(Request.java:369) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at
[JIRA] (JENKINS-59875) Git-client plugin version 2.8.6 breaks authentication on Windows box
Title: Message Title
Mark Waite updated an issue
Jenkins / JENKINS-59875
Git-client plugin version 2.8.6 breaks authentication on Windows box
Change By:
Mark Waite
When running with git-client plugin 2.8.6 we get the following error in the build log {noformat} Running as SYSTEM [EnvInject] - Loading node environment variables. Building remotely on BUILDAGENT (tool_nuget tool_powershell swarm role_generators team_development tool_msbuild tool_git) in workspace C:\ops\jenkins\workspace\testproduct12---b4eb99a4 [WS-CLEANUP] Deleting project workspace... [WS-CLEANUP] Deferred wipeout is used... using credential sandboxuser Cloning the remote Git repository Cloning repository [http://tfshostname:8080/tfs/projectcollection/sandbox/_git/testproduct123] > C:\Program Files\Git\cmd\git.exe init C:\ops\jenkins\workspace\testproduct12---b4eb99a4 # timeout=10 Fetching upstream changes from [http://tfshostname:8080/tfs/projectcollection/sandbox/_git/testproduct123] > C:\Program Files\Git\cmd\git.exe --version # timeout=10 using GIT_ASKPASS to set credentials User to access the sandbox project and the repos inside it. > C:\Program Files\Git\cmd\git.exe fetch --tags --progress -- [http://tfshostname:8080/tfs/projectcollection/sandbox/_git/testproduct123] +refs/heads/*:refs/remotes/origin/* ERROR: Error cloning remote repo 'origin' hudson.plugins.git.GitException: Command "C:\Program Files\Git\cmd\git.exe fetch --tags --progress -- [http://tfshostname:8080/tfs/projectcollection/sandbox/_git/testproduct123] +refs/heads/*:refs/remotes/origin/*" returned status code 128: stdout: stderr: fatal: Authentication failed for '[http://tfshostname:8080/tfs/projectcollection/sandbox/_git/testproduct123/]' at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2172) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1864) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$500(CliGitAPIImpl.java:78) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:545) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$2.execute(CliGitAPIImpl.java:758) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:153) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:146) at hudson.remoting.UserRequest.perform(UserRequest.java:212) at hudson.remoting.UserRequest.perform(UserRequest.java:54) at hudson.remoting.Request$2.run(Request.java:369) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at
[JIRA] (JENKINS-59875) Git-client plugin version 2.8.6 breaks authentication on Windows box
Title: Message Title
Mark Waite updated an issue
Jenkins / JENKINS-59875
Git-client plugin version 2.8.6 breaks authentication on Windows box
Change By:
Mark Waite
When running with git-client plugin 2.8.6 we get the following error in the build log {noformat} Running as SYSTEM [EnvInject] - Loading node environment variables. Building remotely on BUILDAGENT (tool_nuget tool_powershell swarm role_generators team_development tool_msbuild tool_git) in workspace C:\ops\jenkins\workspace\testproduct12---b4eb99a4 [WS-CLEANUP] Deleting project workspace... [WS-CLEANUP] Deferred wipeout is used... using credential sandboxuser Cloning the remote Git repository Cloning repository [http://tfshostname:8080/tfs/projectcollection/sandbox/_git/testproduct123] > C:\Program Files\Git\cmd\git.exe init C:\ops\jenkins\workspace\testproduct12---b4eb99a4 # timeout=10 Fetching upstream changes from [http://tfshostname:8080/tfs/projectcollection/sandbox/_git/testproduct123] > C:\Program Files\Git\cmd\git.exe --version # timeout=10 using GIT_ASKPASS to set credentials User to access the sandbox project and the repos inside it. > C:\Program Files\Git\cmd\git.exe fetch --tags --progress -- [http://tfshostname:8080/tfs/projectcollection/sandbox/_git/testproduct123] +refs/heads/*:refs/remotes/origin/* ERROR: Error cloning remote repo 'origin' hudson.plugins.git.GitException: Command "C:\Program Files\Git\cmd\git.exe fetch --tags --progress -- [http://tfshostname:8080/tfs/projectcollection/sandbox/_git/testproduct123] +refs/heads/*:refs/remotes/origin/*" returned status code 128: stdout: stderr: fatal: Authentication failed for '[http://tfshostname:8080/tfs/projectcollection/sandbox/_git/testproduct123/]' at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2172) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1864) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$500(CliGitAPIImpl.java:78) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:545) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$2.execute(CliGitAPIImpl.java:758) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:153) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:146) at hudson.remoting.UserRequest.perform(UserRequest.java:212) at hudson.remoting.UserRequest.perform(UserRequest.java:54) at hudson.remoting.Request$2.run(Request.java:369) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at
[JIRA] (JENKINS-54186) No @DataBoundConstructor on any constructor of class jenkins.plugins.git.GitSCMSourceDefaults
Title: Message Title Mark Waite updated JENKINS-54186 Sorry for a second mistake Jesse Glick. Back to closed, it was resolved and delivered earlier as the comments say. Jenkins / JENKINS-54186 No @DataBoundConstructor on any constructor of class jenkins.plugins.git.GitSCMSourceDefaults Change By: Mark Waite Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194817.1540223284000.12666.1571685966467%40Atlassian.JIRA.
[JIRA] (JENKINS-59874) Support resource domain
Title: Message Title Jesse Glick commented on JENKINS-59874 Re: Support resource domain See https://jenkins.io/security/advisory/2015-12-09/ & https://github.com/jenkinsci/htmlpublisher-plugin/pull/22 for background. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202616.157167881.12660.1571685480138%40Atlassian.JIRA.
[JIRA] (JENKINS-59833) Stash Pull Request Builder Multiple PR in single build
Title: Message Title Upkar Rai commented on JENKINS-59833 Re: Stash Pull Request Builder Multiple PR in single build Waiting for merge Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202568.1571346229000.12662.1571685540138%40Atlassian.JIRA.
[JIRA] (JENKINS-54186) No @DataBoundConstructor on any constructor of class jenkins.plugins.git.GitSCMSourceDefaults
Title: Message Title Jesse Glick commented on JENKINS-54186 Re: No @DataBoundConstructor on any constructor of class jenkins.plugins.git.GitSCMSourceDefaults Mark Waite as in JENKINS-43802 is there some reason you changed the Status here? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194817.1540223284000.12588.1571685061339%40Atlassian.JIRA.
[JIRA] (JENKINS-59866) Octane Cucumber test reporter plugin fails previous passed build after Jenkins restarts
Title: Message Title Minh Tran updated an issue Jenkins / JENKINS-59866 Octane Cucumber test reporter plugin fails previous passed build after Jenkins restarts Change By: Minh Tran Attachment: After_Jenkins_Restart.png Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202605.1571659536000.12584.1571684942208%40Atlassian.JIRA.
[JIRA] (JENKINS-59866) Octane Cucumber test reporter plugin fails previous passed build after Jenkins restarts
Title: Message Title Minh Tran updated an issue Jenkins / JENKINS-59866 Octane Cucumber test reporter plugin fails previous passed build after Jenkins restarts Change By: Minh Tran Attachment: After_Jenkins_Restart.png Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202605.1571659536000.12586.1571684942525%40Atlassian.JIRA.
[JIRA] (JENKINS-59875) Git-client plugin version 2.8.6 breaks authentication on Windows box
Title: Message Title Petrik van der Velde created an issue Jenkins / JENKINS-59875 Git-client plugin version 2.8.6 breaks authentication on Windows box Issue Type: Improvement Assignee: Mark Waite Components: git-client-plugin Created: 2019-10-21 19:00 Environment: Server OS: 16.04.6 LTS (GNU/Linux 4.4.0-131-generic x86_64) jenkins: 2.190.1 Git version: N/A Git client plugin: 2.8.6 Agent OS: Windows 2016 - version 1607 (OS build 14393.3274) Jenkins slave version: Swarm slave 3.17 Git version: 2.18.0.windows.1 source control TFS 2018: 16.131.27701.1 Running on HTTP internally, authentication against AD. Username only has normal characters and password has alphanumeric characters and !. Priority: Minor Reporter: Petrik van der Velde When running with git-client plugin 2.8.6 we get the following error in the build log Running as SYSTEM [EnvInject] - Loading node environment variables. Building remotely on BUILDAGENT (tool_nuget tool_powershell swarm role_generators team_development tool_msbuild tool_git) in workspace C:\ops\jenkins\workspace\testproduct12---b4eb99a4 [WS-CLEANUP] Deleting project workspace... [WS-CLEANUP] Deferred wipeout is used... using credential sandboxuser Cloning the remote Git repository Cloning repository http://tfshostname:8080/tfs/projectcollection/sandbox/_git/testproduct123 > C:\Program Files\Git\cmd\git.exe init C:\ops\jenkins\workspace\testproduct12---b4eb99a4 # timeout=10 Fetching upstream changes from http://tfshostname:8080/tfs/projectcollection/sandbox/_git/testproduct123 > C:\Program Files\Git\cmd\git.exe --version # timeout=10 using GIT_ASKPASS to set credentials User to access the sandbox project and the repos inside it. > C:\Program Files\Git\cmd\git.exe fetch
[JIRA] (JENKINS-43802) Shared Library using folder-scoped credential fails to authenticate
Title: Message Title Mark Waite updated JENKINS-43802 Jenkins / JENKINS-43802 Shared Library using folder-scoped credential fails to authenticate Change By: Mark Waite Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.181318.1493051062000.12553.1571684463019%40Atlassian.JIRA.
[JIRA] (JENKINS-43802) Shared Library using folder-scoped credential fails to authenticate
Title: Message Title Mark Waite commented on JENKINS-43802 Re: Shared Library using folder-scoped credential fails to authenticate Sorry about that mistake. I failed to read the comment which says that it was released in git plugin 3.11.0. Returning to CLOSED since it is resolved. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.181318.1493051062000.12524.1571684400730%40Atlassian.JIRA.
[JIRA] (JENKINS-56252) Futures.addCallback uses method deleted in Guava 21
Title: Message Title Basil Crow commented on JENKINS-56252 Re: Futures.addCallback uses method deleted in Guava 21 I think it is OK to put shared utilities into workflow-step-api if they are @Restricted(Beta.class) and clearly documented as being solely for the use of other workflow-* plugins. Sounds like Jesse Glick and I are in agreement so far that we should follow the plan roughly outlined by my first comment, modulo putting the org.jenkinsci.plugins.workflow.concurrent package in workflow-step-api rather than workflow-api. At this point I just need confirmation from Devin Nusbaum about this plan of action. Then I will begin submitting PRs. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197819.1550860823000.12521.1571683980374%40Atlassian.JIRA.
[JIRA] (JENKINS-43353) Ability to abort all previous running builds
Title: Message Title Kamil Magomedov commented on JENKINS-43353 Re: Ability to abort all previous running builds Brandon Squizzato Not sure how your solution is supposed to work after the first build. Each subsequent build will create two milestones and pass them immediately. First build is the only one that will be aborted. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.180501.1491336786000.12504.1571682540404%40Atlassian.JIRA.
[JIRA] (JENKINS-56252) Futures.addCallback uses method deleted in Guava 21
Title: Message Title Jesse Glick commented on JENKINS-56252 Re: Futures.addCallback uses method deleted in Guava 21 We could only bundle a newer Guava by shading it, which is possible but would increase download size quite a bit (unless we set a build-time option to strip unused methods/classes) makes life harder if we ever need to ship, say, an emergency security update So if possible I would prefer to use the version from core. I think it is OK to put shared utilities into workflow-step-api if they are @Restricted(Beta.class) and clearly documented as being solely for the use of other workflow-* plugins. Devin Nusbaum as maintainer (last I checked) should weigh in here. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197819.1550860823000.12465.1571680680223%40Atlassian.JIRA.
[JIRA] (JENKINS-59851) Stash Pull Request Builder plugin keeps on posting the Build Started comment without build result
Title: Message Title Nareen M updated an issue Jenkins / JENKINS-59851 Stash Pull Request Builder plugin keeps on posting the Build Started comment without build result Change By: Nareen M Summary: Stash Pull Request Builder plugin keep keeps on posting the Build Started comment without build result Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202587.1571422014000.12496.1571680920156%40Atlassian.JIRA.
[JIRA] (JENKINS-43802) Shared Library using folder-scoped credential fails to authenticate
Title: Message Title Jesse Glick commented on JENKINS-43802 Re: Shared Library using folder-scoped credential fails to authenticate Mark Waite is there a reason you just marked this issue (and another one similar to it) FIXED BUT UNRELEASED when there is in fact a release with the fix? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.181318.1493051062000.12467.1571680740834%40Atlassian.JIRA.
[JIRA] (JENKINS-59874) Support resource domain
Title: Message Title Jesse Glick created an issue Jenkins / JENKINS-59874 Support resource domain Issue Type: New Feature Assignee: Richard Bywater Components: htmlpublisher-plugin Created: 2019-10-21 17:26 Priority: Major Reporter: Jesse Glick As of JENKINS-41891 in Jenkins 2.200, the way this plugin works is undesirable—much too complex, and not very functional. It should merely copy the selected files to htmlreports and then serve them via DirectoryBrowserSupport (using target="_blank" so as not to lose track of the Jenkins site) without further mutilation. No BaseHTMLAction/index, no htmlpublisher-wrapper.html generation, etc. Ideally this would be done automatically when ResourceDomainConfiguration.isResourceDomainConfigured, though currently this is a @Restricted API. Add Comment
[JIRA] (JENKINS-59245) Create "Saltstack view" for displaying Saltstack Console output
Title: Message Title Tzach Solomon commented on JENKINS-59245 Re: Create "Saltstack view" for displaying Saltstack Console output Henrik Helmø Larsen the 'console-log-text-replacer-plugin' Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201708.1567687675000.12453.1571678640740%40Atlassian.JIRA.
[JIRA] (JENKINS-59836) HashiCorp Vault plugin configuration cannot be enabled for Freestyle projects
Title: Message Title Erica Norton commented on JENKINS-59836 Re: HashiCorp Vault plugin configuration cannot be enabled for Freestyle projects Seeing this same issue with Jenkins Jenkins ver. 2.190.1 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202571.1571380365000.12427.1571675280340%40Atlassian.JIRA.
[JIRA] (JENKINS-59836) HashiCorp Vault plugin configuration cannot be enabled for Freestyle projects
Title: Message Title Erica Norton edited a comment on JENKINS-59836 Re: HashiCorp Vault plugin configuration cannot be enabled for Freestyle projects Seeing this same issue with Jenkins [Jenkins ver. 2.190.1|https://jenkins.io/] Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202571.1571380365000.12430.1571675280596%40Atlassian.JIRA.
[JIRA] (JENKINS-58344) User with only project level create credentials permission can't create credentials
Title: Message Title Christoph Papke commented on JENKINS-58344 Re: User with only project level create credentials permission can't create credentials Hello everyone, we currently have the same issue in our company. Did you find a workaround for this in the meantime Rick Clephas? Is there an estimated time when this bug will be fixed Oleg Nenashev? Thanks for your help. Best regards Chris Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200458.1562247469000.12416.1571674800671%40Atlassian.JIRA.
[JIRA] (JENKINS-59873) Add Artifact Archiver to configuration slicing plugin
Title: Message Title Abhishek Sharma created an issue Jenkins / JENKINS-59873 Add Artifact Archiver to configuration slicing plugin Issue Type: New Feature Assignee: Mikael Gaunin Components: configurationslicing-plugin Created: 2019-10-21 16:01 Priority: Minor Reporter: Abhishek Sharma Currently, there is no option to edit Artifact Archiver configuration through the configuration slicing plugin. Adding that would be useful. Add Comment This message was sent by Atlassian Jira
[JIRA] (JENKINS-44450) Block scoped usage
Title: Message Title Oleg Nenashev started work on JENKINS-44450 Change By: Oleg Nenashev Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.182278.1495543785000.12328.1571671860550%40Atlassian.JIRA.
[JIRA] (JENKINS-59872) Allow Poweshell Stage Steps to run without -noprofile
Title: Message Title sebastian slutzky created an issue Jenkins / JENKINS-59872 Allow Poweshell Stage Steps to run without -noprofile Issue Type: Improvement Assignee: Unassigned Components: durable-task-plugin Created: 2019-10-21 15:15 Environment: Jenkins ver: 2.176.2 OS: Windows Server 16 Pipeline plugin: 2.4 Priority: Minor Reporter: sebastian slutzky Powershell steps are executed with the -noprofile powershell option. This is not always desired. In our case we add setup and configuration tasks to the default profile. A workaround if to add ". $profile" at the beginning of each powershell step but this adds overhead to all steps and is a maintenance burden. Additionally, the powershell plugin for jenkins doesn't use -noprofile, so it would be good to preserve that behaviour to make the switch to the jenkins pipeline seemless. Suggestion: Make the hardcoded command line to powershell configurable globally, so that a "use default profile" global checkbox can drive this behaviour. Add Comment
[JIRA] (JENKINS-34581) Please add support for Pipelines to the Powershell plugin
Title: Message Title sebastian slutzky commented on JENKINS-34581 Re: Please add support for Pipelines to the Powershell plugin Gabriel Loewen Running powershell in the Jenkins Pipeline is hardcoded to use no profile. The powershell plugin defaults to the opposite. Can this be made configurable? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.170202.1462313059000.12247.1571670301188%40Atlassian.JIRA.
[JIRA] (JENKINS-50029) Powershell treats warnings as errors
Title: Message Title sebastian slutzky assigned an issue to Gabriel Loewen Jenkins / JENKINS-50029 Powershell treats warnings as errors Change By: sebastian slutzky Assignee: sebastian slutzky Gabriel Loewen Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.189029.1520535534000.12240.1571669880371%40Atlassian.JIRA.
[JIRA] (JENKINS-50029) Powershell treats warnings as errors
Title: Message Title sebastian slutzky assigned an issue to sebastian slutzky Jenkins / JENKINS-50029 Powershell treats warnings as errors Change By: sebastian slutzky Assignee: Gabriel Loewen sebastian slutzky Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.189029.1520535534000.12235.1571669820270%40Atlassian.JIRA.
[JIRA] (JENKINS-59871) env hashmap randomly mixes values of two parallel nodes
Title: Message Title
Alexander Samoylov updated an issue
Jenkins / JENKINS-59871
env hashmap randomly mixes values of two parallel nodes
Change By:
Alexander Samoylov
Please, look at this simple pipeline script:{code:java}def build(label) {// Set env globally (for all stages) on the current nodeenv.MYENVVAR = env.WORKSPACE// Printout outside of stageprint('WORKSPACE 0=' + env.WORKSPACE)print('MYENVVAR 0=' + env.MYENVVAR)stage ('Stage 1' + label) { // Printout in a stageprint('WORKSPACE 1=' + env.WORKSPACE)print('MYENVVAR 1=' + env.MYENVVAR)}}// Mainparallel('Unix' : {node ('build-linux') {build('Unix')}},'Windows' : {node ('build-win') {build('Windows')}}){code}This results to this output:{code:java}Running on build-linux in /home/build/jenkins/workspace/pipeline_bug_parallel_env_mixed_upRunning on build-win in c:\build\jenkins\pipeline_bug_parallel_env_mixed_up[Unix] WORKSPACE 0=/home/build/jenkins/workspace/pipeline_bug_parallel_env_mixed_up[Unix] MYENVVAR 0=/home/build/jenkins/workspace/pipeline_bug_parallel_env_mixed_up [Windows] WORKSPACE 0=c:\build\jenkins\pipeline_bug_parallel_env_mixed_up[Windows] MYENVVAR 0=c:\build\jenkins\pipeline_bug_parallel_env_mixed_up[Unix] WORKSPACE 1=/home/build/jenkins/workspace/pipeline_bug_parallel_env_mixed_up*[Unix] MYENVVAR 1=c:\build\jenkins\pipeline_bug_parallel_env_mixed_up* // BUG !![Windows] WORKSPACE 1=c:\build\jenkins\pipeline_bug_parallel_env_mixed_up[Windows] MYENVVAR 1=c:\build\jenkins\pipeline_bug_parallel_env_mixed_up{code}So the bug is that the env.MYENVVAR inside the [Unix] parallel branch on Unix node somehow takes value of the [Windows] parallel branch.Expected result: env.MYENVVAR = env.WORKSPACE before all stages should have assigned env.MYENVVAR for all further stages, because it was done outside the stage, that is globally for the node.There is a workaround. If I change the pipeline script by adding withEnv{} this way it works:{code:java}def build(label) {withEnv([ "MYENVVAR=" + env.WORKSPACE ]) { // WORKAROUND// Global//env.MYENVVAR = env.WORKSPACEprint('WORKSPACE 0=' + env.WORKSPACE)print('MYENVVAR 0=' + env.MYENVVAR)stage ('Stage 1' + label) {print('WORKSPACE 1=' + env.WORKSPACE)print('MYENVVAR 1=' + env.MYENVVAR)}}}{code}I don't know if my example is supposed to be supported, but if not then please fix it so that the null value is assigned. If the variable in one node {} takes value from another parallel node {} in a random way that seems to be really wrong.
[JIRA] (JENKINS-59871) env hashmap randomly mixes values of two parallel nodes
Title: Message Title
Alexander Samoylov created an issue
Jenkins / JENKINS-59871
env hashmap randomly mixes values of two parallel nodes
Issue Type:
Bug
Assignee:
Unassigned
Components:
pipeline
Created:
2019-10-21 14:36
Environment:
Labels:
pipeline pipeline-environment
Priority:
Major
Reporter:
Alexander Samoylov
Please, look at this simple pipeline script:
def build(label) {
// Set env globally (for all stages) on the current node
env.MYENVVAR = env.WORKSPACE
// Printout outside of stage
print('WORKSPACE 0=' + env.WORKSPACE)
print('MYENVVAR 0=' + env.MYENVVAR)
stage ('Stage 1' + label) { // Printout in a stage
print('WORKSPACE 1=' + env.WORKSPACE)
print('MYENVVAR 1=' + env.MYENVVAR)
}
}
// Main
parallel(
'Unix' : {
node ('build-linux') {
build('Unix')
}
},
'Windows' : {
node ('build-win') {
build('Windows')
}
}
)
This results to this output:
Running on build-linux in /home/build/jenkins/workspace/pipeline_bug_parallel_env_mixed_up
Running on build-win in
[JIRA] (JENKINS-59870) build-env-propagator java.lang.ClassNotFoundException: hudson.cli.CommandDuringBuild
Title: Message Title
Cesar Jorge Martínez updated an issue
Jenkins / JENKINS-59870
build-env-propagator java.lang.ClassNotFoundException: hudson.cli.CommandDuringBuild
Change By:
Cesar Jorge Martínez
Multiple errors as (with last plugins and jenkins 2.190.1): {{}}{{ 2019-10-21 14:04: 19 20 . 155 378 + [id=29] WARNING hudson h .ExtensionFinder$ Sezpoz GuiceFinder$SezpozModule # _find configure : Failed to load org.jenkinsci.plugins.envpropagator.SetEnvVariables }} {{ java.lang.ClassNotFoundException: hudson.cli.CommandDuringBuild }} {{ at jenkins.util.AntClassLoader.findClassInComponents(AntClassLoader.java:1383) }} {{ at jenkins.util.AntClassLoader.findClass(AntClassLoader.java:1336) }} {{ at jenkins.util.AntClassLoader.loadClass(AntClassLoader.java:1083) }} {{ at java.lang.ClassLoader.loadClass(ClassLoader.java:357) }} {{ Caused: java.lang.NoClassDefFoundError: hudson/cli/CommandDuringBuild }} {{ at java.lang.ClassLoader.defineClass1(Native Method) }} {{ at java.lang.ClassLoader.defineClass(ClassLoader.java:763) }} {{ at jenkins.util.AntClassLoader.defineClassFromData(AntClassLoader.java:1149) }} {{ at hudson.ClassicPluginStrategy$AntClassLoader2.defineClassFromData(ClassicPluginStrategy.java:712) }} {{ at jenkins.util.AntClassLoader.getClassFromStream(AntClassLoader.java:1320) }} {{ at jenkins.util.AntClassLoader.findClassInComponents(AntClassLoader.java:1373) }} {{ at jenkins.util.AntClassLoader.findClass(AntClassLoader.java:1336) }} {{ at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source) }} {{ at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) }} {{ at java.lang.reflect.Method.invoke(Method.java:498) }} {{ at jenkins.ClassLoaderReflectionToolkit.invoke(ClassLoaderReflectionToolkit.java:44) }} {{ at jenkins.ClassLoaderReflectionToolkit._findClass(ClassLoaderReflectionToolkit.java:81) }} {{ at hudson.PluginManager$UberClassLoader.findClass(PluginManager.java:2041) }} {{ at java.lang.ClassLoader.loadClass(ClassLoader.java:424) }} {{ at java.lang.ClassLoader.loadClass(ClassLoader.java:357) }} {{ at net.java.sezpoz.IndexItem.element(IndexItem.java:134) }} {{ Caused: java.lang.InstantiationException }} {{ at net.java.sezpoz.IndexItem.element(IndexItem.java:146) }} {{ at hudson.ExtensionFinder $GuiceFinder$SezpozModule . getClassFromIndex configure (ExtensionFinder.java: 741 519 ) }} {{ at hudson com . ExtensionFinder google . access$900 inject.AbstractModule.configure ( ExtensionFinder AbstractModule .java: 89 62 ) }} {{ at hudson com . ExtensionFinder google.inject.spi.Elements $ Sezpoz RecordingBinder . _find install ( ExtensionFinder Elements .java: 701 340 ) }} {{ at hudson com . ExtensionFinder$Sezpoz google . find inject.spi.Elements.getElements ( ExtensionFinder Elements .java: 690 110 ) }} {{ at hudson com . ExtensionFinder google.inject.internal.InjectorShell $ GuiceFinder Builder . refreshExtensionAnnotations build ( ExtensionFinder InjectorShell .java: 302 138 ) }}
[JIRA] (JENKINS-59870) build-env-propagator java.lang.ClassNotFoundException: hudson.cli.CommandDuringBuild
Title: Message Title
Cesar Jorge Martínez created an issue
Jenkins / JENKINS-59870
build-env-propagator java.lang.ClassNotFoundException: hudson.cli.CommandDuringBuild
Issue Type:
Bug
Assignee:
Unassigned
Components:
build-env-propagator-plugin
Created:
2019-10-21 14:33
Labels:
plugin
Priority:
Major
Reporter:
Cesar Jorge Martínez
Multiple errors as (with last plugins and jenkins 2.190.1): }}{{2019-10-21 14:04:19.155+ [id=29] WARNING hudson.ExtensionFinder$Sezpoz#_find: Failed to load org.jenkinsci.plugins.envpropagator.SetEnvVariables java.lang.ClassNotFoundException: hudson.cli.CommandDuringBuild {{ at jenkins.util.AntClassLoader.findClassInComponents(AntClassLoader.java:1383)}} {{ at jenkins.util.AntClassLoader.findClass(AntClassLoader.java:1336)}} {{ at jenkins.util.AntClassLoader.loadClass(AntClassLoader.java:1083)}} {{ at java.lang.ClassLoader.loadClass(ClassLoader.java:357)}} Caused: java.lang.NoClassDefFoundError: hudson/cli/CommandDuringBuild {{ at java.lang.ClassLoader.defineClass1(Native Method)}} {{ at java.lang.ClassLoader.defineClass(ClassLoader.java:763)}} {{ at jenkins.util.AntClassLoader.defineClassFromData(AntClassLoader.java:1149)}} {{ at hudson.ClassicPluginStrategy$AntClassLoader2.defineClassFromData(ClassicPluginStrategy.java:712)}} {{ at jenkins.util.AntClassLoader.getClassFromStream(AntClassLoader.java:1320)}} {{ at jenkins.util.AntClassLoader.findClassInComponents(AntClassLoader.java:1373)}} {{ at jenkins.util.AntClassLoader.findClass(AntClassLoader.java:1336)}} {{ at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source)}} {{ at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)}} {{ at java.lang.reflect.Method.invoke(Method.java:498)}} {{ at
[JIRA] (JENKINS-59869) OWASP Dependency-Check Plugin v5.2.2 declarative pipeline java not recognized
Title: Message Title
Terry van der Griend created an issue
Jenkins / JENKINS-59869
OWASP Dependency-Check Plugin v5.2.2 declarative pipeline java not recognized
Issue Type:
Bug
Assignee:
Unassigned
Components:
dependency-check-jenkins-plugin
Created:
2019-10-21 14:32
Environment:
Windows 2012 Server, Jenkins 2.190.1, Maven 3.6.0, JDK 11.0.1
Priority:
Major
Reporter:
Terry van der Griend
When upgrading the Dependency Check Plugin from version 4 to 5.2.2, we found the following problem. We are using declarative pipeline scripts to run the Dependency Check Plugin. Formerly with version 4 we could use this setup for running the dependency check.
pipeline {
agent {
label 'master'
}
environment {
JAVA_HOME = tool 'jdk-11.0.1'
mvnHome = tool 'apache-maven-3.6.0'
PATH = "${JAVA_HOME}\\bin;${mvnHome}\\bin;${env.PATH}"
}
stages {
stage('Build sources') {
steps {
bat 'mvn clean verify -DskipTests'
}
}
stage('Analyze dependencies') {
dependencyCheckAnalyzer(outdir: 'Dependency-Check',
suppressionFile: 'owasp-suppressions.xml',
scanpath: '',
datadir: '',
hintsFile: '',
zipExtensions: '',
isAutoupdateDisabled: true,
skipOnScmChange: false,
skipOnUpstreamChange: false,
includeHtmlReports: true,
includeVulnReports: true,
[JIRA] (JENKINS-51291) 'new view' wrong url - not relative
Title: Message Title Ilia Zasimov started work on JENKINS-51291 Change By: Ilia Zasimov Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.190625.1526291411000.12210.1571667841330%40Atlassian.JIRA.
[JIRA] (JENKINS-51291) 'new view' wrong url - not relative
Title: Message Title Ilia Zasimov assigned an issue to Ilia Zasimov Jenkins / JENKINS-51291 'new view' wrong url - not relative Change By: Ilia Zasimov Assignee: Ilia Zasimov Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.190625.1526291411000.12208.1571667841147%40Atlassian.JIRA.
[JIRA] (JENKINS-59638) Notify Testers
Title: Message Title Mez Pahlan commented on JENKINS-59638 Re: Notify Testers You're welcome, it was really thanks to Niall Kelly for the fix! Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202320.1570088671000.12202.1571667720192%40Atlassian.JIRA.
[JIRA] (JENKINS-59807) Credentials Unavailable in SSH Agent
Title: Message Title Jonathan Buck updated an issue Jenkins / JENKINS-59807 Credentials Unavailable in SSH Agent Change By: Jonathan Buck When using the "SSH Agent" setting in the "Build Environment" section, credentials are not showing up when creating/modifying a freestyle project. This is the case with both credentials created from the credential page or from the "Credentials" option under the "SSH Agent" option. I've tried multiple types of credentials to see what would populate the list, although my understanding is that this should work with credentials stored as "SSH Username with private key". I also use the Ansible plugin and all available credentials are showing up within that credentials drop-down menu within the same project configuration page. My assumption is that this has something to do with the "SSH Agent" plugin interacting with the "Credentials" or "SSH Credentials" plugin. There's no option do downgrade the plugin, so that was not attempted. I have no problem getting the SSH-Agent plugin working within a pipeline job. So, the issue doesn't seem to have anything to do with the Credentials themselves. The problem seems specific to the User Interface. !image-2019-10-17-14-42-56-399.png!!Jenkins_Credentials.PNG! Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-59863) currentBuild.changeSets always null
Title: Message Title Alex Earl closed an issue as Not A Defect There is no currentBuild in the context of an email-ext template. You can use build.currentChangesets Jenkins / JENKINS-59863 currentBuild.changeSets always null Change By: Alex Earl Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To
[JIRA] (JENKINS-59800) Overlapping Multiline Headlines in the 'Create Admin User' view
Title: Message Title Daniel Beck resolved as Fixed Released in 2.201, due to infra issue it doesn't appear yet. Jenkins / JENKINS-59800 Overlapping Multiline Headlines in the 'Create Admin User' view Change By: Daniel Beck Status: Open Resolved Resolution: Fixed Released As: jenkins-2.201 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message
[JIRA] (JENKINS-59638) Notify Testers
Title: Message Title Paul O'Brien commented on JENKINS-59638 Re: Notify Testers Mez Pahlan, have tested and working as expected. Thanks for this Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202320.1570088671000.12165.1571665860592%40Atlassian.JIRA.
[JIRA] (JENKINS-59724) no known implementation of class java.lang.String is named Target
Title: Message Title Aleksi Simell commented on JENKINS-59724 Re: no known implementation of class java.lang.String is named Target I'm not sure I understand what you mean by "does it work for all builds", but I could only reproduce this with having a pipeline job with "target" instead of "selectedTarget". After the change the logs still showed that error, but after a Jenkins restart the error is not showing, unless I change my pipeline back to "target" (which, as I have mentioned, is not supported anymore and would therefore be silly to do). I have not touched my xml files in the slightest. But on a further note, I did notice another bug due to this, which is now fixed related to this pull request for this issue. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202441.1570700819000.12158.1571665620650%40Atlassian.JIRA.
[JIRA] (JENKINS-59724) no known implementation of class java.lang.String is named Target
Title: Message Title Aleksi Simell edited a comment on JENKINS-59724 Re: no known implementation of class java.lang.String is named Target I'm not sure I understand what you mean by "does it work for all builds", but I could only reproduce this with having a pipeline job with "target" instead of "selectedTarget". After the change the logs still showed that error, but after a Jenkins restart the error is not showing, unless I change my pipeline back to "target" (which, as I have mentioned, is not supported anymore and would therefore be silly to do).I have not touched my xml files in the slightest.But on a further note, I did notice another bug due to this , which is now fixed related (very similar to [this pull request|https://github.com/jenkinsci/kubernetes-plugin/pull/486] for [this issue|https://issues.jenkins-ci.org/browse/JENKINS-57827] ) . That's fixed now. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202441.1570700819000.12161.1571665681232%40Atlassian.JIRA.
[JIRA] (JENKINS-19053) FATAL: HTML Publisher failure
Title: Message Title Dmitriy Oleynik reopened an issue 16:24:32 [htmlpublisher] Archiving HTML reports...16:24:32 [htmlpublisher] Archiving at PROJECT level /home/jenkins/workspace/test-pipe to /var/lib/jenkins/jobs/test-pipe/htmlreports/Version_3a_200_2e34_2e13_2e8262488*16:24:36* FATAL: HTML Publisher failure*16:24:36* java.io.IOException: Failed to extract /home/jenkins/workspace/test-pipe/*/16:24:36 at hudson.FilePath.readFromTar(FilePath.java:2608)16:24:36 at hudson.FilePath.copyRecursiveTo(FilePath.java:2386)16:24:36 at hudson.FilePath.copyRecursiveTo(FilePath.java:2350)16:24:36 at hudson.FilePath.copyRecursiveTo(FilePath.java:2338)16:24:36 at hudson.FilePath.copyRecursiveTo(FilePath.java:2321)16:24:36 at htmlpublisher.HtmlPublisher.publishReports(HtmlPublisher.java:277)16:24:36 at htmlpublisher.workflow.PublishHTMLStepExecution.run(PublishHTMLStepExecution.java:70)16:24:36 at htmlpublisher.workflow.PublishHTMLStepExecution.run(PublishHTMLStepExecution.java:45)16:24:36 at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1$1.call(AbstractSynchronousNonBlockingStepExecution.java:47)16:24:36 at hudson.security.ACL.impersonate(ACL.java:290)16:24:36 at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1.run(AbstractSynchronousNonBlockingStepExecution.java:44)16:24:36 at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)16:24:36 at java.util.concurrent.FutureTask.run(FutureTask.java:266)16:24:36 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)16:24:36 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)16:24:36 at java.lang.Thread.run(Thread.java:748)16:24:36 Suppressed: java.util.concurrent.ExecutionException: java.io.IOException: This archive contains unclosed entries.16:24:36 at hudson.remoting.Channel$2.adapt(Channel.java:992)16:24:36 at hudson.remoting.Channel$2.adapt(Channel.java:986)16:24:36 at hudson.remoting.FutureAdapter.get(FutureAdapter.java:59)16:24:36 at hudson.FilePath.copyRecursiveTo(FilePath.java:2389)16:24:36 ... 14 more*16:24:36* Caused by: java.io.IOException: This archive contains unclosed entries.16:24:36 at org.apache.commons.compress.archivers.tar.TarArchiveOutputStream.finish(TarArchiveOutputStream.java:289)16:24:36 at org.apache.commons.compress.archivers.tar.TarArchiveOutputStream.close(TarArchiveOutputStream.java:307)16:24:36 at hudson.util.io.TarArchiver.close(TarArchiver.java:126)16:24:36 at hudson.FilePath.writeToTar(FilePath.java:2568)16:24:36 at hudson.FilePath.access$4000(FilePath.java:211)16:24:36 at hudson.FilePath$CopyRecursiveRemoteToLocal.invoke(FilePath.java:2531)16:24:36 at hudson.FilePath$CopyRecursiveRemoteToLocal.invoke(FilePath.java:2518)16:24:36 at hudson.FilePath$FileCallableWrapper.call(FilePath.java:3069)16:24:36 at hudson.remoting.UserRequest.perform(UserRequest.java:211)16:24:36 at hudson.remoting.UserRequest.perform(UserRequest.java:54)16:24:36 at hudson.remoting.Request$2.run(Request.java:369)16:24:36 at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)16:24:36 ... 4 more*16:24:36* Suppressed: hudson.remoting.Channel$CallSiteStackTrace: Remote call to dev*16:24:36* at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1741)16:24:36 at hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:356)16:24:36 at hudson.remoting.Channel$2.adapt(Channel.java:990)16:24:36 at hudson.remoting.Channel$2.adapt(Channel.java:986)16:24:36 at hudson.remoting.FutureAdapter.get(FutureAdapter.java:59)16:24:36 at hudson.FilePath.copyRecursiveTo(FilePath.java:2389)16:24:36 at hudson.FilePath.copyRecursiveTo(FilePath.java:2350)16:24:36 at hudson.FilePath.copyRecursiveTo(FilePath.java:2338)16:24:36 at hudson.FilePath.copyRecursiveTo(FilePath.java:2321)16:24:36 at htmlpublisher.HtmlPublisher.publishReports(HtmlPublisher.java:277)16:24:36 at htmlpublisher.workflow.PublishHTMLStepExecution.run(PublishHTMLStepExecution.java:70)16:24:36 at
[JIRA] (JENKINS-44930) Allow sh to return exit status, stdout and stderr all at once
Title: Message Title
Alexander Samoylov edited a comment on JENKINS-44930
Re: Allow sh to return exit status, stdout and stderr all at once
Using a temp file is an ugly workaround which has at least these obvious disadvantages:1. You never have 100% guarantee that you don't break parallelism. Every time you introduce one more parallel "axe" (such as release/debug conf, branch, os whatever) you must take care that the temp file has the corresponding suffix.2. This method won't work in some cases if a command already contains output redirection. For example, on Linux this works: rm 123 > temp.txt 2>&1. I am not sure if we can do the same on Windows. There may be more complex cases with tricky double/single quote combinations and multiple output redirections, of a command which consists of several commands, semicolon separated. At the end we always loose generality and platform-independency if we use a temp file.3. You must remove the temp file after the command execution, but how do you do it on the node if the pipeline stuff is executed on master? You cannot use Java method File.createTempFile() for this, because it creates the temp file on master. It means that the code which generates the file name must run on master and then you pass this name to the "sh" or "bat" when you remove it. Distinguishing to "sh" and "bat" is also losing of platform-independency by the way.My current solution with which tried looks like this:{code:java}def getOSPathSep() {if (isUnix()) {return '/'} else { return '\\'}}def getTempDirOnNode() {if (isUnix()) {return env.TMPDIR != null ? env.TMPDIR : '/tmp'} else { return env.TEMP}}/* May not work if "cmd" already contains output redirection or more complex shell syntax. */def runCmdOnNodeSavingExitCodeAndStdout(cmd) {def rc = 0def stdout = nulldef tempFileName = 'runCmdOnNodeSavingExitCodeAndStdout_' + UUID.randomUUID() + '.txt'def tempFilePath = getTempDirNode() + getOSPathSep() + tempFileNamedef tempFileHandle = new File(tempFilePath)print("Using temp file: " + tempFilePath)if (isUnix()) {rc = sh(script: cmd + ' > ' + tempFilePath, returnStatus: true)} else {rc = bat(script: cmd + ' > ' + tempFilePath, returnStatus: true);}stdout = readFile(tempFilePath).trim()// Delete temporary file from the nodeif (isUnix()) {sh(script: 'rm -f ' + tempFilePath, returnStatus: true)} else {bat(script: 'del /q ' + tempFilePath, returnStatus: true);}return [ rc, stdout ]}{code}This workaround looks super ugly and of course I would want just say response = sh(cmd); response.getStatus() etc. without the tones of lines.I vote +1 for this feature. It is such a basic thing that I am surprised what else can be discussed here. just must be.If pipeline maintainers refuse to implement it we will probably need to write a plugin. I tried to implement a Java function which executes another arbitrary Java code of the given node, but it does not work directly from the pipeline script due to another limitation (see [Pipeline scripts fails to call Java code on slave: Failed to deserialize the Callable object|https://issues.jenkins-ci.org/browse/JENKINS-59778], however from a plugin it must work. But I still hope this feature will be implemented, because it is in high demand and I don't see any reason to not have it.
[JIRA] (JENKINS-44930) Allow sh to return exit status, stdout and stderr all at once
Title: Message Title
Alexander Samoylov edited a comment on JENKINS-44930
Re: Allow sh to return exit status, stdout and stderr all at once
Using a temp file is an ugly workaround which has at least these obvious disadvantages:1. You never have 100% guarantee that you don't break parallelism. Every time you introduce one more parallel "axe" (such as release/debug conf, branch, os whatever) you must take care that the temp file has the corresponding suffix.2. This method won't work in some cases if a command already contains output redirection. For example, on Linux this works: rm 123 > temp.txt 2>&1. I am not sure if we can do the same on Windows. There may be more complex cases with tricky double/single quote combinations and multiple output redirections, of a command which consists of several commands, semicolon separated. At the end we always loose generality and platform-independency if we use a temp file.3. You must remove the temp file after the command execution, but how do you do it on the node if the pipeline stuff is executed on master? You cannot use Java method File.createTempFile() for this, because it creates the temp file on master. It means that the code which generates the file name must run on master and then you pass this name to the "sh" or "bat" when you remove it. Distinguishing to "sh" and "bat" is also losing of platform-independency by the way.My current solution with which tried looks like this:{code:java}def getTempDirOnNode() {if (isUnix()) {return env.TMPDIR != null ? env.TMPDIR : '/tmp'} else { return env.TEMP}}/* May not work if "cmd" already contains output redirection or more complex shell syntax. */def runCmdOnNodeSavingExitCodeAndStdout(cmd) {def rc = 0def stdout = null print("Using temp directory: " + getTempDirOnNode()) def tempFileName = 'runCmdOnNodeSavingExitCodeAndStdout_' + UUID.randomUUID() + '.txt'def tempFilePath = getTempDirNode() + getOSPathSep() + tempFileNamedef tempFileHandle = new File(tempFilePath)print("Using temp file: " + tempFilePath)if (isUnix()) {rc = sh(script: cmd + ' > ' + tempFilePath, returnStatus: true)} else {rc = bat(script: cmd + ' > ' + tempFilePath, returnStatus: true);}stdout = readFile(tempFilePath).trim()// Delete temporary file from the nodeif (isUnix()) {sh(script: 'rm -f ' + tempFilePath, returnStatus: true)} else {bat(script: 'del /q ' + tempFilePath, returnStatus: true);}return [ rc, stdout ]}{code}This workaround looks super ugly and of course I would want just say response = sh(cmd); response.getStatus() etc. without the tones of lines.I vote +1 for this feature. It is such a basic thing that I am surprised what else can be discussed here. just must be.If pipeline maintainers refuse to implement it we will probably need to write a plugin. I tried to implement a Java function which executes another arbitrary Java code of the given node, but it does not work directly from the pipeline script due to another limitation (see [Pipeline scripts fails to call Java code on slave: Failed to deserialize the Callable object|https://issues.jenkins-ci.org/browse/JENKINS-59778], however from a plugin it must work. But I still hope this feature will be implemented, because it is in high demand and I don't see any reason to not have it.
[JIRA] (JENKINS-44930) Allow sh to return exit status, stdout and stderr all at once
Title: Message Title
Alexander Samoylov commented on JENKINS-44930
Re: Allow sh to return exit status, stdout and stderr all at once
Using a temp file is an ugly workaround which has at least these obvious disadvantages: 1. You never have 100% guarantee that you don't break parallelism. Every time you introduce one more parallel "axe" (such as release/debug conf, branch, os whatever) you must take care that the temp file has the corresponding suffix. 2. This method won't work in some cases if a command already contains output redirection. For example, on Linux this works: rm 123 > temp.txt 2>&1. I am not sure if we can do the same on Windows. There may be more complex cases with tricky double/single quote combinations and multiple output redirections, of a command which consists of several commands, semicolon separated. At the end we always loose generality and platform-independency if we use a temp file. 3. You must remove the temp file after the command execution, but how do you do it on the node if the pipeline stuff is executed on master? You cannot use Java method File.createTempFile() for this, because it creates the temp file on master. It means that the code which generates the file name must run on master and then you pass this name to the "sh" or "bat" when you remove it. Distinguishing to "sh" and "bat" is also losing of platform-independency by the way. My current solution with which tried looks like this:
def getTempDirOnNode() {
if (isUnix()) {
return env.TMPDIR != null ? env.TMPDIR : '/tmp'
} else {
return env.TEMP
}
}
/* May not work if "cmd" already contains output redirection or more complex shell syntax. */
def runCmdOnNodeSavingExitCodeAndStdout(cmd) {
def rc = 0
def stdout = null
print("Using temp directory: " + getTempDirOnNode())
def tempFileName = 'runIgnoreExitCodeStdout_' + UUID.randomUUID() + '.txt'
def tempFilePath = getTempDirNode() + getOSPathSep() + tempFileName
def tempFileHandle = new File(tempFilePath)
print("Using temp file: " + tempFilePath)
if (isUnix()) {
rc = sh(script: cmd + ' > ' + tempFilePath, returnStatus: true)
} else {
rc = bat(script: cmd + ' > ' + tempFilePath, returnStatus: true);
}
stdout = readFile(tempFilePath).trim()
// Delete temporary file from the node
if (isUnix()) {
sh(script: 'rm -f ' + tempFilePath, returnStatus: true)
} else {
bat(script: 'del /q ' + tempFilePath, returnStatus: true);
}
return [ rc, stdout ]
}
This workaround looks super ugly and of course I would want just say response = sh(cmd); response.getStatus() etc. without the tones of lines. I vote +1 for this feature. It is such a basic thing that I am surprised what else can be discussed here. just must be. If pipeline maintainers refuse to implement it we will probably need to write a plugin. I tried to implement a Java function which executes another arbitrary Java code of the given node, but it does not work directly from the pipeline script due to another limitation (see Pipeline scripts fails to call Java code on slave: Failed to deserialize the Callable object, however from a plugin it must work. But I still hope this feature will be implemented, because it is in high demand and I don't see any reason to not have it.
[JIRA] (JENKINS-44930) Allow sh to return exit status, stdout and stderr all at once
Title: Message Title
Alexander Samoylov edited a comment on JENKINS-44930
Re: Allow sh to return exit status, stdout and stderr all at once
Using a temp file is an ugly workaround which has at least these obvious disadvantages:1. You never have 100% guarantee that you don't break parallelism. Every time you introduce one more parallel "axe" (such as release/debug conf, branch, os whatever) you must take care that the temp file has the corresponding suffix.2. This method won't work in some cases if a command already contains output redirection. For example, on Linux this works: rm 123 > temp.txt 2>&1. I am not sure if we can do the same on Windows. There may be more complex cases with tricky double/single quote combinations and multiple output redirections, of a command which consists of several commands, semicolon separated. At the end we always loose generality and platform-independency if we use a temp file.3. You must remove the temp file after the command execution, but how do you do it on the node if the pipeline stuff is executed on master? You cannot use Java method File.createTempFile() for this, because it creates the temp file on master. It means that the code which generates the file name must run on master and then you pass this name to the "sh" or "bat" when you remove it. Distinguishing to "sh" and "bat" is also losing of platform-independency by the way.My current solution with which tried looks like this:{code:java}def getTempDirOnNode() {if (isUnix()) {return env.TMPDIR != null ? env.TMPDIR : '/tmp'} else { return env.TEMP}}/* May not work if "cmd" already contains output redirection or more complex shell syntax. */def runCmdOnNodeSavingExitCodeAndStdout(cmd) {def rc = 0def stdout = nullprint("Using temp directory: " + getTempDirOnNode())def tempFileName = ' runIgnoreExitCodeStdout_ runCmdOnNodeSavingExitCodeAndStdout_ ' + UUID.randomUUID() + '.txt'def tempFilePath = getTempDirNode() + getOSPathSep() + tempFileNamedef tempFileHandle = new File(tempFilePath)print("Using temp file: " + tempFilePath)if (isUnix()) {rc = sh(script: cmd + ' > ' + tempFilePath, returnStatus: true)} else {rc = bat(script: cmd + ' > ' + tempFilePath, returnStatus: true);}stdout = readFile(tempFilePath).trim()// Delete temporary file from the nodeif (isUnix()) {sh(script: 'rm -f ' + tempFilePath, returnStatus: true)} else {bat(script: 'del /q ' + tempFilePath, returnStatus: true);}return [ rc, stdout ]}{code}This workaround looks super ugly and of course I would want just say response = sh(cmd); response.getStatus() etc. without the tones of lines.I vote +1 for this feature. It is such a basic thing that I am surprised what else can be discussed here. just must be.If pipeline maintainers refuse to implement it we will probably need to write a plugin. I tried to implement a Java function which executes another arbitrary Java code of the given node, but it does not work directly from the pipeline script due to another limitation (see [Pipeline scripts fails to call Java code on slave: Failed to deserialize the Callable object|https://issues.jenkins-ci.org/browse/JENKINS-59778], however from a plugin it must work. But I still hope this feature will be implemented, because it is in high demand and I don't see any reason to not have it.
[JIRA] (JENKINS-59868) Add information about missing working directory to Polling logs
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-59868 Add information about missing working directory to Polling logs Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202608.157166054.11793.1571662560216%40Atlassian.JIRA.
[JIRA] (JENKINS-59868) Add information about missing working directory to Polling logs
Title: Message Title Allan BURDAJEWICZ created an issue Jenkins / JENKINS-59868 Add information about missing working directory to Polling logs Issue Type: Improvement Assignee: Mark Waite Components: git-plugin Created: 2019-10-21 12:22 Priority: Minor Reporter: Allan BURDAJEWICZ Troubleshooting Git Polling may be cumbersome. Found out recently a case where Polling would report changes without telling us why: Using strategy: Default [poll] Last Built Revision: Revision xxx (refs/remotes/origin/) no polling baseline in on Done. Took 6 ms Changes found Looking at the code, there might be cases where the workspace exists but the workingDirectory doesn't: https://github.com/jenkinsci/git-plugin/blob/git-4.0.0-rc/src/main/java/hudson/plugins/git/GitSCM.java#L773. It would be ideal for diagnosability that before returning any PollingResult, a relevant log be printed. Add Comment
[JIRA] (JENKINS-59867) NodeJS tool installation fails on Windows
Title: Message Title James Howe created an issue Jenkins / JENKINS-59867 NodeJS tool installation fails on Windows Issue Type: Bug Assignee: Nikolas Falco Attachments: image-2019-10-21-13-07-02-606.png Components: nodejs-plugin Created: 2019-10-21 12:11 Environment: Windows Server 2019 (OS Build 17763.678) Labels: windows Priority: Major Reporter: James Howe Tool installation on a Windows node fails for some reason at this rename: Unpacking [https://nodejs.org/dist/v10.16.3/node-v10.16.3-win-x64.zip] to C:\Users\jenkins\tools\jenkins.plugins.nodejs.tools.NodeJSInstallation\v10 on devops-test3-vm java.io.IOException: Failed to rename C:\Users\jenkins\tools\jenkins.plugins.nodejs.tools.NodeJSInstallation\v10\node-v10.16.3-win-x64 to C:\Users\jenkins\tools\jenkins.plugins.nodejs.tools.NodeJSInstallation\v10\node-v10.16.3-win-x64.__rename at hudson.FilePath$MoveAllChildrenTo.invoke(FilePath.java:2171) at hudson.FilePath$MoveAllChildrenTo.invoke(FilePath.java:2159) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:3052) at hudson.remoting.UserRequest.perform(UserRequest.java:212) at hudson.remoting.UserRequest.perform(UserRequest.java:54) at
[JIRA] (JENKINS-59866) Octane Cucumber test reporter plugin fails previous passed build after Jenkins restarts
Title: Message Title Minh Tran updated an issue Jenkins / JENKINS-59866 Octane Cucumber test reporter plugin fails previous passed build after Jenkins restarts Change By: Minh Tran Environment: Jenkins version: 2.190.1 LTS (Windows Installer) .Java version: JDK 1.8.0_181Jenkins host: WS2012 R2 Standard No service pack.Plugin: Micro Focus Application Automation Tools’ plugin version 5.9.ALM Octane version: 12.60 (CP10).ALM Octane O/S: Windows 2016 ALM Octane setup: Clustered environment. ALM Octane: Using TLS 1.2 (Port 8443).Octane API: API Access is successfully generated. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202605.1571659536000.11764.1571659740160%40Atlassian.JIRA.
[JIRA] (JENKINS-59280) jiraJqlSearch Error Message: null value after upgrade
Title: Message Title
Benjamin Kihm edited a comment on JENKINS-59280
Re: jiraJqlSearch Error Message: null value after upgrade
We have still the issue with jira-steps-plugin 1.5.1:{code:java}[Pipeline] jiraGetFields [Pipeline] jiraGetFieldsJIRA: Site - Jira - Querying All Fields including Custom fields. Error Code: - 1Error 1Error Message: null [Pipeline] }[Pipeline] // scriptError when executing always post condition:hudson.AbortException at org.thoughtslive.jenkins.plugins.jira.util.JiraStepExecution.logResponse(JiraStepExecution.java:132) at org.thoughtslive.jenkins.plugins.jira.steps.GetFieldsStep$Execution.run(GetFieldsStep.java:68) at org.thoughtslive.jenkins.plugins.jira.steps.GetFieldsStep$Execution.run(GetFieldsStep.java:45) at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748){code}
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit
[JIRA] (JENKINS-59280) jiraJqlSearch Error Message: null value after upgrade
Title: Message Title
Benjamin Kihm edited a comment on JENKINS-59280
Re: jiraJqlSearch Error Message: null value after upgrade
We have still the issue with jira-steps-plugin 1.5.1:{code:java}[Pipeline] jiraGetFields[Pipeline] jiraGetFieldsJIRA: Site - Jira - Querying All Fields including Custom fields.Error Code: -1Error Message: null[Pipeline] } [Pipeline] // scriptError when executing always post condition:hudson.AbortException at org.thoughtslive.jenkins.plugins.jira.util.JiraStepExecution.logResponse(JiraStepExecution.java:132) at org.thoughtslive.jenkins.plugins.jira.steps.GetFieldsStep$Execution.run(GetFieldsStep.java:68) at org.thoughtslive.jenkins.plugins.jira.steps.GetFieldsStep$Execution.run(GetFieldsStep.java:45) at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748){code}
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit
[JIRA] (JENKINS-59866) Octane Cucumber test reporter plugin fails previous passed build after Jenkins restarts
Title: Message Title Minh Tran created an issue Jenkins / JENKINS-59866 Octane Cucumber test reporter plugin fails previous passed build after Jenkins restarts Issue Type: Bug Assignee: Maria Narcisa Galan Attachments: After_Jenkins_Restart.png, Before_Jenkins_Restart.png, Jenkins_Console_Output.png, Octane_Job_Status.png, Post_build_Actions.png Components: hp-application-automation-tools-plugin Created: 2019-10-21 12:05 Environment: Jenkins version: 2.190.1 LTS. Java version: JDK 1.8.0_181 Jenkins host: WS2012 R2 Standard No service pack. Plugin: Micro Focus Application Automation Tools’ plugin version 5.9. ALM Octane version: 12.60 (CP10). ALM Octane O/S: Windows 2016 ALM Octane setup: Clustered environment. ALM Octane: Using TLS 1.2 (Port 8443). Octane API: API Access is successfully generated. Labels: hp-application-automation-tools Priority: Minor Reporter: Minh Tran Hi, I am currently having issue with "Octane Cucumber test reporter" plugin which could be reproduced as below steps: Steps: Create a Maven project using cucumber framework and "com.hpe.alm.octane.OctaneGherkinFormatter:target\\gherkin-resultsManualRunnerTest_OctaneGherkinResults.xml" plugin. Create a
[JIRA] (JENKINS-59280) jiraJqlSearch Error Message: null value after upgrade
Title: Message Title Benjamin Kihm reopened an issue We have still the issue with jira-steps-plugin 1.5.1: [Pipeline] jiraGetFields[Pipeline] jiraGetFieldsJIRA: Site - Jira - Querying All Fields including Custom fields.Error Code: -1Error Message: null[Pipeline] }[Pipeline] // scriptError when executing always post condition:hudson.AbortException at org.thoughtslive.jenkins.plugins.jira.util.JiraStepExecution.logResponse(JiraStepExecution.java:132) at org.thoughtslive.jenkins.plugins.jira.steps.GetFieldsStep$Execution.run(GetFieldsStep.java:68) at org.thoughtslive.jenkins.plugins.jira.steps.GetFieldsStep$Execution.run(GetFieldsStep.java:45) at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) Jenkins / JENKINS-59280 jiraJqlSearch Error Message: null value after upgrade Change By: Benjamin Kihm Resolution: Fixed Status: Closed Reopened Add Comment
[JIRA] (JENKINS-56586) Parallel stages or branches cannot be nested ("can only be included in a top-level stage")
Title: Message Title
Sergio Mira edited a comment on JENKINS-56586
Re: Parallel stages or branches cannot be nested ("can only be included in a top-level stage")
You can use a script and run the parallel in there as a workaround in declarative pipelines :{noformat} pipeline {agent nonestages {stage('Cancel Previous Builds') { steps { echo "Cancel Previous Builds" } }stage('Pre-build') { steps { echo "Pre-build" } }stage("Build and Test") {parallel {stage('Build and Test') {stages { stage('Build Platform 1') { steps { echo "Build Platform 1" } } stage('Test Platform 1') { script { parallel([ 'Test 1': { echo "Test 1" }, 'Test 2': { echo "Test 2" }, 'Test 3') { echo "Test 3" } ]) } }}}stage('Build Platform 2') { steps { echo "Build Platform 2" } }stage('Build Platform 3') { steps { echo "Build Platform 3" } }}}}}{noformat}I
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit
[JIRA] (JENKINS-59865) Bogus Scala Compiler warning about missing files after test failure in sbt
Title: Message Title
Patrick Roemer created an issue
Jenkins / JENKINS-59865
Bogus Scala Compiler warning about missing files after test failure in sbt
Issue Type:
Bug
Assignee:
Ulli Hafner
Components:
warnings-ng-plugin
Created:
2019-10-21 11:44
Environment:
Jenkins v2.190.1 Warnings-NG v6.1.1
Labels:
sbt
Priority:
Trivial
Reporter:
Patrick Roemer
sbt test run fails in Jenkins build, producing a line such as: [error] Total time: 127 s, completed Oct 7, 2019 9:11:30 AM Later, during post { always { recordIssues enabledForFailure: true, tools: [scala()] } } the following output occurs in Jenkins log: [Scala Compiler] [-ERROR-] Can't resolve absolute paths for some files: [Scala Compiler] [-ERROR-] - Total time: 127 s, completed Oct 7, 2019 9 [Scala Compiler] [-ERROR-] Can't create fingerprints for some files: [Scala Compiler] [-ERROR-] - 'Total time: 127 s, completed Oct 7, 2019 9', IO exception has been thrown: java.nio.file.NoSuchFileException: Total time: 127 s, completed Oct 7, 2019 9 Looks like a false positive from [Sbt]ScalacParser regex capture at first glance: https://github.com/jenkinsci/analysis-model/blob/ddc3068166835508c4a5b1a8d30cec7d92109bfc/src/main/java/edu/hm/hafner/analysis/parser/SbtScalacParser.java#L19 https://github.com/jenkinsci/analysis-model/blob/ddc3068166835508c4a5b1a8d30cec7d92109bfc/src/main/java/edu/hm/hafner/analysis/parser/ScalacParser.java#L20 Not a big deal at all, but can be confusing (in particular since scalac ran green).
[JIRA] (JENKINS-56586) Parallel stages or branches cannot be nested ("can only be included in a top-level stage")
Title: Message Title
Sergio Mira commented on JENKINS-56586
Re: Parallel stages or branches cannot be nested ("can only be included in a top-level stage")
You can use a script and run the parallel in there:
pipeline {
agent none
stages {
stage('Cancel Previous Builds') { steps { echo "Cancel Previous Builds" } }
stage('Pre-build') { steps { echo "Pre-build" } }
stage("Build and Test") {
parallel {
stage('Build and Test') {
stages {
stage('Build Platform 1') { steps { echo "Build Platform 1" } }
stage('Test Platform 1') {
script {
parallel([
'Test 1': { echo "Test 1" },
'Test 2': { echo "Test 2" },
'Test 3') { echo "Test 3" }
])
}
}
}
}
stage('Build Platform 2') { steps { echo "Build Platform 2" } }
stage('Build Platform 3') { steps { echo "Build Platform 3" } }
}
}
}
}
I
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you
[JIRA] (JENKINS-59826) Error launching agent into second cloud
Title: Message Title Andrew Cameron-Douglas edited a comment on JENKINS-59826 Re: Error launching agent into second cloud Thanks Carlos. [~csanchez]! I'm just looking into the reasons for the failures a little deeper. The Jenkins file is actually part of a shared library. Two files of that are the deploy.groovy file and the TestRunner.groovy file. These spin up an agent for use during deployment (deploy.groovy) and then spin up an agent for testing in the target cluster at the end of the deployment (TestRunner . groovy). Please find these attached (abridged).I'll be working on this most of the day so feel free to respond and I'll get back to you asap.[^TestRunner.groovy] Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202561.157132511.11705.1571657944175%40Atlassian.JIRA.
[JIRA] (JENKINS-59826) Error launching agent into second cloud
Title: Message Title Andrew Cameron-Douglas commented on JENKINS-59826 Re: Error launching agent into second cloud Thanks Carlos. I'm just looking into the reasons for the failures a little deeper. The Jenkins file is actually part of a shared library. Two files of that are the deploy.groovy file and the TestRunner.groovy file. These spin up an agent for use during deployment and then spin up an agent for testing at the end of the deployment. Please find these attached (abridged). I'll be working on this most of the day so feel free to respond and I'll get back to you asap. TestRunner.groovy Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202561.157132511.11698.1571657880396%40Atlassian.JIRA.
[JIRA] (JENKINS-59826) Error launching agent into second cloud
Title: Message Title Andrew Cameron-Douglas updated an issue Jenkins / JENKINS-59826 Error launching agent into second cloud Change By: Andrew Cameron-Douglas Attachment: TestRunner.groovy Attachment: deploy.groovy Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202561.157132511.11677.1571657821952%40Atlassian.JIRA.
[JIRA] (JENKINS-57204) Provision failures does not clean up deployments
Title: Message Title
Olivier Vernin commented on JENKINS-57204
Re: Provision failures does not clean up deployments
It appears this issue is back on ci.jenkins.io, for some reason, deployments are not cleaned up 2019-10-21 10:50:55.713+ [id=55] WARNING hudson.slaves.NodeProvisioner#lambda$update$6: Unexpected exception encountered while provisioning agent aci-maven java.lang.Exception: Status code 409, {"error":{"code":"DeploymentQuotaExceeded","message":"Creating the deployment 'aci-maven-h3c19t5n' would exceed the quota of '800'. The current deployment count is '800', please delete some deployments before creating a new one. Please see https://aka.ms/arm-debug for usage details."}} at com.microsoft.jenkins.containeragents.aci.AciService.createDeployment(AciService.java:141) at com.microsoft.jenkins.containeragents.aci.AciContainerTemplate.provisionAgents(AciContainerTemplate.java:128) at com.microsoft.jenkins.containeragents.aci.AciCloud$1.call(AciCloud.java:104) Caused: java.lang.Exception at com.microsoft.jenkins.containeragents.aci.AciCloud$1.call(AciCloud.java:140) at com.microsoft.jenkins.containeragents.aci.AciCloud$1.call(AciCloud.java:80) at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46) at jenkins.security.ImpersonatingExecutorService$2.call(ImpersonatingExecutorService.java:71) at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) at java.base/java.lang.Thread.run(Thread.java:834)
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-57204) Provision failures does not clean up deployments
Title: Message Title Olivier Vernin updated JENKINS-57204 Jenkins / JENKINS-57204 Provision failures does not clean up deployments Change By: Olivier Vernin Status: In Review Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198961.155637878.11639.1571655601306%40Atlassian.JIRA.
[JIRA] (JENKINS-57204) Provision failures does not clean up deployments
Title: Message Title Olivier Vernin updated JENKINS-57204 Jenkins / JENKINS-57204 Provision failures does not clean up deployments Change By: Olivier Vernin Resolution: Fixed Status: Resolved In Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198961.155637878.11636.1571655480410%40Atlassian.JIRA.
[JIRA] (JENKINS-59833) Stash Pull Request Builder Multiple PR in single build
Title: Message Title Jakub Bochenski commented on JENKINS-59833 Re: Stash Pull Request Builder Multiple PR in single build Upkar Rai can you please check if the incremental build fixes the issue for you? It should be available soonish, once https://ci.jenkins.io/job/Plugins/job/stash-pullrequest-builder-plugin/job/PR-151/ completes. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202568.1571346229000.11627.1571654640450%40Atlassian.JIRA.
[JIRA] (JENKINS-59833) Stash Pull Request Builder Multiple PR in single build
Title: Message Title Jakub Bochenski started work on JENKINS-59833 Change By: Jakub Bochenski Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202568.1571346229000.11633.1571654640629%40Atlassian.JIRA.
[JIRA] (JENKINS-59833) Stash Pull Request Builder Multiple PR in single build
Title: Message Title Jakub Bochenski assigned an issue to Pavel Roskin Jenkins / JENKINS-59833 Stash Pull Request Builder Multiple PR in single build Change By: Jakub Bochenski Assignee: Pavel Roskin Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202568.1571346229000.11630.1571654640529%40Atlassian.JIRA.
[JIRA] (JENKINS-59844) Process Launcher shouldn't throw ArrayIndexOutOfBoundException on empty command
Title: Message Title Ramon Leon commented on JENKINS-59844 Re: Process Launcher shouldn't throw ArrayIndexOutOfBoundException on empty command Dishit Devasia I've been working on it for a while. Are you fine if I take care of it? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202579.1571403818000.11623.1571653560756%40Atlassian.JIRA.
[JIRA] (JENKINS-59844) Process Launcher shouldn't throw ArrayIndexOutOfBoundException on empty command
Title: Message Title Esther Álvarez Feijoo edited a comment on JENKINS-59844 Re: Process Launcher shouldn't throw ArrayIndexOutOfBoundException on empty command [ Here you have a test to reproduce it: [ https://github.com/EstherAF/jenkins/commit/198e0a22c326f7d5a1c130deb56063592e646d41 |https://github.com/EstherAF/jenkins/commit/198e0a22c326f7d5a1c130deb56063592e646d41 ] Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202579.1571403818000.11617.1571653140137%40Atlassian.JIRA.
[JIRA] (JENKINS-59844) Process Launcher shouldn't throw ArrayIndexOutOfBoundException on empty command
Title: Message Title Esther Álvarez Feijoo commented on JENKINS-59844 Re: Process Launcher shouldn't throw ArrayIndexOutOfBoundException on empty command [Here you have a test to reproduce it: https://github.com/EstherAF/jenkins/commit/198e0a22c326f7d5a1c130deb56063592e646d41|https://github.com/EstherAF/jenkins/commit/198e0a22c326f7d5a1c130deb56063592e646d41] Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202579.1571403818000.11615.1571653080404%40Atlassian.JIRA.
[JIRA] (JENKINS-59826) Error launching agent into second cloud
Title: Message Title Carlos Sanchez commented on JENKINS-59826 Re: Error launching agent into second cloud I answered the email. Do you have your Jenkinsfile to see how are you configuring the pod? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202561.157132511.11613.1571652960211%40Atlassian.JIRA.
