Ulli Hafner added a comment - 2017-10-26 21:01 - edited I think this is already considered in the requirements document , can you please check if that will work for you?

Aaron D. Marasco added a comment - 2017-10-27 10:55 drulli I had not seen that document. I'm not sure I follow it all, sorry, but I do see under publishIssues "Merges all issues of the provided parsers into a single result." This seems to take the issue generator plugin as an option. I'm thinking a little beyond that and maybe a way to tag/label them as they go in (at scanForIssues step) that you can then only collect the subset with publishIssues. // This is not valid but to give you the idea stage( "Build" ) { parsteps[ 'Build CentOS6' ] = { node( 'docker && C6' ) {      do_build( 'C6' ) scanForIssues ..., tag: "C6_GCC" } } parsteps[ 'Build CentOS7' ] = { node( 'docker && C7' ) {      do_build( 'C7' ) scanForIssues ..., tag: "C7_CLANG" } } parallel parsteps } stage( "Publish" ) { publishIssues ..., tag: "C6_GCC" , displayName: "CentOS 6 Compiler Warnings" publishIssues ..., tag: "C7_CLANG" , displayName: "CentOS 7 Compiler Warnings" }

Ulli Hafner added a comment - 2017-10-27 11:06 Actually the scanForIssues step returns a result (the warnings), i.e. your code will look like: do_build('C6') def c6Gcc = scanForIssues ... I'm not sure if the variable is then visible in the Publish stage scope. If not you need to write: do_build('C6') def c6Gcc = scanForIssues ... publishIssues ..., issues:c6Gcc, id="c6gcc" name: "CentOS 6 Compiler Warnings"

Aaron D. Marasco added a comment - 2017-10-27 11:16 Yeah, the variable scope stuff is still confusing to me, I think @Field fixes most of it... But anyway, yeah, what you have there with an id/name is what I'm looking for.