Child pages
  • Components participating in TFS / Azure DevOps check-ins synchronization

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 23 Current »

Contents        

In order to successfully synchronize TFS / Azure DevOps (formerly VSTS) check-ins to Jira a number of components has to cooperate. Communication between all these components is explained on this page.

The diagrams below contains following elements:

  • Jira User - personal computer of Jira user.
  • Jira Server - Jira instance with TFS4JIRA plugin installed.
  • TFS4JIRA Synchronizer - external application coming with TFS4JIRA (available to download from Spartez home page).
  • TFS4JIRA Web Application (only for Jira Cloud) - cloud application hosted and maintained by Spartez.
  • TFS / Azure DevOps (formerly VSTS) - TFS server or Azure DevOps (formerly VSTS) instance which we will synchronized with Jira.

Check-ins synchronization for Jira Standalone

When synchronizing check-ins for Jira Standalone, TFS4JIRA plugin communicates directly to Synchronizer application. 

architecture-jira-standalone

Check-ins synchronization for Jira Cloud

In case of Jira Cloud, there is an additional component between Jira plugin and TFS4JIRA Synchronizer. This component is called TFS4JIRA Web Application and it serves as a proxy server.

architecture-jira-cloud

This document is part of tutorial on configuring TFS / Azure DevOps (formerly VSTS) check-ins synchronization.

Please go to one of following pages to continue:

  • No labels

This page has no comments.