Candice Yono

Deliver User Value Faster with CI/CD Integrations

Productivity Updates Community

Delivering user value quickly and reliably are key behaviors for businesses to succeed. As a PM or developer, it can be challenging to keep track of what features your team is delivering and when. It can be even harder to communicate progress to stakeholders who might not be in tune with the team’s day to day cadence. Connecting your backlog with the CI/CD tools that your team uses can provide more insight into what your team is doing, and help you better track the path to production.

Continuous Integration and Continuous Deployment

Pivotal Tracker now supports integrations with CI/CD tools to make the backlog a greater source of truth for work that a team has actually shipped. CI/CD pipelines allow you to build and automate testing for any language or platform.

What is CI and CD?

  • CI, or Continuous Integration, means automatically testing and building software after pieces of code are integrated into a shared repository.
  • CD, or Continuous Delivery, means that applications are automatically tested and pushed to production environments, and in the hands of real users.

With CI/CD integrations, you can look at the backlog and know what stories your team has deployed to production. Additionally, our Analytics page will help you track your delivery cadence, or how long it takes your team to get features in production. Currently, Tracker has three CI/CD integrations available: Concourse, Jenkins, and a custom form that allows you to add any CI/CD tool of your choice.

Project View

Track Your Team’s Delivery Cadence with New Metrics

Beyond increased visibility into the path to production, the CI/CD integrations provide teams with three new metrics to help them track how quickly they are completing work, and delivering to users. The Project Overview section of Analytics provides the following new metrics:

CI/CD analytics

  1. Time to Production: total active time on a story from start to production
  2. Wait Time: total active time on a story from acceptance to production
  3. Time Since Last Deployment to Production

What Do the Integrations Do?

We created Concourse and Jenkins Pipeline Integrations to make it easy for teams to connect builds on their production pipeline to individual stories. We also created a custom form that allows you to add any CI/CD tool of your choice.

To set up the Integration, there are two steps. First, complete a form in Tracker with the name of the integration, job URL, and the name of the resource that points to your git repository. Second, after you hit save, two code snippets will appear on the page. Copy and paste these snippets to your Concourse, Jenkins or Custom configuration file. You can read the Concourse Pipeline Integration, Jenkins Integration and Custom CI/CD Integration Help Center articles for more details.

Once you complete the steps listed above, you will be able to see whether builds have passed or failed in the expanded view of a story.

Production build passed section of expanded story

We Want Your Feedback!

Let us know what you think about these features by emailing us at or using Provide Feedback under the Help menu in Tracker. Your feedback will help us shape future feature iterations. Please don’t hesitate to get in touch with any questions or concerns. We can’t wait to hear from you - thanks in advance!