Skip to main content

Visual Studio Online and Team City - How to integrate them

Until now I played with Team City and different versions of TFS and GIT that were installed on premises. Today I wanted something more, I decided to connect Visual Studio Online TFS repository to my own Team City instance.
Unfortunately, I discover that even if it is possible, we need to do a special configuration to our Visual Studio Online account for that.
Below, you can find a short tutorial about what you need to do if you want to connect your Visual Studio Online repository to Team City.

TFS URL
The TFS URL that you need to use is the following, where [accountName] needs to be replaced with you own account name.
https://[accountName].visualstudio.com/DefaultCollection/

ROOT
The TFS path to your repository. In my case the path was following:
$/mssummit2014/CoolWebSite/
This can be obtained very easily from Source Control Explorer windows of Visual Studio.

USERNAME
Surprise. You cannot use by default your LIVE credentials. To be able to connect you will need to use and activate “ALTERNATE AUTHENTICATION CREDENTIALS” from Visual Studio Online portal. To be able to activate them, you need to go login on Visual Studio Online portal, go to your profile and select ‘Credentials’ tab. You’ll need to activate this feature from here, don’t forget to not use the same password as your use for your live account.

Also, I recommend to set a secondary username that can be used to connect to your account. In this way you add a little more protection to your account. The secondary user can be deleted or change is you credentials are hacked.
After you done this configuration, you can set the username with the following format:
##LIVE##\[seccondaryUsername]
Where [seccondaryUsername] is the secondary username that you crated in the portal, few seconds ago.

PASSWORD
The password that you set at previous step.



Done! Enjoy Team City!

Comments

Popular posts from this blog

Why Database Modernization Matters for AI

  When companies transition to the cloud, they typically begin with applications and virtual machines, which is often the easier part of the process. The actual complexity arises later when databases are moved. To save time and effort, cloud adoption is more of a cloud migration in an IaaS manner, fulfilling current, but not future needs. Even organisations that are already in the cloud find that their databases, although “migrated,” are not genuinely modernised. This disparity becomes particularly evident when they begin to explore AI technologies. Understanding Modernisation Beyond Migration Database modernisation is distinct from merely relocating an outdated database to Azure. It's about making your data layer ready for future needs, like automation, real-time analytics, and AI capabilities. AI needs high throughput, which can be achieved using native DB cloud capabilities. When your database runs in a traditional setup (even hosted in the cloud), in that case, you will enc...

Cloud Myths: Migrating to the cloud is quick and easy (Pill 2 of 5 / Cloud Pills)

The idea that migration to the cloud is simple, straightforward and rapid is a wrong assumption. It’s a common misconception of business stakeholders that generates delays, budget overruns and technical dept. A migration requires laborious planning, technical expertise and a rigorous process.  Migrations, especially cloud migrations, are not one-size-fits-all journeys. One of the most critical steps is under evaluation, under budget and under consideration. The evaluation phase, where existing infrastructure, applications, database, network and the end-to-end estate are evaluated and mapped to a cloud strategy, is crucial to ensure the success of cloud migration. Additional factors such as security, compliance, and system dependencies increase the complexity of cloud migration.  A misconception regarding lift-and-shits is that they are fast and cheap. Moving applications to the cloud without changes does not provide the capability to optimise costs and performance, leading to ...

Cloud Myths: Cloud is Cheaper (Pill 1 of 5 / Cloud Pills)

Cloud Myths: Cloud is Cheaper (Pill 1 of 5 / Cloud Pills) The idea that moving to the cloud reduces the costs is a common misconception. The cloud infrastructure provides flexibility, scalability, and better CAPEX, but it does not guarantee lower costs without proper optimisation and management of the cloud services and infrastructure. Idle and unused resources, overprovisioning, oversize databases, and unnecessary data transfer can increase running costs. The regional pricing mode, multi-cloud complexity, and cost variety add extra complexity to the cost function. Cloud adoption without a cost governance strategy can result in unexpected expenses. Improper usage, combined with a pay-as-you-go model, can result in a nightmare for business stakeholders who cannot track and manage the monthly costs. Cloud-native services such as AI services, managed databases, and analytics platforms are powerful, provide out-of-the-shelve capabilities, and increase business agility and innovation. H...