Overview
Background
After code development, you need to package the code into an image or software package on Jenkins before each rollout, upload the image to SWR or upload the software package to OBS, and then upgrade the component in CAE. This process is complex. Frequent version tests cause low development and O&M efficiency and poor user experience. The following best practice can improve development efficiency. The following uses Java project build and deployment as an example to describe how to submit code. If other languages such as Golang are involved, you only need to install the compilation and build environment.
Scenario
This function is applicable to the scenario where your code has been managed on GitLab, built and packaged using Jenkins, and hosted using CAE. After components have been deployed, you need to upgrade the components.
For the first deployment, see Creating a Component.
Solution
The solution for uploading JAR packages and images and upgrading CAE components is provided. A shell script is generated. After the code is built and packaged using Jenkins, the script is invoked to deploy the package in the CAE environment. In this way, the code is automatically built, packaged, and deployed after being integrated.
Process Comparison
Original rollout process:
New rollout process:
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