-
New Feature
-
Resolution: Fixed
-
Minor
-
-
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
- relates to
-
JENKINS-52304 Make the plugin fully configurable via configuration-as-code
-
- Resolved
-
[JENKINS-50571] Add support of Configuration-as-Code in Artifact Manager S3
Code changed in jenkins
User: Jesse Glick
Path:
src/main/java/io/jenkins/plugins/artifact_manager_s3/JCloudsArtifactManager.java
http://jenkins-ci.org/commit/artifact-manager-s3-plugin/721f9916b5d465924807505d605b744ff1210360
Log:
Merge pull request #5 from oleg-nenashev/JENKINS-50571
JENKINS-50571 - Make JCloudsArtifactManager fields non-final to allow configuration via System Groovy Hooks.
Compare: https://github.com/jenkinsci/artifact-manager-s3-plugin/compare/3a5d4d308c0d...721f9916b5d4
Closing it. JCasC compatibility is trackes as JENKINS-52304 created by batmat
Code changed in jenkins
User: Oleg Nenashev
Path:
src/main/java/io/jenkins/plugins/artifact_manager_s3/JCloudsArtifactManager.java
http://jenkins-ci.org/commit/artifact-manager-s3-plugin/c423b4f6ba20d984278ff819f927fe091e55702b
Log:
JENKINS-50571- Make JCloudsArtifactManager fields non-final to allow configuration via System Groovy Hooks.Ideally a better non-static configuration UI needed so that each run persists information about its artifact manager parameters.
Otherwise reconfiguration will likely cause regressions.