Yeah—enterprise is especially restricted. The hole Sarbanes-Oxley and separation of duties is huge, especially when you are talking corporate companies. I know when I worked at McGraw-Hill as a Business Analyst, code was always migrated by the management software. From Dev > Staging > Quality > Production. A little bit of a different setup, as it was all Java based, but the idea I’m sure is the same. We could move it from dev > Staging but change control had to move it to quality & production, and this was all permissions driven (of course). This eliminated a lot of purpose for access to the production environment to be spread around, except to a select few key individuals.
And yes, you are right. This type of system setup is dependent on a lot of other items, and has a lot of building/exceptions/testing to go through before it could be trusted. I think this was mentioned elsewhere, but interfacing with SVN might be an awesome way to go about setting this up as well.
I know this isn’t coming to conception anytime soon, but it would be recomended that you set up ‘sources’. These sources are where the files are pulled / put from. I ready somewhere earlier in the thread about someone mentioning interfacing with SVN. This could also be a source, as well as ftp access.
I know for me, I develop locally, commit changes, then push to a staging environment.
For this setup, you would develop locally, commit the changes, then have the system look for any changed files (and select which ones of course)... and have it push it to whatever the next source is. It gives a little bit more integration between the different environments and SVN in my opinion.
But i’ll stop letting my thoughts flow, as I am really awesome at creating scope creep 😊