Project/Build configuration guidance
Hello, we are looking into migrating our current CI setup from Jenkins to TeamCity.
Our main project is composed of three parts and we would like guidance on how to best configure this in TeamCity.
We currently have 4 jobs in Jenkins :
- .NET debug build and unit tests x2 (we have 2 webservice in .NET both living in a single git repository)
- PHP/JS bundling and unit tests
- .NET release build, PHP/JS bundling and E2E tests
What would be the best way to configure this in TeamCity? Do we create a single project and recreate those 3 jobs as 3 build configuration or would we be better of creating different projects for .NET and PHP/JS (those correspond to two git repositories)?
Please sign in to leave a comment.
There is a dedicated documentation page regarding the Jenkins to TeamCity migration: https://www.jetbrains.com/help/teamcity/2023.11/jenkins-to-teamcity-migration-guidelines.html.
Please take a look at it for general recommendations.
There is no best way in regard to project structure; the best way is one that best suits your requirements. In general, if you have 2 different VCS roots, and their builds are unrelated (i.e., the artifacts are not used in dependencies, etc.), having them as separate projects may be more convenient.
Best regards,
Anton
Oh thanks I did not find or think to search for this migration guide.
Since in our case both VCS roots are used to create one final product used in our E2E tests (using generated artifacts from both VCS roots) I think we are going to make them share the same project.
Thank you again!