# Setting up a Pipeline ## 1. Setting up a Pipeline ### 1-1. Creating a Pipeline 1\) To create a pipeline, click on the '+ Create Pipeline' button located in the top right corner of the \[CI/CD] - \[Pipeline] tab.

[Screen] Initial Pipeline Creation Screen

2\) After entering the pipeline creation information, click the 'Save' button located in the top right corner.

[Screen] Pipeline Creation Information Input Screen

Item (* is required)	content
Name*	Enter the pipeline name to create
Version*	Input the version for the pipeline
Service Map*	Select the service map to execute the pipeline

3\) Click the "Add Resource" button in the deployment resources section to apply the items you want to configure for the pipeline. {% hint style="info" %} * Workloads need to be created by default {% endhint %}

[Screen] Add Deployment Resources to the Pipeline

4\) After selecting the workload to add from the workload section, click the "Save" button

[Screen] Select Workload in Add Deployment Resources

5\) Once the workload is registered, confirm that the container images registered with the workload are automatically added. {% hint style="warning" %} * Only images built using the image build feature in Cocktail are integrated {% endhint %}

[Screen] Registering Workload for Pipeline

6\) After selecting the service to add from the service exposure section, click the "Save" button.

[Screen] Selecting Service Exposure in Add Deployment Resources

7\) After selecting the Ingress to add from the Ingress section, click the "Save" button.

[Screen] Selecting Ingress in Add Deployment Resources

8\) After completing the registration of all resources, click the "Run" button located in the top right corner.

[Screen] Screen after registering all resources for the pipeline

9\) When the \[run popup] appears, enter the content for the execution note regarding this pipeline version, then click the "Save" button.

[Screen] Inputting Pipeline Execution Notes

10\) Once the pipeline execution is complete, the release version will be indicated correctly in the top left corner.

[Screen] Screen after Pipeline Execution Completion

## 2. Modify Pipeline {% hint style="danger" %} * When modifying each workload, service exposure, and Ingress in the \[Service Map] tab, changes are not reflected in the pipeline. You need to make modifications directly in the pipeline. * Modifying the pipeline ensures that each workload and deployment resource is updated to the latest version {% endhint %} 1\) Select the pipeline name that needs modification in the \[Pipeline] tab.

2\) Click the "Create Pipeline Version" button in the top right corner of the pipeline, enter the version, and then click "Create".

### 2-1. If there are changes in the source requiring rebuilding of images 1\) Activate the "Build Run" button on the right side of the \[Image Build] section, then click "Run". {% hint style="info" %} * The image build is re-executed and immediately reflected in the workload {% endhint %}

[Screen] Screen with Build Execution Enabled and in Progress

2\) The image is rebuilt, and you can check the progress of each step in the process.

3\) When the image is rebuilt through the pipeline, verify that the image name in the workload is updated to the tag of the image built through the pipeline.

[Screen] Confirmation of Image Tag Change

### 2-2. If there are changes to the workload, such as replicas or other configurations {% hint style="info" %} * Deactivate the "Build Run" button on the right side of the \[Image Build] section (no image changes required) {% endhint %} 1\) Select the workload name in the \[Deployment Resources] section.

[Screen] Screen with Build Execution Disabled

2\) Make the necessary modifications by selecting the relevant parts, then click the "Save" button in the top right corner.

[Screen] Workload Configuration Change Screen

3\) After confirming the change in replicas from 1 to 2 in the workload, click the "Close" button in the top right corner.

[Screen] Information after Workload Configuration Change

4\) Once you return to the pipeline modification section, click the "Run" button in the top right corner, and enter the changes in the execution note."

[Screen] Screen after Clicking the "Run" Button

5\) In the pipeline's \[Deployment Status] tab, verify that there are two pods running.

## 3. Pipeline Rollback {% hint style="info" %} * If you need to rollback to a previous configuration while continuously registering versions through the pipeline. {% endhint %} 1\) Select the pipeline name that needs modification in the \[Pipeline] tab. Once changes are made in the modification section, click the "Rollback" button in the top right corner.

2\) When the \[Rollback Popup] window appears, review the execution notes of the versions created so far, select the desired version, then click the "Save" button.

[Screen] Popup window with Execution Notes after Clicking Rollback

3\) Once the rollback is completed successfully, confirm that the modified version has been changed to the rollback target (e.g., V3 -> V2)

[Screen] Confirmation of Rollback Version Change

4\) Verify that the pod count has returned to normal, such as 2 -> 1.

--- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://cocktailcloud.gitbook.io/cocktail-cloud-online-en/ci-cd/pipeline.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.