- Service Overview
- Getting Started
- User Guide
-
API Reference
- Before You Start
- API Overview
- Calling APIs
-
API
- Template management
-
Pipeline Management
- Execute Pipeline
- Obtaining Pipeline Status in Batches
- Obtaining the Pipeline Status/Obtaining Pipeline Execution Details
- Obtaining the Pipeline List/Obtaining the Pipeline Execution Status of a Project
- Deleting a Pipeline
- Stopping a Pipeline
- Obtaining Pipeline Execution Records
- Creating a Pipeline Using a Template
- Creates a pipeline.
- Re-trial Run Pipeline
- Pass the manual review.
- Reject to Manual Review
- Querying Pipeline Logs
- Manage by group
- Rule Management
- Tenant-level policy management
- Project-level policy management
-
Tenant-level open source governance policy management
- Creating a Tenant-Level Open Source Governance Policy
- Modifying a Tenant-Level Open Source Governance Policy
- Querying Details About a Tenant-Level Open Source Governance Policy
- Querying the Tenant-Level Open Source Governance Policy List
- Deleting a Tenant-Level Open Source Governance Policy
- Changing the Enabling Status of a Tenant-Level Open Source Governance Policy
- Project-level open source governance policy management
-
Extension Plug-in Management
- Creating a Plug-in Version
- Creating a Plug-in Draft Version
- Creating a publisher
- Update Plug-in Draft
- Releasing a Plug-in Draft
- Updating Basic Plug-in Information
- Releasing a Plug-in
- Binding a Plug-in to a Publisher
- Updating the Plug-in Icon
- Updating the Publisher Icon
- Deleting a Plug-in Draft
- Querying the Publisher List
- Querying Available Publishers
- Querying the List of Optional Plug-ins
- Querying the Basic Plug-in List
- Querying the List of Optional Plug-ins in Pagination Mode
- Listing add-ons
- Query Plug-in Indicator Configuration
- Query Plug-in Input Configuration
- Query Plug-in Output Configuration
- Querying All Plug-in Version Information
- Querying Plug-in Version Details
- Querying the Plug-in Version
- Deleting a publisher
- Querying Publisher Details
- Creating a Basic Plug-in
- Updating Basic Plug-ins
- Deleting a Basic Plug-in
- Uploading Basic Plug-ins
- Querying Basic Plug-in Details
- Appendixes
- Change History
-
FAQs
- Functions
-
Troubleshooting
- The Pipeline Parameter Referenced by the Task Does Not Exist
- Test Suite Was Running
- Failed to Obtain Tenant Information During Code Check Task Execution
- The Pipeline That Does Not Listen to the Push Event Is Triggered When the Code Is Committed
- Scheduled Task of a Pipeline Was Not Triggered
- Run Button Was Unavailable
Show all
Can Multiple Packages Be Installed in a Certain Sequence?
In microservice scenarios, if a Java project contains multiple modules, multiple packages will be packed for these modules at a time. In addition, these packages need to be deployed in sequence during deployment. You can perform the following operations:
- Create a code repository.
- Go to CodeArts Repo, click New Repository.
- Enter a repository name and click OK.
- Upload the Java project code to the created repository by referring to Uploading Local Code to CodeArts Repo.
- Create a build task.
- Go to CodeArts Build, click Create Task.
- On the Set Information page, select the code source Repo, the created code repository, and the branch master. Select the Maven template, and click Next.
- On the Build Actions tab, retain the default build actions. For details about how to configure build actions, see Build Actions.
- After the configuration is complete, click Create and Run. After the execution is complete, you can view the generated software package in the release repository.
- Create a deployment task.
Add the action Select Deployment Source, select the build task created in the previous step and the build package uploaded to the release repository, and download the build package to the specified path on the server. For details, see Selecting a Deployment Source.
Add the action Start/Stop Spring Boot to start a specified JAR package. For details, see Starting or Stopping Spring Boot.
- Create a pipeline. Add the build and deployment tasks to the pipeline and run the pipeline.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.