Page Comparison

...

1. 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.
2. 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>"

3. 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.
4. 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 svn command specifying the repository, tag and release:

     Code Block
     svn co https://svn.ucdavis.edu/svn/kuali/RiceApplications/KualiCoeus/tags/2.0

1. The Rice DBA checks the data set out from the repository.

   Code Block
   borderStyle solid title Example:Checking Out Data Set from Repository
   $ svn co https://svn.ucdavis.edu/svn/kuali/RiceApplications/KualiCoeus/trunk/datasets or svn co https://svn.ucdavis.edu/svn/kuali/RiceApplications/KualiCoeus/tags/2.0 or [subversionFiles/dataSets/KualiCoeus/]$ svn update

2. During a dry-run deployment, the Rice DBA executes the data set scripts against the UPSTAGE environment database.
3. At deployment time, the Rice DBA executes the data set scripts against the production database.