Child pages
  • Check-ins with Jira Cloud and Azure DevOps Cloud

Contents        

Components and Deployment

Interactions

Encryption

TFS4JIRA Synchronizer and TFS4JIRA OnDemand communicate over HTTPS, in addition the payload is encrypted with a tenant - specific key, using standard .NET implementation of the Advanced Encryption Standard (AES) algorithm.

Synchronizer Endpoints

In order for the check-ins functionality to work, the following TFS4JIRA Synchronizer endpoints need to be visible from the outside world, as they are used by the TFS4JIRA OnDemand application:

  • GetIssueAssociatedChangesets

  • GetIssueChangesets

  • Rescan

  • TestConnection

GetIssueAssociatedChangesets

Retrieves check-ins associated with a Jira issue via TFS commit Note, as described in Associating using a check-in note.
Input: Jira url and issue key(s).
Output: Check-ins.

GetIssueChangesets

Retrieves check-ins associated with a Jira issue via TFS commit message text, as described Associating using a check-in comment.
Input: Jira url and issue key(s).
Output: Check-ins.

Rescan

Scans target repository one more time, in an attempt to find a missing check-in.
Input: repository, change set.
Output: success flag.

TestConnection

Tests connection between TFS4JIRA OnDemand application and TFS4JIRA Synchronizer.
Input: Jira url, sample data to verify encryption correctness (literally, “test” sting).
Output: Jira url, number of repositories configured, sample data.

Check-ins Schema

See json schema attached

TFS4JIRA Check-ins.schema.json

  • No labels

This page has no comments.