User guide

36
3.5 Copying a stage to another
It is possible to copy the entire deployment sequence of a stage onto another one. This is done by using the
contextual menu of the stage. To access it, right-click the stage to copy and then right-click again on the destination
stage to paste it. It is also possible to undo the last paste to recover the previous deployment sequence of the
destination stage:
Since the allowed servers are usually different from stage to stage, when pasting, a new window will be shown to
identify the equivalence in the servers. Also, if copying from one release template to another, it could be possible
that the destination release template is missing some of the component being copied. If it is the case, the new
window will show the list of component that will automatically be added to the destination release template. Be
aware that components added in this way will not be removed if the paste is undone.
3.6 Locking Mechanism
To prevent having two users editing a release template at the same time and hence overwriting each other’s work, a
locking mechanism has been put in place. As soon as a user opens a release template, the template is locked. Other
users will not be able to edit this release template until the first user leaves that release template (with or without
saving).
Users will be informed that a release template is locked to another user in two ways.
1. The list of release template shows a small icon to the left of the name to indicate that it is locked. When
hovering over the icon, more information will be shown.