Backing-up and Restoring BuildMaster
January 5, 2012
This article has been moved to: http://inedo.com/support/kb/1001/backing-up-and-restoring-buildmaster
A collection of articles regarding software best-practices, technologies, and more.
January 5, 2012
This article has been moved to: http://inedo.com/support/kb/1001/backing-up-and-restoring-buildmaster
May 17, 2011
We are pleased to announce that BuildMaster 2.4 has been released!
BuildMaster’s automated deployment system is designed to be a repeatable method in which to release software. Sometimes there are cases when one-time manual changes must be made to an environment before software can be promoted to it. For example, if you’ve just added a new website or service and wish to have BuildMaster automate its deployment, you must actually create that website in IIS/Apache or register the service before it can be deployed:
You can add a step to any deployment plan that will pause until all change controls in a specific group have been performed for an environment, or even a promotion requirement (introduced in the previous release) that will block promotion to the next environment until all change controls have been performed for that environment.
BuildMaster will maintain a history of all change control performances and indicate which environments the change control was performed on the release details page.
In a previous blog post, Alex recently described methods for securing an API, which is now included with this release of BuildMaster.
Previous installations of BuildMaster required the web application to run on IIS. This newest release introduces a self-contained web server that removes the dependency on the IIS web server. Additionally, the BuildMaster installer will work on Windows XP! This feature brings us one step closer to our BuildMaster Express goal.
Despite the fact that BuildMaster contains an ever-growing number of features, many of our customers do not always require all of them to be active/visible for every application managed through the software. Release 2.4 also includes the ability to granularly enable or disable specific features either across the complete application portfolio, or for specific applications:
Feel free to try it out for yourself at http://inedo.com/downloads/buildmaster !
March 21, 2011 1 Comment
We are pleased to announce that BuildMaster 2.3 has been released! In addition to some exciting new features, trying BuildMaster is easier than ever. Just download and install; no registration required.
Often, many requirements must be met by a build before it may be promoted from one environment to the next. For example, company policy may require that all unit tests of a build have passed before a build may progress past an Integration environment. Previously, this could be accomplished in BuildMaster using Manual Actions, but with the new Promotion Requirements feature, BuildMaster can enforce it automatically.
Of course, Promotion Requirements are fully extensible via command line extensibility or a simple C# API, allowing virtually any type of rule to be implemented. Promotion Requirements are available in BuildMaster Enterprise Edition.
A common development and architecture pattern is to have a common framework that is used by multiple applications. When the framework is updated, it may be desirable to initiate a new build of all applications which have the framework as a dependency.
BuildMaster now provides actions to Build/Promote all dependent applications as part of any deployment plan.
Need a quick answer to a quick question?
With the new Live Help link, you can start chatting with support instantly.
As always, we are continuing to add support for additional development tools. With BuildMaster 2.3, we have provided integration with:
If there are any tools you think we should add to the integration list, just let us know.