Child pages
  • Required network configuration

Contents        

This page contains information on how TFS4JIRA components communicate with one another and therefore what networking rules should be provided (e.g. in terms of port forwarding) in order for the product to work. 

Below you'll find detailed information for each Jira and TFS /Azure DevOps supported variants:


Legend:

network_legend

Jira Server + TFS / Azure DevOps Server

network_jira_server_onpremises_tfs

Jira Server + Azure DevOps Services

network_jira_server_microsoft_hosted_tfs

Jira Cloud + TFS / Azure DevOps Server

Note: In this configuration our TFS4JIRA OnDemand checkins component hosted on tfs4jira-ondemand-checkins.spartez.com connects (red line) to your TFS4JIRA Synchronizer application using HTTP/HTTPS calls. You should configure your firewall in such a way that the web interface of your Synchronizer application will be reachable from tfs4jira-ondemand-checkins.spartez.com. In most cases it means you should open port 80 (for HTTP) or 443 (for HTTPS) for incoming connections from tfs4jira-ondemand-checkins.spartez.com (18.195.184.68), but the port may vary depending on your configuration.


network_jira_cloud_onpremises_tfs

Jira Cloud + Azure DevOps Services

Note: In this configuration our TFS4JIRA on-demand checkins component hosted on tfs4jira-ondemand-checkins.spartez.com connects(red line) to your TFS4JIRA Synchronizer application using HTTP/HTTPS calls. You should configure your firewall in such a way that the web interface of your Synchronizer application will be reachable from tfs4jira-ondemand-checkins.spartez.com. In most cases it means you should open port 80 (for HTTP) or 443 (for HTTPS) for incoming connections from tfs4jira-ondemand-checkins.spartez.com (18.195.184.68), but the port may vary depending on your configuration.


network_jira_cloud_microsoft_hosted_tfs


  • No labels

This page has no comments.