Environments

Environments can be configured to align to the Clients existing SDLC. There is no limit to the number of Environments that can be added. As an example a SDLC has the following phases:

Development -> System Integration testing -> Quality Assurance -> Production

To support this SDLC the following Environments will be created:

  • DEV
  • SIT
  • PRE-PROD
  • PROD

For each environment the Outbound Connectors will (typically) have different End Points – Hosts (IP/Port or URLs). Thus for each Outbound Connector you will need to define the Environment specific host details. In this way, all host configurations are defined in the GLU.Console so that there is no need for any SDLC related configuration changes to be made outside of GLU as GLU.Engines are promoted through the SDLC.

Note that as a ‘way of working’ there is merit in always having a ‘PRE-PROD’ Environment which has all the PROD host details … this will enable you to build a PRE-PROD GLU.Engine that is identical to what will be the PROD GLU.Engine. The PRE-PROD GLU.Engine can then be used for PROD smoke testing etc. then when ‘cut over’ to PROD is signed off, the PROD build can be built and deployed in confidence.

 

Add Environment

Use the ‘Add Environment’ Tool to add Environments, where the following details need to be provided.

Field Name Description
Environment Name Assign a Unique Name for the Environment
Production Checkbox To identify this as a ‘Production’ Environment. When a build is created using this environment the GLU.Engine will be tagged as a ‘Release’. All preceding Environment related builds in the SDLC will be tagged as ‘snapshot’ builds.
Description To explain the purpose of this Environment

 

 

Manage SDLC Tool

Use this tool to define a particular SDLC to be used for the specified Application which you select from the first pop-up box as below.

 

Once selected – you can add your pre-defined ‘Environments’ to this SDLC using the drop-down list. If an SDLC is going to conclude with a ‘Production’ release, select one of the pre-defined Environments that you flagged as a ‘Production’ Environment when using the ‘Add Environment’ Tool.

 

Please Note: There is no limit to the number of Environments you can add where the Production Checkbox has not been selected. You cannot add more than one ‘Prod’ Environment to an SDLC.

 

The ‘Skip Test’ toggle allows the Release Manager to quickly adjust the SDLC sequence. This may be useful for example where there is a Production bug that is low risk and urgent, instead of the fix having to follow the full SDLC sequence, the Release Manager can ‘Skip Testing’ on any Environments (except if flagged as Production) to fast track the Production fix. The RED CROSS can be used to de-activate the environment. It is not possible to delete environments once created and used for historic audit reasons.

 

Was this article helpful?

Leave a Reply

Your email address will not be published. Required fields are marked *

Need Support?

Can't find the answer you're looking for?
Contact Support
Fill the form and we’ll contact you shortly

    I agree with

    cookies
    We uses cookies to make your experience on this website better. Learn more
    Accept cookies