GoCD Pipeline Templates

GoCD Pipeline Templates

Templating helps to create reusable workflows in order to make tasks like creating and maintaining branches, and managing large number of pipelines easier.

Creating Pipeline Templates

Pipeline Templates can be managed from the Templates tab on the Administration Page.

Clicking on the “Add New Template” brings up the following form which allows you to create a fresh template, or extract it from an existing pipeline. Once saved, the pipeline indicated will also start using this newly created template.

A template can also be extracted from a pipeline using the “Extract Template” link. This can be found on the “Pipelines” tab in the Administration page.

Example

As an example, assume that there is a pipeline group called “my-app” and it contains a pipeline called “app-trunk” which builds the application from trunk. Now, if we need to create another pipeline called “app-1.0-branch” which builds 1.0 version of the application, we can use Pipeline Templates as follows

Using Administration UI

Create a template “my-app-build” by extracting it from the pipeline “app-trunk”, as shown in the previous section.
Create a new pipeline “app-1.0-branch” which defines SCM material with the branch url and uses the template “my-app-build”.

Using XML

Power users can configure the above as follows:

<pipelines group="my-app">
  <pipeline name="app-trunk" template="my-app-build">
    <materials>
      <svn url="http://my-svn-url/trunk" />
    </materials>
  </pipeline>
  <pipeline name="app-1.0-branch" template="my-app-build">
    <materials>
      <svn url="http://my-svn-url/branches/1.0" />
    </materials>
  </pipeline>
</pipelines>
<templates>
  <pipeline name="my-app-build">
    <stage name="build">
      <jobs>
        <job name="compile">
          <tasks>
            <ant target="compile" />
          </tasks>
        </job>
      </jobs>
    </stage>
  </pipeline>
</templates>

Editing Pipeline Templates

GoCD Administrators can now enable any GoCD user to edit a template by making them a template administrator.

Template administrators can view and edit the templates to which they have permissions, on the template tab of the admin page. Template Administrators, will however not be able to add, delete or change permissions for a template. They will also be able to see the number of pipelines in which the template is being used, but not the details of those pipelines.

Viewing Pipeline Templates

Pipeline Templates can now be viewed by Administrators and Pipeline Group Administrators while editing or creating a Pipeline.

Clicking on the icon indicated by arrow will display the following:

The pop-up shows the extract of the template “Services-Template” configured for the pipeline “Service_1”.

Shows the details of the job “compile-job” configured for the stage “compile”.
Indicates that the working directory set for the task is “go/service_1”, which is followed by the “$” symbol and then the command.
If any “On Cancel Task” has been configured, it will be indicated like this.
Shows the “Run If Condition” for this task.

Pipeline Templates