Integrating TeamCity and BuildMaster
Although BuildMaster has Continuous Integration (CI) features, it is not designed solely as a CI server. JetBrains
TeamCity, on the other hand, is designed specifically to solve the problem of CI and has several features that
BuildMaster does not. For a more detailed comparison, see
KB #1023: BuildMaster vs. TeamCity.
By integrating with BuildMaster, different users can easily deploy TeamCity artifacts to various
environments, whether in-house or on the cloud.
This combination of tools offer several advantages:
- Deploy from existing TeamCity configurations
- Use advanced features only offered by TeamCity
- Maintain separation of build/deployment responsibilities
Getting Started with TeamCity and BuildMaster
To get started, check out
Deploying a TeamCity Build in BuildMaster
The Inedo Den has arrived!
We'll tidying up the Den and migrating/redirecting these pages in the coming weeks, but in the meantime, feel free to learn about the BuildMaster integrations/extensions here, or there.
This functionality is delivered as a BuildMaster Extension and can be installed or upgraded from within BuildMaster. See installation instructions for more details.
The source code for this extension is available on GitHub: View on GitHub