Datree + CircleCi = 😍
  • Updated on 06 May 2019
  • 1 minute to read
  • Contributors
  • Share
  • Dark
    Light
Contents
Contents x

Datree + CircleCi = 😍

  • Updated on 06 May 2019
  • 1 minute to read
  • Contributors
  • Share
  • Dark
    Light

What is it?

By verifying the mention of issue ticket number in the Pull Request title and \ or branch name, you can make sure every code change is linked to your issue tracking system (e.g. Jira \ Pivotal Tracker). We patnered with CircleCi, to enable (part of) Datree's governance policy solution, as part of your CI flow.

Study: How Developers Document Pull Requests with External References
This study found that when developers are mentioning an external resource in a Pull Request - 1/3 of those mentions will be to an issue tracker system.

Why is it important?

When your GitHub account is linked to your issue tracking system, your team gets to see their branches, commit messages and pull requests in the context of the issues they are working on. This way, you can create a logical link between planing (issue tracking) and the subsequent code change (GitHub) for better collaboration, visibility and compliance.

jira-github-1

jira-github-2

How does it work?

Add our Orb to CircileCI config file and call the relevent commands. Every time a CircleCi build job is triggered, the commands in the config file will execute.

🚓 Avilable policies (commands):

Every build will verify the branch name includes a reference to an issue. Branches are linked automatically to your issue tracking system if the issue key included in the branch name (e.g. git branch “features/PROJECT-549”)

Every build triggered by a Pull Request will verify the Pull Request title includes a reference to an issue. Pull requests are automatically linked if the issue key included in the pull request title (e.g. “PROJECT-123 fix: Update auth flow for new users”)

Who gets it?

All CirecleCi user. There is no need to signup to Datree to use this feature.

Was this article helpful?