[JCLOUDS-576] Automate releases

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.9.0
• Assignee: Ignasi Barrera
• Reporter: Everett Toews
• Created: 27/May/14 18:14
• Updated: 30/Mar/15 10:28
• Resolved: 30/Mar/15 10:28

Description

I am emotionally scarred by trying to release jclouds. The release process is sort of documented in Releasing jclouds. It's a 17 step process that has a lot of assumptions baked into it. There is a lot of manual steps and manual data entry that are all very error prone. It's also very time consuming.

These problems are compounded by the fact that we have so many repos. Whether or not we bring the repos back together we need to work towards automating the release process. Performing a release should be a trivial thing to do.

This isn't going to happen all at once. We need to take steps to get there. Here's what I propose as the first steps.

1. Change the release:prepare step so that it isn't interactive and require you to manually enter info to resolve the dependencies.
2. Automate the release of the jclouds main repo. This probably means a script with the steps in Releasing jclouds coded into it.

Issue Links

• is related to: JCLOUDS-104 Change labs/cli/karaf to have their own parent POMs separate from the top-level POM