Bu sayfa henüz yerel dilinizde mevcut değildir. Daha fazla dil seçeneği eklemek için yoğun bir şekilde çalışıyoruz. Desteğiniz için teşekkür ederiz.
Upgrading a CAE Component After Uploading a Software Package Built Using the Pipeline to the OBS Bucket
Creating a Build Task
Create a build task for a code repository.
- Go to the CodeArts console and click Access Service in the upper right corner.
- Choose Services > Build.
Figure 1 Selecting a service
- On the Build page, click Create Task. In the Basic Information area, set Task Name, Project, Code Source, Source Code Repository, and Branch, and click Next.
Figure 2 Configuring basic build information
- Select a template for build and click Next. In this example, Java code is used. Therefore, select the Maven template.
Figure 3 Selecting a build template
- On the Build Actions page, click Add step > Upload related > Upload Files to OBS > Add.
Figure 4 Uploading a file
- On the Parameters page, configure build parameters and default values by referring to Figure 5, and enable Runtime Settings. bucket_name: name of the OBS bucket to which the file is uploaded, for example, caetest.
- file_name: name of the software package uploaded to the OBS bucket, for example, cae-backend.jar.
- On the Build Actions page, delete step Upload Software Package to Release Repository.
Figure 6 Deleting step Upload Software Package to Release Repository
- Click Yes.
- Configure Upload Files to OBS.
- Build Directory: Enter **/target/*.?ar.
- Bucket Name: Use ${bucket_name}.
- OBS Directory: Use the default value.
- File Name: Use ${file_name}.
Figure 7 Configuring Upload Files to OBS - Click Create and Run in the upper right corner, confirm the runtime parameter, and click Confirm.
Figure 8 Running a task
- View the build log and wait until the build is successful and the software package is uploaded to OBS.
- Log in to OBS and check whether the software package has been uploaded to the OBS bucket.
Figure 9 Viewing an OBS bucket
Creating a Pipeline to Upgrade CAE Components Using the OBS Software Package
Create a CodeArts pipeline.
- Go to the CodeArts homepage.
- Choose Services > Pipeline. On the Pipeline page, click Create Pipeline.
Figure 10 Selecting a serviceFigure 11 Creating a pipeline
- On the Create Pipeline page, set Name, Pipeline Source, Repository, and Default Branch, and click Next.
Figure 12 Configuring basic pipeline information
- In Template, choose All > Blank Template and click OK.
Figure 13 Selecting a template
- On the Task Orchestration page, click Stage. Click
and change the names of stages 1 and 2 to Build and Deploy, respectively.
Figure 14 Creating a stage - Create a build job.
- In the Build stage, click Job.
- On the NewJob page, click Build > Build > Add.
Figure 15 Creating a taskFigure 16 Adding a build job
- Select the created build job and repository, set bucket_name and file_name configured in 6 as the pipeline parameter, and click OK.
- On the NewJob page, click Build > Build > Add.
- In the Deploy stage, click Job.
- Enter CAE in the search box and click
. Select the CAE Release extension and click Add.
Figure 17 Adding a deploy job - Configure the extension parameters and click OK.
- Region: Select a region for deployment, which is the same as the CodeArts region.
- Environment: Select the environment to which the component belongs.
- Application: Select the application to which the component belongs.
- Component: Select the component to be upgraded. (You need to select a component that is deployed using the software package in CAE.)
- Component Source: Select Software packages.
- Runtime System: Select the runtime system corresponding to the software package.
- Software Package Repository: Select OBS.
- Software Package Address: See Parameters.
Figure 18 Configuring the extension parameters - On the Parameter Configuration page, add custom parameters by referring to Parameters.
- bucket_name: name of the OBS bucket, for example, caetest.
- file_name: name of the software package uploaded to the OBS bucket, for example, cae-backend.jar.
- file_dir: directory for storing the software package uploaded to the OBS bucket, for example, /test/ (if the root directory is /).
- obs_address: address of the OBS bucket. The format is obs.Region project name.myhuaweicloud.com.
Figure 19 Configuring custom parameters
- Enter CAE in the search box and click
- In the Build stage, click Job.
- Click Save and Run. On the Execution Configuration page, confirm the configurations and click Run.
Figure 20 Running a taskFigure 21 Confirming the pipeline configurations
- On the pipeline details page, view the pipeline execution result.
Figure 22 Viewing the pipeline execution result
- Log in to CAE and check the component status. If Upgraded is displayed in the Last Change Status/Time column, the component has been upgraded using the CodeArts pipeline.
Figure 23 Viewing component status
Parameters
Parameter |
Mandatory |
Type |
Description |
---|---|---|---|
bucket_name |
Yes |
String |
OBS bucket name. The region selected for the CAE release extension must be the same as the region where the OBS bucket is located. |
file_name |
Yes |
String |
Name of the software package uploaded to the OBS bucket. |
file_dir |
Yes |
String |
Directory for storing the software package uploaded to the OBS bucket. The directory must end with a slash (/). If the directory does not exist in the OBS bucket, it will be automatically created. For example, the root directory is /, and the test directory in the root directory is /test/. |
obs_address |
Yes |
String |
The format is obs.Region project name.myhuaweicloud.com. The region project name is region. For details, see Obtaining Values. |
Software Package Address |
Yes |
String |
Address of the software package uploaded to OBS. Enter https://${bucket_name}.${obs_address}${file_dir}${file_name}. |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot