Configuring Schedules
To deliver a more powerful, flexible, and efficient CI/CD experience, the scheduling and commit-triggering capabilities have been enhanced and consolidated into the pipeline framework. You are encouraged to adopt the execution plan feature within pipeline jobs, as the legacy scheduling feature in CodeArts Build is being phased out.
- New users: configure scheduling exclusively through the pipeline execution plan.
- Existing users: disable any build task schedules and switch to the pipeline execution plan.
Constraints
Scheduling a Build Task
On the build task configuration page, navigate to the Schedule tab to define an execution plan.
- Continuous Integration: Enable Run upon Code Commit to trigger a build whenever the referenced code source receives a new commit.
This capability is available only when CodeArts Repo is installed, the code source is Repo, and the code repository is in MR mode.
Figure 1 Configuring continuous integration
- Scheduled Execution: Enable this option and define when and how your build task should run. You can optionally enable Run upon code change.
After this function is enabled, the build task is run at the specified date and time.
If both Scheduled Execution and Run upon code change are enabled, the build task executes at the specified date and time only when code has changed since the last build.
If a scheduled build task fails to run 10 times in a row, it will automatically stop being triggered further.
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
