Creating a Pipeline

Prerequisites

A build job has been created. For details, see Creating a Source Code Job or Creating a Package Job.

Creating a Pipeline

1. Log in to ServiceStage.
2. Choose Continuous Delivery > Pipeline.
3. Click Create Pipeline and set basic pipeline information by referring to the following table. Parameters marked with an asterisk (*) are mandatory.

   Parameter	Description
   *Pipeline	Pipeline name. Enter 1 to 99 characters. Start with a letter. Only use letters, digits, periods (.), at signs (@), and hyphens (-).
   *Enterprise Project	Enterprise projects let you manage cloud resources and users by project. It is available after you enable the enterprise project function.
   Description	Pipeline description. Enter up to 255 characters.

4. Click Back to Template, and select and configure a pipeline template by referring to the following table.
   ServiceStage provides built-in pipeline templates for typical scenarios. After a pipeline template is selected, a pipeline model is automatically generated.

   Template Name	Description
   Empty Template	You need to add a pipeline model. Click the Empty Template card. Add a build job to generate an image package. Click Select Build Job. Select a build job. If there is no build job, create one by referring to Creating a Source Code Job or Creating a Package Job. Click OK. Repeat this step to add more build jobs. The build job must belong to the enterprise project set in 3. Add a deployment environment to deploy the image package generated by build job to the environment. Click Add Environment. Click and enter an environment name. Select the deployed application component in the build job and click OK. If there is no application component in the environment, create and deploy one by referring to Creating and Deploying a Component Based on a Container Using UI Configurations and Creating and Deploying a Component Based on a Container Using YAML Configurations. Click Change Component to select another component. Select Build Job: Select the added build job for build. Build Output: Set the archive path of the image generated by the build job. Click OK. Repeat this step to add more deployment environments. Configure pipeline approval to determine whether to deploy the image package generated during build to the environment. Click on an environment card. Set Approval Mode. By all: The image package generated during build can be deployed in the environment only after all selected approvers approve the deployment. By one person: The image package generated during build can be deployed in the environment after any approver approves the deployment. Set Approved By. You can select multiple approvers. The system automatically loads all subaccounts of the account. Click OK.
   Simple Template	The "build" model is automatically added to compile and build the source code of the code library. Select Simple Template. Click Create. Add a build job to generate an image package. Click on a build job card. Select a build job. If there is no build job, create one by referring to Creating a Source Code Job or Creating a Package Job. Click OK. Click Select Build Job to add multiple build jobs. The build job must belong to the enterprise project set in 3.
   Common Template	The "Build/Production environment" model is automatically added to compile and build the source code of the code library, and the generated software package or image is continuously released to the production environment. Select Common Template. Click Create. Add a build job to generate an image package. Click on a build job card. Select a build job. If there is no build job, create one by referring to Creating a Source Code Job or Creating a Package Job. Click OK. Click Select Build Job to add multiple build jobs. The build job must belong to the enterprise project set in 3. Add a deployment environment to deploy the image package generated by build job to the environment. Click Add Environment. Click on the empty environment card. The Add Environment dialog box is displayed. Click and enter an environment name. Click to save the environment name. Select the deployed application component in the build job and click OK. If there is no application component in the environment, create and deploy one by referring to Creating and Deploying a Component Based on a Container Using UI Configurations and Creating and Deploying a Component Based on a Container Using YAML Configurations. Click Change Component to select another component. Select Build Job: Select the added build job for build. Build Output: Set the archive path of the image generated by the build job. Click OK. Repeat this step to add more deployment environments. Configure pipeline approval to determine whether to deploy the image package generated during build to the environment. Click on an environment card. Set Approval Mode. By all: The image package generated during build can be deployed in the environment only after all selected approvers approve the deployment. By one person: The image package generated during build can be deployed in the environment after any approver approves the deployment. Set Approved By. You can select multiple approvers. The system automatically loads all subaccounts of the account. Click OK.

5. Determine whether to start the pipeline:
   • If yes, click Create and Execute to save the settings and start the pipeline. After the pipeline is started, its status is Successful .
     

     If the pipeline need to be approved, it is in the To be confirmed state during component deployment. The pipeline can continue to run only after you notify the approvers for approval. For details, see Approving a Pipeline.

   • If no, click Create to save the settings only. After the pipeline is created, its status is Not executed.

   To view the pipeline, see Viewing Pipeline Details.