Skip to main content

Managing the Applications Lifecycle

 

OutSystems

Deploy an Application with Dependencies

An application that is deployed to another environment may experience runtime errors if it depends on functionality of other applications that are not deployed together with it. LifeTime validates these type of dependencies before deploying applications.

LifeTime highlights in red all application dependencies that are not up-to-date in the destination environment.

For each one of them, do the following:

  1. Identify the team responsible for it;
  2. Tag a version of the application with the right code to be deployed with your application.

After all dependencies are tagged:

  1. Deploy your application again;
  2. Validate the deployment;
  3. Dependencies are tagged by now, so just select the version to deploy with your application;
  4. LifeTime validation should go green (OK) and you can go ahead with the deployment.

Here's an example of how to do it.

Deploy MyApp to Quality for Testing

In this example, there's is a Web application (MyWebApp) already running. To extend it to mobile devices a new mobile app (MyApp) was developed:

  • New functionality was added to MyWebApp to be used by MyApp;
  • MyApp is tagged with version 0.2 and is ready to be deployed to Quality for testing;

Deploy the Mobile App

Select the deployment option of MyApp to Quality to 'Deploy 0.2'. Validate the deployment.

LifeTime detects that MyApp depends on MyWebApp that also needs to be updated in Quality. So, both applications become red (error), and it’s not possible to continue with the deployment.

Understand the Dependencies

To understand the dependencies, click on the error message on MyApp.

LifeTime is warning that deploying this version of MyApp will make the application misbehave in Quality. This happens because, MyApp is not compatible with MyWebApp that is deployed in Quality.

To understand what will cause MyApp to misbehave, click the 'Show Details' link.

Clicking on the error icon reveals the problem: the 'ServerActionForMyApp' action, that MyApp depends, is not available on the MyWebApp version deployed in Quality.

Resolve the Dependencies

MyWebApp 1.0+ is exposing the required functionality and has to be tagged to be deployed to Quality:

  1. Go back to the applications list and tag MyWebApp with version 1.1.
  2. Deploy MyApp again;
  3. This time, resolve the dependency of MyWebApp by choosing 'Deploy 1.1' for it.
  4. Validate the deploy again. This time, all should go green (OK) and the deployment can go ahead.

Deploy to Quality

Click 'Continue' to move to the deployment plan.

Review the deployment plan, add a deployment note like 'First round of tests of MyApp.', and click on 'Deploy Now'.

MyApp and MyWebApp are deployed to Quality. MyApp is ready for testing.

  • Was this article helpful?