![]() ![]() To allow TeamCity to access Bitbucket data, you need to create an incoming application link in Bitbucket to grant TeamCity required permissions.Ĭreate a new connection and choose the "Bitbucket Server / Data Center" option. Integration with Bitbucket Server and Data Center currently allows you to:Ĭreate a project and build configuration from Bitbucket URL If you configure multiple Bitbucket connections, the server URL will be displayed next to each icon, so it is easier to distinguish the server in use. TeamCity will be granted access to your repositories. Click it to authorize TeamCity in your Bitbucket profile. Go back to the connection form in TeamCity.Ī Bitbucket icon will become active in several places where a repository URL can be specified. You need to use them for creating a new OAuth consumer in Bitbucket. The Bitbucket Cloud connection form provides multiple parameters. Integrate with a Bitbucket Cloud issue tracker. Bitbucket CloudĪ connection to Bitbucket Cloud can be used to: In this case, the server URL will be displayed next to the VSTS icon to distinguish the server in use. It is possible to configure several VSTS connections. ![]() When configuring Commit Status Publisher for Git repositories hosted in TFS/VSTS, the personal access token can be filled out automatically if a VSTS project connection is configured. TeamCity will be granted full access to all the resources that are available to you. Click the icon, log in to Azure DevOps Services and authorize TeamCity. The connection is configured, and now a small Azure DevOps Services icon becomes active in several places where a repository URL can be specified: create project from URL, create VCS root from URL, create Azure DevOps Server VCS root, create Azure Board Work Items tracker. The server URL in the format or your Azure DevOps Server as Log in to your Azure DevOps Services account to create a personal access token with All scopes as described in the Microsoft documentation.Ĭontinue configuring the connection in TeamCity: on the Add Connection page that is open, specify ![]() The page that opens provides the parameters to be used when connecting TeamCity to Azure DevOps Services. ![]() Select Azure DevOps PAT as the connection type. To configure an Azure DevOps PAT connection: It allows creating a project from a Git or TFVC repository URL, creating an Azure DevOps VCS root, or integrating with the Azure Board Work Items tracker. This type of connection uses personal access tokens. To activate the Azure DevOps Services authentication on your server, proceed to enabling the respective authentication module. Specify the application scope that must be the same as the scope of the created Azure DevOps OAuth App. Go back to the connection form in TeamCity and enter the Azure DevOps Services URL, the new application ID, and client secret. When created, copy the app's ID and client secret. Go to the Register Application page in Azure and create a new app using the provided parameters. TeamCity will display the Callback URL and scopes required for registering an OAuth application in Azure DevOps. Select Azure DevOps OAuth 2.0 as the connection type. In Project Administration | Connections, click Add Connection. To configure an Azure DevOps OAuth 2.0 connection: This connection can be used for authenticating users via Azure DevOps as well as creating projects and build configurations. It uses the OAuth 2.0 protocol based on JWT tokens and requires creating a dedicated app in your Azure profile. This type of connection supports only Azure DevOps Services. There are two types of Azure DevOps connections in TeamCity:Īzure DevOps OAuth 2.0 allows signing in to TeamCity via an Azure DevOps Services account and creating TeamCity projects from Azure Git and TFVC repositories.Īzure DevOps PAT allows creating TeamCity projects from Azure Git and TFVC repositories. After configuring the proxy, remember to also set the new address as the Server URL in Global Settings of TeamCity. When configuring a callback URL for a connection, you need to specify all URLs by which the current server can be accessed. If your TeamCity server is installed behind a proxy, it is important to ensure that this is reflected in the connection settings, if applicable. If you add a connection in the Root project, it will become available on the whole server. When created, a connection can be used in all the nested subprojects of the current project. Select the connection type, set its Display name to distinguish it from the others, and configure it as described below. To add a connection, go the target project's settings, open the Connections page, and click Add Connection. This article gives instructions on how to add each type of connection. You can reuse these presets in various places on the server: when creating projects, configuring notifications, integrating with issue trackers, and more. TeamCity allows storing presets of connections to external services. ![]()
0 Comments
Leave a Reply. |