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

3 views
Skip to first unread message

o.v.nenashev@gmail.com (JIRA)

unread,
Apr 4, 2018, 10:35:02 AM4/4/18
to jenkinsc...@googlegroups.com
Oleg Nenashev started work on New Feature JENKINS-50571
 
Change By: Oleg Nenashev
Status: Open In Progress
Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
Atlassian logo

o.v.nenashev@gmail.com (JIRA)

unread,
Apr 4, 2018, 10:35:02 AM4/4/18
to jenkinsc...@googlegroups.com

o.v.nenashev@gmail.com (JIRA)

unread,
Apr 4, 2018, 10:35:02 AM4/4/18
to jenkinsc...@googlegroups.com
Oleg Nenashev created an issue
Issue Type: New Feature New Feature
Assignee: Jesse Glick
Components: artifact-manager-s3-plugin
Created: 2018-04-04 14:34
Priority: Minor Minor
Reporter: Oleg Nenashev

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

jglick@cloudbees.com (JIRA)

unread,
Apr 4, 2018, 10:46:02 AM4/4/18
to jenkinsc...@googlegroups.com

scm_issue_link@java.net (JIRA)

unread,
Apr 9, 2018, 8:55:03 AM4/9/18
to jenkinsc...@googlegroups.com
SCM/JIRA link daemon commented on New Feature JENKINS-50571
 
Re: 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

scm_issue_link@java.net (JIRA)

unread,
Apr 9, 2018, 8:55:03 AM4/9/18
to jenkinsc...@googlegroups.com

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.

o.v.nenashev@gmail.com (JIRA)

unread,
Jul 2, 2018, 4:03:01 AM7/2/18
to jenkinsc...@googlegroups.com
Oleg Nenashev updated New Feature JENKINS-50571
 

Closing it. JCasC compatibility is trackes as JENKINS-52304 created by Baptiste Mathus

Change By: Oleg Nenashev
Status: In Review Resolved
Resolution: Fixed
This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)

o.v.nenashev@gmail.com (JIRA)

unread,
Oct 19, 2018, 2:07:06 AM10/19/18
to jenkinsc...@googlegroups.com
Oleg Nenashev updated an issue
Change By: Oleg Nenashev
Labels: jcasc-compatibility
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

o.v.nenashev@gmail.com (JIRA)

unread,
Sep 16, 2019, 9:56:03 AM9/16/19
to jenkinsc...@googlegroups.com
Oleg Nenashev updated an issue
Change By: Oleg Nenashev
Released As: Artifact Manager S3 1.0
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
Atlassian logo
Reply all
Reply to author
Forward
0 new messages