You can configure either a source control or a build repository with a trigger step in your pipeline.
To save your pipeline, it must contain more than a trigger step. |
Adding a source control trigger step
You can configure all your source control parameters after adding a trigger step into the pipeline editor.
To configure a source control in a trigger step:
-
From the CloudBees Release Orchestration SaaS Home page, select .
-
Select an existing pipeline, or create a new pipeline. Refer to Working with pipelines for more information.
-
Select Trigger from the icon options, which adds it to your pipeline.
-
On the right pane:
-
Select Source Control.
-
Enter SCM Name from the options.
-
Enter Repository from the options.
-
Enter Branch Name from the options.
-
If necessary, enter the Directory/Folder(s) to include. This feature is supported for SVN and Perforce.
Figure 1. Source control set up in a trigger step
-
-
Select SAVE (for a new pipeline) or UPDATE (for an existing pipeline).
You have added a source control trigger step to your pipeline.
Adding a build repository trigger step
You can configure all your build repository parameters after adding a trigger step into the pipeline editor.
To configure a build repository in a trigger step:
-
From the CloudBees Release Orchestration SaaS Home page, select .
-
Select an existing pipeline, or create a new pipeline. Refer to Working with pipelines for more information.
-
Select Trigger from the icon options, which adds it to your pipeline.
-
On the right pane:
-
Select Build Repository.
-
Enter Build Repository Name from the options.
-
Enter Repo Config Name from the options.
Figure 2. Build repository set up in a trigger step
-
-
Select SAVE (for a new pipeline) or UPDATE (for an existing pipeline).
You have added a build repository trigger step to your pipeline.
To update trigger step settings, refer to Working with pipelines. |