Seeking Advice on Migrating Over 200 Bitbucket Repositories to TeamCity
Hello,
I am currently a student assigned to evaluate the feasibility of transitioning our Jenkins systems to TeamCity. As part of our software development, we use Maven for building, and our codebase is distributed across more than 200 Bitbucket repositories.
I am looking for insights or guidance on how to efficiently import these repositories into a TeamCity on-premise. So far, I have only been able to find manual methods for setting up each repository individually. Is there a more comfortable way to automate this process or possibly a feature I might be overlooking that can facilitate this import?
Furthermore, in our current setup, we manually input dependency snapshots. Is there a way in TeamCity to automate this or manage it through an API?
Any assistance or suggestions from those with experience in large-scale TeamCity implementations, especially concerning integration with Bitbucket and Maven, would be greatly appreciated.
Please sign in to leave a comment.
This documentation section has some vital points regarding the Jenkins to TeamCity transition: https://www.jetbrains.com/help/teamcity/2024.03/jenkins-to-teamcity-migration-guidelines.html.
Now, for the automation of the process, there are two methods (you can use any of them or combine):
1. REST API: https://www.jetbrains.com/help/teamcity/2024.03/teamcity-rest-api.html
2. Kotlin DSL, which allows you to store projects as Kotlin script in the VCS: https://www.jetbrains.com/help/teamcity/2024.03/storing-project-settings-in-version-control.html
You can add .teamcity directory to your repository, store the project settings in Kotlin DSL format in it, and then use REST API to create a project with the VCS root and enable versioned settings for the project. The settings will then be synchronized from the VCS.
Or you can use REST API for everything; it allows you to define all project/build configuration settings.
Best regards,
Anton