Step 5: Building an Application

Introduction to Preset Tasks

There are five build tasks preset in the sample project.

For details about Vote, Result, and Worker, see Solution Architecture.

This section uses the phoenix-sample-ci task as an example. The following table shows the steps involved in this task.

During project deployment, failures often occur due to environment inconsistency. For example, after the JDK in the R&D debugging environment is upgraded, the JDK is not marked in the environment list. As a result, the production environment is not upgraded, causing failures. To avoid problems caused by environment inconsistency, Docker is used to package microservice applications and environments into images to ensure that each environment (development and commissioning environment, test environment, QA environment, and production environment) is consistent.

Configuring SWR

In this example, environment images are stored in SWR. Configure SWR first.

1. Log in to the SWR console.

   Check the region list in the upper left corner of the page and ensure that the region is the same as the region where the build task is compiled. If the regions are different, select the same region.

2. Click Generate Login Command. The login command is displayed in a dialog box.
   where,

   • The character string following -u is the user name.
   • The character string following -p is the password.
   • The last character string is the address of the SWR server, which is the value of dockerServer for configuring and executing tasks later.

   Figure 1 Generating a login command
   

   

   The login instruction generated here is a temporary login instruction with a validity period of 24 hours. If a long-term valid login command is required, see Obtaining a Long-Term Valid Login Command.

3. Click Create Organization. In the displayed dialog box, enter phoenix as the organization name and click OK. (The organization name must be globally unique. If a message is displayed indicating that the organization already exists, enter another name.)

   The organization name is the value of dockerOrg, which will be used for configuring and executing tasks later.

Configuring and Executing a Task

1. Configure a task.
   1. Go to the Phoenix Mall project and choose CICD > Build. The built-in build task of the sample project is displayed on the page.
   2. Find the phoenix-sample-ci task in the list. Click and choose Edit from the drop-down list.
   3. Click the Parameters tab, and set parameters by referring to Table 3.

      Table 3 Setting Parameters

      Name	Default Value
      codeBranch	master
      dockerOrg	Organization created in SWR. For this example, enter phoenix.
      version	1.0.0
      dockerServer	SWR server address obtained from SWR.

      

      Ensure that the values of dockerOrg and dockerServer are correct. Otherwise, the task fails.

2. Click Save and Run. In the dialog box that is displayed, click OK and start the build task.

   When is displayed, the task is successfully executed. Record the character string starting with # (for example, ).

   If the build fails, rectify the fault based on the failed action information and error information in logs.

3. Check the release file.
   1. Choose Artifact in the navigation pane and click the Release Repos tab.
   2. In the repository named after the project, you can find the docker-stack and phoenix-sample-ci folders.
      • In the docker-stack folder, you can find the folder named after the character string recorded in 2. In this folder, you can find the release file docker-stack.tar.gz.
      • In the phoenix-sample-ci/1.0.0 folder, you can find 10 archived .yaml files.
   3. Go to SWR. In the navigation pane, choose Organizations, and click the organization with the same name as the value of the build task parameter dockerOrg.

      Click the Images tab. You can find five images (redis, postgres, worker, result and vote) in the list.

      Figure 2 Viewing images
      
   4. Click the names of the five images in sequence to go to the image details page. View the image version on the Tags tab page.
      • The Redis image version is alpine.
      • The image version of postgres is 9.4.
      • The image versions of worker, result, and vote are the same as those recorded in 2.

Setting Code Submission to Trigger Automatic Compilation

After the following configuration, the application build task can be automatically triggered after the code is changed for continuous project integration.

1. On the details page of the task phoenix-sample-ci, click Modify in the upper right corner of the page.
2. Click the Schedule tab.
3. Enable Run upon Code Commit. When is displayed, click Save.

   The default value of the codeBranch parameter on the parameter setting page is master. Therefore, the build is automatically triggered when the master code changes.

4. Verify the configuration result: Modify the project code and submit it to master to check whether the build task is automatically executed.

Configuring Scheduled Execution

To prevent a code bug from entering the production environment and ensure that the application is always in a deployable state, the team recommends continuous verification of the application.

You can perform the following operations to execute the build task at a scheduled time:

1. On the details page of the task phoenix-sample-ci, click Modify in the upper right corner of the page.
2. Click the Schedule tab.
3. Enable Scheduled Execution. After is displayed, and click Save.

   In this document, select All. The execution time is 12:00.

4. Verify the configuration result: Check whether the build task is automatically executed at the configured time. We will not elaborate on the details in this section.