Skip to content

CircleCI Pipelines


SpiraTest, SpiraTeam, and SpiraPlan (from here on called SpiraPlan) integrated seamlessly with CircleCI in a number of ways. In this section we discuss SpiraPlan's CircleCI Pipelines reporting integration.

You can easily configure your CircleCI Pipelines to report against a release and create a new build in SpiraPlan each time they run. This let's you see the health of your CI/CD process within SpiraPlan.

CircleCI SpiraApp

You can also let end users start CircleCI Pipelines from within SpiraPlan itself. To do so you will need to enable and configure the CircleCI SpiraApp

The integration has two parts, which are discussed below:

  1. Setting things up in SpiraPlan (in the product and in its template)
  2. Configuring CircleCI (by adding a custom webhook to your repo)


  1. Create a release custom property (plain text) called "circleci-branch-name" in SpiraPlan
  2. Add the name of the CircleCI project, surrounded by square brackets, into the product description (e.g. "[my-new-circle-ci-project]")
  3. Link a release to your CI/CD code branch by entering the branch name into the custom property on the release page in SpiraPlan
  4. In CircleCI, create a webhook with a url in the form: {{base url}}/Services/Webhooks/BuildService.svc/CircleCI?username={{username}}&api-key={{api key}}
  5. Make sure the user in the webhook has access to the product and can create releases in that product

Setting up the integration in Spiraplan

The integration with CircleCI Pipelines works by having a dedicated custom field for CircleCI. This lets you link a release or sprint to a specific branch in a CircleCI repo. In SpiraPlan we need to specify the branch name. Then from CircleCI we configure our specific repo to talk to the correct SpiraPlan product.

The first step in SpiraPlan is to create a release custom property:

  • As a product template administrator open the template admin menu for the relevant product(s). These are products that you want to integrate with CircleCI
  • Go to the Releases Custom Properties page
  • Add a new custom property called "circleci-branch-name" that is of type Text (not rich text)

Custom property definition popup

Next, we have to add the CircleCI project name into the SpiraPlan product description, so that the two are linked together.

  • As a system administrator, go to System Administrtation > View/Edit Products
  • Edit the relevant product
  • Add the name of the CircleCI project, surrounded by square brackets, into the product description (e.g. "[my-new-circle-ci-project]")
  • Click "Save"

Finally, in your SpiraPlan product itself (not administration):

  • Find the release you want to connect to CircleCI
  • Set the "circleci-branch-name" to the exact name of the branch in the relevant CircleCI repo (for instance "develop")
  • Save the release

Release list page with custom property filled in

Setting up the integration in CircleCI

In CircleCI we now need to setup our repo to talk to the SpiraPlan each time a Pipeline builds. To do this, you need to add a dedicated webhook. This means that when the CircleCI Pipeline(s) completes, CircleCI will send the results to SpiraPlan via that webhook. SpiraPlan processes that data and adds it as a build to the correct release, in the correct product.

  • Go to the Settings > Webhooks page of the CircleCI repo

Project settings

  • Click "Add Webhook"
  • Enter a Webhook name (SpiraPlan does not use this field)
  • Enter the URL (see below)
  • The secret token is not used by SpiraPlan can be left blank
  • Make sure "Certificat verification" is checked (default)
  • Make sure that in the Events section, "Workflow Completed" is checked
  • Click "Add Webhook"

Add webhook page

The webhook URL

The webhook URL is made of different parts.

  • First get the base url of your instance - for instance This is the start of every URL you use when using SpiraPlan
  • Add the following to the end of that URL /Services/Webhooks/BuildService.svc/CircleCI
  • Add your SpiraPlan user authentication to the end of this url. This needs a username and an api-key. The user must be a member of the relevant product and be able to create releases. This part of the URL looks like ?username={{username}}&api-key={{api key}}

The final URL will look like this:{11111111-1111-1111-1111-111111111111}

Run the Action

When an Action on the CircleCI project next runs (either from CircleCI, or with the CircleCI SpiraApp) it will report its results to SpiraPlan. SpiraPlan finds the first product that has the project name in its description. SpiraPlan then looks the first release in that product that has the repo branch in the correct custom property that the CircleCI Pipeline was run against.

SpiraPlan creates a build against that release, with the key information, including the build status.

Build list on the release details page

You can click on the build name/link to open its build details page. The build will also appear on any relevant widgets in SpiraPlan.