Page tree
Skip to end of metadata
Go to start of metadata

Once a release has been defined it can be installed in the UAT (User Acceptance Testing) or the Live environment. Typically, a new release is first installed in UAT for testing first. UAT is the environment where stakeholders, such as authors and site managers, can see the development changes that have been made and decide whether they satisfy their requirements. Once the changes have been tested and accepted in the UAT environment, the release can be installed in the Live environment

To install a release:

  1. In Installed releases click Install an update .
  2. Click Install a release.
  3. Installing is a four-step process:
    1. Select the release you want to install and click Next. Latest versions display first. Select Other releases for a dropdown of earlier versions.
    2. Select the environment to install in and click Next. Environments that have not been set up and therefore do not contain spaces  are not available for selection.
    3. Confirm the consequences of the installation and click Install

    4. Installation may take a few minutes. As all actions in the cockpit are asynchronous, you can click on OK before the installation is complete: the action will run in the background and a notification will appear once it is complete. 
  4. The new release now displays in the selected environment. Placing the mouse pointer over the version icon will show a tooltip containing the essential information about the release:

    The installation action appears in the activity log and a notification banner is displayed:

Test changes on updated environment

To check that the environment is running on the correct release:

  • Click Edit content in Author space of the environment on which you installed the release.
  • Log in to Magnolia and check that the updates included in the release are present. Usually a content editor may try out new features such as templates, etc. or a stakeholder may check updated style, etc. pp.

Always avoid hotfixing problems in the Resources app because the changes are not propagated back to your GIT repository.


* Installing a release in Live