[JIRA] (JENKINS-57731) Enable to register aws ec2 slave
Title: Message Title Swanand Kulkarni updated an issue Jenkins / JENKINS-57731 Enable to register aws ec2 slave Change By: Swanand Kulkarni Attachment: On_prem_error.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.199674.1559111787000.14782.1559112480335%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57731) Enable to register aws ec2 slave
Title: Message Title Swanand Kulkarni updated an issue Jenkins / JENKINS-57731 Enable to register aws ec2 slave Change By: Swanand Kulkarni Attachment: 27_may.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.199674.1559111787000.14780.1559112480219%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44659) Missing workspace - workspace deleted during concurrent build
Title: Message Title elhay efrat reopened an issue this is still happed i found the RCA Jenkins / JENKINS-44659 Missing workspace - workspace deleted during concurrent build Change By: elhay efrat Resolution: Not A Defect Status: Resolved Reopened Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.182518.1496442162000.14773.1559111880531%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57731) Enable to register aws ec2 slave
Title: Message Title Swanand Kulkarni created an issue Jenkins / JENKINS-57731 Enable to register aws ec2 slave Issue Type: Story Assignee: FABRIZIO MANFREDI Attachments: 27_may.PNG Components: ec2-plugin Created: 2019-05-29 06:36 Environment: Jenkins master (Version 2.179) on windows server 2012 , Amazon ec2 plugin(1.43) Labels: slave plugin Priority: Blocker Reporter: Swanand Kulkarni As jenkins master is installed on Windows server.With amazon EC2 plugin I am able to launch instane but enable to register as a slave. As it is showing the error "The system cannot find the specified file ". As i manually check .pem file is not present at that location.
[JIRA] (JENKINS-44659) Missing workspace - workspace deleted during concurrent build
Title: Message Title elhay efrat assigned an issue to elhay efrat Jenkins / JENKINS-44659 Missing workspace - workspace deleted during concurrent build Change By: elhay efrat Assignee: elhay efrat 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.182518.1496442162000.14769.1559111820653%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57730) Automatically detect Benchmark classes
Title: Message Title Abhyudaya Sharma updated an issue Jenkins / JENKINS-57730 Automatically detect Benchmark classes Change By: Abhyudaya Sharma Labels: gsoc-2019 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.199673.1559108515000.14749.1559108580121%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57730) Automatically detect Benchmark classes
Title: Message Title Abhyudaya Sharma created an issue Jenkins / JENKINS-57730 Automatically detect Benchmark classes Issue Type: Improvement Assignee: Abhyudaya Sharma Components: role-strategy-plugin Created: 2019-05-29 05:41 Priority: Minor Reporter: Abhyudaya Sharma 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.199673.1559108515000.14747.1559108520275%40Atlassian.JIRA. For more options, visit https://groups.google.com/
[JIRA] (JENKINS-57698) Results are not saving in the mentioned directory after the execution in Execute Microfocus Test from Filesystem
Title: Message Title tanmoy roy commented on JENKINS-57698 Re: Results are not saving in the mentioned directory after the execution in Execute Microfocus Test from Filesystem Thanks Rolando-Mihai Vlad for the update. Please let me know if you need any information from my end. 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.199636.155895364.14744.1559098440114%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57729) Add Failure Cause Indications to Jenkins REST API
Title: Message Title Kurt Routley commented on JENKINS-57729 Re: Add Failure Cause Indications to Jenkins REST API Tomas Westling We have these changes in our own fork, I will create a merge request for pushing back to the community version shortly. 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.199672.1559094469000.14736.1559094540039%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57729) Add Failure Cause Indications to Jenkins REST API
Title: Message Title Kurt Routley assigned an issue to Kurt Routley Jenkins / JENKINS-57729 Add Failure Cause Indications to Jenkins REST API Change By: Kurt Routley Assignee: Tomas Westling Kurt Routley 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.199672.1559094469000.14735.1559094480363%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57729) Add Failure Cause Indications to Jenkins REST API
Title: Message Title Kurt Routley created an issue Jenkins / JENKINS-57729 Add Failure Cause Indications to Jenkins REST API Issue Type: New Feature Assignee: Tomas Westling Components: build-failure-analyzer-plugin Created: 2019-05-29 01:47 Environment: Java 8 Jenkins 2.164.3 Priority: Major Reporter: Kurt Routley REST API is used to determine useful build information. Having the BFA Found Failure Causes and Indications accessible through the REST API Would be useful. Add Comment
[JIRA] (JENKINS-28010) Use Google Apps group for Authorization
Title: Message Title Michael Dao commented on JENKINS-28010 Re: Use Google Apps group for Authorization Hey all, has anyone made any progress on this feature? I have been looking at the source code for google-login-plugin to understand how it works, but the only unit tests currently inside are just validation unit tests for domain input. I have been trying to write new mockito unit tests to test login, but i haven't figured out how to properly test authentication for plugins. Does anyone have any documentation or examples on how to debug this kind of 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.162209.142951271.14708.1559091480388%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-28010) Use Google Apps group for Authorization
Title: Message Title Michael Dao stopped work on JENKINS-28010 Change By: Michael Dao 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.162209.142951271.14682.1559090881066%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-28010) Use Google Apps group for Authorization
Title: Message Title Michael Dao started work on JENKINS-28010 Change By: Michael Dao 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.162209.142951271.14656.1559090820846%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43001) Editor should offer to save without running the Pipeline
Title: Message Title harry chang edited a comment on JENKINS-43001 Re: Editor should offer to save without running the Pipeline This is a very good advice. We ofter often just want to save after editing pipeline in blue ocean without running the Pipeline. Now we have to save and run it, then stop the run. This is not normal. 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.180015.1490132242000.14651.1559090760267%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43001) Editor should offer to save without running the Pipeline
Title: Message Title harry chang commented on JENKINS-43001 Re: Editor should offer to save without running the Pipeline This is a very good advice. We ofter just want to save after editing pipeline in blue ocean without running the Pipeline. Now we have to save and run it, then stop the run. This is not normal. 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.180015.1490132242000.14647.1559090700156%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57728) Why I have to run it after editing pipeline in blueocean? I just want to save it sometimes ,not run.
Title: Message Title harry chang created an issue Jenkins / JENKINS-57728 Why I have to run it after editing pipeline in blueocean? I just want to save it sometimes ,not run. Issue Type: New Feature Assignee: Unassigned Components: blueocean-pipeline-editor-plugin Created: 2019-05-29 00:30 Priority: Critical Reporter: harry chang Why I have to run it after editing pipeline in blueocean? I just want to save it sometimes ,not run. I hope to add a save button, not "save and run". Add Comment This
[JIRA] (JENKINS-44930) Allow sh to return exit status, stdout and stderr all at once
Title: Message Title Fernando Nasser commented on JENKINS-44930 Re: Allow sh to return exit status, stdout and stderr all at once Norbert Lange The "command" was in a quote, but yes, we were talking about the 'sh' step. In fact we use "tee" after the '|' so we are also showing the command output in the log. I agree that the output should also go to the log. 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.183003.149756330.14644.1559089502369%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-18077) libvirt slaves plugin says hyperviser exceeds threshold
Title: Message Title Mike Kingsbury commented on JENKINS-18077 Re: libvirt slaves plugin says hyperviser exceeds threshold Still present in 2019. v1.8.5. Even with an arbitrarily high number in the thousands. 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.149374.1369419569000.14565.1559088360217%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47867) Make "Committers To Ignore" configurable via traits
Title: Message Title John Gaunt edited a comment on JENKINS-47867 Re: Make "Committers To Ignore" configurable via traits FIled a PR with an implementation of the Trait: [ https:// issues github . jenkins-ci.org com / browse jenkinsci / JENKINS bitbucket - 47867 branch-source-plugin/pull/194] The previous PR ([https://github.com/jenkinsci/bitbucket-branch-source-plugin/pull/77]) had a similar implementation but it was stated that this trait should exist in an external plugin. No rationale for that was given and it seems very logical for it to live in this plugin, to me. The class it modifies is implemented in this plugin and several other traits that also modify the BitbucketSCMSource exist in this 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.186379.1510079108000.14557.1559085600156%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44930) Allow sh to return exit status, stdout and stderr all at once
Title: Message Title
Suraj Sharma edited a comment on JENKINS-44930
Re: Allow sh to return exit status, stdout and stderr all at once
Maybe this small function can help take care of exit status and stdout.{code:java}def runCommand(script) {echo "[runCommand:script] ${script}"def stdoutFile = "rc.${BUILD_NUMBER}.out"script = script + " > " + stdoutFiledef res = [:]res["exitCode"] = sh(returnStatus: true, script: script)res["stdout"] = sh(returnStdout: true, script: "cat " + stdoutFile)sh(returnStatus: true, script: "rm -f " + stdoutFile)echo "[runCommand:response] ${res}"return res}{code} Example Usage{code}def response = runCommand("date")echo response["exitCode"]echo response["stdout"]{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.183003.149756330.14555.1559083922795%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44930) Allow sh to return exit status, stdout and stderr all at once
Title: Message Title
Suraj Sharma commented on JENKINS-44930
Re: Allow sh to return exit status, stdout and stderr all at once
Maybe this small function can help take care of exit status and stdout.
def runCommand(script) {
echo "[runCommand:script] ${script}"
def stdoutFile = "rc.${BUILD_NUMBER}.out"
script = script + " > " + stdoutFile
def res = [:]
res["exitCode"] = sh(returnStatus: true, script: script)
res["stdout"] = sh(returnStdout: true, script: "cat " + stdoutFile)
sh(returnStatus: true, script: "rm -f " + stdoutFile)
echo "[runCommand:response] ${res}"
return res
}
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.183003.149756330.14405.1559083801450%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57727) ConcurrentModificationException from lock step
Title: Message Title William Brode created an issue Jenkins / JENKINS-57727 ConcurrentModificationException from lock step Issue Type: Bug Assignee: Tobias Gruetzmacher Components: lockable-resources-plugin Created: 2019-05-28 22:05 Environment: Jenkins 2.150.2 Lockable Resources Plugin 2.5 Priority: Minor Reporter: William Brode I got this ConcurrentModificationException when using "lock" step for several pipelines running on the same master at the same time. I believe it can happen when new locks are being created while the list of locks is being looped through. java.util.ConcurrentModificationException at java.util.ArrayList$Itr.checkForComodification(ArrayList.java:909) at java.util.ArrayList$Itr.next(ArrayList.java:859) at org.jenkins.plugins.lockableresources.LockableResourcesManager.fromName(LockableResourcesManager.java:156) at org.jenkins.plugins.lockableresources.queue.LockableResourcesStruct.(LockableResourcesStruct.java:83) at org.jenkins.plugins.lockableresources.LockStepExecution.start(LockStepExecution.java:62) at org.jenkinsci.plugins.workflow.cps.DSL.invokeStep(DSL.java:268) at org.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:176) at org.jenkinsci.plugins.workflow.cps.CpsScript.invokeMethod(CpsScript.java:122) at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:48) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:113) at com.cloudbees.groovy.cps.sandbox.DefaultInvoker.methodCall(DefaultInvoker.java:20)
[JIRA] (JENKINS-57713) Cloud agent provisioning errors due to Remoting behaviour change
Title: Message Title Javier Delgado commented on JENKINS-57713 Re: Cloud agent provisioning errors due to Remoting behaviour change Certainly, trying to connect before the agent creation will cause the remoting attempt to fail and exit. The reconnect flag wont cover the initial bug, as it is interesting to keep on reconnecting while the agent is still registered (but stop doing so if the agent gets removed as happened after a master restart) Is there some rule or recommendation about the procedure and order of the "agent endpoint register" and "remoting start" order? It seems weird to kick a process that will have to retry until an endpoint becomes available 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.199655.1559046575000.14398.1559080020307%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57708) Check if X-Forwarded-For is present
Title: Message Title Owen Wood updated JENKINS-57708 Jenkins / JENKINS-57708 Check if X-Forwarded-For is present Change By: Owen Wood Status: In Review Resolved Resolution: Done 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.199648.1558993672000.14395.1559079480177%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57708) Check if X-Forwarded-For is present
Title: Message Title Owen Wood updated an issue Jenkins / JENKINS-57708 Check if X-Forwarded-For is present Change By: Owen Wood Summary: Attempt to detect reverse proxy Check if X-Forwarded-For is present 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.199648.1558993672000.14393.1559079360182%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47867) Make "Committers To Ignore" configurable via traits
Title: Message Title John Gaunt commented on JENKINS-47867 Re: Make "Committers To Ignore" configurable via traits FIled a PR with an implementation of the Trait: https://issues.jenkins-ci.org/browse/JENKINS-47867 The previous PR (https://github.com/jenkinsci/bitbucket-branch-source-plugin/pull/77) had a similar implementation but it was stated that this trait should exist in an external plugin. No rationale for that was given and it seems very logical for it to live in this plugin, to me. The class it modifies is implemented in this plugin and several other traits that also modify the BitbucketSCMSource exist in this 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.186379.1510079108000.14391.1559079120175%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46076) Test flake in CpsThreadTest.stop
Title: Message Title
Devin Nusbaum edited a comment on JENKINS-46076
Re: Test flake in CpsThreadTest.stop
I saw this flake again today along with {{ParallelStepTest.failureReporting}}. Both failed looking for {{Finished: $RESULT}}. I think it might have to do with the same a similar problem I ran into in Declarative which I worked around by adding a sleep when checking the build result did not match fails and checking again, see [here|https://github.com/jenkinsci/pipeline-model-definition-plugin/blob/31569c0385f555f0b3146c68eb748a5dcf16efd6/pipeline-model-definition/src/test/java/org/jenkinsci/plugins/pipeline/modeldefinition/AbstractModelDefTest.java#L511-L539].
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.184309.1502230337000.14385.1559077980120%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46076) Test flake in CpsThreadTest.stop
Title: Message Title Devin Nusbaum commented on JENKINS-46076 Re: Test flake in CpsThreadTest.stop I saw this flake again today along with ParallelStepTest.failureReporting. Both failed looking for Finished: $RESULT. I think it might have to do with the same problem I ran into in Declarative which I worked around by adding a sleep when the result did not match and checking again, see here. 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.184309.1502230337000.14381.1559077920136%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-16433) Jabber Plugin does not connect: stream:error conflict
Title: Message Title Florian Schmaus closed an issue as Incomplete Jenkins / JENKINS-16433 Jabber Plugin does not connect: stream:error conflict Change By: Florian Schmaus Status: Open Closed Resolution: Incomplete Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.147253.1358805856000.14378.1559077140308%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31979) Enable SASL authentication checkbox missing
Title: Message Title Florian Schmaus closed an issue as Not A Defect Jenkins / JENKINS-31979 Enable SASL authentication checkbox missing Change By: Florian Schmaus Status: In Progress Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.166938.1449664961000.14370.1559077080578%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-29802) jabber plugin disconnects from server with a socket failure
Title: Message Title Florian Schmaus closed an issue as Incomplete No further response, closing. Jenkins / JENKINS-29802 jabber plugin disconnects from server with a socket failure Change By: Florian Schmaus Status: Open Closed Resolution: Incomplete Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.164378.1438776433000.14368.1559077080553%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31979) Enable SASL authentication checkbox missing
Title: Message Title Florian Schmaus started work on JENKINS-31979 Change By: Florian Schmaus 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.166938.1449664961000.14360.1559077020411%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56890) IOException: "cannot find current thread"
Title: Message Title Devin Nusbaum updated JENKINS-56890 A potential fix for this issue was just released in version 2.69 of Pipeline Groovy Plugin. I was never able to reproduce the issue in a test, so there is a possibility that it is still not fixed, so if you still see the issue in version 2.69 please reopen the ticket and include the stack trace you are getting. Jenkins / JENKINS-56890 IOException: "cannot find current thread" Change By: Devin Nusbaum Status: In Review Resolved Resolution: Fixed Released As: workflow-cps 2.69 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 e
[JIRA] (JENKINS-56890) IOException: "cannot find current thread"
Title: Message Title Devin Nusbaum updated JENKINS-56890 A potential fix for this issue was just released in version 2.69 of Pipeline Groovy Plugin. I was never able to reproduce the issue in a test, so there is a possibility that it is still not fixed, so if you still see the issue in version 2.69 please reopen the ticket and include the stack trace you are getting. Jenkins / JENKINS-56890 IOException: "cannot find current thread" Change By: Devin Nusbaum Status: In Review Resolved Resolution: Fixed Released As: workflow-cps 2.69 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 e
[JIRA] (JENKINS-51487) Update Smack to 4.3
Title: Message Title Florian Schmaus updated JENKINS-51487 Jenkins / JENKINS-51487 Update Smack to 4.3 Change By: Florian Schmaus Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.190847.1527005759000.14355.1559076692829%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51487) Update Smack to 4.3
Title: Message Title Florian Schmaus updated JENKINS-51487 Jenkins / JENKINS-51487 Update Smack to 4.3 Change By: Florian Schmaus Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.190847.1527005759000.14353.1559076692810%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50223) Pipeline Jenkins master ran out of Java Metaspace
Title: Message Title Devin Nusbaum updated JENKINS-50223 A fix for this issue was just released in version 2.69 of Pipeline Groovy Plugin. Jenkins / JENKINS-50223 Pipeline Jenkins master ran out of Java Metaspace Change By: Devin Nusbaum Status: In Review Resolved Resolution: Fixed Released As: workflow-cps 2.69 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.189249.1521223408000.14313.1559076481005%40Atla
[JIRA] (JENKINS-53649) Strings from the "echo" step are suppressed in BlueOcean UI if they contain values found in an environment variable
Title: Message Title Marcello de Sales commented on JENKINS-53649 Re: Strings from the "echo" step are suppressed in BlueOcean UI if they contain values found in an environment variable Ian Katz Hilario Fernandes I will have to take it back after looking at your examples... So far we have observed: Values with references to params Values with references to env This is definitely an annoying situation when we want to show information to users 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.194144.1537309242000.14298.1559075280446%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56007) Can't copy source files from slave to master if security is enabled
Title: Message Title Ulli Hafner updated JENKINS-56007 Jenkins / JENKINS-56007 Can't copy source files from slave to master if security is enabled Change By: Ulli Hafner 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.197425.1549494089000.14290.1559075100862%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56007) Can't copy source files from slave to master if security is enabled
Title: Message Title Ulli Hafner commented on JENKINS-56007 Re: Can't copy source files from slave to master if security is enabled I finally managed it to reproduced it by clearing the contents of the file 30-default.conf. (See https://github.com/jenkinsci/warnings-ng-plugin/commit/d597cbdb6ad5d9709208debc2acecbe66cd6589a) 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.197425.1549494089000.14288.1559075100842%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54373) Quality Gate failure doesn't fail the step.
Title: Message Title Ulli Hafner commented on JENKINS-54373 Re: Quality Gate failure doesn't fail the step. The status is in progress, see https://github.com/jenkinsci/warnings-ng-plugin/pull/58 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.195127.1541002685000.14272.1559074920275%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57726) Gatling build history corrupted after upgrading to 2.178
Title: Message Title Darryl Mosher updated an issue Jenkins / JENKINS-57726 Gatling build history corrupted after upgrading to 2.178 Change By: Darryl Mosher Labels: jenkins 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.199669.1559073449000.14270.1559073900224%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57726) Gatling build history corrupted after upgrading to 2.178
Title: Message Title Darryl Mosher updated an issue Jenkins / JENKINS-57726 Gatling build history corrupted after upgrading to 2.178 Change By: Darryl Mosher Labels: jenkins 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.199669.1559073449000.14269.1559073900195%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57245) Support Kotlin compiler warnings (in an obvious manner)
Title: Message Title Ulli Hafner assigned an issue to Sladyn Nunes Jenkins / JENKINS-57245 Support Kotlin compiler warnings (in an obvious manner) Change By: Ulli Hafner Assignee: Ulli Hafner Sladyn Nunes 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.199008.1556622259000.14268.1559073540181%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57726) Gatling build history corrupted after upgrading to 2.178
Title: Message Title Darryl Mosher created an issue Jenkins / JENKINS-57726 Gatling build history corrupted after upgrading to 2.178 Issue Type: Bug Assignee: Unassigned Attachments: image-2019-05-28-14-56-11-831.png Components: gatling-plugin Created: 2019-05-28 19:57 Priority: Major Reporter: Darryl Mosher Gatling build history was corrupted after upgrading to 2.178. All previous builds lost the gatling reports and dates changed to DEC 31, 1969. Tried the steps suggested here, but it didn't correct the issue. https://support.cloudbees.com/hc/en-us/articles/218434707-Job-builds-timestamps-have-changed-to-DEC-31-1969 All Gatling jobs failed on 2.178 and provided no gatling report. We've since rolled back to 2.174 and have had no issues. Add Comment
[JIRA] (JENKINS-57685) Add button for Server config doesn't work
Title: Message Title Parichay Barpanda updated JENKINS-57685 Fixed by adding Extension annotation to DescriptorImpl of GitLabServer Jenkins / JENKINS-57685 Add button for Server config doesn't work Change By: Parichay Barpanda Status: In Progress 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.199620.1558824489000.14264.1559072160157%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57685) Add button for Server config doesn't work
Title: Message Title Parichay Barpanda started work on JENKINS-57685 Change By: Parichay Barpanda 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.199620.1558824489000.14263.1559071740078%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57725) Proc.executor inherits ContextClassLoader dynamically
Title: Message Title Devin Nusbaum created an issue Jenkins / JENKINS-57725 Proc.executor inherits ContextClassLoader dynamically Issue Type: Bug Assignee: Devin Nusbaum Attachments: 57954701-a859f600-78c1-11e9-823f-6dd0b2e07758.png Components: core Created: 2019-05-28 19:21 Priority: Minor Reporter: Devin Nusbaum The threads in the thread pool used for Proc.joinWithTimeout inherit their context class loader from the thread that calls Proc.joinWithTimeout, which seems undesirable. While looking into JENKINS-50223, I found a case where one of the threads in the thread pool was holding onto a CleanGroovyClassLoader class loader from workflow-cps (see the attached screenshot), which is definitely undesirable. We should wrap this thread pool in ClassLoaderSanityThreadFactory to prevent this kind of issue from happening. Add Comment
[JIRA] (JENKINS-57725) Proc.executor inherits ContextClassLoader dynamically
Title: Message Title Devin Nusbaum updated JENKINS-57725 Jenkins / JENKINS-57725 Proc.executor inherits ContextClassLoader dynamically Change By: Devin Nusbaum Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199668.1559071263000.14262.1559071320238%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57725) Proc.executor inherits ContextClassLoader dynamically
Title: Message Title Devin Nusbaum started work on JENKINS-57725 Change By: Devin Nusbaum 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.199668.1559071263000.14261.1559071320218%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-30600) git isn't run inside build container
Title: Message Title Mark Waite stopped work on JENKINS-30600 Change By: Mark Waite 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.165201.1442960713000.14255.1559070840430%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57683) ClassCastException in git plugin on GitHub branch scan
Title: Message Title Mark Waite closed an issue as Fixed Jenkins / JENKINS-57683 ClassCastException in git plugin on GitHub branch scan Change By: Mark Waite 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.199618.155881147.14247.1559070720095%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55356) Some workflow jobs fail after restart on Java 11 server
Title: Message Title Mark Waite closed an issue as Fixed Jenkins / JENKINS-55356 Some workflow jobs fail after restart on Java 11 server Change By: Mark Waite 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.196459.1546032041000.14249.1559070780318%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57717) podTemplate disclosing sensitive information via log
Title: Message Title Oliver Nocon commented on JENKINS-57717 Re: podTemplate disclosing sensitive information via log Thank you for your feedback, we are exactly on this version. I see the respective checkbox in Jenkins system configuration. When calling via pipeline script I was not able to get it working. When looking into https://github.com/jenkinsci/kubernetes-plugin/blob/master/src/main/java/org/csanchez/jenkins/plugins/kubernetes/pipeline/PodTemplateStep.java I am not able to find the respective setter but maybe there is a misunderstanding on my side and there is something else I overlooked ... 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.199660.1559055292000.14246.1559070480143%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57539) Prepare design document for a top level architecture
Title: Message Title Parichay Barpanda updated an issue Jenkins / JENKINS-57539 Prepare design document for a top level architecture Change By: Parichay Barpanda Comment: The document is being created as the implementation are done. 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.199447.1558177073000.14242.1559069880420%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57539) Prepare design document for a top level architecture
Title: Message Title Parichay Barpanda updated JENKINS-57539 Some important implementation of classes has been added to the document from the SCM API and Branch API docs. Unfortunately couldn't find more support for design document from any experienced developer of any Branch Source Plugin but with the help of well maintained codebase and javadocs I was able to come up with my versions of implementations idea. The design document doesn't provide a concrete idea of our plugin APIs but it will be updated throughout the course of development. So at the end of the plugin release, this design document will contain all the necessary information a user or other plugin authors require to extend or get inspired. Jenkins / JENKINS-57539 Prepare design document for a top level architecture Change By: Parichay Barpanda Status: In Progress Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received thi
[JIRA] (JENKINS-56007) Can't copy source files from slave to master if security is enabled
Title: Message Title Roman Pickl commented on JENKINS-56007 Re: Can't copy source files from slave to master if security is enabled we are using Jenkins ver. 2.164.3 (latest lts release) \secrets\filepath-filters.d\30-default.conf exists and has a timestamp from the last restart of jenkins yesterday (i think) i have added a warningsng.conf file in \secrets\whitelisted-callables.d with one line: io.jenkins.plugins.analysis.core.steps.IssuesScanner$ReportPostProcessor 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.197425.1549494089000.14231.1559069460249%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57722) Build Name and Description Setter 2.0.0 does not change BUILD_DISPLAY_NAME
Title: Message Title Jan Klos closed an issue as Duplicate Jenkins / JENKINS-57722 Build Name and Description Setter 2.0.0 does not change BUILD_DISPLAY_NAME Change By: Jan Klos Status: Open Closed Resolution: Duplicate Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199665.1559068607000.14228.1559069280285%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57539) Prepare design document for a top level architecture
Title: Message Title Parichay Barpanda commented on JENKINS-57539 Re: Prepare design document for a top level architecture The document is being created as the implementation are done. 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.199447.1558177073000.14226.1559069220226%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57691) GitLabAuthSourceTest fails
Title: Message Title Parichay Barpanda updated JENKINS-57691 Jenkins / JENKINS-57691 GitLabAuthSourceTest fails Change By: Parichay Barpanda Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199626.1558901074000.14221.1559069160442%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57691) GitLabAuthSourceTest fails
Title: Message Title Parichay Barpanda updated JENKINS-57691 Solved after adding GitLabAuthToken class to Extension list. Jenkins / JENKINS-57691 GitLabAuthSourceTest fails Change By: Parichay Barpanda Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199626.1558901074000.14222.1559069160463%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57691) GitLabAuthSourceTest fails
Title: Message Title Parichay Barpanda started work on JENKINS-57691 Change By: Parichay Barpanda 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.199626.1558901074000.14218.1559069100259%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57691) GitLabAuthSourceTest fails
Title: Message Title Parichay Barpanda commented on JENKINS-57691 Re: GitLabAuthSourceTest fails The GitLabAuthToken was not annotated with Extension so the credentials plugin always returned `null` for the runtime initalisation. 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.199626.1558901074000.14217.1559069100243%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57724) fixing premature octane logs initialization
Title: Message Title Radi Berkovich updated an issue Jenkins / JENKINS-57724 fixing premature octane logs initialization Change By: Radi Berkovich Environment: if premature octane logs initialization is occurred (before SDK's init ) , plugin initialization may fail in a whole or some parts of 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.199667.1559068956000.14214.1559069040098%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57724) fixing premature octane logs initialization
Title: Message Title Radi Berkovich updated an issue Jenkins / JENKINS-57724 fixing premature octane logs initialization Change By: Radi Berkovich if premature octane logs initialization is occurred (before SDK's init ) , plugin initialization may fail in a whole or some parts of 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.199667.1559068956000.14215.1559069040153%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57724) fixing premature octane logs initialization
Title: Message Title Radi Berkovich created an issue Jenkins / JENKINS-57724 fixing premature octane logs initialization Issue Type: Bug Assignee: Radi Berkovich Components: hp-application-automation-tools-plugin Created: 2019-05-28 18:42 Environment: if premature octane logs initialization is occurred (before SDK's init ) , plugin initialization may fail in a whole or some parts of it Priority: Major Reporter: Radi Berkovich 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
[JIRA] (JENKINS-57722) Build Name and Description Setter 2.0.0 does not change BUILD_DISPLAY_NAME
Title: Message Title Jan Klos commented on JENKINS-57722 Re: Build Name and Description Setter 2.0.0 does not change BUILD_DISPLAY_NAME Also at https://github.com/jenkinsci/build-name-setter-plugin/issues/45 - sorry about the duplicity, please close one of these as appropriate. 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.199665.1559068607000.14212.1559068980227%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57723) Add support of custom converter for testing framework
Title: Message Title Radi Berkovich updated an issue Jenkins / JENKINS-57723 Add support of custom converter for testing framework Change By: Radi Berkovich Summary: Add support of custom converted converter for testing framework 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.199666.1559068734000.14210.1559068860057%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57723) Add support of custom converted for testing framework
Title: Message Title Radi Berkovich created an issue Jenkins / JENKINS-57723 Add support of custom converted for testing framework Issue Type: Improvement Assignee: Radi Berkovich Components: hp-application-automation-tools-plugin Created: 2019-05-28 18:38 Priority: Major Reporter: Radi Berkovich 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.199666.1559068734000.14209.1559068740076%40Atlassian.JIRA. For more options, visit
[JIRA] (JENKINS-57722) Build Name and Description Setter 2.0.0 does not change BUILD_DISPLAY_NAME
Title: Message Title
Jan Klos created an issue
Jenkins / JENKINS-57722
Build Name and Description Setter 2.0.0 does not change BUILD_DISPLAY_NAME
Issue Type:
Bug
Assignee:
Damian Szczepanik
Components:
build-name-setter-plugin
Created:
2019-05-28 18:36
Priority:
Minor
Reporter:
Jan Klos
After an update to 2.178 (+plugins update), Build Name and Description Setter 2.0.0 does not change BUILD_DISPLAY_NAME env. variable when used in Execute Shell part of the job: Set Build Name + Set build name before build starts checked and Build Name value filled Execute shell:
VERSION="${BUILD_DISPLAY_NAME}"
Working build on older version:
13:37:03 First time build. Skipping changelog.
13:37:03 Set build name.
13:37:03 New build name is 'ns-11.10.4-137'
13:37:03 [ns-docker-gitlab] $ /bin/sh -xe /tmp/jenkins5134857411850746959.sh
13:37:03 + VERSION=ns-11.10.4-137
2.178 + 2.0.0:
11:11:52 First time build. Skipping changelog.
11:11:52 New run name is 'ns-11.11.0-143'
11:11:52 [ns-docker-gitlab] $ /bin/sh -xe /tmp/jenkins8791603508002973823.sh
11:11:52 + VERSION='#143'
There seems to be a disco
[JIRA] (JENKINS-57720) Legacy pipeline library definition not supported by JCasC
Title: Message Title
Mark Waite updated an issue
Jenkins / JENKINS-57720
Legacy pipeline library definition not supported by JCasC
Change By:
Mark Waite
When Based on the legacy SCM global pipeline library in my [lts-with-plugins docker image|https://github.com/MarkEWaite/docker-lfs/blob/1f19c254fb86e8503d2d7f3b76289224d6d1cff7/ref/org.jenkinsci.plugins.workflow.libs.GlobalLibraries.xml#L22], when I download the configuration as code suggested definition for my Jenkins server, it reports that the globalLibraries legacySCM section fails to export. The output is:{noformat}jenkins: globalLibraries:libraries:- defaultVersion: "master" name: "globalPipelineLibraryMarkEWaite" retriever:legacySCM: scm: "FAILED TO EXPORT org.jenkinsci.plugins.workflow.libs.SCMRetriever#scm:\\ java.lang.ClassCastException: java.util.Collections$UnmodifiableRandomAccessList\\ cannot be cast to hudson.plugins.git.UserRemoteConfig at hudson.plugins.git.GitSCM.updateFromUserData(GitSCM.java:255)\\ at hudson.plugins.git.GitSCM.(GitSCM.java:209)\nCaused: java.lang.reflect.InvocationTargetException\\ at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)\\ at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)\\ at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)\\ at java.lang.reflect.Constructor.newInstance(Constructor.java:423)\\ at io.jenkins.plugins.casc.impl.configurators.DataBoundConfigurator.describe(DataBoundConfigurator.java:256)\\ at io.jenkins.plugins.casc.impl.configurators.HeteroDescribableConfigurator.lambda$convertToNode$de0cd4f8$1(HeteroDescribableConfigurator.java:233)\\ at io.vavr.CheckedFunction0.lambda$unchecked$52349c75$1(CheckedFunction0.java:201)\\ at io.jenkins.plugins.casc.impl.configurators.HeteroDescribableConfigurator.convertToNode(HeteroDescribableConfigurator.java:233)\\ at io.jenkins.plugins.casc.impl.configurators.HeteroDescribableConfigurator.lambda$describe$5(HeteroDescribableConfigurator.java:103)\\ at io.vavr.control.Option.map(Option.java:373) at io.jenkins.plugins.casc.impl.configurators.HeteroDescribableConfigurator.describe(HeteroDescribableConfigurator.java:103)\\ at io.jenkins.plugins.casc.impl.configurators.HeteroDescribableConfigurator.describe(HeteroDescribableConfigurator.java:51)\\ at io.jenkins.plugins.casc.Attribute.describe(Attribute.java:198) \\ at io.jenkins.plugins.casc.impl.configurators.DataBoundConfigurator.describe(DataBoundConfigurator.java:265)\\ at io.jenkins.plugins.casc.impl.configurators.HeteroDescribableConfigurator.lambda$convertToNode$de0cd4f8$1(HeteroDescribableConfigurator.java:233)\\ at io.vavr.CheckedFunction0.lambda$unchecked$52349c75$1(CheckedFunction0.java:201)\\ a
[JIRA] (JENKINS-57719) Pegdown plugin not supported by JCasC
Title: Message Title
Mark Waite updated an issue
Jenkins / JENKINS-57719
Pegdown plugin not supported by JCasC
Change By:
Mark Waite
When Based on the configuration in my [lts-with-plugins docker image|https://github.com/MarkEWaite/docker-lfs/blob/1f19c254fb86e8503d2d7f3b76289224d6d1cff7/ref/config.xml#L5], when I view JCasC configuration on a system with Pegdown Formatter plugin, it shows:{noformat}jenkins: markupFormatter: "FAILED TO EXPORT hudson.model.Hudson#markupFormatter: java.lang.ClassCastException:\\ java.util.ArrayList cannot be cast to org.jenkins_ci.plugins.pegdown_formatter.PegDownExtension\\ at org.jenkins_ci.plugins.pegdown_formatter.ExtensionUtils.combineFlags(ExtensionUtils.java:56)\\ at org.jenkins_ci.plugins.pegdown_formatter.ExtensionUtils.toFlags(ExtensionUtils.java:50)\\ at org.jenkins_ci.plugins.pegdown_formatter.PegDownFormatter.(PegDownFormatter.java:56)\n\Caused: java.lang.reflect.InvocationTargetException at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native\\ Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)\\ at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)\\ at java.lang.reflect.Constructor.newInstance(Constructor.java:423) at io.jenkins.plugins.casc.impl.configurators.DataBoundConfigurator.describe(DataBoundConfigurator.java:256)\\ at io.jenkins.plugins.casc.impl.configurators.HeteroDescribableConfigurator.lambda$convertToNode$de0cd4f8$1(HeteroDescribableConfigurator.java:233)\\ at io.vavr.CheckedFunction0.lambda$unchecked$52349c75$1(CheckedFunction0.java:201)\\ at io.jenkins.plugins.casc.impl.configurators.HeteroDescribableConfigurator.convertToNode(HeteroDescribableConfigurator.java:233)\\ at io.jenkins.plugins.casc.impl.configurators.HeteroDescribableConfigurator.lambda$describe$5(HeteroDescribableConfigurator.java:103)\\ at io.vavr.control.Option.map(Option.java:373) at io.jenkins.plugins.casc.impl.configurators.HeteroDescribableConfigurator.describe(HeteroDescribableConfigurator.java:103)\\ at io.jenkins.plugins.casc.impl.configurators.HeteroDescribableConfigurator.describe(HeteroDescribableConfigurator.java:51)\\ at io.jenkins.plugins.casc.Attribute.describe(Attribute.java:198) at io.jenkins.plugins.casc.Configurator.describe(Configurator.java:162)"{noformat}
[JIRA] (JENKINS-57721) remote jobs view shows last known status when remote server is unreachable
Title: Message Title John Rocha created an issue Jenkins / JENKINS-57721 remote jobs view shows last known status when remote server is unreachable Issue Type: Bug Assignee: Jeff Horan Components: remote-jobs-view-plugin Created: 2019-05-28 18:20 Environment: Windows and Linux Jenkins version 2.164.2 Priority: Major Reporter: John Rocha The remote view plugin shows the last reported job status when a server is unreachable. The remote view plugin should instead show that the remote server is unreachable. This causes reporting confusion. We have a scenario where the last cached result was pass, then the server went offline. It was several days before the administrator learned that the Jenkins instance on the remote server stopped because the remote view was showing the cached pass results instead of unreachable. Add Comment
[JIRA] (JENKINS-57720) Legacy pipeline library definition not supported by JCasC
Title: Message Title Mark Waite created an issue Jenkins / JENKINS-57720 Legacy pipeline library definition not supported by JCasC Issue Type: Bug Assignee: Unassigned Components: workflow-cps-global-lib-plugin Created: 2019-05-28 18:18 Labels: jcasc-compatibility Priority: Minor Reporter: Mark Waite When I download the configuration as code suggested definition for my Jenkins server, it reports that the globalLibraries legacySCM section fails to export. The output is: jenkins: globalLibraries: libraries: - defaultVersion: "master" name: "globalPipelineLibraryMarkEWaite" retriever: legacySCM: scm: "FAILED TO EXPORT org.jenkinsci.plugins.workflow.libs.SCMRetriever#scm:\ \ java.lang.ClassCastException: java.util.Collections$UnmodifiableRandomAccessList\ \ cannot be cast to hudson.plugins.git.UserRemoteConfig at hudson.plugins.git.GitSCM.updateFromUserData(GitSCM.java:255)\ \ at hudson.plugins.git.GitSCM.(GitSCM.java:209)\nCaused: java.lang.reflect.InvocationTargetException\ \ at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)\ \ at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)\ \ at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)\ \ at java.lang.reflect.Constructor.newInstance(Constructor.java:423)\ \ at io.jenkins.plugins.casc.impl.configurators.DataBoundConfigurator.describe(DataBoundConfigurator.java:256)\ \ at i
[JIRA] (JENKINS-54373) Quality Gate failure doesn't fail the step.
Title: Message Title Ulli Hafner started work on JENKINS-54373 Change By: Ulli Hafner 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.195127.1541002685000.14192.1559066700461%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54010) Support two levels of parallelity in stages
Title: Message Title Rishi Thakkar commented on JENKINS-54010 Re: Support two levels of parallelity in stages I am bumping priority to blocker. Please let me know if this is something that I was not allowed to do. Hopefully, this will bring a little more attention to this issue. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194623.1539245979000.14134.1559065501072%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54010) Support two levels of parallelity in stages
Title: Message Title Rishi Thakkar updated an issue Jenkins / JENKINS-54010 Support two levels of parallelity in stages Change By: Rishi Thakkar Priority: Critical Blocker 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.194623.1539245979000.14132.1559065444133%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55210) Same downstream build is triggered by two different upstream jobs
Title: Message Title Kevin Yu updated an issue Jenkins / JENKINS-55210 Same downstream build is triggered by two different upstream jobs Change By: Kevin Yu Environment: Jenkins ver. 2. 46 138 . 2 4 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196280.1544821771000.14072.1559064540220%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55210) Same downstream build is triggered by two different upstream jobs
Title: Message Title Kevin Yu commented on JENKINS-55210 Re: Same downstream build is triggered by two different upstream jobs This issue happened again with the exact same symptom on version 2.138.4 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196280.1544821771000.14071.1559063700049%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54373) Quality Gate failure doesn't fail the step.
Title: Message Title Arno Moonen commented on JENKINS-54373 Re: Quality Gate failure doesn't fail the step. I'm also facing this issue. It is unclear to me what the status of this issue is. It was blocked by JENKINS-43995, but that issue appears to be resolved. Right now, not having the stage fail immediately prevents us from moving to pipelines. In the end the build fails, but in blue ocean nor in the normal view it is not clear where it actually failed, because it just keeps on going. 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.195127.1541002685000.14052.1559063280695%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-26138) Support workspaces for Pipeline jobs
Title: Message Title Devin Nusbaum commented on JENKINS-26138 Re: Support workspaces for Pipeline jobs David Riemens The fix to this ticket created a new page that lists all workspaces used by the build which is always accessible via a URL like /jobs///ws, which might be good enough for your purposes. If you really need to construct a link to the current workspace inside of of a Pipeline, my recommendation would be to create a new step that looks through enclosing blocks for WorkspaceAction and uses that to return or print a link to the logs. Either way, it would be better to create a new RFE or discuss on the mailing list rather than commenting on this ticket. 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.159718.141883805.14045.1559062320015%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-26138) Support workspaces for Pipeline jobs
Title: Message Title Devin Nusbaum commented on JENKINS-26138 Re: Support workspaces for Pipeline jobs David Riemens The fix to this ticket created a new page that lists all workspaces used by the build which is always accessible via a URL like /jobs///ws, which might be good enough for your purposes. If you really need to construct a link to the current workspace inside of of a Pipeline, my recommendation would be to create a new step that looks through enclosing blocks for WorkspaceAction and uses that to return or print a link to the logs. Either way, it would be better to create a new RFE or discuss on the mailing list rather than commenting on this ticket. 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.159718.141883805.13923.1559062272347%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57719) Pegdown plugin not supported by JCasC
Title: Message Title Mark Waite created an issue Jenkins / JENKINS-57719 Pegdown plugin not supported by JCasC Issue Type: Bug Assignee: bap Components: pegdown-formatter-plugin Created: 2019-05-28 16:41 Labels: jcasc-compatibility Priority: Minor Reporter: Mark Waite When I view JCasC configuration on a system with Pegdown Formatter plugin, it shows: jenkins: markupFormatter: "FAILED TO EXPORT hudson.model.Hudson#markupFormatter: java.lang.ClassCastException:\ \ java.util.ArrayList cannot be cast to org.jenkins_ci.plugins.pegdown_formatter.PegDownExtension\ \ at org.jenkins_ci.plugins.pegdown_formatter.ExtensionUtils.combineFlags(ExtensionUtils.java:56)\ \ at org.jenkins_ci.plugins.pegdown_formatter.ExtensionUtils.toFlags(ExtensionUtils.java:50)\ \ at org.jenkins_ci.plugins.pegdown_formatter.PegDownFormatter.(PegDownFormatter.java:56)\n\ Caused: java.lang.reflect.InvocationTargetException at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native\ \ Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)\ \ at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)\ \ at java.lang.reflect.Constructor.newInstance(Constructor.java:423) at io.jenkins.plugins.casc.impl.configurators.DataBoundConfigurator.describe(DataBoundConfigurator.java:256)\ \ at io.jenkins.plugins.casc.impl.configurators.HeteroDescribableConfigurator.lambda$convertToNode$de0cd4f8$1(HeteroDescribableConfigurator.java:233)\ \ at io.vavr.CheckedFunction0.lambda$unchecked$5
[JIRA] (JENKINS-57717) podTemplate disclosing sensitive information via log
Title: Message Title Carlos Sanchez commented on JENKINS-57717 Re: podTemplate disclosing sensitive information via log showRawYaml is in 1.15.4, what version are you using? 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.199660.1559055292000.13909.1559060760260%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56579) .mvn/extensions.xml not recognized
Title: Message Title Benjamin Brummer updated JENKINS-56579 Jenkins / JENKINS-56579 .mvn/extensions.xml not recognized Change By: Benjamin Brummer 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.198194.155264253.13855.1559058720320%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56579) .mvn/extensions.xml not recognized
Title: Message Title Benjamin Brummer updated JENKINS-56579 I can not reproduce the problem anymore. All maven versions work now as expected. Jenkins / JENKINS-56579 .mvn/extensions.xml not recognized Change By: Benjamin Brummer Status: Open Fixed but Unreleased Resolution: Cannot Reproduce 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.198194.155264253.13852.1559058660475%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57587) Lightweight checkout gives NPE
Title: Message Title Mark Waite commented on JENKINS-57587 Re: Lightweight checkout gives NPE I used an ssh protocol Bitbucket URL (g...@bitbucket.org:markewaite/jenkins-bugs.git) to clone the Pipeline with git plugin 3.10.0 and git plugin 4.0 pre-release without seeing an NPE. I also used ssh://g...@bitbucket.org/markewaite/jenkins-bugs.git to check with git plugin 3.10.0. I'm using an ed235519 ssh credential with the Bitbucket repository. Unfortunately, I still can't duplicate the problem you're seeing. 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.199505.1558465141000.13850.1559058300134%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57718) Cannot disable reduceLog setting
Title: Message Title Steven Wadsworth created an issue Jenkins / JENKINS-57718 Cannot disable reduceLog setting Issue Type: Bug Assignee: Nikolas Falco Components: xunit-plugin Created: 2019-05-28 15:18 Environment: CentOS 7.6.1810 Jenkins LTS 2.164.2 xUnit plugin 2.3.4 Priority: Minor Reporter: Steven Wadsworth I have converted all my jobs to use the Publisher instead of the Builder, but still cannot return to the old default behavior. I have a minimal installation of Jenkins running in the embedded container (java -jar jenkins.war). The xUnit plugin is the latest, 2.3.4. To reproduce: Create job, add "Publish xUnit Report" as Post-build step. Select CTest-Version 3.x (the type of report does not seem to matter) Click Advanced, then uncheck the reduceLog checkbox Save Reopen the job configuration, click Advanced. The reduceLog checkbox is checked. Additional information Manually edit the config.xml to set reduceLog to false. Manage Jenkins -> Reload configuration from disk Go to job configuration and look at advanced Publisher settings reduceLog checkb
[JIRA] (JENKINS-57717) podTemplate disclosing sensitive information via log
Title: Message Title Oliver Nocon created an issue Jenkins / JENKINS-57717 podTemplate disclosing sensitive information via log Issue Type: Bug Assignee: Carlos Sanchez Components: kubernetes-plugin Created: 2019-05-28 14:54 Priority: Major Reporter: Oliver Nocon In our Jenkins pipeline script we pass sensitive environment variables into the pod which come out of the job parameters. This sensitive information is unfortunately disclosed via the log. #459 / JENKINS-57116 introduced the option showRawYaml but this does not seem to take effect within a Jenkins pipeline when using podTemplate(showRawYaml: false, ...) Would be great to make this available. Add Comment
[JIRA] (JENKINS-44930) Allow sh to return exit status, stdout and stderr all at once
Title: Message Title
Norbert Lange commented on JENKINS-44930
Re: Allow sh to return exit status, stdout and stderr all at once
Fernando Nasser: I would like and prefer a dump into a file into workspace, while also having normal output. I am not sure what you mean by "command", you you mean the pipeline command ("sh"), or the native script? The native script is cumbersome, there might even be different ways with different shells, if you meant the pipeline command then I am all for it. but some other idea would be to use a context wrappers like
output(stdout: "build.log", stderr: "err.log") {
sh 'cmake --build .'
}
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.183003.149756330.13821.1559054763251%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57587) Lightweight checkout gives NPE
Title: Message Title Jeff Blaine commented on JENKINS-57587 Re: Lightweight checkout gives NPE Yes, I can still reproduce the same NPE with "Lightweight checkout" enabled using Git Plugin 3.10.0. Our job definition uses a repo URL of the format ssh://g...@bitbucket.our.org/~username/repo.git Our job definition specifies the appropriate Jenkins creds for that URL Maybe that will lead us somewhere? 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.199505.1558465141000.13736.1559054220108%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57587) Lightweight checkout gives NPE
Title: Message Title Mark Waite commented on JENKINS-57587 Re: Lightweight checkout gives NPE Since 3.10.0 doesn't change anything in this area compared to 3.9.3, I assume you will still be able to duplicate it. If you can duplicate it, please upload the config.xml of the job definition so that I can compare it to my test job. Also, please describe any areas where the steps you took were different than the steps I took. 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.199505.1558465141000.13733.1559054040217%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44930) Allow sh to return exit status, stdout and stderr all at once
Title: Message Title Fernando Nasser commented on JENKINS-44930 Re: Allow sh to return exit status, stdout and stderr all at once Although I am one of the supporters for the implementation of a solution to this JIRA I have to object to a solution like: " I believe command "sh" should always return an object with all relevant output (stdout, stderr, exit_code) " Output of sysout and syserr may be too extensive, have all sort of characters, etc. We had a system that included the output as one of the fields of a JSON output and that was always causing problems, requiring retrying, etc. The workaround for this JIRA that we are using for quite some time and it is working very well is to, if output is requested, write it to a file in the WORSPACE. We do it by piping the output (sysout and/or syserr) but that should be much clear if done by the command itself. 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.183003.149756330.13657.1559053801479%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57447) Agents sometimes left as suspended after starting from shutdown state
Title: Message Title Sander Bel commented on JENKINS-57447 Re: Agents sometimes left as suspended after starting from shutdown state Hi Jie, do you have an update? 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.199260.1557821873000.13655.1559053500102%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-3627) Add separate permission to view build logs
Title: Message Title Larkoie commented on JENKINS-3627 Re: Add separate permission to view build logs I'm also in need of this new feature. I've setup a few pipeline to perform various tasks for our team. When the pipeline executes a sh command it shows the whole command which sometimes contains paths or hosts information (IP address etc...) It would be great to allow us to disable the output view to users/groups of users. 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.133700.1241483278000.13643.1559053380433%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56977) Input "ChoiceParameterDefinition" with same name make the UI bug (select wrong choice when clicked)
Title: Message Title Gavin Mogan commented on JENKINS-56977 Re: Input "ChoiceParameterDefinition" with same name make the UI bug (select wrong choice when clicked) Ah, thats how html works in the browser. I don't think its a scenario we need to support since as you said its not a real world example, but i guess it is still a 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.198668.1554994689000.13641.1559052480172%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57696) Make list view properties JCasC-compliant
Title: Message Title Ewelina Wilkosz assigned an issue to Ewelina Wilkosz Jenkins / JENKINS-57696 Make list view properties JCasC-compliant Change By: Ewelina Wilkosz Assignee: Joseph Petersen Ewelina Wilkosz 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.199632.1558936371000.13637.1559051760242%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57696) Make list view properties JCasC-compliant
Title: Message Title Ewelina Wilkosz assigned an issue to Unassigned Jenkins / JENKINS-57696 Make list view properties JCasC-compliant Change By: Ewelina Wilkosz Assignee: Ewelina Wilkosz 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.199632.1558936371000.13639.1559051760266%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57716) Path set by withEnv overwritten
Title: Message Title
Fredrik Broman created an issue
Jenkins / JENKINS-57716
Path set by withEnv overwritten
Issue Type:
Bug
Assignee:
Tomas Salazar
Components:
nvm-wrapper-plugin
Created:
2019-05-28 13:50
Priority:
Minor
Reporter:
Fredrik Broman
Hi, Maybe this is intended behaviour (or maybe I'm doing something wrong) but if i have this test pipeline:
pipeline {
agent none
stages {
stage("nvm") {
agent {label 'npm'}
steps {
withEnv(["PATH+foo=/tmp"]) {
nvm('8.10.0') {
sh 'env'
}
}
}
}
}
}
/tmp is not on PATH: PATH=/var/opt/jenkins-slave/.nvm/versions/node/v8.10.0/bin:/var/opt/jenkins-slave/.nvm/versions/node/v8.10.0/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/opt/rh/git19/root/bin However if I just switch wtihEnv and nvm around:
steps {
nvm('8.10.0') {
withEnv(["PATH+foo=/tmp"]) {
sh 'env'
}
}
}
/tmp is now on the PATH: PATH=/tmp:/var/opt/jenkins-slave/.nvm/versions/node/v8.10.0/bin:/var/opt/jenkins-slave/.nvm/versions/node/v8.10.0/bin:/goss:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/opt/rh/git19/root/bin Wh
