Environments

NCC Sandbox Environment Setup

Sandbox is the environment where we release all our code as soon as the Jira story/task has been completed. As you can see in the below figure, almost all the parts of the component have a test environment setup. Having this setup, the team can complete end-to-end testing before we release the product or stories to the live environment. A story has to be tested and signed off in order to be released on to live environment.

The figure below clearly shows which are cloud services and which are on premises.

We went live with part of the application/module to a few of our users. This meant that we needed to both test in a development environment as well as in a mirror of the live environment, as code was being uploaded to a live service. In order to achieve this, we set up two environments in our Sandbox environment: named as Dev Test and Live Test. See screenshots below which show which environment you are testing on.

Also on live, we are greying out some of the modules which are still being developed as we do not want agents to be visiting these pages. We have devised a setting in our front-end which recognises the environment where the code is released and, accordingly, that part of the application is greyed out for the agent. This allows continuous development and delivery of our product.

NCC Live Environment Setup

The Live environment for websites (SSO & Front-end) is being set up on premises as the application is used by internal agents. The appropriate domain name was registered and was hosted on one of our internal live servers.

APIs have been hosted on our live Hackney API server, as per our other API hosting.