Hmm, seems that the workflow plug-in does not handle the console in the same way as for standard jobs. I’m not sure if this is a bug in the workflow plug-in or in the workflow implementation of the warnings-plug-in.
You can try to pipe the compiler output to a file and then parse the file. > Am 22.12.2015 um 18:27 schrieb Craig Rodrigues <rodr...@freebsd.org>: > > Hi, > > Without workflow it works. > I copied and pasted the logs from my screen into two different files, > because they were on two different screens. > > -- > Craig > > > On Tue, Dec 22, 2015 at 9:20 AM, Ullrich Hafner <ullrich.haf...@gmail.com > <mailto:ullrich.haf...@gmail.com>> wrote: > The warnings should be parsed correctly by the parser. Maybe the input is not > yet accessible when the warnings plugin runs. > > Why is your log (or output) in two different files? (consoleText.txt and no > warnings.txt))? > > Did you try the same without workflow? > > > Am 22.12.2015 um 15:21 schrieb Craig Rodrigues <rodr...@freebsd.org>: > > > > Hi, > > > > I installed: > > workflow-plugin 1.12 > > warnings plugin 4.51 > > jenkins 1.641 > > > > I used the workflow snipper generator to generate code to > > invoke the warnings plugin. > > > > I came up with the following example: > > > > node { > > writeFile(file: "a.c", text: ''' > > #include <sys/types.h> > > #include <stdlib.h> > > > > void > > func1(void) > > { > > } > > > > int > > main(int argc, char *argv[]) > > { > > char *a; > > int64_t *b; > > b = (int64_t *)a; > > printf("Hi"); > > printf(NULL); > > printf("%s %d\\n", "35"); > > func1(); > > } > > ''' > > ) > > sh "cc -Wall -W -Wcast-align -o output a.c" > > > > step([$class: 'WarningsPublisher', > > canComputeNew: false, > > canResolveRelativePaths: false, > > consoleParsers: [[parserName: 'Clang (LLVM based)']], > > defaultEncoding: '', > > excludePattern: '', > > healthy: '', > > includePattern: '', > > messagesPattern: '', > > unHealthy: '']) > > } > > > > This code example triggers warnings with the clang compiler, > > which I can see in the log, but the warnings plugin is reporting 0 warnings. > > > > Any ideas how I can fix this? > > Thanks. > > -- > > Craig > > <consoleText.txt><nowarnings.txt> > > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/2BAAE904-1DEA-42DA-8D89-192AA2B20FD7%40gmail.com. For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: Message signed with OpenPGP using GPGMail
