Jun 122009
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("")
11: .Destination("")
12: .Type(Task.TaskType.AspnetBuild)
13: .Save()
14: );
Deployments and Tasks can be scheduled or interval execution. I’m thinking right now that Task level interval settings will override deployment settings. This will allow you to schedule an entire deployment at X with a single task happening outside of that window. For example; you might want your working copy updated every 10min but have trunk moved to the dev server, an tag created and an email sent off at the end of the day.
