Limiting access to web deployment in VSS 2005
Bill Mason
We're hoping to use shadow folders to publish content to our staging
servers, and web deployment to publish content to our production
servers. The new "rules of the road" require that all code changes to
production applications must first be tested in the staging
environment, approved, and documented prior to deployment to our
production servers. My question is, what's the best way to control
access to the web deployment feature?
According to Microsoft's VSS 2005 documentation "You can use the
Visual SourceSafe Explorer Deploy command on the Web menu to copy the
currently selected project to a live Web server, or to multiple
servers. You can deploy only an entire project, not single files.
Since the Deploy command makes your project public, you must have the
Destroy right for the project.". What is the difference between the
delete and destroy rights? How would denying the developers the
destroy right affect their ability to work with web projects? Ideally
I would like to exclude web deployment rights to network
administration staff, and possibly developer manager.
Our environment consists of....
(1) Win 2003 Server running VSS 2005
(3) Win 2003 Server running IIS (production environment)
(1) Win 2003 Server running IIS (staging environment)
(5) Win XP Pro running Visual Studio 2005/VSS 2005 (developer
workstations)
- content is published to staging servers via shadow folders
- content is published to production servers via web deployment
Bill Mason
I think I answered my own question, but I'd appreciate confirmation.
DELETE right: Allows deletion of an object in the VSS database, but
retains history allowing object to be recovered using the RECOVER
command.
DESTROY right: Allows deletion of an object in the VSS database, and
history.
As far as I can see, the only things developers will need to watch out
for is the scenario below.
1. Developer creates main.asp file in VSS
2. Developer deletes main.asp file
3. Developer creates another (different) main.asp file
4. Developer attempts to delete new main.asp file (Not possible
because of history from 1st main.asp)
Jeff Clausius
Bill:
Actually, main.asp can be deleted the 2nd time as well. Deleted files
end up in the properties of the folder. If you need to restore a file,
simple show the properties, pick the "correct" file, and undelete it.
You can have multiple, deleted files of the same name, but only one
non-deleted file in the folder.
HTH
Jeff Clausius
SourceGear
Jeff Clausius
When you delete the file the 2nd time, VSS explorer sees it already has
a name conflict of a file in deleted state. So, to proceed with the
deletion of the undeleted file, the 1st file must be purged (which can
be done automatically).
Once the deleted file has been purged, the 2nd file is then deleted.
Sorry if I caused any confusion.
Jeff
SourceGear