A
asthomas
Guest
There's quite a bit more to it with making deployments than creating releases. Creating a release is a simple marker in a workspace that can be used for imports and deployments of changes from a workspace up to a certain point in time. Think of it as a marker on a timeline. For deployments, you need to create a release as well as a site (deployment recipient) for deployments before you can create a deployment. If you have not done so already, I would strongly recommend going through the RTB documentation on deployments - as it is important to understand the various requirements to work with this. We have actually added support for automating deployments in the Automation Toolkit, which Jeff has referred to a few times. The same pre-requisites apply here as well for being able to use this. There are some additional things needed with setting up config files and marking deployment sites for automated deployments before you can automate this. I would say that using the deployments feature is an advanced feature - and would also suggest that the other automation features supported by the toolkit have been set up and tested before using this. The toolkit is currently available as open source, and you can have a look at this to see how this works.
Continue reading...
Continue reading...