Urban Deploy is the latest, bleeding-edge deployment tool created by Urban Code, the same creators of Anthill Pro. More information about uDeploy can be found here:
http://www.urbancode.com/html/products/deploy/default.html
Since this is such a new tool, with perhaps about 9 months on the market since the date of this post. There are some features of this tool that are not documented so well. I’ve been working with it, in an attempt to migrate deployment workflows out of Anthill Pro into uDeploy. The primary reason for this is because uDeploy provides something very specific that Anthill Pro does not. The means to connect singular versions of deploy-time components into what is referred to as a ‘snapshot’. Some people call this component based deployment. The general idea is that my application consists of a collection of components, each with their own versions and configurations. I want to be able to change any of these versions of these components and elegantly deploy them to test and see if they are going to work together. I also want to add and remove additional components. In order do this well, you would need to either use uDeploy, get very fancy with AnthillPro (which we’ve done) or write your own mechanism (which I’ve done, but I prefer uDeploy at this point).
As the effort moves forward using uDeploy, we see lots of variables being used in the application. I wanted to have a list of all the predefined vars, and I was luckily able to obtain one, right from the horses mouth. Here it is:
${p:version.name}
${p:version.id}
${p:component.name}
${p:component.id}
${p:resource.name}
${p:resource.id}
${p:application.name}
${p:application.id}
${p:environment.name}
${p:environment.id}
${p:
${p:component/
${p:environment/
${p:resource/
${p:resource/
${p:application/
All of the following are comma-separated series of name=value, including each property on the given object.
${p:component/allProperties}
${p:environment/allProperties}
${p:resource/allProperties}
${p:system/allProperties}