This topic describes how a new application is developed and deployed to the Development environment and, when a development milestone is reached, how it is deployed to the Quality Assurance environment for testing.

In this example the Expenses application is going to be created. This application allows employees to submit their expenses.

1. First Deployment of the New Application

The Expenses application is created and developed by a team using Service Studio : each member of the team has permission to connect and deploy the application to the Development environment.

The first time the Expenses application is deployed to Development, using the 1-Click Publish button in Service Studio, LifeTime automatically tags it with version 0.1 .

2. Further Changes to the Application

After the first deployment of the Expenses application, the development of the application continues, and new deployments to Development will occur. When that happens, LifeTime automatically identifies that Expenses was already deployed in Development and adds a '+' (plus) sign to the version number to highlight that the application has been changed.

3. Deploying to Quality Assurance

Having reached a development milestone, the Expenses application is ready to be deployed to Quality Assurance for testing:

1. Click on the ' Deploy... ' green button between 'Development ' and 'Quality Assurance'. You will later be asked to specify which applications you want to deploy to Quality Assurance;

2. Find the Expenses application in the application list and click on the ' Tag & Deploy 0.2 ' button;

   

The 'Tag & Deploy' option means LifeTime is going to automatically tag the currently running version of Expenses with version 0.2 in Development and then deploy it to Quality Assurance.

After choosing the 'Tag & Deploy 0.2' option, LifeTime runs an impact analysis to validate if the deployment can be performed without impacting other applications running on Quality Assurance: all is ok and both the deployment option and the 'Next' button are green;

4. Click on the 'Confirm Deployment...' button to advance to check out the final deployment plan and execute it;

5. Click on the 'Deploy Now' button to start deploying to Quality Assurance.

6. The version 0.2 of the Expenses application is now tagged and deployed in both Development and Quality Assurance, where it is ready for testing.

Related Articles