[JIRA] (JENKINS-43749) Support multiple Jenkinsfiles from the same repository
Title: Message Title Jeffrey Bennett edited a comment on JENKINS-43749 Re: Support multiple Jenkinsfiles from the same repository I cannot speak to all the various use-cases that people have brought up, but it seems like a fair-number of people looking for this would be satisfied if multi-branch pipelines just supported an 'exclude regions' flag. You get that behavior with regular-pipeline, but not multi-branch pipeline.In my situation (and seems like others have this as well), I have directoryA/Jenkinsfile and directoryB/Jenkinsfile, and I wish to trigger pipelineA when commits are made to DirectoryA, and pipelineB for DirectoryB. There are [ [ a few solutions floating around| |#60316968]] [https://stackoverflow.com/questions/49448029/multiple-jenkinsfile-in-one-repository/60316968] [ ] |#60316968]] that effectively have both pipelineA and pipelineB starting, doing a 'validate' step, and then pipeline logic to short-circuit, causing completing when the commit is on the other side. But I'd really prefer that the build NEVER start in the first place for the wrong pipeline. Commit to DirectoryA -> only PipelineA is triggered. That amounts to PipelineA configuring "DirectoryB" as an excludes region (and vice versa).That said, there are a bunch of use-cases all entwined herein, and this is only one of them. But... it seems like a fairly well-defined one that might mitigate a lot of people's issues. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving
[JIRA] (JENKINS-43749) Support multiple Jenkinsfiles from the same repository
Title: Message Title Jeffrey Bennett edited a comment on JENKINS-43749 Re: Support multiple Jenkinsfiles from the same repository I cannot speak to all the various use-cases that people have brought up, but it seems like a fair-number of people looking for this would be satisfied if multi-branch pipelines just supported an 'exclude regions' flag. You get that behavior with regular-pipeline, but not multi-branch pipeline.In my situation (and seems like others have this as well), I have directoryA/Jenkinsfile and directoryB/Jenkinsfile, and I wish to trigger pipelineA when commits are made to DirectoryA, and pipelineB for DirectoryB. There are [ [ a few solutions floading floating around| |#60316968]] [https://stackoverflow.com/questions/49448029/multiple-jenkinsfile-in-one-repository/60316968 ] []| #60316968]] that effectively have both pipelineA and pipelineB starting, doing a 'validate' step, and then pipeline logic to short-circuit, causing completing when the commit is on the other side. But I'd really prefer that the build NEVER start in the first place for the wrong pipeline. Commit to DirectoryA -> only PipelineA is triggered. That amounts to PipelineA configuring "DirectoryB" as an excludes region (and vice versa).That said, there are a bunch of use-cases all entwined herein, and this is only one of them. But... it seems like a fairly well-defined one that might mitigate a lot of people's issues. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop
[JIRA] (JENKINS-43749) Support multiple Jenkinsfiles from the same repository
Title: Message Title Jeffrey Bennett edited a comment on JENKINS-43749 Re: Support multiple Jenkinsfiles from the same repository I cannot speak to all the various use-cases that people have brought up, but it seems like a fair-number of people looking for this would be satisfied if multi-branch pipelines just supported an 'exclude regions' flag. You get that behavior with regular-pipeline, but not multi-branch pipeline.In my situation (and seems like others have this as well), I have directoryA/Jenkinsfile and directoryB/Jenkinsfile, and I wish to trigger pipelineA when commits are made to DirectoryA, and pipelineB for DirectoryB. There are [a few solutions floating floading around|[https://stackoverflow.com/questions/49448029/multiple-jenkinsfile-in-one-repository/60316968#60316968]] that effectively have both pipelineA and pipelineB starting, doing a 'validate' step, and then pipeline logic to short-circuit, causing completing when the commit is on the other side. But I'd really prefer that the build NEVER start in the first place for the wrong pipeline. Commit to DirectoryA -> only PipelineA is triggered. That amounts to PipelineA configuring "DirectoryB" as an excludes region (and vice versa).That said, there are a bunch of use-cases all entwined herein, and this is only one of them. But... it seems like a fairly well-defined one that might mitigate a lot of people's issues. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send
[JIRA] (JENKINS-43749) Support multiple Jenkinsfiles from the same repository
Title: Message Title Jeffrey Bennett commented on JENKINS-43749 Re: Support multiple Jenkinsfiles from the same repository I cannot speak to all the various use-cases that people have brought up, but it seems like a fair-number of people looking for this would be satisfied if multi-branch pipelines just supported an 'exclude regions' flag. You get that behavior with regular-pipeline, but not multi-branch pipeline. In my situation (and seems like others have this as well), I have directoryA/Jenkinsfile and directoryB/Jenkinsfile, and I wish to trigger pipelineA when commits are made to DirectoryA, and pipelineB for DirectoryB. There are a few solutions floating around that effectively have both pipelineA and pipelineB starting, doing a 'validate' step, and then pipeline logic to short-circuit, causing completing when the commit is on the other side. But I'd really prefer that the build NEVER start in the first place for the wrong pipeline. Commit to DirectoryA -> only PipelineA is triggered. That amounts to PipelineA configuring "DirectoryB" as an excludes region (and vice versa). That said, there are a bunch of use-cases all entwined herein, and this is only one of them. But... it seems like a fairly well-defined one that might mitigate a lot of people's issues. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit
[JIRA] (JENKINS-59813) JacocoPublisher (part of pipeline-maven) does not deal with excludes properly
Title: Message Title Jeffrey Bennett commented on JENKINS-59813 Re: JacocoPublisher (part of pipeline-maven) does not deal with excludes properly Found a work-around of sorts. Completely disable the JacocoPublisher and use the external 'jacoco' step instead. Since the latter accepts exclude, it can be properly configured. If you don't disable the JacocoPublisher, you wind up with two similar looking reports in Jenkins. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202545.1571276714000.13240.1571755200205%40Atlassian.JIRA.
[JIRA] (JENKINS-59813) JacocoPublisher (part of pipeline-maven) does not deal with excludes properly
Title: Message Title Jeffrey Bennett created an issue Jenkins / JENKINS-59813 JacocoPublisher (part of pipeline-maven) does not deal with excludes properly Issue Type: Bug Assignee: Alvaro Lobato Components: pipeline-maven-plugin Created: 2019-10-17 01:45 Priority: Major Reporter: Jeffrey Bennett The jacoco report published by pipeline indicates classes that should have been excluded. Our build, a multi-module maven build executes jacoco on multiple modules. In the POM, we indicate on a number of classes (generated java). When built by maven (command-line), the jacoco report is properly created - excluded files are properly excluded. When we wrapper this build into a jenkinsfile and invoke it via a withMaven(..), the JacocoPublisher kicks in. The jacoco report on the Jenkins job appears to include the excluded files. It looks to me like JacocoPublisher is reinvoking Jacoco-Plugin with default parameters. The Jacoco-Plugin output shows a blank line for 'exclude', which explains why the report has things it should not. I suspect the easiest solution is to offer a parameter on JacocoPubisher that would pass-through to the Jacoco-Plugin. This would allow people to write Jenkinsfiles, enter the 'excludes' they desire, and Jacoco-Plugin would then run properly.
[JIRA] (JENKINS-37984) org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script
Title: Message Title Jeffrey Bennett commented on JENKINS-37984 Re: org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script Carsten's approach seems to suggest that the behavior of all node() elements can be offloaded to subordinate groovy scripts. Rather than having the developer do it manually, wouldn't it be nice if that's what Jenkins did for you. In other words, jenkins parses the developer provided jenkinsfile, and manufactures script-with-load and the loaded-scripts that it then works off of. This would then be a true solution. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.174127.1473169024000.7910.1571145605481%40Atlassian.JIRA.
[JIRA] (JENKINS-37984) org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script
Title: Message Title Jeffrey Bennett commented on JENKINS-37984 Re: org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script There is a work around, of sorts. There is a fixed limit to the size of the groovy. No way around that limit, but you can do things to minimize what's in groovy. Eliminate clutter. For us, that was stuff like echo statements, and unused variables. You might also be able to alter the jenkins job's configuration rather than setting options in the groovy. A better answer is to shift large blocks to scripts. For example, if you have a bunch of "sh" or "bat" commands in a row, put them in a script file, then invoke the script from groovy. Good luck. This limit should still be fixed (or raised). You just cannot get to enterprise worthy pipelines with 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.174127.1473169024000.11065.1561674001276%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56445) Pipeline stages not showing up correctly
Title: Message Title Jeffrey Bennett updated an issue Jenkins / JENKINS-56445 Pipeline stages not showing up correctly Change By: Jeffrey Bennett A pipeline that has multiple stages, with parallel stages inside each stage is not rendering correctly. It appears to truncate after the first stage (showing stage#1 parallel stages), but stage #2-N do not appear (Capture2.jpg). They run - as evidenced by the log (not included) - and show in other places (e.g. Stages View, Capture1.jpg), but just do not show up in the pipeline. Other than the nodes not showing up, I see nothing else wrong. I have checked the Jenkins.log for issues (nothing obviously present). I have checked the console in Chrome (nothing present). I have tried both Microsoft Edge and Chrome - both display the same. I have checked another pipeline job (completely different project), and it also truncates display. I have cloned this job to a new job, and the clone also truncates. 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-56445) Pipeline stages not showing up correctly
Title: Message Title Jeffrey Bennett updated an issue Jenkins / JENKINS-56445 Pipeline stages not showing up correctly Change By: Jeffrey Bennett A pipeline that has multiple stages, with parallel stages inside each stage is not rendering correctly. It appears to truncate after the first stage (showing stage#1 parallel stages), but stage #2-N do not appear (Capture2 . jpg). They run - as evidenced by the log (not included) - and show in other places (e.g. Stages View , Capture1.jpg ), but just do not show up in the pipeline. Other than the nodes not showing up, I see nothing else wrong. I have checked the Jenkins.log for issues (nothing obviously present). I have checked the console in Chrome (nothing present). I have tried both Microsoft Edge and Chrome - both display the same. 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-56445) Pipeline stages not showing up correctly
Title: Message Title Jeffrey Bennett updated an issue Jenkins / JENKINS-56445 Pipeline stages not showing up correctly Change By: Jeffrey Bennett Attachment: Capture2.JPG Attachment: Capture1.JPG 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-56445) Pipeline stages not showing up correctly
Title: Message Title Jeffrey Bennett created an issue Jenkins / JENKINS-56445 Pipeline stages not showing up correctly Issue Type: Bug Assignee: Unassigned Attachments: Jenkinsfile Components: pipeline Created: 2019-03-06 16:20 Environment: Jenkins 2.150.3 Priority: Minor Reporter: Jeffrey Bennett A pipeline that has multiple stages, with parallel stages inside each stage is not rendering correctly. It appears to truncate after the first stage (showing stage#1 parallel stages), but stage #2-N do not appear. They run - as evidenced by the log - and show in other places (e.g. Stages View), but just do not show up in the pipeline. Add Comment
[JIRA] (JENKINS-56445) Pipeline stages not showing up correctly
Title: Message Title Jeffrey Bennett updated an issue Jenkins / JENKINS-56445 Pipeline stages not showing up correctly Change By: Jeffrey Bennett Attachment: Jenkinsfile Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56380) Last Changes plugin looking for .git in wrong location
Title: Message Title Jeffrey Bennett updated an issue Jenkins / JENKINS-56380 Last Changes plugin looking for .git in wrong location Change By: Jeffrey Bennett Attachment: 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56380) Last Changes plugin looking for .git in wrong location
Title: Message Title Jeffrey Bennett updated an issue Jenkins / JENKINS-56380 Last Changes plugin looking for .git in wrong location Change By: Jeffrey Bennett Attachment: Jenkinsfile Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56380) Last Changes plugin looking for .git in wrong location
Title: Message Title Jeffrey Bennett created an issue Jenkins / JENKINS-56380 Last Changes plugin looking for .git in wrong location Issue Type: Bug Assignee: Rafael Pestano Components: last-changes-plugin Created: 2019-03-04 05:19 Environment: Jenkins 2.150.3 Last Changes Plugin 2.6.8 Priority: Major Reporter: Jeffrey Bennett Receiving error: 00:00:04.421 Publishing build last changes... 00:00:04.422 ERROR: Last Changes NOT published due to the following error: Could not find previous head of repository located at /var/lib/jenkins/jobs/omni-pipeline/branches/release-3-8.d1f6no/builds/28/.git. Its your first commit? The lastChangesPlugin appears to be looking for ".git" in jobs/.../branches/.../builds rather than in workspace. This was with vcsDir: ''. I've additionally tried providing it hints via a more explicit vcsDir, but it still seems to go looking in jobs directory. Add Comment
[JIRA] (JENKINS-56336) In 'Changes' view, for git, show the file differences
Title: Message Title Jeffrey Bennett created an issue Jenkins / JENKINS-56336 In 'Changes' view, for git, show the file differences Issue Type: Improvement Assignee: Rafael Pestano Components: core, last-changes-plugin Created: 2019-02-28 21:27 Environment: Jenkins 2.150.3 Priority: Minor Reporter: Jeffrey Bennett The changes view would be far more useful if it yielded a way to see the actual changes within the files. Currently, for git, it lists the commit ID, and the files in the commit. It would be nice if it either: did a gitdiff to see within the affected files, or provided a way to specify a URL (e.g. of the git-repo, of fisheye, etc) so that you could navigate from changes to something capable of exploring the change in more detail. There are plugins, e.g. Last Changes, that do this but are additional effort to install and configure, and their output is not part of the standard 'Changes' view.
[JIRA] (JENKINS-56304) jiraAddComment terminates the step prematurely
Title: Message Title Jeffrey Bennett updated JENKINS-56304 work-around found. Invocation of step from method is illegal. Jenkins / JENKINS-56304 jiraAddComment terminates the step prematurely Change By: Jeffrey Bennett 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56304) jiraAddComment terminates the step prematurely
Title: Message Title Jeffrey Bennett updated JENKINS-56304 Jenkins / JENKINS-56304 jiraAddComment terminates the step prematurely Change By: Jeffrey Bennett Status: Open Fixed but Unreleased 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56304) jiraAddComment terminates the step prematurely
Title: Message Title Jeffrey Bennett commented on JENKINS-56304 Re: jiraAddComment terminates the step prematurely OK resolved it - many thanks. Indeed, you have to build an array of Jiras to update in a method, then do the updating back in the stage (inside a script marker). I added my final code to output-final.txt in the hopes maybe it will benefit the next person. Naresh Rayapati Thank you for the help! Issue can be 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56304) jiraAddComment terminates the step prematurely
Title: Message Title Jeffrey Bennett updated an issue Jenkins / JENKINS-56304 jiraAddComment terminates the step prematurely Change By: Jeffrey Bennett Attachment: output-final.txt Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56304) jiraAddComment terminates the step prematurely
Title: Message Title Jeffrey Bennett commented on JENKINS-56304 Re: jiraAddComment terminates the step prematurely I'm inferring that if I use the @NonCPS method to build an array of Jiras to update (ID + Comment), pass the array back to the stage, iterate and call jiraAddComment for each element in the array (from the stage), it would work. I think? My groovy skills are weak. Built an array in the method, but cannot figure out how to get it back to the stage 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-56304) jiraAddComment terminates the step prematurely
Title: Message Title Jeffrey Bennett commented on JENKINS-56304 Re: jiraAddComment terminates the step prematurely Experiment #4: calling jiraAddComment twice directly from steps(), i.e. no method call, definitely works. Just verified that 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-56304) jiraAddComment terminates the step prematurely
Title: Message Title Jeffrey Bennett commented on JENKINS-56304 Re: jiraAddComment terminates the step prematurely Experiment #3: Complete replacement of the method with a trivial invocation that invokes jiraAddComment twice - Failure (in same manner as original issue) See output-truncatedCall.txt. The stage succeeds (green and not red). However, logs indicate that we only invoked the first jiraAddComment and no further steps were performed (like the original bug). Inspection in Jira confirms that only the FIRST jiraAddComment was received. 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-56304) jiraAddComment terminates the step prematurely
Title: Message Title Jeffrey Bennett updated an issue Jenkins / JENKINS-56304 jiraAddComment terminates the step prematurely Change By: Jeffrey Bennett Attachment: output-truncatedCall.txt Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56304) jiraAddComment terminates the step prematurely
Title: Message Title Jeffrey Bennett commented on JENKINS-56304 Re: jiraAddComment terminates the step prematurely Experiment #2: (restored @NonCPS) replace invocation of jiraAddComment with echo instead - qualified success The Stage succeeds. The log messages indicate it goes through the expected pathways - looping and recursing as expected. Message payload looks correct. No errors. Obviously, we are NOT sending anything to Jira with this approach, but it verifies syntax. See output-stubCall.txt for details This seems to firmly point the finger at the call to jiraAddComment as the culprit 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-56304) jiraAddComment terminates the step prematurely
Title: Message Title Jeffrey Bennett updated an issue Jenkins / JENKINS-56304 jiraAddComment terminates the step prematurely Change By: Jeffrey Bennett Attachment: output-stubCall.txt Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56304) jiraAddComment terminates the step prematurely
Title: Message Title Jeffrey Bennett commented on JENKINS-56304 Re: jiraAddComment terminates the step prematurely Experiment #1: Remove @NonCPS - Failed The stage now fails (red instead of green stage). The log messages indicate it went into jiraAddComment and then hit a "Failed in branch Update Jira". There is a stack-trace later in the log that indicates "java.io.NotSerializableException: hudson.plugins.git.GitChangeSetList" 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-56304) jiraAddComment terminates the step prematurely
Title: Message Title Jeffrey Bennett updated an issue Jenkins / JENKINS-56304 jiraAddComment terminates the step prematurely Change By: Jeffrey Bennett At the end of my pipeline, I am iterating the changeSets and the commits therein looking for strings that match Jira tickets, in order to update all Jira's with code present in a build. In theory, this could result in multiple Jiras needing to be updated, so this is done in a loop, potentially making multiple calls to jiraAddComment(..). However, the entire step stops (seems to return success) once the first jiraAddComment is completed. See attached source and output. Following call to jiraAddComment(..), the subsequent echo should fire indicating that execution flow has continued. The first jiraAddComment appears in the log (and the comment appears in Jira). However, no subsequent echos in the log. No subsequent call to jiraAddComment in the log, and no subsequent comments in Jira. It is as-if execution stops at the first call to jiraAddComment 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-56304) jiraAddComment terminates the step prematurely
Title: Message Title Jeffrey Bennett updated an issue Jenkins / JENKINS-56304 jiraAddComment terminates the step prematurely Change By: Jeffrey Bennett Attachment: output.txt Attachment: source.txt Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56304) jiraAddComment terminates the step prematurely
Title: Message Title Jeffrey Bennett created an issue Jenkins / JENKINS-56304 jiraAddComment terminates the step prematurely Issue Type: Bug Assignee: Naresh Rayapati Components: jira-steps-plugin Created: 2019-02-27 05:37 Environment: jenkins 2.150.3 Jira Pipeline Steps 1.4.4 Priority: Critical Reporter: Jeffrey Bennett At the end of my pipeline, I am iterating the changeSets and the commits therein looking for strings that match Jira tickets, in order to update all Jira's with code present in a build. In theory, this could result in multiple Jiras needing to be updated, so this is done in a loop, potentially making multiple calls to jiraAddComment(..). However, the entire step stops (seems to return success) once the first jiraAddComment is completed. Add Comment
[JIRA] (JENKINS-51025) whitesource-plugin affected by JEP-200
Title: Message Title Jeffrey Bennett updated an issue Jenkins / JENKINS-51025 whitesource-plugin affected by JEP-200 Change By: Jeffrey Bennett Environment: whitesource-plugin 18.2 with Jenkins 2.107.2 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-51025) whitesource-plugin affected by JEP-200
Title: Message Title Jeffrey Bennett closed an issue as Fixed Jenkins / JENKINS-51025 whitesource-plugin affected by JEP-200 Change By: Jeffrey Bennett Status: Open Closed Resolution: Fixed 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-51025) whitesource-plugin affected by JEP-200
Title: Message Title Jeffrey Bennett updated an issue Jenkins / JENKINS-51025 whitesource-plugin affected by JEP-200 Change By: Jeffrey Bennett whitesource-plugin 18.2 is a post-build action. stack: ERROR: Asynchronous execution failurejava.util.concurrent.ExecutionException: java.lang.Error: Failed to deserialize the Callable object. at hudson.remoting.Channel$2.adapt(Channel.java:988) at hudson.remoting.Channel$2.adapt(Channel.java:983) at hudson.remoting.FutureAdapter.get(FutureAdapter.java:55) at hudson.maven.AbstractMavenBuilder.waitForAsynchronousExecutions(AbstractMavenBuilder.java:186) at hudson.maven.Maven3Builder.call(Maven3Builder.java:146) at hudson.maven.Maven3Builder.call(Maven3Builder.java:70) at hudson.remoting.UserRequest.perform(UserRequest.java:210) at hudson.remoting.UserRequest.perform(UserRequest.java:53) at hudson.remoting.Request$2.run(Request.java:364) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748)Caused by: java.lang.Error: Failed to deserialize the Callable object. at hudson.remoting.UserRequest.perform(UserRequest.java:194) at hudson.remoting.UserRequest.perform(UserRequest.java:53) at hudson.remoting.Request$2.run(Request.java:364) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at org.jenkinsci.remoting.CallableDecorator.call(CallableDecorator.java:19) at hudson.remoting.CallableDecoratorList$1.call(CallableDecoratorList.java:21) at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46) ... 4 more Suppressed: hudson.remoting.Channel$CallSiteStackTrace: Remote call to channel at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1737) at hudson.remoting.UserResponse.retrieve(UserRequest.java:313) at hudson.remoting.Channel$2.adapt(Channel.java:986) at hudson.remoting.Channel$2.adapt(Channel.java:983) at hudson.remoting.FutureAdapter.get(FutureAdapter.java:55) at hudson.maven.AbstractMavenBuilder.waitForAsynchronousExecutions(AbstractMavenBuilder.java:186) at hudson.maven.Maven3Builder.call(Maven3Builder.java:146) at hudson.maven.Maven3Builder.call(Maven3Builder.java:70) at hudson.remoting.UserRequest.perform(UserRequest.java:210) at hudson.remoting.UserRequest.perform(UserRequest.java:53) at hudson.remoting.Request$2.run(Request.java:364) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) ... 4 moreCaused by: java.lang.SecurityException: Rejected: org.whitesource.agent.api.model.DependencyInfo; see [https://jenkins.io/redirect/class-filter/] at hudson.remoting.ClassFilter.check(ClassFilter.java:76) at hudson.remoting.MultiClassLoaderSerializer$Input.resolveClass(MultiClassLoaderSerializer.java:129) at
[JIRA] (JENKINS-51025) whitesource-plugin affected by JEP-200
Title: Message Title Jeffrey Bennett commented on JENKINS-51025 Re: whitesource-plugin affected by JEP-200 Upgrading plugin to 18.3.2. appears to solve the issue. 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-51025) whitesource-plugin affected by JEP-200
Title: Message Title Jeffrey Bennett updated an issue Jenkins / JENKINS-51025 whitesource-plugin affected by JEP-200 Change By: Jeffrey Bennett Labels: JEP-200 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-51025) whitesource-plugin affected by JEP-200
Title: Message Title Jeffrey Bennett created an issue Jenkins / JENKINS-51025 whitesource-plugin affected by JEP-200 Issue Type: Bug Assignee: Unassigned Components: whitesource-plugin Created: 2018-04-26 15:59 Priority: Major Reporter: Jeffrey Bennett whitesource-plugin is a post-build action. stack: ERROR: Asynchronous execution failure java.util.concurrent.ExecutionException: java.lang.Error: Failed to deserialize the Callable object. at hudson.remoting.Channel$2.adapt(Channel.java:988) at hudson.remoting.Channel$2.adapt(Channel.java:983) at hudson.remoting.FutureAdapter.get(FutureAdapter.java:55) at hudson.maven.AbstractMavenBuilder.waitForAsynchronousExecutions(AbstractMavenBuilder.java:186) at hudson.maven.Maven3Builder.call(Maven3Builder.java:146) at hudson.maven.Maven3Builder.call(Maven3Builder.java:70) at hudson.remoting.UserRequest.perform(UserRequest.java:210) at hudson.remoting.UserRequest.perform(UserRequest.java:53) at hudson.remoting.Request$2.run(Request.java:364) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) Caused by: java.lang.Error: Failed to deserialize the Callable object. at hudson.remoting.UserRequest.perform(UserRequest.java:194) at hudson.remoting.UserRequest.perform(UserRequest.java:53) at hudson.remoting.Request$2.run(Request.java:364) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at org.jenkinsci.remoting.CallableDecorator.call(CallableDecorator.java:19) at hudson.remoting.CallableDecoratorList$1.call(CallableDecoratorList.java:21) at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46) ... 4 more Suppressed:
