...

Pre-production Deployments

...

1. All deployments outside of the production environment will be executed from the client application trunk (e.g. https://svn.ucdavis.edu/svn/kuali/RiceApplications/KualiFinancialSystem/trunk)
2. Pre-production deployment should follow the same data set requirements listed below.

Data Set Management Requirements

1. Release versions of data sets must be stored in <Repository Root/tags/<client release version> (e.g. https://svn.ucdavis.edu/svn/kuali/RiceApplications/MyInfoVault/tags/3.5)
2. Only the Rice DBA and appropriate client application migrators have access to the tags directory in the repositories.
3. The data sets must come in the form of SQL scripts. Each deployment will contain a deployment wrapper script and then one or more data scripts.
   1. You can download template templates of deploy script and data script.

---------------Opening Section-------------------
COL DT NOPRINT NEW_VALUE db_date;
SELECT TO_CHAR(SYSDATE, 'YYYY-MM-DD-HH24MISS') DT FROM DUAL;
COL db NOPRINT NEW_VALUE db_name;
SELECT SYS_CONTEXT ('RICE', 'MOTHRA') DB FROM DUAL;
----- Name the spool file -----
SPOOL ./deploy-rice-KR-<Jira-####>--&db_date-&db_name.log;
SET ECHO ON;
SET TERMOUT ON;
SET VERIFY OFF;
SET TRIMSPOOL ON;
SET SERVEROUTPUT ON SIZE 1000000;
WHENEVER SQLERROR EXIT SQL.SQLCODE ROLLBACK;
WHENEVER OSERROR EXIT SQL.SQLCODE ROLLBACK;

SET ECHO ON;

----- RICE KR-#### Deployment -----
SHOW USER;
@<child-script1>.sql
@<child-script2>.sql


----- Deployment Complete -----
SPOOL OFF;

...