How can we get the current pipeline execution specific counter?
I’m using $[/myPipeline/ec_counters/pipelineCounter] to track a counter at pipeline run level. However, I realized if I get the value in step 1 below, the value is 100. If I in parallel run another pipeline run, this first pipeline run will return 101 in step 3. (i.e. it got unexpectedly incremented by another pipeline) How can I ensure that the pipelineCounter remains static throughout the entire pipeline run? Is setting a property the only way? Is there a unique counter I can use PER pipeline run
In this case, we can generate a global property that using regular expressions can obtain the pipeline execution number according to the Pipeline running name (if this contains this value). In our example, the current value for "CloudBees CD Menu -> Server -> Settings -> Pipeline name template" is the default one "$[/myPipeline]_$[/increment /myPipeline/ec_counters/pipelineCounter]_$[/timestamp yyyyMMddHHmmss]" As you can see it´s using the pipelineName + _ + the pipelineCounter + _ ... Knowing this we can develop a regular expression to get the value of this pipeline counter. In my case, I have created a pipeline "getPipelineCounter" and in my latest execution, my Pipeline Runtime Name was: "getPipelineCounter_37_20200916205110", that is coherent with the Pipeline name template and according to it, the value 37is the specific execution number for this running.Knowing this, a regular expression to get this execution number could be: "getPipelineCounter_37_20200916191918".match("^getPipelineCounter_(\\d+)")[1] CloudBees CD allow us also to get these specific properties for an specific running using the properties: <ul> <li> myPipelineRuntime.name -> getPipelineCounter_37_20200916191918 </li> <li> myPipeline.pipelineName -> getPipelineCounter </li> </ul> So the previous regular expression could be rewritten as: myPipelineRuntime.name.match("^" + myPipeline.pipelineName + "_(\\d+)")[1] And used as a property in a pipeline context as: $[/javascript myPipelineRuntime.name.match("^" + myPipeline.pipelineName + "_(\\d+)")[1]] So using this literal (adapting the regular expression to your pipeline name template) will allow you to get the pipeline execution number. In addition, CloudBees CD allows you to create server scope properties, that could be used anywhere in the system. They are created in "CloudBees CD Menu -> Server -> (at the bottom) Custom Server Properties" Here, you can create a new Nested Sheet "globalProperties", and inside this sheet, a property "getPipelineRunNumber" with the property value previously used to get this execution number $[/javascript myPipelineRuntime.name.match("^" + myPipeline.pipelineName + "_(\\d+)")[1]]** ![GlobalProperty][1] With this approach, knowing the current pipeline execution number is as simple as adding a reference to the "property/server/globalProperties/getPipelineRunNumber· For example, we could add in a pipeline a command instruction with the content echo "runNumber: $[/server/globalProperties/getPipelineRunNumber]" And the output result of this operation will be: ![GetPipelineRuntimeNumber][2] [1]: /storage/temp/538-globalproperty-lowquality.png [2]: /storage/temp/537-runnumber.png
