I looked at cruise and really liked its pipeline, as it gives QA the ability to push buttons and deploy code manually once it passes manual QA. But the funds don't appear to stretch that far. Is there an equivalent, or a workaround, in TeamCity? I'll be using Phing, which I know I can use to update working copies & deploy that way, but our QA (and therefore deployment) team are non-technical, so whatever I use needs a pretty and intuitive interface. Command line is out. I also don't want to go reinventing the wheel, cos the dashboard for TeamCity/Cruise do an excellent job of telling people what is deployed where.
I can't make these deploy configurations dependent one after the other, the QA team need to sanction the code moving from test -> QA and from QA -> live.
Our codebase is too big to zip and move around, we make probably over 100 changes to the websites a day but they're small - people don't want to wait half an hour for their changes to go live. I introduced deployment via SVN for one system & people got sick of waiting 2 minutes, so ingrained is the 'go-live-now' ethos. So my preferred method is to keep the working copies within the agents on each machine and just rsync the changed files to where they need to go, via very simple scripts, once approved by QA.
Anyway back to my original question - is there a way to manually run a stage, not trigger it via the commit to SVN? Or is this the wrong tool for the job?