Jenkins Artifactory Plugin: Improvement example: towards automatic release

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Jenkins Artifactory Plugin: Improvement example: towards automatic release

Nicolas
Hi

I know JFrog has plans to improve the release management plugin, but here are some thoughts and examples of what I'm doing.
Main idea: the plugin needs to default/guess all required values according to the user's needs.

For this, I first standardized the artifact version scheme as can be seen here: https://issues.jfrog.org/jira/browse/HAP-263
Based on that, the plugin is able to increment any specific part of the version as the user indicates, and even include the job's build number.

If you look at jenkins_artifactory-plugin_1.png, you'll notice that several variables can be used.
You can specify a "version upgrade strategy" that tells the plugin how to increase the version (for example, I could decide to increment the major, minor, etc.).
Ih the example, I chose "Least significant number" which increases the last number component.

In jenkins_artifactory-plugin_2.png you can see how it guesses the right versions and uses variables for special values like the build number.

Finally, I'm able to trigger the release automatically by hitting this URL: http://localhost:8080/job/dummy-mvn-single/release/schedule

This is just something I hacked for a demo. I would like to know what you think and, if it's possible, what are your plans regarding automation what ideas you have. If we share a common goal, I'll be able to work on this at my job. I'd rather collaborate and stay close to your plans before I fork the project.

Best regards.
Nicolas.


------------------------------------------------------------------------------
RSA(R) Conference 2012
Mar 27 - Feb 2
Save $400 by Jan. 27
Register now!
http://p.sf.net/sfu/rsa-sfdev2dev2
_______________________________________________
Artifactory-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/artifactory-users

jenkins_artifactory-plugin_1.png (57K) Download Attachment
jenkins_artifactory-plugin_2.png (79K) Download Attachment
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Re: Jenkins Artifactory Plugin: Improvement example: towards automatic release

Nicolas
Posting just in case the email got lost in the stack and no one was able to read it.

On Fri, Jan 13, 2012 at 12:13 PM, Nicky Ramone <[hidden email]> wrote:
Hi

I know JFrog has plans to improve the release management plugin, but here are some thoughts and examples of what I'm doing.
Main idea: the plugin needs to default/guess all required values according to the user's needs.

For this, I first standardized the artifact version scheme as can be seen here: https://issues.jfrog.org/jira/browse/HAP-263
Based on that, the plugin is able to increment any specific part of the version as the user indicates, and even include the job's build number.

If you look at jenkins_artifactory-plugin_1.png, you'll notice that several variables can be used.
You can specify a "version upgrade strategy" that tells the plugin how to increase the version (for example, I could decide to increment the major, minor, etc.).
Ih the example, I chose "Least significant number" which increases the last number component.

In jenkins_artifactory-plugin_2.png you can see how it guesses the right versions and uses variables for special values like the build number.

Finally, I'm able to trigger the release automatically by hitting this URL: http://localhost:8080/job/dummy-mvn-single/release/schedule

This is just something I hacked for a demo. I would like to know what you think and, if it's possible, what are your plans regarding automation what ideas you have. If we share a common goal, I'll be able to work on this at my job. I'd rather collaborate and stay close to your plans before I fork the project.

Best regards.
Nicolas.



------------------------------------------------------------------------------
RSA(R) Conference 2012
Mar 27 - Feb 2
Save $400 by Jan. 27
Register now!
http://p.sf.net/sfu/rsa-sfdev2dev2
_______________________________________________
Artifactory-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/artifactory-users
Loading...