• 1.5.1

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

          [JENKINS-56774] Support Configuration as Code

          We currently do not support map.

          The suggestion is to use a list of objects with data binding

          Joseph Petersen (old) added a comment - We currently do not support map. The suggestion is to use a list of objects with data binding

          Matrix Auth and role based Auth decided to implement a Configurator and so so did credentials plugin to get around the limitations.

          Joseph Petersen (old) added a comment - Matrix Auth and role based Auth decided to implement a Configurator and so so did credentials plugin to get around the limitations.

          Ben Faucher added a comment -

          +1 for wanting this fixed

          Ben Faucher added a comment - +1 for wanting this fixed

          Marc Cortinas added a comment -

          +1 

          Marc Cortinas added a comment - +1 

          Rico Chen added a comment -

          +10

          Rico Chen added a comment - +10

          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.

          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.

          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 

          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 

          Basil Crow added a comment -

          Hi cpottiers, 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.

          Basil Crow added a comment - Hi cpottiers , 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.

          Basil Crow added a comment -

          Basil Crow added a comment - Fixed in jenkinsci/authorize-project-plugin#129 . Released in 1.5.0 .

          Mark Waite added a comment -

          I was unable to push 1.5.0 to the artifact repository, so it has been released as 1.5.1. Thanks basil!

          Mark Waite added a comment - I was unable to push 1.5.0 to the artifact repository, so it has been released as 1.5.1. Thanks basil !

            basil Basil Crow
            jnz_topdanmark Jon Brohauge
            Votes:
            27 Vote for this issue
            Watchers:
            34 Start watching this issue

              Created:
              Updated:
              Resolved: