-
New Feature
-
Resolution: Won't Fix
-
Minor
-
None
My actual requirements are pretty simple:
- All jobs on Continuous Integration can be easily configured to use the same trending settings
- All jobs on Public Dashboard can be easily configured to use the same trending settings (we use the build-publisher plugin to push some of our jobs from CI to the dashboard)
- Make this possible for PMD and my own custom (AppScan) subclass of the hudson.plugins.analysis.core.PluginDescriptor (these are the only two analysis-core plugins we use at this time)
- Possible (lower priority) requirement - in some cases we may want to have custom settings for some jobs
Your suggestion to have a global configuration would be perfect for what I really need at this time. If the "*.txt" file doesn't exist, it could fall back on the global configuration. Because I have created my own PluginDescriptor, it would be nice if the global configuration could apply across all extensions, or else make it very easy for me to hook into that global config.
This feature makes not only sense for graphs but also for all other aspects of the plug-ins.
- is blocking
-
JENKINS-22874 Ability to configure thresholds for each Warnings parser used
-
- Resolved
-
- is duplicated by
-
-
- Resolved
-
- is related to
-
JENKINS-4555 Source links from the FindBugs report do not get published
-
- Open
-
-
-
- Open
-
-
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
[JENKINS-14185] Provide global configuration of settings
Jacob Robertson
created issue -
Jacob Robertson
made changes -
| Component/s | Original: warnings [ 15513 ] | |
| Description |
Original:
I get the following error when trying to view the source of a compiler warning: {noformat} 01 Copying the source file 'main.c' from the workspace to the build folder '/var/lib/jenkins/home/jobs/Job Clean Build/builds/2011-08-05_00-04-13/workspace-files/bf88816e.tmp' on the Hudson master failed. 02 Seems that the path is relative, however an absolute path is required when copying the sources. 03 Is the file 'main.c' contained more than once in your workspace? 04 Is the file 'main.c' a valid filename? 05 If you are building on a slave: please check if the file is accessible under '$HUDSON_HOME/[job-name]/main.c' 06 If you are building on the master: please check if the file is accessible under '$HUDSON_HOME/[job-name]/workspace/main.c' 07 hudson.util.IOException2: remote file operation failed: main.c at hudson.remoting.LocalChannel@1eac6995 08 at hudson.FilePath.act(FilePath.java:754) 09 at hudson.FilePath.act(FilePath.java:740) 10 at hudson.FilePath.copyTo(FilePath.java:1410) 11 at hudson.plugins.analysis.core.HealthAwarePublisher.copyFilesWithAnnotationsToBuildFolder(HealthAwarePublisher.java:354) 12 at hudson.plugins.analysis.core.HealthAwarePublisher.perform(HealthAwarePublisher.java:316) 13 at hudson.tasks.BuildStepMonitor$2.perform(BuildStepMonitor.java:27) 14 at hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:682) 15 at hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:657) 16 at hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:635) 17 at hudson.model.Build$RunnerImpl.post2(Build.java:161) 18 at hudson.model.AbstractBuild$AbstractRunner.post(AbstractBuild.java:604) 19 at hudson.model.Run.run(Run.java:1400) 20 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) 21 at hudson.model.ResourceController.execute(ResourceController.java:88) 22 at hudson.model.Executor.run(Executor.java:175) 23 Caused by: java.io.FileNotFoundException: main.c (No such file or directory) 24 at java.io.FileInputStream.open(Native Method) 25 at java.io.FileInputStream.<init>(FileInputStream.java:120) 26 at hudson.FilePath$30.invoke(FilePath.java:1414) 27 at hudson.FilePath$30.invoke(FilePath.java:1410) 28 at hudson.FilePath$FileCallableWrapper.call(FilePath.java:1980) 29 at hudson.remoting.LocalChannel.call(LocalChannel.java:45) 30 at hudson.FilePath.act(FilePath.java:747) 31 ... 14 more {noformat} This job uses a custom workspace dir so maybe the plugin doesn't support that? |
New: I would like to configure a template job with the correct pmd preferences for the trend graph, and then create new jobs by copying that job. However, the "pmd.txt" file is not getting copied over. |
| Environment | Original: Jenkins 1.423, Warnings plugin 3.20 | |
| Issue Type | Original: Improvement [ 4 ] | New: Bug [ 1 ] |
| Summary | Original: Using "New Job > Copy existing job" does not copy "configureDefaults" files such as pmd.txt | New: Using "New Job > Copy existing job" does not copy the trending "/configureDefaults" files such as pmd.txt |
Jacob Robertson
added a comment - I notice this other issue which is related, because the pmd.txt is not being published when I publish these jobs to our public dashboard, which we also want to have configured correctly with the right trending settings.
https://issues.jenkins-ci.org/browse/JENKINS-4555
More generally - why do these plugins persist their settings to a text file instead of config.xml? If this behavior was changed it would fix these behaviors completely, because then these settings would be part of the object model instead of being "special". I have the same problem for an in-house extension to analysis-core that we use. It creates a ".txt" file that we want copied and published, but it doesn't do that.
Jacob Robertson
added a comment - I notice this other issue which is related, because the pmd.txt is not being published when I publish these jobs to our public dashboard, which we also want to have configured correctly with the right trending settings.
https://issues.jenkins-ci.org/browse/JENKINS-4555
More generally - why do these plugins persist their settings to a text file instead of config.xml? If this behavior was changed it would fix these behaviors completely, because then these settings would be part of the object model instead of being "special". I have the same problem for an in-house extension to analysis-core that we use. It creates a ".txt" file that we want copied and published, but it doesn't do that. Jacob Robertson
made changes -
| Link | New: This issue is related to JENKINS-4555 [ JENKINS-4555 ] |
Well, the reason is that I can't access the global config.xml file when I'm not in the job configuration transaction. Since the graphs are configured in a separate view, I need to persist them manually.
What is your actual requirement? Would it help if we have a global (system wide) configuration of the graphs?
Jacob Robertson
added a comment - My actual requirements are pretty simple
- All jobs on Continuous Integration can be easily configured to use the same trending settings
- All jobs on Public Dashboard can be easily configured to use the same trending settings (we use the build-publisher plugin to push some of our jobs from CI to the dashboard)
- Make this possible for PMD and my own custom (AppScan) subclass of the hudson.plugins.analysis.core.PluginDescriptor (these are the only two analysis-core plugins we use at this time)
- Possible (lower priority) requirement - in some cases we may want to have custom settings for some jobs
Your suggestion to have a global configuration would be perfect for what I really need at this time. If the "*.txt" file doesn't exist, it could fall back on the global configuration. Because I have created my own PluginDescriptor, it would be nice if the global configuration could apply across all extensions, or else make it very easy for me to hook into that global config.
Jacob Robertson
added a comment - My actual requirements are pretty simple
All jobs on Continuous Integration can be easily configured to use the same trending settings
All jobs on Public Dashboard can be easily configured to use the same trending settings (we use the build-publisher plugin to push some of our jobs from CI to the dashboard)
Make this possible for PMD and my own custom (AppScan) subclass of the hudson.plugins.analysis.core.PluginDescriptor (these are the only two analysis-core plugins we use at this time)
Possible (lower priority) requirement - in some cases we may want to have custom settings for some jobs
Your suggestion to have a global configuration would be perfect for what I really need at this time. If the "*.txt" file doesn't exist, it could fall back on the global configuration. Because I have created my own PluginDescriptor, it would be nice if the global configuration could apply across all extensions, or else make it very easy for me to hook into that global config. | Description | Original: I would like to configure a template job with the correct pmd preferences for the trend graph, and then create new jobs by copying that job. However, the "pmd.txt" file is not getting copied over. |
New:
My actual requirements are pretty simple: * All jobs on Continuous Integration can be easily configured to use the same trending settings * All jobs on Public Dashboard can be easily configured to use the same trending settings (we use the build-publisher plugin to push some of our jobs from CI to the dashboard) * Make this possible for PMD and my own custom (AppScan) subclass of the hudson.plugins.analysis.core.PluginDescriptor (these are the only two analysis-core plugins we use at this time) * Possible (lower priority) requirement - in some cases we may want to have custom settings for some jobs Your suggestion to have a global configuration would be perfect for what I really need at this time. If the "*.txt" file doesn't exist, it could fall back on the global configuration. Because I have created my own PluginDescriptor, it would be nice if the global configuration could apply across all extensions, or else make it very easy for me to hook into that global config. |
| Issue Type | Original: Bug [ 1 ] | New: New Feature [ 2 ] |
| Summary | Original: Using "New Job > Copy existing job" does not copy the trending "/configureDefaults" files such as pmd.txt | New: Provide global configuration for trend graphs |
| Link |
New:
This issue is related to |
| Link |
New:
This issue is related to |
Hmm, I don't think that there is an extension point available for that action which I can overwrite...