Deze pagina is nog niet beschikbaar in uw eigen taal. We werken er hard aan om meer taalversies toe te voegen. Bedankt voor uw steun.
- 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
Getting Started with CodeArts Pipeline
This document describes how to create a pipeline, including the preparations and basic procedure. You can use the pipeline after performing routine operation settings.
Preparations
- Create a project
- Log in to the CodeArts home page and click Create Project.
- Select a Scrum project template, enter information such as the project name, and click OK.
For details, see Creating a Scrum Project.
- Create a code repository
- Click the created project, and choose Code > Repo.
- Click the drop-down button next to New Repository, select Template Repository, and select the Java Maven Demo template.
- Click Next, enter basic information such as the repository name, and click OK.
For details, see Creating a Repository Using a Template.
- Create a build task
- Go to the created project and choose CICD > Build.
- Click Create Task and perform the following operations as prompted:
- On the Set Basic Information page, select the created code repository, select the default branch master, and click Next.
- On the Build Template page, select the system template Maven, click Next, and retain the default configurations on the displayed Build Actions tab page.
- Click Create to complete the creation.
For details, see Creating a Build Task.
- Create a code check task
- Click the created project, and choose Code > Check.
- Click Create Task, select a code source, search for the target repository, and click Create next to the repository.
- After the creation is complete, go to the details page and modify the task name as required.
For details, see Creating a Task to Check Code from Repo.
Procedure
- Go to the created project and choose CICD > Pipeline.
- On the CodeArts Pipeline homepage displayed, click Create Pipeline.
On the displayed page, enter a pipeline name, select a pipeline source and template (a blank template is used as an example), and click OK.
NOTE:
Alternatively, click Create Pipeline on the CodeArts Pipeline homepage, select a pipeline source and project.
- On the Task Orchestration tab page, add the created code check task in the build stage.
Add the created build task.
- Click
under a stage. In the dialog box displayed, move the cursor to different pass condition cards and click Add to add a pass condition for the current stage and configure a policy for the condition.
- After the configuration is complete, click Save and Run. In the displayed dialog box, select the branch or tag of the pipeline source, configure parameters, select the execution stage, and click Run.
- View the execution result.
- Click Download next to Output to download the build package automatically built using the pipeline.
- Click a task card to view the task log.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.