Table of Contents
Process
Promotion of code can be done in the Solution Manager (see Denodo Servers and URLs ).
The process below outlines how to create. Each revision should be added to the Revision Tracker table below for the purpose of tracking approvals.
Create a revision. All revisions should use DEV as their source environment.
Select your revision elements
If making role changes, be sure to include all objects in any VDB associated with that role so the necessary VQL for permissions updates is generated
DO NOT promote the dev role when promoting to STAGE or PROD. This will ensure that all VDB’s/Object are read only.
Give revision a name and description and save
Create a row in the Revision Tracker below for your revision
Have a peer review the revision and add their name under the Approved By column in the Revision Tracker once approved.
Deploy the revision to STAGE and perform smoke testing
If smoke testing passes, deploy to PROD
If smoke testing fails, investigate, then create a new revision to address the issues