Afin que nos visiteurs aient accès à un maximum de contenu en français, certaines pages de ce site ont été entièrement ou partiellement traduites à l'aide d'un moteur de traduction automatique. Même si tous les efforts raisonnables ont été faits pour vous proposer une traduction fidèle à l'original, aucune traduction ainsi produite ne se veut parfaite ou du même niveau de qualité que le résultat du travail d'un traducteur ou d'une traductrice professionnelle.

Blog Planview

Mener la conversation sur le travail numérique connecté

DevOps Teams

Tasktop Gateway and Code Review

Publié le By Tasktop Blogger

Wouldn’t it be great if you could enable visibility across your entire lifecycle management tools and code review systems in your development environment? Wouldn’t it be useful to be able to trace a user story in JIRA back to the code reviews in Gerrit that are associated with it? This can be easily achieved using Tasktop Gateway. In fact, this is exactly what we use at Tasktop to increase traceability.

In this short video, we demonstrate a scenario where Tasktop Gateway sits between JIRA and Gerrit. Gerrit is a code review tool built on top of the git version control system. In our video, a developer is working on a code change related to a user story in JIRA. After the code change is submitted to Gerrit, and approved by reviewers, it will be committed to the repository. At this point, we use a hook in Gerrit to extract metadata from the commit message, and then send this information to Tasktop Gateway using the REST API. A Tasktop Gateway collection is configured to modify the JIRA story based on the JSON payload received.

By using this simple configuration we have traceability from the story to the commit and code review so that we know what was changed as a part of that work.

Articles similaires

Rédaction du contenu Tasktop Blogger