TeamCity vs BuildMaster [closed]

Question

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.

Closed 9 years ago.

Somebody mentioned BuildMaster to me lately as build management environment.

http://inedo.com/buildmaster/features/all-features

Does anybody have any experience with this one. I would like to know how it stacks against TeamCity ?

Answer 1

As a developer for BuildMaster, I can say that TeamCity and BuildMaster are different products... the main difference being that TeamCity is a Continuous Integration server (i.e. it will automatically take code from SCM, build it, then put an artifact on an integration server), while BuildMaster is designed to do this and take your builds through various environments (dev, test, production, etc.) while also:

• managing database updates
• providing a mechanism to manage and deploy configuration files (e.g. web.config)
• adding on an optional workflow process (e.g. you can add required approvals before promoting a build) if you desire it
• manage application and artifact dependencies
• etc...

Some people even use TeamCity for CI then let BuildMaster handle deployment of the artifact, DB, and configuration files.