[JIRA] (JENKINS-35988) Equivalent to polling commit exclusions for branch indexing
Title: Message Title Torben Knerr commented on JENKINS-35988 Re: Equivalent to polling commit exclusions for branch indexing +1 to what Kevin Phillips mentioned above. "Polling ignores commits in certain paths" is available for "normal" Pipelines, just not for Multibranch Pipelines. Jesse Glick any chance the extension to scm-api you mentioned in https://issues.jenkins-ci.org/browse/JENKINS-35988?focusedCommentId=295310=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-295310 are on the roadmap? (in my case, it would even be for the bitbucket-branch-source-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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54036) Write-Error in powershell step behaves confusingly
Title: Message Title Torben Knerr commented on JENKINS-54036 Re: Write-Error in powershell step behaves confusingly Jarrad Whitaker did you observe this is happening only with "PERFORMANCE_OPTIMIZED" durability? Asking, because we have that globally set to "PERFORMANCE_OPTIMIZED" too... 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54036) Write-Error in powershell step behaves confusingly
Title: Message Title Torben Knerr commented on JENKINS-54036 Re: Write-Error in powershell step behaves confusingly The documentation that is referred to can be found here: https://jenkins.io/blog/2017/07/26/powershell-pipeline/#what-causes-a-failing-exit-status (found it in a blog post only, the actual pipeline step reference does not mention this in detail) 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54036) Write-Error in powershell step behaves confusingly
Title: Message Title Torben Knerr commented on JENKINS-54036 Re: Write-Error in powershell step behaves confusingly I was about to create the same issue, but gladly found Jarrad Whitaker already created this one For us this is happening on Jenkins LTS 2.150.1 with workflow-durable-task-step plugin v2.26 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34256) Preparing Jenkins For Shutdown Hangs Running Pipelines
Title: Message Title Torben Knerr edited a comment on JENKINS-34256 Re: Preparing Jenkins For Shutdown Hangs Running Pipelines same Same issue here with Jenkins LTS 2.150.2 I'm seeing this with pipeline durability set to "PERFORMANCE_OPTIMIZED" in the global configuration.[~svanoort] re-reading your comment here https://issues.jenkins-ci.org/browse/JENKINS-34256?focusedCommentId=332080=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-332080 I am wondering why the currently executing pipeline should actually halt by design -- wouldn't it be more intuitive if any running pipelines just complete (as it was the case with freestyle jobs earlier) 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34256) Preparing Jenkins For Shutdown Hangs Running Pipelines
Title: Message Title Torben Knerr commented on JENKINS-34256 Re: Preparing Jenkins For Shutdown Hangs Running Pipelines same issue here with Jenkins LTS 2.150.2 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41709) Blue Ocean doesnt render Active Choices parameters
Title: Message Title Torben Knerr commented on JENKINS-41709 Re: Blue Ocean doesnt render Active Choices parameters Hi Bruno P. Kinoshita and Jenkins team, as a long term user and big fan of active choices, I would really love to see it being supported in blue ocean That's what is currently preventing us to upgrade from Jenkins classic to blue ocean. I can't help much more that than, just providing feedback that this would really be awesome to have Cheers, Torben 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53186) NUnit 2.x test cases with result Error are reported as Success
Title: Message Title Torben Knerr commented on JENKINS-53186 Re: NUnit 2.x test cases with result Error are reported as Success Hi Nikolas Falco, any news yet about a potential 2.2.4 release or expected timeline? Cheers, Torben 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53186) NUnit 2.x test cases with result Error are reported as Success
Title: Message Title Torben Knerr commented on JENKINS-53186 Re: NUnit 2.x test cases with result Error are reported as Success Thanks Nikolas Falco, just saw you already fixed it in master! Any plans for pushing out a 2.2.4 release with that included anytime soon? Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53186) NUnit 2.x test cases with result Error are reported as Success
Title: Message Title Torben Knerr edited a comment on JENKINS-53186 Re: NUnit 2.x test cases with result Error are reported as Success [~nfalco] however the reason we are converting to nunit2 format is actually that the previous version of xunit-plugin we used (1.102) did not support nunit3 yet. So while we are using nunit2 format in other places , we could indeed try to use nunit3 format here to work around that issue with xunit-plugin 2.2.3.Regarding the nunit-version attribute, I suspected that the "3.5.0.0" version was the culprit. However, I changed that to "2.5.0.0" manually before the report publishing and still got the same misbehaviour . So I concluded that even though this is a bug in nunit-v2-result-writer (thanks for digging out the link to the github issue!) it would not resolve the issue reported here. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53186) NUnit 2.x test cases with result Error are reported as Success
Title: Message Title Torben Knerr commented on JENKINS-53186 Re: NUnit 2.x test cases with result Error are reported as Success Nikolas Falco however, I changed that to "2.5.0.0" manually and still got the same misbehaviour Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53186) Test Failures reported as Success when using nunit3-console with nunit2 output formatter
Title: Message Title Torben Knerr updated an issue Jenkins / JENKINS-53186 Test Failures reported as Success when using nunit3-console with nunit2 output formatter Change By: Torben Knerr Priority: Minor Major Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53186) Test Failures reported as Success when using nunit3-console with nunit2 output formatter
Title: Message Title Torben Knerr updated an issue Jenkins / JENKINS-53186 Test Failures reported as Success when using nunit3-console with nunit2 output formatter Change By: Torben Knerr Issue Type: Improvement Bug Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53186) Test Failures reported as Success when using nunit3-console with nunit2 output formatter
Title: Message Title Torben Knerr updated an issue Jenkins / JENKINS-53186 Test Failures reported as Success when using nunit3-console with nunit2 output formatter Change By: Torben Knerr Summary: Test Failures not reported as Success when using nunit3-console with nunit2 output formatter Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53186) Test Failures not reported when using nunit3-console with nunit2 output formatter
Title: Message Title Torben Knerr updated an issue Jenkins / JENKINS-53186 Test Failures not reported when using nunit3-console with nunit2 output formatter Change By: Torben Knerr We are running `nunit3-console -result:TestResult.xml;format=nunit2` to produce NUnit2 compatible test reports with the NUnit3 runner.With the earlier xunit-plugin 1.102 version this worked just fine. Now with xunit-plugin 2.2.3, if we have errors / failures in the test results, these are not reported as failures anymore. Even worse, they are reported as success! TestResults.xml report file says: !screenshot-2.png|thumbnail! Jenkins / xunit-plugin 2.2.3 says: !screenshot-1.png|thumbnail! See the full example XML report attached Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53186) Test Failures not reported when using nunit3-console with nunit2 output formatter
Title: Message Title Torben Knerr updated an issue Jenkins / JENKINS-53186 Test Failures not reported when using nunit3-console with nunit2 output formatter Change By: Torben Knerr Attachment: screenshot-2.png Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53186) Test Failures not reported when using nunit3-console with nunit2 output formatter
Title: Message Title Torben Knerr updated an issue Jenkins / JENKINS-53186 Test Failures not reported when using nunit3-console with nunit2 output formatter Change By: Torben Knerr Attachment: screenshot-1.png Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53186) Test Failures not reported when using nunit3-console with nunit2 output formatter
Title: Message Title Torben Knerr commented on JENKINS-53186 Re: Test Failures not reported when using nunit3-console with nunit2 output formatter Nikolas Falco my first impression was that the "nunit-version" field (which is set to "3.5.0.0" in the attached example) might get interpreted. However, I manually changed this to "2.5.0.0" but still the same issue, failures were not reported correctly Note: we use "NUnitJunitHudsonTestType" assuming this will handle the NUnit2 format correctly (which it did in the xunit-plugin 1.102 version at least) Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53186) Test Failures not reported when using nunit3-console with nunit2 output formatter
Title: Message Title Torben Knerr updated an issue Jenkins / JENKINS-53186 Test Failures not reported when using nunit3-console with nunit2 output formatter Change By: Torben Knerr Attachment: Nunit3-in-nunit2-format-with-failures-TestReport.xml Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53186) Test Failures not reported when using nunit3-console with nunit2 output formatter
Title: Message Title Torben Knerr updated an issue Jenkins / JENKINS-53186 Test Failures not reported when using nunit3-console with nunit2 output formatter Change By: Torben Knerr Attachment: Nunit3-in-nunit2-format-with-failures-TestReport.xml Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53186) Test Failures not reported when using nunit3-console with nunit2 output formatter
Title: Message Title Torben Knerr created an issue Jenkins / JENKINS-53186 Test Failures not reported when using nunit3-console with nunit2 output formatter Issue Type: Improvement Assignee: Nikolas Falco Attachments: Nunit3-in-nunit2-format-with-failures-TestReport.xml Components: xunit-plugin Created: 2018-08-22 11:29 Environment: xunit-plugin 2.2.3 nunit3-console.exe 3.7.0 Priority: Minor Reporter: Torben Knerr We are running `nunit3-console -result:TestResult.xml;format=nunit2` to produce NUnit2 compatible test reports with the NUnit3 runner. With the earlier xunit-plugin 1.102 version this worked just fine. Now with xunit-plugin 2.2.3, if we have errors / failures in the test results, these are not reported anymore. See the example XML report attached Add Comment
[JIRA] (JENKINS-53165) Conversion Exception for NUnit2 XML Format when nunit-version is a String
Title: Message Title Torben Knerr commented on JENKINS-53165 Re: Conversion Exception for NUnit2 XML Format when nunit-version is a String See related PR here: https://github.com/kingatlas/jest-nunit-reporter/pull/3 Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53165) Conversion Exception for NUnit2 XML Format when nunit-version is a String
Title: Message Title Torben Knerr commented on JENKINS-53165 Re: Conversion Exception for NUnit2 XML Format when nunit-version is a String Thanks Nikolas Falco for pointing me to the XSD file, I totally missed that. Will create a PR in the jest-nunit-publisher repo with the version being properly set to 2.5.0.0. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53165) Conversion Exception for NUnit2 XML Format when nunit-version is a String
Title: Message Title Torben Knerr commented on JENKINS-53165 Re: Conversion Exception for NUnit2 XML Format when nunit-version is a String Nikolas Falco will do so, thanks! Regarding validity of version number: what is considered a valid "nunit-version"? I have seen digits only (e.g. "2.4.0.0") but also things like " 2.6.0.0" Any recommendation on this? Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53165) Conversion Exception for NUnit2 XML Format when nunit-version is a String
Title: Message Title Torben Knerr updated an issue Jenkins / JENKINS-53165 Conversion Exception for NUnit2 XML Format when nunit-version is a String Change By: Torben Knerr Attachment: TestResult-nunitVersion.xml Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53165) Conversion Exception for NUnit2 XML Format when nunit-version is a String
Title: Message Title
Torben Knerr updated an issue
Jenkins / JENKINS-53165
Conversion Exception for NUnit2 XML Format when nunit-version is a String
Change By:
Torben Knerr
This seems to be an incompatibility with [https://github.com/kingatlas/jest-nunit-reporter] which generates "na" as the nunitVersion nunit-version .As a result we get this conversion error:{noformat}org.jenkinsci.plugins.xunit.service.TransformerException: Conversion error: Cannot convert string "" to a double at org.jenkinsci.plugins.xunit.service.XUnitConversionService.convert(XUnitConversionService.java:81) at org.jenkinsci.plugins.xunit.service.XUnitTransformerCallable.invoke(XUnitTransformerCallable.java:120) at org.jenkinsci.plugins.xunit.service.XUnitTransformerCallable.invoke(XUnitTransformerCallable.java:39) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2750) at hudson.remoting.UserRequest.perform(UserRequest.java:208) at hudson.remoting.UserRequest.perform(UserRequest.java:54) at hudson.remoting.Request$2.run(Request.java:360) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at hudson.remoting.Engine$1$1.run(Engine.java:98) at java.lang.Thread.run(Thread.java:745) at ..remote call to JNLP4-connect connection from 10.48.41.61/10.48.41.61:49693(Native Method) at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1654) at hudson.remoting.UserResponse.retrieve(UserRequest.java:311) at hudson.remoting.Channel.call(Channel.java:905) at hudson.FilePath.act(FilePath.java:987){noformat}Root cause seems to be the {{ nunitVersion nunit-version ="na"}} attribute:{code}{code}See attached report file
Add Comment
[JIRA] (JENKINS-53165) Conversion Exception for NUnit2 XML Format when nunit-version is a String
Title: Message Title Torben Knerr updated an issue Jenkins / JENKINS-53165 Conversion Exception for NUnit2 XML Format when nunit-version is a String Change By: Torben Knerr Summary: Conversion Exception for NUnit2 XML Format when nunitVersion nunit-version is a String Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53165) Conversion Exception for NUnit2 XML Format when nunitVersion is a String
Title: Message Title Torben Knerr commented on JENKINS-53165 Re: Conversion Exception for NUnit2 XML Format when nunitVersion is a String probably related to JENKINS-52107 Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53165) Conversion Exception for NUnit2 XML Format when nunitVersion is a String
Title: Message Title Torben Knerr updated an issue Jenkins / JENKINS-53165 Conversion Exception for NUnit2 XML Format when nunitVersion is a String Change By: Torben Knerr Environment: xUnit Plugin 2.2.3 jest-nunit-reporter 1.3.0 Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53165) Conversion Exception for NUnit2 XML Format when nunitVersion is a String
Title: Message Title Torben Knerr updated an issue Jenkins / JENKINS-53165 Conversion Exception for NUnit2 XML Format when nunitVersion is a String Change By: Torben Knerr Summary: Conversion Exception for NUnit2 XML Format when nunitVersion is a string String Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53165) Conversion Exception for NUnit2 XML Format when nunitVersion is a string
Title: Message Title Torben Knerr created an issue Jenkins / JENKINS-53165 Conversion Exception for NUnit2 XML Format when nunitVersion is a string Issue Type: Improvement Assignee: Nikolas Falco Components: xunit-plugin Created: 2018-08-21 13:35 Environment: xUnit Plugin 2.2.3 Priority: Major Reporter: Torben Knerr This seems to be an incompatibility with https://github.com/kingatlas/jest-nunit-reporter which generates "na" as the nunitVersion. As a result we get this conversion error: org.jenkinsci.plugins.xunit.service.TransformerException: Conversion error: Cannot convert string "" to a double at org.jenkinsci.plugins.xunit.service.XUnitConversionService.convert(XUnitConversionService.java:81) at org.jenkinsci.plugins.xunit.service.XUnitTransformerCallable.invoke(XUnitTransformerCallable.java:120) at org.jenkinsci.plugins.xunit.service.XUnitTransformerCallable.invoke(XUnitTransformerCallable.java:39) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2750) at hudson.remoting.UserRequest.perform(UserRequest.java:208) at hudson.remoting.UserRequest.perform(UserRequest.java:54) at hudson.remoting.Request$2.run(Request.java:360) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at hudson.remoting.Engine$1$1.run(Engine.java:98) at java.lang.Thread.run(Thread.java:745) at ..remote call to
[JIRA] (JENKINS-42891) Using `vars/pipeline.groovy` causes script-security error starting with Jenkins 2.32.3
Title: Message Title Torben Knerr commented on JENKINS-42891 Re: Using `vars/pipeline.groovy` causes script-security error starting with Jenkins 2.32.3 Andrew Bayer I have assumed something like this, but this was only after hours of debugging. Questions: Is this new behaviour documented somewhere, like a warning / breaking changes in the CHANGELOG? Can you point me to the complete list of variables that can no longer be used? Would it be possible to check for inappropriate usage of these vars and throw a proper exception with a meaningful message instead? While I am somehow "sensitized" for this error now, I bet others will be tapping in the dark when they suddenly get totally unrelated exceptions like the one reported above. What do you think? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42891) Using `vars/pipeline.groovy` causes script-security error starting with Jenkins 2.32.3
Title: Message Title
Torben Knerr updated an issue
Jenkins / JENKINS-42891
Using `vars/pipeline.groovy` causes script-security error starting with Jenkins 2.32.3
Change By:
Torben Knerr
We are using a global lib with `vars/pipeline.groovy` in Jenkins 2.32.1 and everything works fine. When using the same lib with Jenkins 2.32.3 we suddenly get failing pipeline builds with this error: {code:java}org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: Scripts not permitted to use method groovy.lang.GroovyObject invokeMethod java.lang.String java.lang.Object (org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter doTry org.jenkinsci.plugins.workflow.cps.CpsClosure2) at org.jenkinsci.plugins.scriptsecurity.sandbox.whitelists.StaticWhitelist.rejectMethod(StaticWhitelist.java:183) at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onMethodCall(SandboxInterceptor.java:117) at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onMethodCall(SandboxInterceptor.java:103) at org.kohsuke.groovy.sandbox.impl.Checker$1.call(Checker.java:149) at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:146) at com.cloudbees.groovy.cps.sandbox.SandboxInvoker.methodCall(SandboxInvoker.java:16) ...{code} The `vars/pipeline.groovy` looks as simple as that: {code:java}def doStuff() {echo "hello!"}{code} And within our `Jenkinsfile` we call it like that: {code:java}node {stage("do stuff") {pipeline.doStuff() // throws above exception }}{code} It pretty much looks like a script-security plugin issue on first sight. (this was updated from 1.25 to 1.27 when we use Jenkins 2.32.3). However, after having simplified our `vars/pipeline.groovy` to such a mininmal helper method example there is really nothing that script security should complain about. But it still does throw the exception above.In a desperate move I renamed `vars/pipeline.groovy` to `vars/wat.groovy`, and guess what? It works... {code:java} node {stage("do stuff") {wat.doStuff() // works!}}{code} So my conclusion is that it must have something to do with either the name `pipeline.groovy`, or simply a variable named `pipeline` being implicitly defined in the global scope with newer Jenkins versions.I'm not sure which component exactly produces the error, so the ones I assigned are the most likely culprits for me.
[JIRA] (JENKINS-42891) Using `vars/pipeline.groovy` causes script-security error starting with Jenkins 2.32.3
Title: Message Title Torben Knerr created an issue Jenkins / JENKINS-42891 Using `vars/pipeline.groovy` causes script-security error starting with Jenkins 2.32.3 Issue Type: Bug Assignee: Andrew Bayer Components: pipeline-model-definition-plugin, script-security-plugin, workflow-cps-global-lib-plugin Created: 2017/Mar/17 5:58 PM Environment: Jenkins 2.32.3 LTS, with - script-security 1.27 - workflow-cps-global-lib 2.7 - pipeline-model-definition 1.1.1 Priority: Minor Reporter: Torben Knerr We are using a global lib with `vars/pipeline.groovy` in Jenkins 2.32.1 and everything works fine. When using the same lib with Jenkins 2.32.3 we suddenly get failing pipeline builds with this error: org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: Scripts not permitted to use method groovy.lang.GroovyObject invokeMethod java.lang.String java.lang.Object (org.jenkinsci.plugins.pipeline.modeldefinition.ModelInterpreter doTry org.jenkinsci.plugins.workflow.cps.CpsClosure2) at org.jenkinsci.plugins.scriptsecurity.sandbox.whitelists.StaticWhitelist.rejectMethod(StaticWhitelist.java:183) at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onMethodCall(SandboxInterceptor.java:117) at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onMethodCall(SandboxInterceptor.java:103) at org.kohsuke.groovy.sandbox.impl.Checker$1.call(Checker.java:149) at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:146) at com.cloudbees.groovy.cps.sandbox.SandboxInvoker.methodCall(SandboxInvoker.java:16) ...
[JIRA] (JENKINS-42878) Bitbucket-branch-source Plugin notifies library repository, not project repository
Title: Message Title Torben Knerr commented on JENKINS-42878 Re: Bitbucket-branch-source Plugin notifies library repository, not project repository Attached the job config.xml for inspection. You won't find the "base-jenkins-lib" repo mentioned here, because we set it to "Load implicitly" for every pipeline job via the global Jenkins configuration Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42878) Bitbucket-branch-source Plugin notifies library repository, not project repository
Title: Message Title Torben Knerr updated an issue Jenkins / JENKINS-42878 Bitbucket-branch-source Plugin notifies library repository, not project repository Change By: Torben Knerr Attachment: job_config.xml Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42878) Bitbucket-branch-source Plugin notifies library repository, not project repository
Title: Message Title Torben Knerr updated an issue Jenkins / JENKINS-42878 Bitbucket-branch-source Plugin notifies library repository, not project repository Change By: Torben Knerr Attachment: job.xml Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42878) Bitbucket-branch-source Plugin notifies library repository, not project repository
Title: Message Title Torben Knerr updated an issue Jenkins / JENKINS-42878 Bitbucket-branch-source Plugin notifies library repository, not project repository Change By: Torben Knerr Attachment: job.xml Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41214) bitbucket branch source plugin notifies wrong repository
Title: Message Title Torben Knerr edited a comment on JENKINS-41214 Re: bitbucket branch source plugin notifies wrong repository [~adaphi] [~escoem] just reported a similar / related issue here, but this happens without a custom recognizer: JENKINS-42878 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41214) bitbucket branch source plugin notifies wrong repository
Title: Message Title Torben Knerr commented on JENKINS-41214 Re: bitbucket branch source plugin notifies wrong repository Philip Adams just reported a similar / related issue here, but this happens without a custom recognizer: JENKINS-42878 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42878) Bitbucket-branch-source Plugin notifies library repository, not project repository
Title: Message Title Torben Knerr commented on JENKINS-42878 Re: Bitbucket-branch-source Plugin notifies library repository, not project repository Is probably related to JENKINS-41214, but we are not using a custom recognizer, so I'm not sure you consider this a duplicate Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42878) Bitbucket-branch-source Plugin notifies library repository, not project repository
Title: Message Title Torben Knerr commented on JENKINS-42878 Re: Bitbucket-branch-source Plugin notifies library repository, not project repository Set priority to "critical" because notifications are the whole point of this plugin (for us at least) Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42878) Bitbucket-branch-source Plugin notifies library repository, not project repository
Title: Message Title
Torben Knerr updated an issue
Jenkins / JENKINS-42878
Bitbucket-branch-source Plugin notifies library repository, not project repository
Change By:
Torben Knerr
I was wondering to get totally unrelated build status notifications in our "base-jenkins-lib" global CPS library repository.Turned out that when the actual project's ("example-hello-world") job was run (which uses the "base-jenkins-lib" library) the notifications ended up in last Bitbucket commit for the library, not in the commit for the project.Also note that it ended up exclusively in the commit of the library, no status was reported to the project's commit.I guess it just takes the wrong SHA as two git sources are present when you use a global library: { { code:java} Started by user admin }} {{ > git rev-parse --is-inside-work-tree # timeout=10 }} {{ Setting origin to ssh://git@stash.intranet. company acme .com:7999/devops/example-hello-world.git }} {{ > git config remote.origin.url ssh://git@stash.intranet. company acme .com:7999/devops/example-hello-world.git # timeout=10 }} {{ Fetching origin... }} {{ Fetching upstream changes from origin }} {{ > git --version # timeout=10 }} {{ > git fetch --tags --progress origin +refs/heads/*:refs/remotes/origin/* }} {{ Seen branch in repository origin/feature/do-try-improved }} {{ Seen branch in repository origin/feature/sonarqube }} {{ Seen branch in repository origin/feature/xxx }} {{ Seen branch in repository origin/master }} {{ Seen 4 remote branches }} {{ Obtained Jenkinsfile from 5dce620f781e59afb1e960aa6a8e32a1e0cf83b8 }} {{ Loading library base-jenkins-lib@feature/do-try-improved }} {{ > git rev-parse --is-inside-work-tree # timeout=10 }} {{ Setting origin to ssh://git@stash.intranet. company acme .com:7999/devops/base-jenkins-lib.git }} {{ > git config remote.origin.url ssh://git@stash.intranet. company acme .com:7999/devops/base-jenkins-lib.git # timeout=10 }} {{ Fetching origin... }} {{ Fetching upstream changes from origin }} {{ > git --version # timeout=10 }} {{ > git fetch --tags --progress origin +refs/heads/*:refs/remotes/origin/* }} {{ > git rev-parse feature/do-try-improved^ \ {commit} # timeout=10 }} {{ > git rev-parse origin/feature/do-try-improved^ \ {commit} # timeout=10 }} {{ > git rev-parse --is-inside-work-tree # timeout=10 }} {{ Fetching changes from the remote Git repository }} {{ > git config remote.origin.url ssh://git@stash.intranet. company acme .com:7999/devops/base-jenkins-lib.git # timeout=10 }} {{ Fetching upstream changes from ssh://git@stash.intranet. company acme .com:7999/devops/base-jenkins-lib.git }} {{ > git --version # timeout=10 }} {{ > git fetch --tags --progress ssh://git@stash.intranet. company acme .com:7999/devops/base-jenkins-lib.git +refs/heads/*:refs/remotes/origin/* }} {{ Checking out Revision 43a8bcec5d1eb28df07b736a2fb82e08960a6121 (feature/do-try-improved) }} {{ > git config core.sparsecheckout # timeout=10 }} {{ > git checkout -f
[JIRA] (JENKINS-42878) Bitbucket-branch-source Plugin notifies library repository, not project repository
Title: Message Title Torben Knerr updated an issue Jenkins / JENKINS-42878 Bitbucket-branch-source Plugin notifies library repository, not project repository Change By: Torben Knerr Priority: Minor Critical Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42878) Bitbucket-branch-source Plugin notifies library repository, not project repository
Title: Message Title
Torben Knerr created an issue
Jenkins / JENKINS-42878
Bitbucket-branch-source Plugin notifies library repository, not project repository
Issue Type:
Bug
Assignee:
Antonio Muñiz
Components:
bitbucket-branch-source-plugin
Created:
2017/Mar/17 12:22 PM
Environment:
Jenkins v2.32.3, bitbucket-branch-source v2.1.1
Priority:
Minor
Reporter:
Torben Knerr
I was wondering to get totally unrelated build status notifications in our "base-jenkins-lib" global CPS library repository. Turned out that when the actual project's ("example-hello-world") job was run (which uses the "base-jenkins-lib" library) the notifications ended up in last Bitbucket commit for the library, not in the commit for the project. Also note that it ended up exclusively in the commit of the library, no status was reported to the project's commit. I guess it just takes the wrong SHA as two git sources are present when you use a global library: Started by user admin {{ > git rev-parse --is-inside-work-tree # timeout=10}} Setting origin to ssh://g...@stash.intranet.company.com:7999/devops/example-hello-world.git {{ > git config remote.origin.url ssh://g...@stash.intranet.company.com:7999/devops/example-hello-world.git # timeout=10}} Fetching origin... Fetching upstream changes from origin {{ > git --version # timeout=10}} {{ > git fetch --tags --progress origin +refs/heads/:refs/remotes/origin/}} Seen branch in repository origin/feature/do-try-improved Seen branch in repository origin/feature/sonarqube Seen branch in repository origin/feature/xxx Seen branch in repository origin/master Seen 4 remote branches Obtained Jenkinsfile from 5dce620f781e59afb1e960aa6a8e32a1e0cf83b8 Loading library base-jenkins-lib@feature/do-try-improved {{ > git rev-parse --is-inside-work-tree # timeout=10}}
[JIRA] (JENKINS-38268) Parallel step and closure scope
Title: Message Title
Torben Knerr edited a comment on JENKINS-38268
Re: Parallel step and closure scope
I believe [~nvgoldin]'s example is not representative for this issue, since `get_dummy_params` is a method. If it were closure instead (which is totally not needed in this case, so it would be quite artificial) it would fail again, I suspect.Here is another example which suffers from the issue, and I have totally no clue how to work around it:{code:groovy}def onEachSlave(doStuff) { def doStuffClosures = [:] for (slave in ['slavelnx1', 'slavelnx2', 'slavelnx3']) {def s = slavedoStuffClosures[s] = { echo "running on ${s}..."; doStuff(s); echo "...done on ${s}!" } } return doStuffClosures}parallel(onEachSlave { slave ->echo " do doing stuff on ${slave}..."}){code}The output is:{noformat}[Pipeline] parallel[Pipeline] [slavelnx1] { (Branch: slavelnx1)[Pipeline] [slavelnx2] { (Branch: slavelnx2)[Pipeline] [slavelnx3] { (Branch: slavelnx3)[Pipeline] [slavelnx1] echo[slavelnx1] running on slavelnx1...[Pipeline] [slavelnx2] echo[slavelnx2] running on slavelnx2...[Pipeline] [slavelnx3] echo[slavelnx3] running on slavelnx3...[Pipeline] [slavelnx1] echo[slavelnx1] doing stuff on slavelnx3[Pipeline] [slavelnx1] echo[slavelnx1] ...done on slavelnx1![Pipeline] [slavelnx1] }[Pipeline] [slavelnx2] echo[slavelnx2] doing stuff on slavelnx3[Pipeline] [slavelnx2] echo[slavelnx2] ...done on slavelnx2![Pipeline] [slavelnx2] }[Pipeline] [slavelnx3] echo[slavelnx3] doing stuff on slavelnx3[Pipeline] [slavelnx3] echo[slavelnx3] ...done on slavelnx3![Pipeline] [slavelnx3] }[Pipeline] // parallel[Pipeline] End of Pipeline{noformat}This is Jenkins 2.32.1 and workflow-cps 2.23[~jglick] can you confirm this is the issue, or is it just my missing groovy foo?Would also be happy to hear if someone can come up with a workaround for this
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-38268) Parallel step and closure scope
Title: Message Title
Torben Knerr edited a comment on JENKINS-38268
Re: Parallel step and closure scope
I believe [~nvgoldin]'s example is not representative for this issue, since `get_dummy_params` is a method. If it were closure instead (which is totally not needed in this case, so it would be quite artificial) it would fail again, I suspect.Here is another example which suffers from the issue, and I have totally no clue how to work around it:{code:groovy}def onEachSlave(doStuff) { def slaves doStuffClosures = [ :] for (slave in [ 'slavelnx1', 'slavelnx2', 'slavelnx3'] def doStuffClosures = [:] for (slave in slaves ) {def s = slavedoStuffClosures[s] = { echo "running on ${s}..."; doStuff(s); echo "...done on ${s}!" } } return doStuffClosures}parallel(onEachSlave { slave ->echo "do stuff on ${slave}..."}){code}The output is:{noformat}[Pipeline] parallel[Pipeline] [slavelnx1] { (Branch: slavelnx1)[Pipeline] [slavelnx2] { (Branch: slavelnx2)[Pipeline] [slavelnx3] { (Branch: slavelnx3)[Pipeline] [slavelnx1] echo[slavelnx1] running on slavelnx1...[Pipeline] [slavelnx2] echo[slavelnx2] running on slavelnx2...[Pipeline] [slavelnx3] echo[slavelnx3] running on slavelnx3...[Pipeline] [slavelnx1] echo[slavelnx1] doing stuff on slavelnx3[Pipeline] [slavelnx1] echo[slavelnx1] ...done on slavelnx1![Pipeline] [slavelnx1] }[Pipeline] [slavelnx2] echo[slavelnx2] doing stuff on slavelnx3[Pipeline] [slavelnx2] echo[slavelnx2] ...done on slavelnx2![Pipeline] [slavelnx2] }[Pipeline] [slavelnx3] echo[slavelnx3] doing stuff on slavelnx3[Pipeline] [slavelnx3] echo[slavelnx3] ...done on slavelnx3![Pipeline] [slavelnx3] }[Pipeline] // parallel[Pipeline] End of Pipeline{noformat}This is Jenkins 2.32.1 and workflow-cps 2.23[~jglick] can you confirm this is the issue, or is it just my missing groovy foo?Would also be happy to hear if someone can come up with a workaround for this
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-38268) Parallel step and closure scope
Title: Message Title
Torben Knerr edited a comment on JENKINS-38268
Re: Parallel step and closure scope
I believe [~nvgoldin]'s example is not representative for this issue, since `get_dummy_params` is a method. If it were closure instead (which is totally not needed in this case, so it would be quite artificial) it would fail again, I suspect. [~jglick] here Here is another example which suffers from the issue, and I have totally no clue how to work around it:{code:groovy}def onEachSlave(doStuff) { def slaves = ['slavelnx1', 'slavelnx2', 'slavelnx3'] def doStuffClosures = [:] for (slave in slaves) {def s = slavedoStuffClosures[s] = { echo "running on ${s}..."; doStuff(s); echo "...done on ${s}!" } } return doStuffClosures}parallel(onEachSlave { slave ->echo "do stuff on ${slave}..."}){code}The output is:{noformat}[Pipeline] parallel[Pipeline] [slavelnx1] { (Branch: slavelnx1)[Pipeline] [slavelnx2] { (Branch: slavelnx2)[Pipeline] [slavelnx3] { (Branch: slavelnx3)[Pipeline] [slavelnx1] echo[slavelnx1] running on slavelnx1...[Pipeline] [slavelnx2] echo[slavelnx2] running on slavelnx2...[Pipeline] [slavelnx3] echo[slavelnx3] running on slavelnx3...[Pipeline] [slavelnx1] echo[slavelnx1] doing stuff on slavelnx3[Pipeline] [slavelnx1] echo[slavelnx1] ...done on slavelnx1![Pipeline] [slavelnx1] }[Pipeline] [slavelnx2] echo[slavelnx2] doing stuff on slavelnx3[Pipeline] [slavelnx2] echo[slavelnx2] ...done on slavelnx2![Pipeline] [slavelnx2] }[Pipeline] [slavelnx3] echo[slavelnx3] doing stuff on slavelnx3[Pipeline] [slavelnx3] echo[slavelnx3] ...done on slavelnx3![Pipeline] [slavelnx3] }[Pipeline] // parallel[Pipeline] End of Pipeline{noformat}This is Jenkins 2.32.1 and workflow-cps 2.23 [~jglick] can you confirm this is the issue, or is it just my missing groovy foo?Would also be happy to hear if someone can come up with a workaround for this
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-38268) Parallel step and closure scope
Title: Message Title
Torben Knerr commented on JENKINS-38268
Re: Parallel step and closure scope
I believe Nadav Goldin's example is not representative for this issue, since `get_dummy_params` is a method. If it were closure instead (which is totally not needed in this case, so it would be quite artificial) it would fail again, I suspect. Jesse Glick here is another example which suffers from the issue, and I have totally no clue how to work around it:
Unable to find source-code formatter for language: groovy. Available languages are: actionscript, html, java, _javascript_, none, sql, xhtml, xml
def onEachSlave(doStuff) {
def slaves = ['slavelnx1', 'slavelnx2', 'slavelnx3']
def doStuffClosures = [:]
for (slave in slaves) {
def s = slave
doStuffClosures[s] = { echo "running on ${s}..."; doStuff(s); echo "...done on ${s}!" }
}
return doStuffClosures
}
parallel(onEachSlave { slave ->
echo "do stuff on ${slave}..."
})
The output is:
[Pipeline] parallel
[Pipeline] [slavelnx1] { (Branch: slavelnx1)
[Pipeline] [slavelnx2] { (Branch: slavelnx2)
[Pipeline] [slavelnx3] { (Branch: slavelnx3)
[Pipeline] [slavelnx1] echo
[slavelnx1] running on slavelnx1...
[Pipeline] [slavelnx2] echo
[slavelnx2] running on slavelnx2...
[Pipeline] [slavelnx3] echo
[slavelnx3] running on slavelnx3...
[Pipeline] [slavelnx1] echo
[slavelnx1] doing stuff on slavelnx3
[Pipeline] [slavelnx1] echo
[slavelnx1] ...done on slavelnx1!
[Pipeline] [slavelnx1] }
[Pipeline] [slavelnx2] echo
[slavelnx2] doing stuff on slavelnx3
[Pipeline] [slavelnx2] echo
[slavelnx2] ...done on slavelnx2!
[Pipeline] [slavelnx2] }
[Pipeline] [slavelnx3] echo
[slavelnx3] doing stuff on slavelnx3
[Pipeline] [slavelnx3] echo
[slavelnx3] ...done on slavelnx3!
[Pipeline] [slavelnx3] }
[Pipeline] // parallel
[Pipeline] End of Pipeline
This is Jenkins 2.32.1 and workflow-cps 2.23
Add Comment
[JIRA] (JENKINS-41308) support Use Groovy Sandbox scripts in activeChoiceParams
Title: Message Title
Torben Knerr commented on JENKINS-41308
Re: support Use Groovy Sandbox scripts in activeChoiceParams
Daniel Spilker nevermind, I found it. Did not notice that the generated parameter is named differently ("choiceParameter"):Your example from above is working (in that it generates a valid config.xml at least) and gets me a big step further. Thanks a lot!
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41308) support Use Groovy Sandbox scripts in activeChoiceParams
Title: Message Title Torben Knerr updated an issue Jenkins / JENKINS-41308 support Use Groovy Sandbox scripts in activeChoiceParams Change By: Torben Knerr Attachment: screenshot-2.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41308) support Use Groovy Sandbox scripts in activeChoiceParams
Title: Message Title Torben Knerr commented on JENKINS-41308 Re: support Use Groovy Sandbox scripts in activeChoiceParams Daniel Spilker oh that is possible? It wasn't showing up on my local instances embedded API viewer, so I thought the automatically generated DSL would not be available. How can I tell if it is? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41308) support Use Groovy Sandbox scripts in activeChoiceParams
Title: Message Title Torben Knerr updated an issue Jenkins / JENKINS-41308 support Use Groovy Sandbox scripts in activeChoiceParams Change By: Torben Knerr Attachment: screenshot-1.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41308) support Use Groovy Sandbox scripts in activeChoiceParams
Title: Message Title
Torben Knerr commented on JENKINS-41308
Re: support Use Groovy Sandbox scripts in activeChoiceParams
Did anyone ever get this to work with the `configure` block? I lost a day of my life trying to modify the job xml in a `configure` block to enable the sandbox. Finally I got it so far:
pipelineJob("foo") {
parameters {
activeChoiceParam('Param') {
choiceType('SINGLE_SELECT')
groovyScript {
script('return ["a","b","c"]')
}
}
}
// we need to wrap the active choice parameters' groovy script and fallbackScript
// inside a secureScript wrapper with the sandbox enabled
configure { proj ->
// find all
[JIRA] (JENKINS-37781) Pipeline Config: ability to skip whole pipeline or stages based on boolean condition
Title: Message Title Torben Knerr edited a comment on JENKINS-37781 Re: Pipeline Config: ability to skip whole pipeline or stages based on boolean condition Is this a blue ocean only thing?I'm wondering if there is a "skipped" state in plain Pipeline DSL / Stage View Plugin, but haven't found it yet... - Also not clear how to use it in the DSL. Can you point me to an example? -*update: * found the docs:https://github.com/jenkinsci/pipeline-model-definition-plugin/commit/71c3d60ee486e48757bbd76315dc69a9e0418775#diff-fa1a1fd4274e733b635b3978b3d39ce6R88 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37781) Pipeline Config: ability to skip whole pipeline or stages based on boolean condition
Title: Message Title Torben Knerr edited a comment on JENKINS-37781 Re: Pipeline Config: ability to skip whole pipeline or stages based on boolean condition Is this a blue ocean only thing?I'm wondering if there is a "skipped" state in plain Pipeline DSL / Stage View Plugin, but haven't found it yet... Also not clear how to use it in the DSL. Can you point me to an example? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37781) Pipeline Config: ability to skip whole pipeline or stages based on boolean condition
Title: Message Title Torben Knerr commented on JENKINS-37781 Re: Pipeline Config: ability to skip whole pipeline or stages based on boolean condition Is this a blue ocean only thing? I'm wondering if there is a "skipped" state in plain Pipeline DSL / Stage View Plugin, but haven't found it yet... Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35230) The environment variables of git plugin not working in pipeline script.
Title: Message Title Torben Knerr commented on JENKINS-35230 Re: The environment variables of git plugin not working in pipeline script. Anyone still working on really fixing this in the Git plugin? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33185) Visualize parallel steps within a Pipeline Stage
Title: Message Title Torben Knerr commented on JENKINS-33185 Re: Visualize parallel steps within a Pipeline Stage Sam Van Oort Jesse Glick thanks for the feedback! Good to hear that stage view is still maintained. Understood it needs a community PR. Would love to see it, but currently too short on time too :-/ Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39977) Support for bitbucket-branch-source-plugin
Title: Message Title
Torben Knerr commented on JENKINS-39977
Re: Support for bitbucket-branch-source-plugin
Mike Kobit thanks taking this on! I was also confused as I was simply using the "Bitbucket Branch Source" in a standard "WorkflowMultiBranchProject". It was only later that I realized there is also the "Teams" configuration via the "OrganizationFolder". Here is how I configured it for a Multibranch Pipeline for now:
multibranchPipelineJob("somePipeline") {
configure {
it / sources / data / 'jenkins.branch.BranchSource' / source(class: 'com.cloudbees.jenkins.plugins.bitbucket.BitbucketSCMSource') {
credentialsId('bitbucketUserPasswordAPICredentialsForCheckingBranches')
checkoutCredentialsId('bitbucketCredentialsForCloningAndPulling')
repoOwner("KEY")
repository("my-repo")
includes('master release/* feature/*')
excludes()
bitbucketServerUrl('https://my.bitbucket.com')
sshPort('7999')
}
}
// check every minute for scm changes as well as new / deleted branches
triggers {
periodic(1)
}
}
Do you plan to add DSL support for this as well?
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-33185) Visualize parallel steps within a Pipeline Stage
Title: Message Title Torben Knerr edited a comment on JENKINS-33185 Re: Visualize parallel steps within a Pipeline Stage Would love to see something like [~johnwynne] proposed here as a an intermediate solution for the current pipeline stage view: https://issues.jenkins-ci.org/browse/JENKINS-33185?focusedCommentId=258129=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-258129 Blue Ocean is a huge update (30 plugins?) and probably not everyone can (or wants) to adopt it and has to stay with the classical jenkins UI for quite a while.Is there any ongoing work in PRs to implement [~johnwynne]'s proposal? Would it even have a chance to be accepted as an intermediate solution? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33185) Visualize parallel steps within a Pipeline Stage
Title: Message Title Torben Knerr commented on JENKINS-33185 Re: Visualize parallel steps within a Pipeline Stage Would love to see something like John Wynne proposed here as a https://issues.jenkins-ci.org/browse/JENKINS-33185?focusedCommentId=258129=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-258129 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39982) Add repo browser for Bitbucket Branch Sources
Title: Message Title Torben Knerr created an issue Jenkins / JENKINS-39982 Add repo browser for Bitbucket Branch Sources Issue Type: Improvement Assignee: Antonio Muñiz Components: bitbucket-branch-source-plugin Created: 2016/Nov/23 4:44 PM Environment: Jenkins v2, bitbucket-branch-source-plugin v1.8 Priority: Minor Reporter: Torben Knerr Until now there is no repo browser configurable, ie. whenever jenkins detects new commits there is no back-link to bitbucket. The GitSCMSource implements this already, but BitbucketSCMSource extends from plain SCMSource and thus doesn't have it. It should be even easier for BitbucketSCMSource to implement because all the information is already there (e.g. the bitbuckerServerUrl), so it's just a matter of having jenkins render the correct links to Bitbucket, I assume Add Comment
[JIRA] (JENKINS-39977) Support for bitbucket-branch-source-plugin
Title: Message Title Torben Knerr created an issue Jenkins / JENKINS-39977 Support for bitbucket-branch-source-plugin Issue Type: Improvement Assignee: Daniel Spilker Components: job-dsl-plugin Created: 2016/Nov/23 3:20 PM Environment: Jenkins v2, bitbucket-branch-source-plugin v1.8 Priority: Minor Reporter: Torben Knerr It would be nice to have a DSL for the bitbucket-branch-source-plugin See here: https://github.com/jenkinsci/bitbucket-branch-source-plugin Add Comment
[JIRA] (JENKINS-36283) PR builds customization
Title: Message Title Torben Knerr commented on JENKINS-36283 Re: PR builds customization Is PR 25 going in a good direction for this? https://github.com/jenkinsci/bitbucket-branch-source-plugin/pull/25 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-21892) Swarm client fails to create slave if CSRF filter is enabled
Title: Message Title Torben Knerr commented on JENKINS-21892 Re: Swarm client fails to create slave if CSRF filter is enabled Now it actually breaks if CSRF is disabled in Jenkins. See https://issues.jenkins-ci.org/browse/JENKINS-25421 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32793) POSTing to pluginManager/installNecessaryPlugins to install an older version of a plugin than the latest version will unexpectedly install the latest version
Title: Message Title Torben Knerr commented on JENKINS-32793 Re: POSTing to pluginManager/installNecessaryPlugins to install an older version of a plugin than the latest version will unexpectedly install the latest version It's 2016 and there is still no way to install a plugin at a specific version (inlcuding it's dependencies) from the commandline? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [packaging] (JENKINS-33285) Old jenkins versions are not listed in Debian repository Packages.gz
Title: Message Title Torben Knerr commented on JENKINS-33285 Re: Old jenkins versions are not listed in Debian repository Packages.gz Would love to see this fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [analysis-core-plugin] (JENKINS-31202) Trend Graphs are not shown in Job view for Workflow builds
Title: Message Title Torben Knerr commented on JENKINS-31202 Re: Trend Graphs are not shown in Job view for Workflow builds Antonio Muñiz same here with latest jenkins 2.3 and multibranch pipeline workflows. Would have expected that this is a basic feature with new jenkins 2.3 – or is this a known issue? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cucumber-testresult-plugin] (JENKINS-32095) Show durations per Step
Title: Message Title Torben Knerr created an issue Jenkins / JENKINS-32095 Show durations per Step Issue Type: New Feature Assignee: James Nord Attachments: step_duration.png Components: cucumber-testresult-plugin Created: 16/Dec/15 11:32 AM Environment: jenkins 1.6.38, cucumber-testresult-plugin 0.8.2 Priority: Minor Reporter: Torben Knerr As far as I can tell you get the durations of the individual steps only summarized for the scenario (and then for the feature), but the durations are not visible at the step level (see screenshot) It would be nice to have them visible on step level too, so that you can identify the slow steps. Showing them in a tooltip when hovering above the step would probably be enough, or just showing it beside the step.
[JIRA] [delivery-pipeline-plugin] (JENKINS-28582) MethodNotAllowed error when start new build
Title: Message Title Torben Knerr commented on JENKINS-28582 Re: MethodNotAllowed error when start new build Same here on Jenkins v1.572 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven-plugin] (JENKINS-10406) Maven Jobs with build modules in parallel always ABORTED
Torben Knerr commented on JENKINS-10406 Maven Jobs with build modules in parallel always ABORTED Tried adding a dummy post build step in the hope that the build status would be derived from the last build step, but that did not help either... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-10540) Maven build aborted without cause
Torben Knerr commented on JENKINS-10540 Maven build aborted without cause Tried adding a dummy post build step in the hope that the build status would be derived from the last build step, but that did not help either... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven-plugin] (JENKINS-10406) Maven Jobs with build modules in parallel always ABORTED
Torben Knerr commented on JENKINS-10406 Maven Jobs with build modules in parallel always ABORTED Same here, seeing this with Jenkins 1.572 and Maven 3.0.5 parallel builds This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-10540) Maven build aborted without cause
Torben Knerr commented on JENKINS-10540 Maven build aborted without cause Same here, seeing this with Jenkins 1.572 and Maven 3.0.5 parallel builds. @sniglom @slash @taeric @sraf did you ever find a suitable workaround? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-10540) Maven build aborted without cause
Torben Knerr edited a comment on JENKINS-10540 Maven build aborted without cause Same here, seeing this with Jenkins 1.572 and Maven 3.0.5 parallel builds. Adam H Bernhard Trummer Josh Berry S Raf did you ever find a suitable workaround? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven-plugin] (JENKINS-10406) Maven Jobs with build modules in parallel always ABORTED
Torben Knerr commented on JENKINS-10406 Maven Jobs with build modules in parallel always ABORTED Bob Tiernay did you find a workaround in the meantime? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [groovy-postbuild] (JENKINS-18989) Cannot get Plugin to honor Java Jar added via Additional groovy classpath
Torben Knerr commented on JENKINS-18989 Cannot get Plugin to honor Java Jar added via Additional groovy classpath Frank Merrow, Viktor Berke would be higly interested in that, too This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jira] (JENKINS-16292) Set Release date to now() for Post Build Step 'Mark a JIRA Version as Released'
Torben Knerr
commented on JENKINS-16292
Set Release date to now() for Post Build Step Mark a JIRA Version as Released
Does "Mark a JIRA Version as Released" actually work for you?
It will create new versions in jira, but marking an existing version as released does not work for me at all...
This is what I get:
FATAL: Unable to release jira version 2.3-dev88/MAV: com.atlassian.jira.rpc.exception.RemoteValidationException: Error retrieving project with key 'MAV': Es konnte kein Projekt mit Schlüssel 'MAV' gefunden werden.
AxisFault
faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
faultSubcode:
faultString: com.atlassian.jira.rpc.exception.RemoteValidationException: Error retrieving project with key 'MAV': Es konnte kein Projekt mit Schlüssel 'MAV' gefunden werden.
faultActor:
faultNode:
faultDetail:
{}com.atlassian.jira.rpc.exception.RemoteException:null
{http://xml.apache.org/axis/}hostname:s0046
Would be interesting to hear from someone who had that actually working. We are on jenkins v1.5.72 btw
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [jira] (JENKINS-20322) JIRA plugin should be configurable to decide where to write other than comments
Torben Knerr commented on JENKINS-20322 JIRA plugin should be configurable to decide where to write other than comments That would be a very handy feature. We currently disabled updating the jira issues because we couldn't find our real comments anymore... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jira] (JENKINS-25015) RemoteValidationException when using Mark JIRA Version as Released
Torben Knerr
created JENKINS-25015
RemoteValidationException when using Mark JIRA Version as Released
Issue Type:
Bug
Assignee:
Unassigned
Components:
jira
Created:
07/Oct/14 8:53 AM
Description:
Trying to use the "Mark JIRA Version as Released" post build step I get the follwoing exception / build failure:
...
FATAL: Unable to release jira version 2.3-dev88/MAV: com.atlassian.jira.rpc.exception.RemoteValidationException: Error retrieving project with key 'MAV': Es konnte kein Projekt mit Schlüssel 'MAV' gefunden werden.
AxisFault
faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
faultSubcode:
faultString: com.atlassian.jira.rpc.exception.RemoteValidationException: Error retrieving project with key 'MAV': Es konnte kein Projekt mit Schlüssel 'MAV' gefunden werden.
faultActor:
faultNode:
faultDetail:
{}com.atlassian.jira.rpc.exception.RemoteException:null
{http://xml.apache.org/axis/}hostname:s0046
com.atlassian.jira.rpc.exception.RemoteValidationException: Error retrieving project with key 'MAV': Es konnte kein Projekt mit Schlüssel 'MAV' gefunden werden.
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
at java.lang.Class.newInstance(Class.java:374)
at org.apache.axis.encoding.ser.BeanDeserializer.init(BeanDeserializer.java:104)
at org.apache.axis.encoding.ser.BeanDeserializer.init(BeanDeserializer.java:90)
at hudson.plugins.jira.soap.RemoteValidationException.getDeserializer(RemoteValidationException.java:75)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.apache.axis.encoding.ser.BaseDeserializerFactory.getSpecialized(BaseDeserializerFactory.java:154)
at org.apache.axis.encoding.ser.BaseDeserializerFactory.getDeserializerAs(BaseDeserializerFactory.java:84)
at org.apache.axis.encoding.DeserializationContext.getDeserializer(DeserializationContext.java:464)
at org.apache.axis.encoding.DeserializationContext.getDeserializerForType(DeserializationContext.java:547)
at org.apache.axis.message.SOAPFaultDetailsBuilder.onStartChild(SOAPFaultDetailsBuilder.java:157)
at org.apache.axis.encoding.DeserializationContext.startElement(DeserializationContext.java:1035)
at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.startElement(AbstractSAXParser.java:509)
at com.sun.org.apache.xerces.internal.parsers.AbstractXMLDocumentParser.emptyElement(AbstractXMLDocumentParser.java:182)
at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.scanStartElement(XMLNSDocumentScannerImpl.java:355)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:2770)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:606)
at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(XMLNSDocumentScannerImpl.java:117)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:510)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:848)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:777)
at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:141)
at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1213)
at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:649)
at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl.parse(SAXParserImpl.java:333)
at
[JIRA] [jira] (JENKINS-25015) RemoteValidationException when using Mark JIRA Version as Released
Torben Knerr updated JENKINS-25015 RemoteValidationException when using Mark JIRA Version as Released added screenshot Change By: Torben Knerr (07/Oct/14 8:56 AM) Attachment: mar_version_as_released_doesnt_work.png This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jira] (JENKINS-16292) Set Release date to now() for Post Build Step 'Mark a JIRA Version as Released'
Torben Knerr commented on JENKINS-16292 Set Release date to now() for Post Build Step Mark a JIRA Version as Released Created JENKINS-25015 for the above error This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jira] (JENKINS-25015) RemoteValidationException when using Mark JIRA Version as Released
Torben Knerr commented on JENKINS-25015 RemoteValidationException when using Mark JIRA Version as Released don't see anything suspicious in the log (hudson.plugins.jira set to ALL level): Oct 07, 2014 11:22:23 AM FINE hudson.plugins.jira.JiraSession Fetching versions from project: MAV Oct 07, 2014 11:22:23 AM FINE hudson.plugins.jira.JiraSession Fetching versions from project: MAV Oct 07, 2014 11:22:24 AM FINE hudson.plugins.jira.JiraSession Releaseing version: 2.3-dev88 Oct 07, 2014 11:22:24 AM FINE hudson.plugins.jira.JiraSession Fetching versions from project: MAV This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [scm-sync-configuration] (JENKINS-24686) scm-sync-configuration fails if job name contains a whitespace
Torben Knerr commented on JENKINS-24686 scm-sync-configuration fails if job name contains a whitespace me too This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [scm-sync-configuration] (JENKINS-22666) No popup window when committing changes to job config for putting in commit message
Torben Knerr commented on JENKINS-22666 No popup window when committing changes to job config for putting in commit message Can confirm that reverting the commit mentioned by @colonelcoder indeed fixes the problem: https://github.com/tknerr/scm-sync-configuration-plugin/compare/reverted Providing a better fix (rather than just plain reverting) proves to be difficult as the tests for 0.0.8 don't pass in my environment. Also, you need JDK6 in order to compile it. @fcamblor: if you like I can create a PR for the revert though This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [scm-sync-configuration] (JENKINS-22666) No popup window when committing changes to job config for putting in commit message
Torben Knerr commented on JENKINS-22666 No popup window when committing changes to job config for putting in commit message Donwgraded to 0.0.7.4 as suggested by @colonelcoder above. The popup now appears, but the commits are not being pushed to the remote repo anymore... any ideas? P.S.: the log looks fine, though: Sep 17, 2014 11:09:54 AM FINE hudson.plugins.scm_sync_configuration.SCMManipulator Checked in SCM files ! Sep 17, 2014 11:09:54 AM FINEST hudson.plugins.scm_sync_configuration.ScmSyncConfigurationBusiness Commit Commit hudson.plugins.scm_sync_configuration.model.Commit@268189ca : Author : Torben Knerr Comment : Job [maven.dummy] configuration updated by torben.knerr with following comment : NAUA-25 yes we can! (now add commit messages to build plan changes :-)) Changeset : A jobs/maven.dummy/config.xml pushed to SCM ! Sep 17, 2014 11:14:05 AM FINEST hudson.plugins.scm_sync_configuration.ScmSyncConfigurationBusiness Queuing commit Commit hudson.plugins.scm_sync_configuration.model.Commit@5a1ab9cb : Author : Torben Knerr Comment : Jenkins configuration files updated by torben.knerr Changeset : A hudson.plugins.groovy.Groovy.xml A hudson.plugins.jira.JiraProjectProperty.xml A hudson.plugins.emailext.ExtendedEmailPublisher.xml A hudson.maven.MavenModuleSet.xml A hudson.plugins.git.GitSCM.xml A hudson.triggers.SCMTrigger.xml A hudson.plugins.git.GitTool.xml A scm-sync-configuration.xml A hudson.plugins.gradle.Gradle.xml A hudson.tasks.Mailer.xml A config.xml A hudson.tasks.Maven.xml A hudson.tasks.Shell.xml to SCM ... Sep 17, 2014 11:14:05 AM FINEST hudson.plugins.scm_sync_configuration.ScmSyncConfigurationBusiness This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [scm-sync-configuration] (JENKINS-22666) No popup window when committing changes to job config for putting in commit message
Torben Knerr commented on JENKINS-22666 No popup window when committing changes to job config for putting in commit message Same here with Jenkins 1.5.72 and scm-sync-config 0.0.8 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
