We’re Here to Help!!

Find A Solution, Learn Best Practices & Get Support 24x7

Branch level pipelines

Follow

Flosum has a brand new way of doing CICD. This version of Flosum introduces the pipeline record. This record can be created and accessed via the settings tab. 

PipelinesSS1.png

Pipeline records can be created with the parameters :

Pipeline Name: Name of pipeline

Deployment Mode: 

STAND BY: No action is taken

VALIDATE: Automatically validates on commit the committed components in the branch or Repository that this pipeline is associated with.

DEPLOY: Automatically deploys on commit the committed components in the branch or Repository that this pipeline is associated with.

Pipeline Deployment Style:

STOP ON FAILURE: With this setting enabled, when the deployment of an org in the sequence of orgs fails, the deployment does not proceed to the subsequent orgs in the sequence. 

CONTINUE ON FAILURE: With this setting enabled, when the deployment of an org in the sequence of orgs fails, the deployment still proceeds to the subsequent orgs in the sequence. 

Available/Selected Organizations:

Select the organizations where you would like the committed components to be automatically deployed. 

Run tests on Deployment: 

Select the type of tests that you would like to run for the automated deployments. This has a selection of the same test options as a manual deployment. 

 

 Once a pipeline is saved, pipelines can be associated with a branch or Repository to enable them for automated deployments. Please refer to the screenshots below. 

 

RepoPipelineDefine.png

 

 BranchPipelineDefine.png

 

Print Friendly and PDF
Was this article helpful?
0 out of 0 found this helpful

Comments