sfpowerscripts logo sfpowerscripts

This pipeline demonstrates how you can build a continous integration pipeline for if you are using  an org model of development  . Here is a snapshot of the steps we have used to configure a pipeline. The pipeline mimics creating a version number as in Continous Integration (Unlocked Packaging) pipeline to simulate version based deployment in the release pipelines and create meaninguful dashboards

This pipeline is triggered on every successfull completion of a feature branch into the develop/master branch. If the frequency is quite high, you can look into utilizing \[ci skip\] in front of the commit message to skip a trigger of this pipeline

Pipeline Snapshot

 

You can import and modify this pipeline using the file provide in the link

Tasks Involved

The steps that are part of this pipeline are (in the exact order)

  1. Increment the version number ( optional step, if you want to increment the build number or any segment number)
  2. Create a new version of the source package

Pipeline Trigger

This pipeline need to be enabled only with CI triggers, PR triggers for pipeline should be disabled. Follow this  documentation to enable this CI trigger using this link