Shawn Talbert wrote:
> Using this approach it makes it easy to do the whole enchilada (build, test,
> tag, package, deployment) automatically via target dependencies if you
> really want to go against my advice :) I'd recommend a target chain like
> "build,test,tag,package" at most, leaving a "deployment" target for a
> separate step made by humans. In this scenario, the deployment task would do
> the SFTP transfar or use an "SFTP" task.
Note, in the workflow at my previous job, which was strictly focused on
websites, tagging was the equivalent of "release" and commit to trunk
was the equivalent of "test". There was no need for "build" or
"package" because the sites were all in-house. Once a change was
validate on the test servers (autosynced to trunk), it could be promoted
to production by a tag that matched "RELEASE-YYYYMMDDSEQ". It worked
remarkably well and made for good security (the developers didn't
strictly need to have any rights to the production server).
YMMV...
John
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Dec 10 18:02:55 2007