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

Add support for configuration-as-code

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      Please add support for configuration-as-code for this plugin so we can use it in a fully automated installation of our Jenkins instance.

      Guide for plugin developers:
      https://github.com/jenkinsci/configuration-as-code-plugin/blob/master/docs/PLUGINS.md

        Attachments

          Activity

          Hide
          sspringett Steve Springett added a comment -

          Actually, it should decrease duplication. Use one or more property files and specify them with -p as defined in https://jeremylong.github.io/DependencyCheck/dependency-check-cli/arguments.html The property file will have all the NIST, proxy, and analyzer settings. Use multiple property files for different types of jobs if necessary.

          Show
          sspringett Steve Springett added a comment - Actually, it should decrease duplication. Use one or more property files and specify them with -p as defined in  https://jeremylong.github.io/DependencyCheck/dependency-check-cli/arguments.html  The property file will have all the NIST, proxy, and analyzer settings. Use multiple property files for different types of jobs if necessary.
          Hide
          jansohn Robin Jansohn added a comment -

          I have to disagree. Needing to specify a property file for every dependency check call still leads to duplicate configuration settings (besides the additional nuisance of having to manage another separate property file).

          Please don't remove the global configuration options (at least not for the global data directory and NIST mirror settings). It should still be possible to set global defaults which may be overwritten on the job-level if necessary.

          Show
          jansohn Robin Jansohn added a comment - I have to disagree. Needing to specify a property file for every dependency check call still leads to duplicate configuration settings (besides the additional nuisance of having to manage another separate property file). Please don't remove the global configuration options (at least not for the global data directory and NIST mirror settings). It should still be possible to set global defaults which may be overwritten on the job-level if necessary.
          Hide
          malhelo Bernd O added a comment - - edited

          I'm currently working on integrating CasC support for the global configration in the plugin in this forked branch:
          https://github.com/malheleco/dependency-track-plugin/tree/casc
          I will test my implementation on my Jenkins instance and given that it works would open a PR to get it into the official master.

          Steve Springett is your "offer" that "PRs are welcome" still standing?

          Show
          malhelo Bernd O added a comment - - edited I'm currently working on integrating CasC support for the global configration in the plugin in this forked branch: https://github.com/malheleco/dependency-track-plugin/tree/casc I will test my implementation on my Jenkins instance and given that it works would open a PR to get it into the official master. Steve Springett is your "offer" that "PRs are welcome" still standing?
          Hide
          sspringett Steve Springett added a comment -

          Of course. I typically do not have a lot of time to maintain this plugin, so yes, PRs are helpful to improve the plugins overall quality and capability.

          Show
          sspringett Steve Springett added a comment - Of course. I typically do not have a lot of time to maintain this plugin, so yes, PRs are helpful to improve the plugins overall quality and capability.
          Hide
          malhelo Bernd O added a comment - - edited

          I just noticed I was in the wrong issue all along... this one is for DependencyCheck, not DependencyTrack... I acutally worked on JENKINS-57640

          Show
          malhelo Bernd O added a comment - - edited I just noticed I was in the wrong issue all along... this one is for DependencyCheck, not DependencyTrack... I acutally worked on JENKINS-57640

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            jansohn Robin Jansohn
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Dates

              Created:
              Updated: