The page has been translated by Gen AI.

Multibranch Pipeline

Note

For more detailed information on Jenkins multibranch pipeline, please refer to the official website.

Users can manage multiple branches of a code repository as a single job through the multibranch pipeline.

Getting Started with Multibranch Pipeline

To start using the multibranch pipeline, follow these steps:

Main page, click the Project card. Move to the Project Dashboard page.
Click the Build/Deployment > Build Pipeline menu on the left. Move to the Build Pipeline page.

To add a multibranch pipeline, follow these steps:

Main page, click the Project card. Move to the Project Dashboard page.
Click the Build/Deployment > Build Pipeline menu on the left. Move to the Build Pipeline page.
On the Build Pipeline page, click the Add Multibranch Pipeline button at the top right. The Add Multibranch Pipeline popup window opens.
In the Add Multibranch Pipeline popup window, enter each item and click the Save button.

Item	Description
Type	Select the development and operation distinction Actions that can be performed by each role vary depending on development and operation. Role-based permissions can be found in Table. Authority by Role in Project (1).
Jenkins URL	Select Jenkins to add a multibranch pipeline from the list.
Folder Type	Select the folder type Existing folder: Add a pipeline under an existing folder in Jenkins. New folder: Create a new folder in Jenkins and add a pipeline under it.
Folder Name	Select a folder from the list or enter the name of the new folder to be created.
Pipeline Name	Enter the pipeline name.
Git Repository	Select the code repository to perform branch-based builds. Only code repositories registered in the DevOps Console project can be selected.
Branch Filtering	Filter the branch names to be built from the registered branches in the code repository. If filtering is used, enter the filtering conditions in Java regular expression format.
Jenkinsfile Path	Enter the path to the Jenkinsfile that defines the pipeline build in the code repository.

Table. Multibranch Pipeline Addition Information Input Items

Item	Description
Multibranch Icon and Label	The icon and label representing the multibranch pipeline are displayed.
URL	Move to the Multibranch Pipeline page in Jenkins.
Scan Log	The Multibranch Pipeline Scan Log popup window opens.
Scan	Scan the multibranch pipeline.
More	Display additional menus. Pipeline modification Pipeline deletion Build history

Table. Multibranch Pipeline List Screen Items

To scan a multibranch pipeline, follow these steps:

On the Build Pipeline page, click the Scan button on the multibranch pipeline card you want to scan.
In the confirmation popup window, click the Confirm button.

To view the scan logs of a multibranch pipeline, follow these steps:

On the Build Pipeline page, click the Scan Log button on the multibranch pipeline card you want to view the scan log for. The Multibranch Pipeline Scan Log popup window opens.
In the Multibranch Pipeline Scan Log popup window, check the contents and click the Confirm button to close.

To view the branch-based build history of a multibranch pipeline, follow these steps:

On the Build Pipeline page, click the More icon on the multibranch pipeline card you want to view the build history for.
Click the Build History menu. Move to the Branch-based Build History screen in Jenkins (Not provided by DevOps Console).

To modify a multibranch pipeline, follow these steps:

On the Build Pipeline page, click the More icon on the multibranch pipeline card you want to modify.
Click the Pipeline Modification menu. Move to the Settings screen in Jenkins (Not provided by DevOps Console).

To delete a multibranch pipeline, follow these steps:

On the Build Pipeline page, click the More icon on the multibranch pipeline card you want to delete.
Click the Pipeline Deletion menu. The Pipeline Deletion popup window opens.
In the Pipeline Deletion popup window, select whether to delete the pipeline in Jenkins together and click the Confirm button.

Note

Delete pipeline in Jenkins together

Selected: The pipeline is actually deleted in Jenkins.
Not selected: The pipeline is deleted only from the Build Pipeline list and remains in Jenkins.

Stage

Kubernetes Deployment