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

Add support of Configuration-as-Code in Artifact Manager S3

    • Artifact Manager S3 1.0

      Currently ArtifactManager is configured via system properties and environment variables. It is not comfortable for automation purposes, because one would need to setup them for any container for testing purposes. https://github.com/jenkinsci/artifact-manager-s3-plugin/blob/master/src/main/java/io/jenkins/plugins/artifact_manager_s3/JCloudsArtifactManager.java

      • Minimum: Make the fields non-final so that the settings can be configured via Groovy hook scripts
      • Nice2Have: Add support of proper UI AND allow configuring ArtifactManagerFactory via DataBoundSetters. It would allow using Configuration-as-Code plugin and other such tools

          [JENKINS-50571] Add support of Configuration-as-Code in Artifact Manager S3

          Oleg Nenashev created issue -
          Oleg Nenashev made changes -
          Assignee Original: Jesse Glick [ jglick ] New: Oleg Nenashev [ oleg_nenashev ]
          Oleg Nenashev made changes -
          Status Original: Open [ 1 ] New: In Progress [ 3 ]
          Jesse Glick made changes -
          Status Original: In Progress [ 3 ] New: In Review [ 10005 ]
          Oleg Nenashev made changes -
          Link New: This issue relates to JENKINS-52304 [ JENKINS-52304 ]
          Oleg Nenashev made changes -
          Resolution New: Fixed [ 1 ]
          Status Original: In Review [ 10005 ] New: Resolved [ 5 ]
          Oleg Nenashev made changes -
          Labels New: jcasc-compatibility
          Oleg Nenashev made changes -
          Released As New: Artifact Manager S3 1.0

            oleg_nenashev Oleg Nenashev
            oleg_nenashev Oleg Nenashev
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: