To create a history of ServerTemplate versions. For a conceptual understanding our version control system from a Lifecycle Management perspective, see ServerTemplate Versioning.
Table of Contents
You can now create multiple revisions of the same ServerTemplate. This feature provides a level of version control that is particularly useful for making changes to a ServerTemplate's RightScripts. Instead of cloning a ServerTemplate to make changes, simply click the Commit button to create a revision of the ServerTemplate.
As a best practice, once you have a functioning ServerTemplate, we recommend creating a revision of the ServerTemplate so that you'll have a version that you can revert back to if you run into problems. The versioning process allows you to annotate as you produce newer versions. (That is, you can create a custom message as you commit a ServerTemplate. These messages will show up under the "Revisions" tab of your ServerTemplate.)
NOTE: You can only commit a [HEAD] version of a private ServerTemplate. The "Head" version is always the version that you are allowed to edit.
Be sure to include a helpful description and click Commit.
Let's say you've made some changes to the [HEAD] version of a ServerTemplate such as adding/removing/rearranging RightScripts or editing individual RightScripts, and want to commit the ServerTemplate and create a new revision.
Before you commit a ServerTemplate, you'll most likely want to commit any RightScripts that you've modified. If you don't commit all [HEAD] RightScripts, you risk future incompatibility issues because you'll be referencing a RightScript whose functionality could have changed since the last commit.
To ensure that all RightScripts are preserved in their current version along with the ServerTemplate, you should commit all RightScripts that have been modified. If you do not click the Commit [HEAD] RightScripts link before clicking the ServerTemplate's Commit button, you will be reminded on the next screen that any RightScripts with [HEAD] versions will be committed.
Click the Commit button of the ServerTemplate.
It's important to leave a detailed description of all of your changes. These messages will be visible under a ServerTemplate's Revisions tab.
Once again, if there are any RightScripts with [HEAD] versions, they will automatically be committed when you commit the ServerTemplate.
NOTE: If there is a special scenario where you do NOT want to commit such changes, uncheck the "Commit [HEAD] RightScripts" box.
Click the Commit button.
Once you've committed a ServerTemplate, you should see a timeline bar underneath the ServerTemplate's name. To change revisions, simply select a revision from the timeline.
You can also click on the Revisions tab to see who created the ServerTemplate revision, when it was committed, as well as the change descriptions for each revision.
If you have a previously committed revision (e.g. rev 5) of a ServerTemplate that you would like to make your new HEAD version, you will need to clone that revision. Currently, that is the only way to revert back to an editable version of a committed template. Essentially, what you are doing with this procedure is creating a new branch of that ServerTemplate. This process ensures that revisions are always updated versions of the previous revision.
© 2006-2014 RightScale, Inc. All rights reserved.
RightScale is a registered trademark of RightScale, Inc. All other products and services may be trademarks or servicemarks of their respective owners.