...
- A migrator files a ticket in the Kuali Rice JIRA project requesting migration of a data set to the Rice database. The JIRA ticket should provide a link to the SVN location of the data files.
- Upon approval, the migrator copies the data set to the
<Repository Root/tags/<client release version>
directory, citing the Kuali Rice JIRA ticket.Code Block borderStyle solid title Example:Migrating to <tags> svn copy https://svn.ucdavis.edu/svn/kuali/RiceApplications/KualiCoeus/trunk/datasets https://svn.ucdavis.edu/svn/kuali/RiceApplications/KualiCoeus/tags/2.0 -m "<KR JIRA ticket>"
- Prior to a release, the migrator adds a task (or requests that a task be added) in the Deployment Plan stating that the data set is to be migrated.
- The Rice Service Manager creates a ticket in the Kuali Rice JIRA project that reflects this task and assigns it to the Rice DBA.
- Jira ticket should specify the KR_1234_deploy.sql script to execute.
- Jira Ticket should contain the specific repository location of the script(s): (eg. https://svn.ucdavis.edu/svn/kuali/RiceApplications/<Application>/tags/<release_version>)
- The Rice DBA checks the data set out from the repository.
- Log onto the appropriate database server
- cd /opt/pkg/oracle/subversion
- Execute svn co https://svn.ucdavis.edu/svn/kuali/RiceApplications/<Application>/tags/<release_version> command against the repository location provided in the Jira Ticket.
Code Block $ svn co https://svn.ucdavis.edu/svn/kuali/RiceApplications/<Application>/tags/<release_version> <Application>
- This will create an <Application> directory with a <release_version> subdirectory
- If the <Application> /<release_version> directory exists from a previous deployment:
- cd /opt/pkg/oracle/subversion/<Application>/<release_version>
- Execute svn update
Code Block $ cd /opt/pkg/oracle/subversion/<Application>/<release_version> $ svn update
- The <release_version> subdirectory will contain script(s) which will be named for the Jira ticket number (eg. KR-1234.sql).
- Access Mothra Test DB as environment schema owner noted in Jira ticket and execute script:
Code Block sqlplus <environment schema owner>/<password> @KR_####_deploy.sql
- During a dry-run deployment, the Rice DBA executes the data set scripts against the UPSTAGE environment database.
- At deployment time, the Rice DBA executes the data set scripts against the production database.