Answer by scottn · Mar 22, 2017 at 03:19 PM
We did find a way to do per-pipeline templates with a bit of property magic. We set the pipeline name template property in Administration->Server to the following:
$[/javascript myPipeline.customPipelineNameTemplate ? myPipeline.customPipelineNameTemplate : "$[/myPipeline]_$[/increment $[/myPipeline]/ec_counters/pipelineCounter]_$[/timestamp yyyyMMddHHmmss]"]
For pipelines that we want to have a custom name, we set a property named "customPipelineNameTemplate" on the pipeline that contains the pipeline specific template. If that property exists, that template is used, otherwise, the default template is used.
Answer by nitinp · Mar 16, 2017 at 12:21 AM
We currently do not support custom template per pipeline and this will require an enhancement.
It is possible to achieve some level of distinction by altering the system level template. For example, if each pipeline has a property called runtimePrefix (which has a unique value per pipeline) then template can be changed as follows:
$[/myPipeline/runtimePrefix]_$[/myPipeline]_$[/increment /myPipeline/ec_counters/pipelineCounter]_$[/timestamp yyyyMMddHHmmss]
Then runtimes for different pipelines will have this unique prefix
Electric Cloud powers Continuous Delivery, helping organizations developing deliver better software faster by automating and accelerating build, test, and deployment processes at scale. Industry leaders like Qualcomm, SpaceX, Cisco, GE, Gap, and E*TRADE use Electric Cloud solutions to boost DevOps productivity and Agile throughput.