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

Support Configuration as Code

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      This plugin should support setting properties via JCasC, i.e. Configuration-as-Code plugin.

        Attachments

          Issue Links

            Activity

            Hide
            mcortinas Marc Cortinas added a comment -

            +1 

            Show
            mcortinas Marc Cortinas added a comment - +1 
            Hide
            rico3452 Rico Chen added a comment -

            +10

            Show
            rico3452 Rico Chen added a comment - +10
            Hide
            basil Basil Crow added a comment -

            jenkinsci/authorize-project-plugin#44 looks correct from a code walk-through. As far as I can tell, there are three things that need to happen for this issue to be resolved:

            • Automated tests added for the migration of the old data structure to the new, using @LocalData
            • Rebase of the PR against the latest HEAD and manual testing of the resulting incremental build (preferably by multiple users)
            • A maintainer who is willing to merge the PR and release the plugin

            Of these, the most significant issue is the lack of a maintainer. Would any of the 29 people watching this issue be willing to adopt this plugin as a maintainer? The first order of business for this new maintainer would be to add the @LocalData tests described above, link to an incremental build for testing in the comments here, merge the PR, and release a new version. I can offer mentorship and guidance for anyone who is interested in doing this, but due to time constraints I cannot commit to maintaining this plugin myself.

            Show
            basil Basil Crow added a comment - jenkinsci/authorize-project-plugin#44 looks correct from a code walk-through. As far as I can tell, there are three things that need to happen for this issue to be resolved: Automated tests added for the migration of the old data structure to the new, using @LocalData Rebase of the PR against the latest HEAD and manual testing of the resulting incremental build (preferably by multiple users) A maintainer who is willing to merge the PR and release the plugin Of these, the most significant issue is the lack of a maintainer. Would any of the 29 people watching this issue be willing to adopt this plugin as a maintainer? The first order of business for this new maintainer would be to add the @LocalData tests described above, link to an incremental build for testing in the comments here, merge the PR, and release a new version. I can offer mentorship and guidance for anyone who is interested in doing this, but due to time constraints I cannot commit to maintaining this plugin myself.
            Hide
            cpottiers Cyril Pottiers added a comment -

            Hi, any news regards this issue ?
            It's very boring as at each restart of our Jenkins instance, we need to manually change the configuration in order to add project strategyEnabledMap 

            Show
            cpottiers Cyril Pottiers added a comment - Hi, any news regards this issue ? It's very boring as at each restart of our Jenkins instance, we need to manually change the configuration in order to add project strategyEnabledMap 
            Hide
            basil Basil Crow added a comment -

            Hi Cyril Pottiers, there is a PR open at jenkinsci/authorize-project-plugin#44, but it needs rebasing and test coverage. As far as I can tell, there is no active development being done on this plugin. You can consider adopting the plugin to rebase, test, merge, and release the PR. The "Contributing to Open Source" workshop from DevOps World 2021 is a useful starting point for new maintainers. That document includes links to a five-part video series that illustrates many of the steps. If the plugin is crucial to your work, you may want to ask your employer to support your work efforts by allowing you to adopt the plugin.

            Show
            basil Basil Crow added a comment - Hi Cyril Pottiers , there is a PR open at jenkinsci/authorize-project-plugin#44 , but it needs rebasing and test coverage. As far as I can tell, there is no active development being done on this plugin. You can consider adopting the plugin to rebase, test, merge, and release the PR. The " Contributing to Open Source " workshop from DevOps World 2021 is a useful starting point for new maintainers. That document includes links to a five-part video series that illustrates many of the steps. If the plugin is crucial to your work, you may want to ask your employer to support your work efforts by allowing you to adopt the plugin.

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              jnz_topdanmark Jon Brohauge
              Votes:
              26 Vote for this issue
              Watchers:
              32 Start watching this issue

                Dates

                Created:
                Updated: