Auto builds

So, we have set up TeamCity for CI, and publish of release 'zip' files (compiled code that needs copied to the webserver) and the kicking off of a tool called dbbuild that manages our DBs. Questions are:
When that publish completes successfully in TC, can we easily 'start' a build to DEV integration environment. Then can we schedule this to run (if successful in installing in DEV) that night to TEST.

Lastly, can we schedule a PROD release once we are done for hte middle of the night and have it alert us via text if it fails?

Right now, we have this pretty much all working via batch files and using TC build configurations to kick the batch files....however, promotion, etc is intriguing.

In addition, we don't like the non-graphical configuration, etc of bathc files as it is not overly intuitive (but works fine). Please let me know how this would work in your environment.

Originally our organization mandated octopus, but has since undone that mandate, so I'm trying to see what options I have...The challenge is in general we have it working, so cost may be the reason we don't convert, but that is something to understand after a POC.

Thoughts?

Product: BuildMaster
Version: 4.8.6

Hi, I'll try to answer the various questions here...

When that publish completes successfully in TC, can we easily 'start' a build to DEV integration environment.

Yes, for this , you may want to use a "URL-based Trigger" to import the build files from TC.

Lastly, can we schedule a PROD release once we are done for hte middle of the night and have it alert us via text if it fails?

You can schedule the promotion / deployment, and set up an event listener to email you on failure. These are extensbile, so if the SMS is needed (instead of email), you can either have a script call an SMS gateway or write an extension to do that.

In addition, we don't like the non-graphical configuration, etc of bathc files as it is not overly intuitive (but works fine). Please let me know how this would work in your environment.

Sure, you can run a batch/cmd file... unless it's prompting for input (like by using PAUSE command) or doing other things that can only work interactively. But, you'll find out quickly what works / doesn't. Sometimes it will be easier just to use the built-in actions in BuildMaster.

Originally our organization mandated octopus, but has since undone that mandate, so I'm trying to see what options I have...The challenge is in general we have it working, so cost may be the reason we don't convert, but that is something to understand after a POC.

For a comparison check out A Comparison: BuildMaster vs. Octopus Deploy .