Gateway Integration Style

How do you create traceability in your end-to-end value stream? How would you connect a code commit to a story, a failed automated test to a new defect? How could you create a change request every time code is deployed?

There are lots of tools in the software delivery process, especially in the release and deploy stage, that generate events you’d want to tie into the design and implementation work done further upstream.

These types of events are “fire and forget” - they can create something new or update something that already exists, but they don’t expect anything back. As such, they don’t mandate a full-blown two way synchronization; a lighter integration can usually do the trick.

And that’s where Tasktop’s Gateway integration style comes in.

Gateway is a RESTful API for receiving these events and flowing them to other tools.

When a developer commits code in Git, Tasktop updates the Jira Software story with a link to the Git changeset.

When a test fails in Cucumber, Tasktop creates a defect in Jira.

When a code scan fails in SonarQube, Tasktop creates a defect in CA Agile Central (Rally).

When New Relic detects your system’s slowing down, Tasktop creates a defect in VersionOne.

When UrbanCode Deploy deploys code to a production environment, Tasktop creates a change request in ServiceNow.

When AppScan detects a vulnerability, Tasktop creates a defect in Microsoft TFS.

Tasktop makes all this easy by abstracting the target tool - even if it changes down the line. You just need to pass the event to us, and we’ll take care of the rest. Tasktop will flow the information to one or more target tools, based on the relevant artifact model. It’s simple and scalable.

gateway integration stylegateway integration style