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 autodeployJul 1st, 2009 | No Comments
Its been a very slow road for me and coding the last few weeks. Between constant meetings and having to rebuild my home workstation (beta –> RC), I’m surprised I’ve got anything done.
Current Status
AutoDeploy consists of internal services and a task is simply a container for the service definition and required attributes. the current services and completion % (total guess…there is no road-map so its pretty hard too tell)
ASP.NET Build – 80%
C# Build– 80%
Custom Task (MEF) – 80%
Database Migration – Not Started
Email – 80%
FileCopy – 80%
Folder Monitor – 80%
Ftp – 80%
MS...
Posted by Eric Polerecky in autodeploy, c#Jun 12th, 2009 | No Comments
Tonight I reworked in workflow, persistence, mapping, and entities in AutoDeploy. The fire draft consisted of a single entity type with long descriptive janky attributes. The new core goes something like this
Deployment has a list of tasks. Tasks can be have a task type.
Example 1 Creating a new deployment:
1: var dep = new Deployment()
2: .AddTask(
3: new FluentTask()
4: .Source("")
5: .Destination("")
6: .Type(Task.TaskType.Subversion)
7: .Save())
8: .AddTask(
9: new FluentTask()
10: .Source("")
...
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
...