[JIRA] (JENKINS-57515) AIX slave start error due to can not found /com/sun/jna/aix-ppc64/libjnidispatch.so
Title: Message Title li li created an issue Jenkins / JENKINS-57515 AIX slave start error due to can not found /com/sun/jna/aix-ppc64/libjnidispatch.so Issue Type: Bug Assignee: Jeff Thompson Components: remoting Created: 2019-05-17 07:04 Labels: remoting slave Priority: Major Reporter: li li this issue happend only on starting AIX slave, which will try to find /com/sun/jna/aix-ppc64/libjnidispatch.so However, in jna jar file, i don't found such file actually. the correct file should be com/sun/jna/aix-ppc64/libjnidispatch.a instead of *.so(which are for other unix/linux) this issue will also cause the jobs always run fail on AIX slaves. node start log: Remoting version: 3.29 This is a Unix agent May 16, 2019 11:00:14 PM hudson.remoting.UserRequest perform WARNING: LinkageError while performing UserRequest:jenkins.slaves.StandardOutputSwapper$ChannelSwapper@759450a7 java.lang.UnsatisfiedLinkError: jnidispatch (/com/sun/jna/aix-ppc64/libjnidispatch.so) not found in resource path at com.sun.jna.Native.loadNativeLibraryFromJar(Native.java:723) at com.sun.jna.Native.loadNativeLibrary(Native.java:697) at com.sun.jna.Native.(Native.java:127) at hudson.util.jna.GNUCLibrary.(GNUCLibrary.java:115) at jenkins.slaves.StandardOutputSwapper$ChannelSwapper.swap(StandardOutputSwapper.java:60) at jenkins.slaves.StandardOutputSwapper$ChannelSwapper.call(StandardOutputSwapper.java:45) at jenkins.slaves.StandardOutputSwapper$ChannelSwapper.call(StandardOutputSwapper.java:39) 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.jav
[JIRA] (JENKINS-57501) cmakeBuild does not set environment variables in Windows when run in Pipeline
Title: Message Title Vladimir Eremeev commented on JENKINS-57501 Re: cmakeBuild does not set environment variables in Windows when run in Pipeline Yes, this duplicates JENKINS-51060 with addition of ignorance of "envVars" in steps. According to last comment in that issue, added 2 months after it was closed, the bug was not fixed. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199364.155799447.553.1558077060129%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57501) cmakeBuild does not set environment variables in Windows when run in Pipeline
Title: Message Title
Vladimir Eremeev updated an issue
Jenkins / JENKINS-57501
cmakeBuild does not set environment variables in Windows when run in Pipeline
Change By:
Vladimir Eremeev
Pipeline snippet{{def cmake_tasks() { }} {{ def tasks=[:] }} {{ def steps = [[withCmake: true]] }}{{ def os = "windows" }} {{ def config = "Debug" }} {{ def generator = "Ninja" }}{{ def vars=""" }} {{ LIB=C:\\Program Files (x86)\\Microsoft Visual Studio 14.0\\VC\\LIB\\amd64;C:\\Program Files (x86)\\Microsoft Visual Studio 14.0\\VC\\ATLMFC\\LIB\\amd64;C:\\Program Files (x86)\\Windows Kits\\10\\lib\\10.0.17763.0\\ucrt\\x64;C:\\Program Files (x86)\\Windows Kits\\NETFXSDK\\4.6.1\\lib\\um\\x64;C:\\Program Files (x86)\\Windows Kits\\10\\lib\\10.0.17763.0\\um\\x64; }} {{ PATH=C:\\Program Files (x86)\\MSBuild\\14.0\\bin\\amd64;C:\\Program Files (x86)\\Microsoft Visual Studio 14.0\\VC\\BIN\\amd64;C:\\Windows\\Microsoft.NET\\Framework64\\v4.0.30319;C:\\Windows\\Microsoft.NET\\Framework64\\;C:\\Program Files (x86) \\ }}{{ Windows Kits\\10\\bin\\x64;C:\\Program Files (x86)\\Windows Kits\\10\\bin\\x86;C:\\Program Files (x86)\\Microsoft SDKs\\Windows\\v10.0A\\bin\\NETFX 4.6.1 Tools\\x64\\;C: \\ }}{{ Program Files (x86)\\Common Files\\Oracle\\Java\\javapath;C:\\ProgramData\\Oracle\\Java\\javapath;C:\\CMake\\bin;c:\\windows\\system32;C:\\Program Files \\ }}{{ NVIDIA GPU Computing Toolkit\\CUDA\\v7.0\\bin;C:\\Program Files\\NVIDIA GPU Computing Toolkit\\CUDA\\v7.0\\libnvvp;g:\\Bin; }} {{ """ }} {{ def cmakeArgs = "-DARG=VALUE" }} {{ def cmake_inst = 'InSearchPath' }}{{ steps.add([envVars: vars]) }} {{ cmakeArgs = cmakeArgs + " -DCMAKE_C_COMPILER=cl -DCMAKE_CXX_COMPILER=cl -DCMAKE_MAKE_PROGRAM=g:\\Bin\\ninja" }} {{ tasks["${os}"] = { }} {{ node("${os}"){ }} {{ stage("${os}/ Debug ${config} ") { }} {{ withEnv([vars]){ }} {{ if (os == "windows") }} { {{}} bat "set | sort" println vars println steps {{ } }} {{ cmakeBuild(buildDir: "build_${config}",}}{{ buildType: config,}}{{ cleanBuild: true,}}{{ cmakeArgs: cmakeArgs,}}{{ generator: generator,}}{{ installation: cmake_inst,}}{{ sourceDir: ".",}}{{ steps: steps) }} {{ } }} {{ } }} {{ } }} {{
[JIRA] (JENKINS-55024) Pipeline Job Plugin (workflow-job-plugin) gives empty console output when an error occurs
Title: Message Title Amedee Van Gasse commented on JENKINS-55024 Re: Pipeline Job Plugin (workflow-job-plugin) gives empty console output when an error occurs Hi! I am a colleague of Marco. Looks like we abandoned this issue, I am sorry about that. Other fish to fry at the time because we had a workaround. The issue has resurfaced because the Warnings Next Generations plugin is dependent on a Pipeline Job plugin > 2.28. I will be taking over this issue and answering all your questions about additional information until we get to a solution. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196061.1544001052000.570.1558078680322%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55024) Pipeline Job Plugin (workflow-job-plugin) gives empty console output when an error occurs
Title: Message Title Amedee Van Gasse edited a comment on JENKINS-55024 Re: Pipeline Job Plugin (workflow-job-plugin) gives empty console output when an error occurs Hi! I am a colleague of Marco. Looks like we abandoned this issue, I am sorry about that. Other fish to fry at the time because we had a workaround.The issue has resurfaced because the Warnings Next Generations plugin is dependent on a Pipeline Job plugin > 2.28.I will be taking over this issue and answering all your questions about additional information until we get to a solution. I previously wasn't involved with reporting this issue so it is possible that I will be asking things that have already been asked before, please bear with me. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196061.1544001052000.572.1558080060331%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45479) API tokens and Job/Read permission issue
Title: Message Title Bhavic Patel commented on JENKINS-45479 Re: API tokens and Job/Read permission issue We'd had a similar issue today - But slightly different I think, we assigned the user permissions, but using the token, it couldn't access anything using a curl call. We had to add the group the user is part of (from LDAP), and then it worked. Bit of an issue with this as we only wanted this specific account to have access and not a whole range of accounts in this group. Would get the below error, giving global read permission didn't seem to work Access Denied is missing the Overall/Read permission" Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.183650.1499870282000.579.1558080360154%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57501) cmakeBuild does not set environment variables in Windows when run in Pipeline
Title: Message Title
Vladimir Eremeev commented on JENKINS-57501
Re: cmakeBuild does not set environment variables in Windows when run in Pipeline
Also, it would be good to handle call of "vcvarsall.bat" inside cmakeBuild. Currently I've made a workaround: bat """ call c:\Path\to\Visual\Studio\vcvarsall.bat set > build.props """ var = readFile("build.props") ... cmakeBuild steps: [envVars : vars]
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199364.155799447.581.1558081440092%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57441) Warning on JFR initialization when running with Jenkins 2.164.2 and Jetty 9.4.12.v20180830
Title: Message Title Adrien Lecharpentier updated an issue Jenkins / JENKINS-57441 Warning on JFR initialization when running with Jenkins 2.164.2 and Jetty 9.4.12.v20180830 Change By: Adrien Lecharpentier Issue Type: Bug Improvement Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199254.1557791602000.583.1558081620309%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57441) Warning on JFR initialization when running with Jenkins 2.164.2 and Jetty 9.4.12.v20180830
Title: Message Title Adrien Lecharpentier updated an issue Jenkins / JENKINS-57441 Warning on JFR initialization when running with Jenkins 2.164.2 and Jetty 9.4.12.v20180830 Change By: Adrien Lecharpentier Labels: triaged Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199254.1557791602000.585.1558081620340%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57441) Warning on JFR initialization when running with Jenkins 2.164.2 and Jetty 9.4.12.v20180830
Title: Message Title Adrien Lecharpentier commented on JENKINS-57441 Re: Warning on JFR initialization when running with Jenkins 2.164.2 and Jetty 9.4.12.v20180830 Regression is fixed by reverting Jetty version. Fix is "just" a few days improvements. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199254.1557791602000.587.1558081680129%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55024) Pipeline Job Plugin (workflow-job-plugin) gives empty console output when an error occurs
Title: Message Title Amedee Van Gasse commented on JENKINS-55024 Re: Pipeline Job Plugin (workflow-job-plugin) gives empty console output when an error occurs There were several questions for information. I'll try to bring some structure in them, and then answer them one by one. What does the build folder for the build look like? Does the log file exist? Are there any other errors in the Jenkins logs that seem relevant? Do you know if the build that was broken was building when Jenkins was restarted for the plugin update, or had it already completed? For builds before the upgrade, the full build log should work ok (some markup will not be displayed correctly), but the step logs are expected to be broken. Is that what you are seeing? I am not quite sure what you mean by "full build step logs". Do we have a reproducible bug? Marco Andries are you still seeing this issue? Can you answer the questions in my earlier comment? Can you attach the Pipeline script that is failing so we can see what it is doing? Question 1 I am unsure what kind of answer you want: a screenshot of the build folder? a directory listing of the build folder? a tarball of the build folder? I don't have ssh access to the server that runs Jenkins, and I don't know what you want, so I will take a brute force approach. Difficult also works. I am going to make a job that runs ls -ld $(find /var/lib/jenkins). Please let me know what exactly you need, because I guess that the directory listing may also contain confidential information. Question 2 How can I find out if the log file exists? Question 3 Which Jenkins logs exactly? I'd be happy to provide you the information if I know where to look. Question 4 This is an ambiguous question, the literal answer would be "I know", but that would not be helpful. I will instead answer with steps to reproduce: Pipeline Job Plugin is at version 1.28. Start a failing job, job 1, and let it finish. Look at the console output of job 1 -> there is console output for job 1. Upgrade Pipeline Job Plugin to > 1.28. Restart Jenkins. Look at console output of job 1 -> there is console output for job 1. Start a failing job, job 2, and let it finish.
[JIRA] (JENKINS-55024) Pipeline Job Plugin (workflow-job-plugin) gives empty console output when an error occurs
Title: Message Title Amedee Van Gasse updated JENKINS-55024 Jenkins / JENKINS-55024 Pipeline Job Plugin (workflow-job-plugin) gives empty console output when an error occurs Change By: Amedee Van Gasse Resolution: Incomplete Status: Resolved In Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196061.1544001052000.601.1558081741045%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55024) Pipeline Job Plugin (workflow-job-plugin) gives empty console output when an error occurs
Title: Message Title Amedee Van Gasse updated an issue Jenkins / JENKINS-55024 Pipeline Job Plugin (workflow-job-plugin) gives empty console output when an error occurs Change By: Amedee Van Gasse Attachment: test-pipeline-Jenkinsfile Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196061.1544001052000.593.1558081740921%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57371) error message when building PR
Title: Message Title Audun Halland commented on JENKINS-57371 Re: error message when building PR "Build now" is as broken as the webhook from github, disregarding Closing and re-opening the PR in github had no effect (although the PR was retained as a "disabled" Jenkins job in that meantime. I could try to delete it). I can confirm that 7e88 is the first parent of master HEAD that is not ignored by Ignore Committer Strategy. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199152.155732120.608.1558081860449%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57371) error message when building PR
Title: Message Title Audun Halland edited a comment on JENKINS-57371 Re: error message when building PR "Build now" is as broken as the webhook(?) from github, disregarding Closing and re-opening the PR in github had no effect (although the PR was retained as a "disabled" Jenkins job in that meantime. I could try to delete it).I can confirm that 7e88 is the first parent of master HEAD that is not ignored by Ignore Committer Strategy. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199152.155732120.612.1558081860511%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57371) error message when building PR
Title: Message Title Audun Halland edited a comment on JENKINS-57371 Re: error message when building PR "Build now" is as broken as the webhook( ? ) from github , disregarding . Closing and re-opening the PR in github had no effect (although the PR was retained as a "disabled" Jenkins job in that meantime. I could try to delete it).I can confirm that 7e88 is the first parent of master HEAD that is not ignored by Ignore Committer Strategy. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199152.155732120.616.1558081860553%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-8618) would like to use one instance per build
Title: Message Title Stefan Verhoeff updated JENKINS-8618 Released in EC2 plugin Version 1.43 Jenkins / JENKINS-8618 would like to use one instance per build Change By: Stefan Verhoeff Status: Fixed but Unreleased Resolved Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.138729.1295990555000.620.1558081920665%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55024) Pipeline Job Plugin (workflow-job-plugin) gives empty console output when an error occurs
Title: Message Title Amedee Van Gasse commented on JENKINS-55024 Re: Pipeline Job Plugin (workflow-job-plugin) gives empty console output when an error occurs Meanwhile the job to make a directory listing, mentioned under question 1, had failed line 2: /usr/bin/ls: Argument list too long I should have known... I'll do it again, this time with find . -print0 | xargs -0 ls -ld Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196061.1544001052000.629.1558082220241%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57371) error message when building PR
Title: Message Title Audun Halland edited a comment on JENKINS-57371 Re: error message when building PR "Build now" is as broken as the webhook( ? ) from github. Closing and re-opening the PR in github had no effect (although the PR was retained as a "disabled" Jenkins job in that meantime. I could try to delete it).I can confirm that 7e88 is the first parent of master HEAD that is not ignored by Ignore Committer Strategy. And it is the first one that is a merge commit (a merge of the previous PR). The commits (two, in fact) at the tip of master, generated by jenkins, are regular commits. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199152.155732120.642.1558082340354%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55024) Pipeline Job Plugin (workflow-job-plugin) gives empty console output when an error occurs
Title: Message Title
Amedee Van Gasse edited a comment on JENKINS-55024
Re: Pipeline Job Plugin (workflow-job-plugin) gives empty console output when an error occurs
Meanwhile the job to make a directory listing, mentioned under question 1, had failed {code}line 2: /usr/bin/ls: Argument list too long{code}I should have known... I'll do it again, this time with{code}find . /var/lib/jenkins -print0 | xargs -0 ls -ld{code}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196061.1544001052000.639.1558082340309%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57383) Issue when testing proxy
Title: Message Title Illan RUL-DA CUNHA updated an issue Jenkins / JENKINS-57383 Issue when testing proxy Change By: Illan RUL-DA CUNHA Priority: Minor Major Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199165.1557396422000.644.1558083780123%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57178) ERROR: Caught ComException: Maximum timeout of 120 seconds exceeded: COM server not available! and ERROR: Could not determine ECU-TEST version!
Title: Message Title TraceTronic GmbH updated an issue Jenkins / JENKINS-57178 ERROR: Caught ComException: Maximum timeout of 120 seconds exceeded: COM server not available! and ERROR: Could not determine ECU-TEST version! Change By: TraceTronic GmbH Priority: Blocker Major Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198929.1556174585000.646.1558083960207%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57405) Stop/Disconnect on Idle Timeout feature not working after updating Node description template
Title: Message Title FABRIZIO MANFREDI commented on JENKINS-57405 Re: Stop/Disconnect on Idle Timeout feature not working after updating Node description template Hi Stefan, the Description is one of the element that is used to identify the Slaves. Change the description with instance running or in stop state, break the counting subsystem. We have to change the way how the plugin use the tags Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199189.1557489676000.648.1558084200156%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57392) AWS API timeout
Title: Message Title FABRIZIO MANFREDI commented on JENKINS-57392 Re: AWS API timeout Please export the timeout has an options in the config Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199174.1557437303000.650.1558084260233%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57178) ERROR: Caught ComException: Maximum timeout of 120 seconds exceeded: COM server not available! and ERROR: Could not determine ECU-TEST version!
Title: Message Title TraceTronic GmbH commented on JENKINS-57178 Re: ERROR: Caught ComException: Maximum timeout of 120 seconds exceeded: COM server not available! and ERROR: Could not determine ECU-TEST version! Azra Begzadic: You need to register the COM server of your ECU-TEST installation properly. In your case run the following command in an elevated cmd with administrator privileges: "C:\Program Files\ECU-TEST 7.1\ECU-TEST_COM.exe" /register For further information have a look in the FAQ section. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198929.1556174585000.652.1558084380186%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55639) ec2-plugin only attempts to retrieve spot instance using old id
Title: Message Title FABRIZIO MANFREDI commented on JENKINS-55639 Re: ec2-plugin only attempts to retrieve spot instance using old id The 1.43 contains a fix on the missing default value of the new options that are not present for people that come from old plugin. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196815.1547702452000.656.1558084440505%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57178) ERROR: Caught ComException: Maximum timeout of 120 seconds exceeded: COM server not available! and ERROR: Could not determine ECU-TEST version!
Title: Message Title TraceTronic GmbH started work on JENKINS-57178 Change By: TraceTronic GmbH Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198929.1556174585000.654.1558084440476%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57161) ec2 plugin locks queue until excessWorkload is 0
Title: Message Title FABRIZIO MANFREDI started work on JENKINS-57161 Change By: FABRIZIO MANFREDI Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198911.1556047726000.692.1558084501596%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55639) ec2-plugin only attempts to retrieve spot instance using old id
Title: Message Title FABRIZIO MANFREDI edited a comment on JENKINS-55639 Re: ec2-plugin only attempts to retrieve spot instance using old id The 1.43 contains a fix on the missing default value of the new options that are not present for people that come from old plugin. Can you test ? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196815.1547702452000.690.1558084501554%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57161) ec2 plugin locks queue until excessWorkload is 0
Title: Message Title FABRIZIO MANFREDI commented on JENKINS-57161 Re: ec2 plugin locks queue until excessWorkload is 0 I will merge soon the patch, I am waiting to close some pending of 1.43. After that It will be part of the 1.44 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198911.1556047726000.700.1558084680191%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56443) EC2 plugin doesn't take into account 'shutdown mode' of Jenkins
Title: Message Title FABRIZIO MANFREDI closed an issue as Fixed Jenkins / JENKINS-56443 EC2 plugin doesn't take into account 'shutdown mode' of Jenkins Change By: FABRIZIO MANFREDI Status: In Progress Closed Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198038.1551885858000.702.1558084800337%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56927) Request: EC2 plugin should use SSH keys via credentials plugin
Title: Message Title FABRIZIO MANFREDI commented on JENKINS-56927 Re: Request: EC2 plugin should use SSH keys via credentials plugin I will put in the backlog for the 1.45, if you have time to provide a pull request for that I will be happy to review it Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198606.1554663571000.705.1558084860282%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55639) ec2-plugin only attempts to retrieve spot instance using old id
Title: Message Title Yan Corneille commented on JENKINS-55639 Re: ec2-plugin only attempts to retrieve spot instance using old id Actully I can't, I'm sorry. I had to rollback and fix my instance EC2 plugin to v1.39 due to https://issues.jenkins-ci.org/browse/JENKINS-52362. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196815.1547702452000.708.1558085040609%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55556) EC2 unable to retrieve private IP (+ other buggy behaviour)
Title: Message Title FABRIZIO MANFREDI commented on JENKINS-6 Re: EC2 unable to retrieve private IP (+ other buggy behaviour) 1.43 has been released Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196718.154738602.725.1558085100493%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57455) Jenkins is not exposing cipher for TLSv1.1 and TLS1
Title: Message Title deepak kumar commented on JENKINS-57455 Re: Jenkins is not exposing cipher for TLSv1.1 and TLS1 Thanks a lot Oleg Nenashev for looking into this. It would be great, if you can provide any patch for this (As we are blocked with this). I don't find any solution to enable TLSv1 cipher by setting any property. Thanks in advance! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199315.1557842321000.738.1558085400085%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39203) All stages show up as UNSTABLE when only one stage should
Title: Message Title
Hugo L commented on JENKINS-39203
Re: All stages show up as UNSTABLE when only one stage should
Thank you for making progress on this issue. I updated jenkins and the plugins and tried using unstable(). The build is correctly marked as unstable, however all steps appear green in the pipeline. Here is what I do:
steps {
script {
def r = sh(returnStatus: true, script: "my_script");
if (r != 0) {
unstable(message: "Failed: ${STAGE_NAME} => return UNSTABLE status")
}
}
}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.175630.1477271041000.741.1558085643722%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56350) Week, Day layout incorrect
Title: Message Title Wayne Berry commented on JENKINS-56350 Re: Week, Day layout incorrect Same issue here. Month view renders fine. Issue is only seen on week and day views. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197936.1551468243000.975.1558085880272%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57516) Native implementation does not support tag notification
Title: Message Title Krzysztof Malinowski created an issue Jenkins / JENKINS-57516 Native implementation does not support tag notification Issue Type: Bug Assignee: Unassigned Components: bitbucket-branch-source-plugin Created: 2019-05-17 09:43 Environment: Jenkins 2.138.2, Bitbucket Branch Source Plugin 2.4.4 Priority: Minor Reporter: Krzysztof Malinowski Upon receipt of Bitbucket native webhook notification no project scan is triggered and the log says: May 17, 2019 9:11:55 AM INFO com.cloudbees.jenkins.plugins.bitbucket.hooks.NativeServerPushHookProcessor$HeadEvent addBranches Received event for unknown ref type TAG of ref TEST_TAG Please add support for tag notifications. Add Comment
[JIRA] (JENKINS-53486) email-ext fails when CasC attempts to set smtpHost
Title: Message Title
Robin Smith commented on JENKINS-53486
Re: email-ext fails when CasC attempts to set smtpHost
I think there may still be an issue here. The problem I have happens when I add smtpUsername / smtpPassword configuration fields, to authenticate with an SMTP server. This can be set up 'hands on' in the UI, so using the necessary fields described in the JCasC documentation, I set up something like this:
extendedEmailPublisher:
smtpServer: smtp.server.com
smtpUsername: ale...@company.com
smtpPassword: ${SMTPpass}
useSsl: true
charset: UTF-8
defaultContentType: text/plain
defaultSubject: "Build $BUILD_NUMBER - $BUILD_STATUS"
defaultBody: "Check console output at $BUILD_URL"
But adding the smtpUsername / smtpPassword fields seems to cause the 'smtpServer' value to be ignored completely (it's not ignored when the smtpUsername / smtpPassword fields are not present). Instead, the 'smtpHost' value from the Mailer plugin configuration is used in its place If anyone stumbles across this page and needs to get SMTP authentication working for the Email Extension plugin, I was able to using this setup:
mailer:
smtpHost: smtp.server.com
useSsl: true
charset: UTF-8
extendedEmailPublisher:
smtpUsername: ale...@company.com
smtpPassword: ${SMTPpass}
defaultContentType: text/plain
defaultSubject: "Build $BUILD_NUMBER - $BUILD_STATUS"
defaultBody: "Check console output at $BUILD_URL"
It's not ideal that part of the configuration lives in each plugin though! (mailer plugin does not support SMTP auth fields - JENKINS-55109) See also: https://github.com/jenkinsci/configuration-as-code-plugin/issues/772
Add Comment
[JIRA] (JENKINS-53486) email-ext fails when CasC attempts to set smtpHost
Title: Message Title
Robin Smith edited a comment on JENKINS-53486
Re: email-ext fails when CasC attempts to set smtpHost
I think there may still be an issue here. The problem I have happens when I add smtpUsername / smtpPassword configuration fields, to authenticate with an SMTP server. This can be set up 'hands on' in the UI, so using the necessary fields described in the JCasC documentation, I set up something like this:{code:yaml} extendedEmailPublisher: smtpServer: smtp.server.comsmtpUsername: ale...@company.comsmtpPassword: ${SMTPpass}useSsl: truecharset: UTF-8defaultContentType: text/plaindefaultSubject: "Build $BUILD_NUMBER - $BUILD_STATUS"defaultBody: "Check console output at $BUILD_URL"{code}But adding the smtpUsername / smtpPassword fields seems to cause the 'smtpServer' value to be ignored completely (it's not ignored when the smtpUsername / smtpPassword fields are not present). Instead, the 'smtpHost' value from the Mailer plugin configuration is used in its place :-(If anyone stumbles across this page and needs to get SMTP authentication working for the Email Extension plugin, I was able to using this setup:{code:yaml} mailer: smtpHost: smtp.server.comuseSsl: truecharset: UTF-8 extendedEmailPublisher: smtpUsername: ale...@company.comsmtpPassword: ${SMTPpass}defaultContentType: text/plaindefaultSubject: "Build $BUILD_NUMBER - $BUILD_STATUS"defaultBody: "Check console output at $BUILD_URL"{code}It's not ideal that part of the configuration lives in each plugin though! (mailer plugin does not support SMTP auth fields - JENKINS-55109)See also: https://github.com/jenkinsci/configuration-as-code-plugin/issues/772
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view
[JIRA] (JENKINS-45712) p4 credentials fail, can't write .p4tickets file
Title: Message Title Kieron Kierzo commented on JENKINS-45712 Re: p4 credentials fail, can't write .p4tickets file Just in case this saves some people some time I was using the bitinami jenkins docker image, as per comments above I added this enviroment lines to my docker-compose.yml which fixed this for me It should be the value thats in jenkins at Manage Jenkins -> Configure Sytem -> Home directory environment: - 'JAVA_OPTS=-Duser.home=/opt/bitnami/jenkins/jenkins_home' Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.183909.1500593073000.1001.1558086480498%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53486) email-ext fails when CasC attempts to set smtpHost
Title: Message Title Robin Smith commented on JENKINS-53486 Re: email-ext fails when CasC attempts to set smtpHost David van Laatum Ben Fiedler happy to raise this as a separate issue, if you prefer Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.193954.1536546047000.1004.1558086480530%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57455) Jenkins is not exposing cipher for TLSv1.1 and TLS1
Title: Message Title Oleg Nenashev commented on JENKINS-57455 Re: Jenkins is not exposing cipher for TLSv1.1 and TLS1 Sorry, I have neither time nor interest to help with supporting obsolete and insecure TLS protocols. I can review pull requests from others, but I will not be working on a patch Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199315.1557842321000.1010.1558087020176%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57517) Disable DNS Multicast by default
Title: Message Title Francisco Fernández created an issue Jenkins / JENKINS-57517 Disable DNS Multicast by default Issue Type: Task Assignee: Unassigned Components: core Created: 2019-05-17 09:58 Priority: Minor Reporter: Francisco Fernández Since there are many opened issues related to DNS Multicast and this feature does not seem to be widely used, maybe it is worth to disable by default Acceptance criteria Disable by default the DNS Multicast Update the wiki: https://wiki.jenkins.io/display/JENKINS/Auto-discovering+Jenkins+on+the+network Add Comment
[JIRA] (JENKINS-47307) Add help texts to configuration
Title: Message Title René Scheibe updated JENKINS-47307 Jenkins / JENKINS-47307 Add help texts to configuration Change By: René Scheibe Status: Fixed but Unreleased Resolved Released As: 1.21 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.185732.1507282107000.1013.1558087500144%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53950) Support configuration as code
Title: Message Title René Scheibe updated JENKINS-53950 Jenkins / JENKINS-53950 Support configuration as code Change By: René Scheibe Status: Fixed but Unreleased Resolved Released As: 1.21 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194552.1539028394000.1016.1558087560438%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53950) Support configuration as code
Title: Message Title Aleksi Simell closed an issue as Done Jenkins / JENKINS-53950 Support configuration as code Change By: Aleksi Simell Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194552.1539028394000.1019.1558087860276%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47307) Add help texts to configuration
Title: Message Title Aleksi Simell closed an issue as Done Jenkins / JENKINS-47307 Add help texts to configuration Change By: Aleksi Simell Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.185732.1507282107000.1021.1558087920080%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39203) All stages show up as UNSTABLE when only one stage should
Title: Message Title Torsten Walter commented on JENKINS-39203 Re: All stages show up as UNSTABLE when only one stage should I tried the new functionality Devin Nusbaum mentioned above, but using anything else than the default values in catchError e.g. catchError(buildResult: 'SUCCESS') results in: org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: WorkflowScript: 11: Expecting "class hudson.model.Result" for parameter "buildResult" but got "SUCCESS" of type class java.lang.String instead @ line 11, column 41. catchError(buildResult: 'SUCCESS') Jenkins version: 2.164.3 Pipeline Basic Steps: 2.16 (blue ocean is not installed) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.175630.1477271041000.1256.1558088227135%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48035) Github multibranch: GitHub Webhook is not created right after saving the job
Title: Message Title
Carlos Rodríguez López edited a comment on JENKINS-48035
Re: Github multibranch: GitHub Webhook is not created right after saving the job
[~rsandell] [~stephenconnolly] I am reopening this ticket again because the same reported issue seems to be back running (Regression?)h4. Environment{code:java}Jenkins LTS 2.164.2 * github:1.29.4 'GitHub plugin' * github-api:1.95 'GitHub API Plugin' * github-branch-source:2.5.0 *(update available)* 'GitHub Branch Source Plugin'{code}h4. ObservationWhat we see on Jenkins logs{code:java}May 16, 2019 3:12:38 PM org.jenkinsci.plugins.github.webhook.WebhookManager$2 applyNullSafeWARNING: Failed to add GitHub webhook for GitHubRepositoryName[host=github.com,username=mock-carlosrodlop-org,repository=my-hw-maven-app]java.lang.NullPointerException: There are no credentials with admin access to manage hooks on GitHubRepositoryName[host=github.com,username=mock-carlosrodlop-org,repository=my-hw-maven-app]{code}But it is not right... I am using this repo https://github.com/mock-carlosrodlop-org/my-hw-maven-app with user:carlosrodlop and pass:APIToken and as you can tell from the following images carlosrodlop is an admin!repo-team.png|thumbnail! !repo-team-2.png|thumbnail! Custom dedicated loggers as explained in this guide: [GitHub-Webhook-Troubleshooting |https://support.cloudbees.com/hc/en-us/articles/224621648-GitHub-Webhook-Troubleshooting] are not providing any useful hint just {code:java} May 16, 2019 4:05:50 PM FINE com.cloudbees.jenkins.GitHubWebHook$1 apply Calling registerHooks() for multibranch-example-job May 16, 2019 4:05:51 PM FINE com.cloudbees.jenkins.GitHubWebHook$1 applyCalling registerHooks() for multibranch-example-job{code}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
[JIRA] (JENKINS-39203) All stages show up as UNSTABLE when only one stage should
Title: Message Title
Hugo L edited a comment on JENKINS-39203
Re: All stages show up as UNSTABLE when only one stage should
Thank you for making progress on this issue.I updated jenkins and the plugins and tried confirm it works, using unstable(). The build is correctly marked it as unstable, however all steps appear green in the pipeline.Here is what I do follow : {code:java}steps { script { def r = sh(returnStatus: true, script: "my_script"); if (r != 0) { unstable(message: "Failed: ${STAGE_NAME} => return UNSTABLE status") } }} {code} edit: ok it runs smoothly
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.175630.1477271041000.1500.1558089307580%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57518) Remove XMLUtils from the plugin when it is unrestricted in core
Title: Message Title Ramon Leon created an issue Jenkins / JENKINS-57518 Remove XMLUtils from the plugin when it is unrestricted in core Issue Type: Improvement Assignee: Unassigned Components: credentials-plugin Created: 2019-05-17 10:37 Priority: Minor Reporter: Ramon Leon We removed the dependency to XMLUtils on core from the credentials plugin because it becomes restricted for external use. There is a PR where XMLUtils is again unrestricted: https://github.com/jenkinsci/jenkins/pull/4032 Once this PR is merged and released, we can remove the new util package and restore the dependencies with the core again. Add Comment
[JIRA] (JENKINS-39203) All stages show up as UNSTABLE when only one stage should
Title: Message Title vaishal shah commented on JENKINS-39203 Re: All stages show up as UNSTABLE when only one stage should It's Working Thanks Devin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.175630.1477271041000.1504.1558089547161%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39203) All stages show up as UNSTABLE when only one stage should
Title: Message Title vaishal shah edited a comment on JENKINS-39203 Re: All stages show up as UNSTABLE when only one stage should It's Working Thanks Devin :) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.175630.1477271041000.1739.155808955%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39203) All stages show up as UNSTABLE when only one stage should
Title: Message Title Yves Schumann commented on JENKINS-39203 Re: All stages show up as UNSTABLE when only one stage should Can one please post a screenshot how this looks now on traditional view and on BlueOcean? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.175630.1477271041000.1974.1558089963699%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57482) Heap size issue while building using ANT
Title: Message Title Pelican stopped work on JENKINS-57482 Change By: Pelican Status: In Progress Open Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199342.1557922754000.2208.1558089966681%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57482) Heap size issue while building using ANT
Title: Message Title Pelican updated JENKINS-57482 Hi Stephan We understood the issue here. It was the environment variable that were not getting set when we were initiating a process on the node machien. On declaring the required evironment variable the process was completed successfully. Thank you for your help. Regards Vilas Menon Jenkins / JENKINS-57482 Heap size issue while building using ANT Change By: Pelican Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199342.1557922754000.2210.1558090080423%40Atlassian.JIRA. For more options, visit https://grou
[JIRA] (JENKINS-57482) Heap size issue while building using ANT
Title: Message Title Pelican updated JENKINS-57482 Jenkins / JENKINS-57482 Heap size issue while building using ANT Change By: Pelican Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199342.1557922754000.2212.1558090080447%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39203) All stages show up as UNSTABLE when only one stage should
Title: Message Title vaishal shah updated an issue Jenkins / JENKINS-39203 All stages show up as UNSTABLE when only one stage should Change By: vaishal shah Attachment: image-2019-05-17-16-18-02-806.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.175630.1477271041000.2447.1558090148706%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39203) All stages show up as UNSTABLE when only one stage should
Title: Message Title Reinhold Füreder updated an issue Jenkins / JENKINS-39203 All stages show up as UNSTABLE when only one stage should Change By: Reinhold Füreder Attachment: screenshot-not-showing-unstable-stage.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.175630.1477271041000.2477.1558090746542%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39203) All stages show up as UNSTABLE when only one stage should
Title: Message Title Reinhold Füreder commented on JENKINS-39203 Re: All stages show up as UNSTABLE when only one stage should Hm, while it seems to work fine for junit steps like in the screenshot it does not visualize the unstable stage when using code like Hugo L (in a replayed pipeline): How comes!? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.175630.1477271041000.2724.1558090865320%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57519) JavaScript: switch to let
Title: Message Title Josh Soref created an issue Jenkins / JENKINS-57519 _javascript_: switch to let Issue Type: Task Assignee: Josh Soref Components: core Created: 2019-05-17 11:06 Priority: Trivial Reporter: Josh Soref per Wadeck Follonier we only have to support a limited set of browsers (see compatibility). cc Gavin Mogan References: MDN: Web/_javascript_/Reference/Statements/let Jenkins: Browser Compatibility Matrix This is a chore. I'm going to try to do one piece of it, but after that, someone should find a fancy tool that can do it more generally... Add Comment
[JIRA] (JENKINS-57518) Remove XMLUtils from the plugin when it is unrestricted in core
Title: Message Title Baptiste Mathus commented on JENKINS-57518 Re: Remove XMLUtils from the plugin when it is unrestricted in core We will not really be able to use this from the core as soon as it's released though. It will take a bit of time before we can bump the baseline to the newer Jenkins Core with unrestricted XMLUtils. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199422.1558089461000.2959.1558091460265%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48518) Docker Pipeline: invalid volume specification with Windows slave and Linux master
Title: Message Title Raphael Höser commented on JENKINS-48518 Re: Docker Pipeline: invalid volume specification with Windows slave and Linux master Larry Silverman Sadly not really - the github issue had some ideas with writing libraries, which call the docker commands directly, but that doesn't provide the same feature set. Maybe it is possible to use a kubernetes cluster to use docker on windows. (We switched to jenkins in kubernetes, but we also now use wine in the most part with linux hosts) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.187135.1513098516000.2973.1558091940725%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45579) Step to set stage or parallel status
Title: Message Title RG commented on JENKINS-45579 Re: Step to set stage or parallel status Hi. Would you mind adding an example in https://github.com/jenkinsci/pipeline-examples ? I'm not exactly an expert and coming up with the right syntax assembling bit of code & release note is quite hard. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.183763.1500306894000.3161.1558092369597%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39203) All stages show up as UNSTABLE when only one stage should
Title: Message Title Daan van den Akker commented on JENKINS-39203 Re: All stages show up as UNSTABLE when only one stage should Torsten Walter: using the fully qualified names like hudson.model.Result.FAILURE works for me. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.175630.1477271041000.3394.1558092372584%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57201) [Evergreen-backend] Expose a publicly accessible endpoint for the current last updateLevel
Title: Message Title Baptiste Mathus commented on JENKINS-57201 Re: [Evergreen-backend] Expose a publicly accessible endpoint for the current last updateLevel R. Tyler Croy in case you missed this. When/if you can do it, would be great. Danke! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198956.155631493.3396.1558094040216%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57520) Declaration Tools installation via JCasC doesn't work
Title: Message Title Pavel Janoušek created an issue Jenkins / JENKINS-57520 Declaration Tools installation via JCasC doesn't work Issue Type: Bug Assignee: vjuranek Components: groovy-plugin Created: 2019-05-17 11:53 Priority: Major Reporter: Pavel Janoušek Basic declaration via JCasC yaml like: tool: groovy: installations: - name: "Groovy1" home: "/bin/groovy" doesn't work - it produces an exception: May 17, 2019 11:51:05 AM jenkins.InitReactorRunner$1 onTaskFailed SEVERE: Failed ConfigurationAsCode.init java.lang.Error: java.lang.reflect.InvocationTargetException at hudson.init.TaskMethodFinder.invoke(TaskMethodFinder.java:110) at hudson.init.TaskMethodFinder$TaskImpl.run(TaskMethodFinder.java:175) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:296) at jenkins.model.Jenkins$5.runTask(Jenkins.java:1096) 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) Caused by: java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl
[JIRA] (JENKINS-57201) [Evergreen-backend] Expose a publicly accessible endpoint for the current last updateLevel
Title: Message Title
Baptiste Mathus updated an issue
Jenkins / JENKINS-57201
[Evergreen-backend] Expose a publicly accessible endpoint for the current last updateLevel
Change By:
Baptiste Mathus
h3. Problem statement To enable So an instance can itself detect it's not able to update, it would need to know it's not on latest. And endpoint to easily do that from the Evergreen Jenkins plugin, and then surface an Admin Monitor alert, would be good. h3. ExpectedThe backend should expose a publicly accessible endpoint returning the current updateLevel. (Possibly, this would include the channel for it given also it's easy to retrieve from the disk of the instance, and is next to the current updateLevel).(This would allow the Evergreen Jenkins plugin to consume this easily and display a warning using for example an AdministrativeMonitor to inform users that their instance has the automated upgrade system broken in some way.)h3. Technical asides{noformat}$ docker exec -ti evergreen cat data/updates.json | jq -r .meta.channelgeneral$ docker exec -ti evergreen cat data/updates.json | jq -r .meta.level188{noformat}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsc
[JIRA] (JENKINS-57520) Declaring Tools installation via JCasC doesn't work
Title: Message Title Pavel Janoušek updated an issue Jenkins / JENKINS-57520 Declaring Tools installation via JCasC doesn't work Change By: Pavel Janoušek Summary: Declaration Declaring Tools installation via JCasC doesn't work Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199425.1558094032000.3402.1558094580287%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57521) Export for JCasC is empty
Title: Message Title Pavel Janoušek created an issue Jenkins / JENKINS-57521 Export for JCasC is empty Issue Type: Bug Assignee: vjuranek Components: groovy-plugin Created: 2019-05-17 12:05 Priority: Major Reporter: Pavel Janoušek When configured and seen via Tools configuration WebGUI page I expect an exported record like: tool: groovy: installations: - name: "groovy" home: "/bin/groovy" but nothing is produced. Add Comment
[JIRA] (JENKINS-57522) Export for JCasC is empty
Title: Message Title Pavel Janoušek created an issue Jenkins / JENKINS-57522 Export for JCasC is empty Issue Type: Bug Assignee: Stefan Wolf Components: gradle-plugin Created: 2019-05-17 12:07 Priority: Major Reporter: Pavel Janoušek When configured and seen via Tools configuration WebGUI page I expect an exported record like: tool: gradle: installations: - name: "gradle" home: "/bin/groovy" but nothing is produced. Add Comment
[JIRA] (JENKINS-57523) Export for JCasC is empty
Title: Message Title Pavel Janoušek created an issue Jenkins / JENKINS-57523 Export for JCasC is empty Issue Type: Bug Assignee: Armando Fernandez Components: ant-plugin Created: 2019-05-17 12:07 Priority: Major Reporter: Pavel Janoušek When configured and seen via Tools configuration WebGUI page I expect an exported record like: tool: ant: installations: - name: "ant" home: "/bin/ant" but nothing is produced. Add Comment
[JIRA] (JENKINS-57525) JCasC export contains only one record
Title: Message Title Pavel Janoušek created an issue Jenkins / JENKINS-57525 JCasC export contains only one record Issue Type: Bug Assignee: Unassigned Components: maven-plugin Created: 2019-05-17 12:10 Priority: Minor Reporter: Pavel Janoušek JCasC export contains only one record (not the first - based on WebGUI Tools confiration page) even we have declared more of them. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-57524) JCasC export contains only one record
Title: Message Title Pavel Janoušek created an issue Jenkins / JENKINS-57524 JCasC export contains only one record Issue Type: Bug Assignee: Devin Nusbaum Components: jdk-tool-plugin Created: 2019-05-17 12:10 Priority: Minor Reporter: Pavel Janoušek JCasC export contains only one record (not the first - based on WebGUI Tools confiration page) even we have declared more of them. I'm not sure if the issue can be fixed in plugin or is in the core itself, so feel free to re-route the issue if necessary. Add Comment
[JIRA] (JENKINS-57482) Heap size issue while building using ANT
Title: Message Title Stephan Watermeyer commented on JENKINS-57482 Re: Heap size issue while building using ANT Happy to hear that Pelican and sorry for not being more responsive. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199342.1557922754000.3413.1558095180104%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57482) Heap size issue while building using ANT
Title: Message Title Stephan Watermeyer updated JENKINS-57482 Jenkins / JENKINS-57482 Heap size issue while building using ANT Change By: Stephan Watermeyer Status: Closed Fixed but Unreleased Resolution: Fixed Won't Fix Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199342.1557922754000.3415.1558095240357%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-21248) Add shallow update init for submodule
Title: Message Title Stefan Verhoeff commented on JENKINS-21248 Re: Add shallow update init for submodule Tried this feature in beta git-4.0.0-beta9. But the plugin is refusing the allow the option: > git submodule init # timeout=10 [WARNING] Git client older than 1.8.4 doesn't support shallow submodule updates. This flag is ignored. However my Git version should support this, see output of sh 'git --version' in my pipeline script: + git --version git version 2.11.0 Bug in the version detection? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.152811.138908257.3441.1558095601175%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48035) Github multibranch: GitHub Webhook is not created right after saving the job
Title: Message Title
Carlos Rodríguez López edited a comment on JENKINS-48035
Re: Github multibranch: GitHub Webhook is not created right after saving the job
[~rsandell] [~stephenconnolly] I am reopening this ticket again because the same reported issue seems to be back running (Regression?)h4. Environment{code:java}Jenkins LTS 2.164.2 * github:1.29.4 'GitHub plugin' * github-api:1.95 'GitHub API Plugin' * github-branch-source:2.5.0 *(update available)* 'GitHub Branch Source Plugin'{code}h4. Observation Observations h6. What we see on Jenkins logs{code:java}May 16, 2019 3:12:38 PM org.jenkinsci.plugins.github.webhook.WebhookManager$2 applyNullSafeWARNING: Failed to add GitHub webhook for GitHubRepositoryName[host=github.com,username=mock-carlosrodlop-org,repository=my-hw-maven-app]java.lang.NullPointerException: There are no credentials with admin access to manage hooks on GitHubRepositoryName[host=github.com,username=mock-carlosrodlop-org,repository=my-hw-maven-app]{code}But it is not right... I am using this repo https://github.com/mock-carlosrodlop-org/my-hw-maven-app with user:carlosrodlop and pass:APIToken and as you can tell from the following images carlosrodlop is an admin!repo-team.png|thumbnail! !repo-team-2.png|thumbnail! h6. Custom dedicated loggers as explained in this guide: [GitHub-Webhook-Troubleshooting |https://support.cloudbees.com/hc/en-us/articles/224621648-GitHub-Webhook-Troubleshooting] are not providing any useful hint just{code:java}May 16, 2019 4:05:50 PM FINE com.cloudbees.jenkins.GitHubWebHook$1 applyCalling registerHooks() for multibranch-example-jobMay 16, 2019 4:05:51 PM FINE com.cloudbees.jenkins.GitHubWebHook$1 applyCalling registerHooks() for multibranch-example-job{code} h6. Manage Jenkins > GitHub plugin > Advanced > Re-register hooks for all jobs > webhook in GitHub is NOT generated either. Independently if I enabled or disable Manage hooks options the output is the same: Works only when Jenkins manages hooks (one or more creds specified)
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-21248) Add shallow update init for submodule
Title: Message Title Mark Waite commented on JENKINS-21248 Re: Add shallow update init for submodule There could be a bug in the version detection logic, but you should probably first check that the version of git being used by your job is the same as the version reported in the pipeline script sh step. I've not seen any other bug reports of broken version detection. There are specific automated tests in the plugin to confirm that git version numbers in variouos formats are detected correctly. Those tests don't use 2.11.0 specifically, but they use 2.10.0 and other interesting values near it. If there is a bug in the detection logic, I'll need to update my acceptance test to exercise that bug. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.152811.138908257.3478.1558097340853%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-21248) Add shallow update init for submodule
Title: Message Title
Mark Waite edited a comment on JENKINS-21248
Re: Add shallow update init for submodule
There could be a bug in the [version detection logic|https://github.com/jenkinsci/git-client-plugin/blob/63dd47319914cbe72948e18d83f62c62365ba6c7/src/main/java/org/jenkinsci/plugins/gitclient/CliGitAPIImpl.java#L1269], but you should probably first check that the version of git being used by your job is the same as the version reported in the pipeline script {{sh}} step.I've not seen any other bug reports of broken version detection. There are [specific automated tests|https://github.com/jenkinsci/git-client-plugin/blob/88def8591098610255185f7d895f4474589bc9e2/src/test/java/org/jenkinsci/plugins/gitclient/CliGitAPIImplTest.java#L99] in the plugin to confirm that git version numbers in variouos various formats are detected correctly. Those tests don't use 2.11.0 specifically, but they use 2.10.0 and other interesting values near it.If there is a bug in the detection logic, I'll need to update my [acceptance test|https://github.com/MarkEWaite/jenkins-bugs/blob/52c665176dac63a20b81238c38f25c849e877151/Jenkinsfile#L22] to exercise that bug.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.152811.138908257.3480.1558097400479%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57497) Cucumber Report displays incorrect total duration if total duration is more than 24 hours
Title: Message Title Jayashree Rokde updated an issue Jenkins / JENKINS-57497 Cucumber Report displays incorrect total duration if total duration is more than 24 hours Change By: Jayashree Rokde Attachment: overview-features.html Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199359.1557988825000.3506.1558097880121%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57497) Cucumber Report displays incorrect total duration if total duration is more than 24 hours
Title: Message Title Jayashree Rokde commented on JENKINS-57497 Re: Cucumber Report displays incorrect total duration if total duration is more than 24 hours Thanks Damian Szczepanik fro responding I have executed on 10 parallel sessions, attached zip files contains 85 JSON files that was used to create the Report. (Also attached the overview-feature.html) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199359.1557988825000.3508.1558097940106%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57497) Cucumber Report displays incorrect total duration if total duration is more than 24 hours
Title: Message Title Jayashree Rokde updated an issue Jenkins / JENKINS-57497 Cucumber Report displays incorrect total duration if total duration is more than 24 hours Change By: Jayashree Rokde Attachment: json.zip Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199359.1557988825000.3510.1558098000275%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54363) ERROR: Could not send email as a part of the post-build publishers.
Title: Message Title Alex Earl commented on JENKINS-54363 Re: ERROR: Could not send email as a part of the post-build publishers. I'm still trying to replicate it so that I can make sure the fix is good. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195113.1540977422000.3512.1558098240148%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43587) Pipeline fails to resume after master restart/plugin upgrade
Title: Message Title Mircea-Andrei Albu updated an issue Jenkins / JENKINS-43587 Pipeline fails to resume after master restart/plugin upgrade Change By: Mircea-Andrei Albu Attachment: image-2019-05-17-16-09-05-599.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.180909.1492112497000.3516.1558098601118%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43587) Pipeline fails to resume after master restart/plugin upgrade
Title: Message Title Mircea-Andrei Albu commented on JENKINS-43587 Re: Pipeline fails to resume after master restart/plugin upgrade +1 Same behaviour also on Jenkins 2.164.2 Our master doesn't have any executors and after master restart all the agents are staying like this for a while without resuming: Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.180909.1492112497000.3540.1558098601418%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-21248) Add shallow update init for submodule
Title: Message Title
Mark Waite edited a comment on JENKINS-21248
Re: Add shallow update init for submodule
There could be a bug in the [version detection logic|https://github.com/jenkinsci/git-client-plugin/blob/63dd47319914cbe72948e18d83f62c62365ba6c7/src/main/java/org/jenkinsci/plugins/gitclient/CliGitAPIImpl.java#L1269], but you should probably first check that the version of git being used by your job is the same as the version reported in the pipeline script {{sh}} step.I've not seen any other bug reports of broken version detection. There are [specific automated tests|https://github.com/jenkinsci/git-client-plugin/blob/88def8591098610255185f7d895f4474589bc9e2/src/test/java/org/jenkinsci/plugins/gitclient/CliGitAPIImplTest.java#L99] in the plugin to confirm that git version numbers in various formats are detected correctly. Those tests don't use 2.11.0 specifically, but they use 2.10.0 and other interesting values near it.If there is a bug in the detection logic, I'll need to update my [acceptance test|https://github.com/MarkEWaite/jenkins-bugs/blob/52c665176dac63a20b81238c38f25c849e877151/Jenkinsfile#L22] to exercise that bug. There seem to be some interesting cases in that [acceptance test|https://github.com/MarkEWaite/jenkins-bugs/blob/52c665176dac63a20b81238c38f25c849e877151/Jenkinsfile#L22] when running on command line git version 2.11.0, but the cases that I'm seeing are not related to version checking logic. In my case, the {{git submodule update}} fails with a warning that there are {{no common commits}}. The same message does not appear on at least some other command line git versions. I'll need to extend the acceptance test to execute with each of the versions of command line git in my test environment. That will then tell me if there are problems related to command line git version. Note that the issue I'm investigating shows that in my environment I'm able to perform the expected command line git operations. Thus, at least in my environment, the version check is working, since my investigation could not have started without passing that version check.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha
[JIRA] (JENKINS-57526) Blue Ocean Bitbucket : Failed to get "repositories" is very slow and loops for ever
Title: Message Title Shyamkumar Chintakindi created an issue Jenkins / JENKINS-57526 Blue Ocean Bitbucket : Failed to get "repositories" is very slow and loops for ever Issue Type: Bug Assignee: Unassigned Components: blueocean-plugin Created: 2019-05-17 13:28 Priority: Major Reporter: Shyamkumar Chintakindi 2019-05-17 12:22:02.999+ [id=1097] WARNING i.j.b.c.s.e.ExportInterceptor$1#getValue: Failed to get "repositories" from a io.jenkins.blueocean.blueocean_bitbucket_pipeline.BitbucketRepositoryContainer io.jenkins.blueocean.commons.ServiceException: Unknown Status Code at io.jenkins.blueocean.blueocean_bitbucket_pipeline.HttpResponse.getContent(HttpResponse.java:71) at io.jenkins.blueocean.blueocean_bitbucket_pipeline.cloud.BitbucketCloudApi.getDefaultBranch(BitbucketCloudApi.java:249) at io.jenkins.blueocean.blueocean_bitbucket_pipeline.model.BbRepo.toScmRepository(BbRepo.java:63) at io.jenkins.blueocean.blueocean_bitbucket_pipeline.BitbucketRepositoryContainer$BitbucketRepositories.(BitbucketRepositoryContainer.java:82) at io.jenkins.blueocean.blueocean_bitbucket_pipeline.BitbucketRepositoryContainer.getRepositories(BitbucketRepositoryContainer.java:41) at io.jenkins.blueocean.commons.stapler.export.MethodProperty.getValue(MethodProperty.java:72) Caused: java.lang.reflect.InvocationTargetException at io.jenkins.blueocean.commons.stapler.export.MethodProperty.getValue(MethodProperty.java:74) at io.jenkins.blueocean.commons.stapler.export.ExportInterceptor$1.getValue(ExportInterceptor.java:46) at io.jenkins.blueocean.commons.stapler.Export$BlueOceanExportInterceptor.getValue(Export.java:196) at io.jenkins.blueocean.commons.stapler.export.Property.writeTo(Property.java:136) at io.jenkins.blueocean.commons.stapler.export.Model.writeNestedObjectTo(Model.java:228) at io.jenkins.blueocean.commons.stapler.export.Model.writeNestedObjectTo(Model.java:224) at io.jenkins.blueocean.commons.stapler.export.Model.writeTo(Model.java:199) at io.jenkins.blueocean.commons.stapler.Ex
[JIRA] (JENKINS-39203) All stages show up as UNSTABLE when only one stage should
Title: Message Title Devin Nusbaum commented on JENKINS-39203 Re: All stages show up as UNSTABLE when only one stage should Torsten Walter I just tested your code and it works ok for me in some basic test. Please open a new issue for your problem, assign it to me, add any additional information or context that might be useful and include a list of all plugins you have installed and their versions. Thanks! Reinhold Füreder Can you please open a new issue, including a minimal Pipeline that reproduces the issue and assign the issue to me? Thanks! Also I was not explicit in my original post that these fixes do not currently affect Stage View at all, they only affect Blue Ocean, so I will update my post to make that clear. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.175630.1477271041000.3836.1558100890511%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39203) All stages show up as UNSTABLE when only one stage should
Title: Message Title Devin Nusbaum edited a comment on JENKINS-39203 Re: All stages show up as UNSTABLE when only one stage should [~twalter] I just tested your code and it works ok for me in some basic test tests . Please open a new issue for your problem, assign it to me, add any additional information or context that might be useful and include a list of all plugins you have installed and their versions. Thanks![~reinholdfuereder] Can you please open a new issue, including a minimal Pipeline that reproduces the issue and assign the issue to me? Thanks!Also I was not explicit in my original post that these fixes do not currently affect Stage View at all, they only affect Blue Ocean, so I will update my post to make that clear. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.175630.1477271041000.3838.1558100890536%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39203) All stages show up as UNSTABLE when only one stage should
Title: Message Title
Devin Nusbaum edited a comment on JENKINS-39203
Re: All stages show up as UNSTABLE when only one stage should
Some changes have recently been released to address this issue for Blue Ocean . All of the changes require Jenkins 2.138.4 or newer. The main fixes are in Pipeline: API Plugin version 2.34 and Pipeline: Graph Analysis Plugin version 1.10, but in most cases you will need to change your Pipelines to be able to take advantage of the fixes:* If you are currently setting the build result to unstable using {{currentBuild.result = 'UNSTABLE'}}, you need to update to Pipeline: Basic Steps Plugin version 2.16 and start using the {{unstable}} step instead. See the changelog [here|https://wiki.jenkins.io/display/JENKINS/Pipeline+Basic+Steps+Plugin] for details. You may also be interested in the new {{warnError}} step.** In case you are curious why we can't make {{currentBuild.result = 'UNSTABLE'}} work as-is, the problem is that {{currentBuild}} is implemented as a [GlobalVariable|https://github.com/jenkinsci/workflow-cps-plugin/blob/e5e5f8054ff485685e0a5b36db65d549604ed956/src/main/java/org/jenkinsci/plugins/workflow/cps/GlobalVariable.java#L60] rather than a regular Pipeline Step, so there is no way to associate the setting of the build result with the current Pipeline stage, especially if a {{parallel}} step is being executed.* If the build result is being set to unstable by the {{junit}} step from the JUnit Plugin, then update the JUnit Plugin to version 1.28 and the visualization should be fixed.* If the build result is being set to unstable by the {{publishIssues}} or {{recordIssues}} steps in the Warnings NG Plugin, then keep an eye on [this in-progress PR|https://github.com/jenkinsci/warnings-ng-plugin/pull/58] which will update those steps to use a new API that will fix the visualization.* If the build result is being set to unstable by a Pipeline step in some other plugin, then file a new issue with the component set to that plugin, and ask the maintainer to start using the new [WarningAction API|https://github.com/jenkinsci/workflow-api-plugin/blob/c84dbab8cd35c90f70d84390dc711901fa73b7ad/src/main/java/org/jenkinsci/plugins/workflow/actions/WarningAction.java] from Pipeline: Basic Steps Plugin version 2.16 wherever they change the build result.In case of problems, the new behavior can be disabled by setting the system property {{org.jenkinsci.plugins.workflow.pipelinegraphanalysis.StatusAndTiming.DISABLE_WARNING_ACTION_LOOKUP}} to "true", or by setting the static variable of the same name to {{true}} via the Jenkins script console.Note that the Blue Ocean steps view will not yet display the status of individual steps using the new API correctly, keep an eye on [this in-progress PR|https://github.com/jenkinsci/blueocean-plugin/pull/1954] which will fix that issue. Once that PR is merged and released, I plan to mark this issue as closed. The visualization provided by Pipeline: Stage View Plugin has not been integrated with the new API added in Pipeline: API 2.34, and so that visualization is not currently affected by these changes.
[JIRA] (JENKINS-57527) Unable to update Review due to bad Swarm URL
Title: Message Title
Paul Allen created an issue
Jenkins / JENKINS-57527
Unable to update Review due to bad Swarm URL
Issue Type:
Bug
Assignee:
Paul Allen
Components:
p4-plugin
Created:
2019-05-17 14:07
Priority:
Minor
Reporter:
Paul Allen
Hi Paul
[Pipeline] echo
Review: 12229, review type: SHELVED
[Pipeline] p4approve
... p4 property -nP4.Swarm.URL -l +
... p4 info +
... p4 login -s +
[Pipeline] echoException occurred
[Pipeline] echo
java.io.IOException: Unable to update Review.
[Pipeline] }
In the above, the Swarm URL was incorrect. It would be nice to see something more than “Exception occurred”.
script {
try {
echo "Review type: ${P4_REVIEW_TYPE}"
if ("${P4_REVIEW_TYPE}" == "SHELVED") {
echo "Review: ${P4_REVIEW}, review type: ${P4_REVIEW_TYPE}"
p4approve credential: "${env.p4_credential}",
review: '${P4_REVIEW}', status: 'COMMIT'
// Now set the review state back to 'needs review'
p4approve credential: "${env.p4_credential}",
review: '${P4_REVIEW}', status: 'REVIEW'
} else {
echo "Skipping Swarm approval as changelist already submitted"
}
} catch(Exception e) {
// Do something with the exception
[JIRA] (JENKINS-21248) Add shallow update init for submodule
Title: Message Title Mark Waite commented on JENKINS-21248 Re: Add shallow update init for submodule I've further investigated the JENKINS-21248 acceptance test failures in my environment. The initial submodule checkout succeeds on the following versions of command line git: 2.21 2.20 2.17 2.16 The initial submodule checkout fails on the following versions of command line git: 2.11 2.10 2.7 2.1 The stack trace in the checkout failure is: hudson.plugins.git.GitException: Command "git submodule update --reference /var/lib/git/mwaite/bugs/jenkins-bugs.git --depth=1 modules/JENKINS-46504.url" returned status code 1: stdout: stderr: Cloning into 'modules/JENKINS-46504.url'... warning: no common commits fatal: reference is not a tree: 0736ba35a0d8c05236e3b71584bc4e149aa5f10a Unable to checkout '0736ba35a0d8c05236e3b71584bc4e149aa5f10a' in submodule path 'modules/JENKINS-46504.url' at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2298) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1910) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$400(CliGitAPIImpl.java:81) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$7.lambda$execute$0(CliGitAPIImpl.java:1334) at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) at com.google.common.util.concurrent.MoreExecutors$SameThreadExecutorService.execute(MoreExecutors.java:253) at java.base/java.util.concurrent.ExecutorCompletionService.submit(ExecutorCompletionService.java:184) at org.jenkinsci.plugins.gitclient.cgit.GitCommandsExecutor.submitRemainingCommand(GitCommandsExecutor.java:75) at org.jenkinsci.plugins.gitclient.cgit.GitCommandsExecutor.invokeAll(GitCommandsExecutor.java:64) Also: hudson.remoting.Channel$CallSiteStackTrace: Remote call to debian8-mwaite at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1743) at hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:357) at hudson.remoting.Channel.call(Channel.java:957) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.execute(RemoteGitImpl.java:146) at jdk.internal.reflect.GeneratedMethodAccessor323.invoke(Unknown Source) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:566) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.invoke(RemoteGitImpl.java:132) at com.sun.proxy.$Proxy119.execute(Unknown Source) at hudson.plugins.git.extensions.impl.SubmoduleOption.onChec
[JIRA] (JENKINS-44316) Minimun dependency breaks docker lts build
Title: Message Title Oleg Nenashev resolved as Fixed I believe this was fixed by https://github.com/jenkinsci/docker/pull/495 Jenkins / JENKINS-44316 Minimun dependency breaks docker lts build Change By: Oleg Nenashev Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.182121.1495029922000.4330.1558102380382%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57528) Jenkins in Docker does not install detached plugins when there is no UC data
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-57528 Jenkins in Docker does not install detached plugins when there is no UC data Change By: Oleg Nenashev Summary: Jenkins in Docker does not install detached plugins which are implicit deps of other plugin when there is no UC data Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199434.155810265.4337.1558102680297%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57528) Jenkins in Docker does not install detached plugins which are implicit deps of other plugin when there is no UC data
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-57528 Jenkins in Docker does not install detached plugins which are implicit deps of other plugin when there is no UC data Issue Type: Bug Assignee: Carlos Sanchez Components: core, docker Created: 2019-05-17 14:17 Labels: plugin-manager docker detached-plugin Priority: Critical Reporter: Oleg Nenashev It is a placeholder for https://github.com/jenkinsci/docker/issues/698 and for https://github.com/jenkinsci/jenkins/pull/4000 which addresses it in the core Using newer cores that have part of it moved to plugins and is now implied dependencies in other plugins is causing to have bad Jenkins installation. Add Comment
[JIRA] (JENKINS-57528) Jenkins in Docker does not install detached plugins when there is no UC data
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-57528 Jenkins in Docker does not install detached plugins when there is no UC data Change By: Oleg Nenashev It is a placeholder for [https://github.com/jenkinsci/docker/issues/698] and for [https://github.com/jenkinsci/jenkins/pull/4000] which addresses it in the core Using newer cores that have part of it moved to plugins and is now implied dependencies in other plugins is causing to have bad Jenkins installation. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199434.155810265.4339.1558102680318%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57528) Jenkins in Docker does not install detached plugins when there is no UC data
Title: Message Title Oleg Nenashev assigned an issue to Jesse Glick Jenkins / JENKINS-57528 Jenkins in Docker does not install detached plugins when there is no UC data Change By: Oleg Nenashev Assignee: Carlos Sanchez Jesse Glick Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199434.155810265.4344.1558102800302%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57528) Jenkins in Docker does not install detached plugins when there is no UC data
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-57528 Jenkins in Docker does not install detached plugins when there is no UC data Change By: Oleg Nenashev Labels: detached-plugin docker lts-candidate plugin-manager Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199434.155810265.4341.1558102800262%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
