Environments can be configured to align to the Clients SDLC. There is no limit to the number of Environments that can be added. For instance, consider an SDLC encompassing phases like Development, System Integration Testing, Quality Assurance, and Production.
In accordance with this SDLC, the following environments would be established:
- Development (DEV)
- System Integration Testing (SIT)
- Quality Assurance (PRE-PROD)
- Production (PROD)
Each environment will have different outbound connectors, typically with distinct endpoints such as hosts (IP/Port or URLs). Therefore, it’s necessary to define environment-specific host details for each outbound connector within the GLU.Console. This approach ensures that all host configurations are centralised within GLU, eliminating the need for SDLC-related configuration changes outside of GLU.Engines as they progress through the SDLC.
It’s worth noting that maintaining a “PRE-PROD” environment mirroring the production environment, including all production host details, is beneficial. This setup allows for building a PRE-PROD GLU.Engine identical to the PROD GLU.Engine, facilitating PROD smoke testing. Once the “cut over” to PROD is approved, the transition can be seamlessly executed.
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.
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 ‘grab handles’ on the left of each ‘Environment Block’ can be used to ‘drag’ the Environments up or down, to adjust the SDLC sequence. The SDLC sequence is determined based on the top-down sequence of these Environment blocks.
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 X’ can be used to de-activate the environment. It is not possible to delete environments once created and used for historic audit reasons.
