The introduction of user friendly pipeline wizards in Go 2.2.1 has resulted in reduced functionality around administering pipelines. We used to be able to view and edit the pipeline XML by hand, which was very useful. Crucially, we were able to copy the XML and store it in our project for visibility of the changes made to it over time, and to keep a back up.
Also, we used to edit the pipeline group XML to create branch pipelines, which were similar to our trunk pipeline but had slightly different jobs. We take the trunk XML and apply an XSLT transform to it to create the branch pipeline XML. Some of the jobs have slightly different resources / tasks in our branch pipeline.
I'm aware that the Template feature in Go is meant to be used to have multiple pipelines running against different branches using the same pipeline design. However, it's not possible to introduce variations between pipelines in this way - I'm about to raise a feature request to allow this.
As a result of these changes, we need to be Go Administrators to create pipelines directly from XML, using the 'Source XML' tab in Administration. We are currently trying to convert most of the Go Admins to being Pipeline Group Admins, as we are hoping to use Go to deploy to our production environment. We do not want our developers to be able to alter the pipelines which will run on a subset of production agents (which we are hoping to partition using a production 'environment'). We also do not want developers to be able to access secure artefacts in the live deployment pipelines.
This feature change has essentially prevented us from using this version of Go to deploy to production, since we would no longer be able to effectively create branch pipelines if we revoked the Go Administration permission.
Please sign in to leave a comment.