Posted by Eric Polerecky in ASP.NET, AutoDeploy.NET, GitHub, MEF, Unity, autodeploy, fluent interfaceJul 20th, 2009 | No Comments
First; When I pushed to GitHub I decided to rename the project to AutoDeploy.NET.
In the hopes of keeping my sanity and in the context of working in an organization that strictly follows a 50+ page “release management handbook” I started working on AutoDeploy.NET; a deployment automation tool.
As with all my personal projects I took an academic approach to the design and implementation. Instead of building an entire application I created a class library (dll) and used a few 3rd party libraries that I was either unfamiliar.
Class Library
My thought here is that by just creating the class library...
Posted by Eric Polerecky in autodeploy, fluent interfaceJun 11th, 2009 | No Comments
A class library to help automate simple deployment tasks.
Warning: pre-alpha.
AutoDeploy has 2 main components; deployment objects and a deployment controller. A deployment object holds n+1 deployment tasks. The deployment controller is responsible for executing scheduled, interval and on demand deployment tasks.
AutoDeploy is complete enough for me to start dog fooding it this week. I’ll have a road-map soon after.
Features
Deployment Controller
Scheduled Deployments
Interval Deployments
SVN Checkout
SVN Commit
ASP.NET Build
Example 1: Fluent Interface, SVN Checkout, Interval
...