Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-14185

Provide global configuration of settings

XMLWordPrintable

    • Icon: New Feature New Feature
    • Resolution: Won't Fix
    • Icon: Minor Minor
    • analysis-core-plugin
    • 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.

          [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 made changes -
          Link New: This issue is related to JENKINS-4555 [ JENKINS-4555 ]
          Ulli Hafner made changes -
          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
          Ulli Hafner made changes -
          Link New: This issue is related to JENKINS-9602 [ JENKINS-9602 ]
          Ulli Hafner made changes -
          Link New: This issue is related to JENKINS-7443 [ JENKINS-7443 ]
          Ulli Hafner made changes -
          Link New: This issue is blocking JENKINS-14840 [ JENKINS-14840 ]
          Ulli Hafner made changes -
          Description Original: 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.
          		 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.

          This feature makes not only sense for graphs but also for all other aspects of the plug-ins.
          Summary Original: Provide global configuration for trend graphs New: Provide global configuration of settings
          Ulli Hafner made changes -
          Link New: This issue is related to JENKINS-15246 [ JENKINS-15246 ]
          Ulli Hafner made changes -
          Link New: This issue is duplicated by JENKINS-17100 [ JENKINS-17100 ]
          Ulli Hafner made changes -
          Link New: This issue is related to JENKINS-3157 [ JENKINS-3157 ]

            drulli Ulli Hafner
            jacob_robertson Jacob Robertson
            Votes:
            3 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              Resolved: