|
||||||||
|
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.
console log messages (interesting that analysis collector is before DRY, etc. I had it 1st in list since I wanted its graph to be top of Job splash page.
00:02:18.992 [ANALYSIS-COLLECTOR] Computing warning deltas based on reference build #737
00:02:18.992 [DRY] Collecting duplicate code analysis files...
00:02:18.995 [DRY] Finding all files that match the pattern bin/cpd.xml
00:02:18.995 [DRY] Parsing 1 files in /var/lib/jenkins/workspace/zzz
00:02:18.995 [DRY] Successfully parsed file /var/lib/jenkins/workspace/zzz/bin/cpd.xml of module with 15 warnings.
00:02:19.005 [DRY] Computing warning deltas based on reference build #737
00:02:19.007 [WARNINGS] Parsing warnings in console log with parser GNU C Compiler 4 (gcc)
00:02:19.021 [WARNINGS] Computing warning deltas based on reference build #737
00:02:19.021 [WARNINGS] Plug-in Result: Success - no threshold has been exceeded
00:02:19.235 [TASKS] Scanning folder '/var/lib/jenkins/workspace/zzz' for files matching the pattern '*/.cpp, */.h' - excludes:
00:02:19.235 [TASKS] Found 486 files to scan for tasks
00:02:19.235 [TASKS] Found 138 open tasks.
00:02:19.265 [TASKS] Computing warning deltas based on reference build #737
not latest, our tool governance model typically imposes a one-two quarter lag, but reasonably current (this year anyway)
Jenkins ver. 1.581
Static Analysis Collector Plug-in 1.41
I changed the publisher order to be
1. DRY
2. WARNINGS
3. TASKS
4. ANALYSIS-COLLECTOR
and AH-HA! now I'm seeing something more reasonable in the graph.
It looks like
1. there is an (unobvious) dependency between the plugins, and
2. order of graphs on the splash page can't be adjusted independently?
As a minimum I'd recommend putting text on the base (not advanced) SA-Collector plugin configurator to say it needs to be below any of the plugins you want it to be summarizing. And the wiki should explain it more?....
I don't know if core has any kind of dependency model for plugins to allow automatic reordering of execution? and allowing user to order the display (graphs) in some desired summary/details or priority high/low order in the job config, suspecting not?......