Just wanted to post a thread to get a feel for how it works. I plan on posting the following:
We have concerns as to the security and procedures involved in deploying code from one environment to another. We currently have 4 environments, Development, Quality Assurance (QA), User Acceptance Testing (UAT) and Production, each resident on its own server with its own IS. In order to standardize the object migration process, we’d like to set up all our migration procedures from a single IS. Each package would have multiple projects in deployer, with the project name identifying the migration path. Questions:
- Is it viable and within best practices concepts to have all the deployment done from a single IS?
- We want to be able to have the developers migrate their code from Development to QA but not from QA to UAT, and not from UAT to Production. Is there a way to put security on the packages or within deployer to prevent all users other than the System Administrator from having authority to do the forbidden deployments? How is this done?
- Any other suggestions? One that comes to mind is utilize deployer on the Development IS for Development to QA deployments, and then use the deployer on the QA IS for all the other deployments; locking everyone out of deployer on the QA IS except for the system administrator.
Looking forward to responses and ideas.