| Issue Number | 3937 |
|---|---|
| Summary | Fix schema selection and deployment in the CDR build/deploy software |
| Created | 2015-06-30 11:07:30 |
| Issue Type | Bug |
| Submitted By | alan |
| Assigned To | alan |
| Status | Closed |
| Resolved | 2016-02-09 11:58:22 |
| Resolution | Fixed |
| Path | /home/bkline/backups/jira/ocecdr/issue.164302 |
In our last deployment, modified schemas were not deployed automatically as they should have been.
This needs to be fixed.
I have begun working on this while our CDR DEV server was unavailable due to the server migration, so I have also added more code to the build and deploy software to support build and deployment on drives other than a d: drive. This is turning out to be desirable for the long term and not just during the period of DEV server migration.
I have fixed the schema build and also modified all of the build scripts to work on any destination drive (e.g., c:, d:, etc.) and tested by building on my own workstation that has no d: drive.
There are a couple of other minor changes that we have discussed, logging the svn version number of the software used in build and deploy, and maybe integrating a backup option into the deploy script. I'm going to go ahead and implement those under the aegis of this JIRA issue.
I thought I had everything working but, in fact, I had commented out something that required database access from my machine. I uncommented that and got it working.
I've also added subversion revision number logging to both the build and deploy software - though only to the top level python programs. I don't know if we need revision numbers on the .cmd scripts. If we do I can implement that.
I'm doing some testing with the deploy software. I'm not aware of any problems but I need more testing to be sure that it works properly on my workstation. Unfortunately, the part that particularly needs testing is the part that updates schemas in the database. I'm not running a local database copy, so that could make some undesirable changes in the database on whatever server I test with. I leave that alone until we've discussed it.
As per my previous comment, I believe this is fixed and am marking it so.
I hope to be doing more testing of the build deploy software for other reasons and will check to be sure that schemas are properly handled.
Considering that we finished the deployment of Darwin I
consider this issue to fix the deployment script as complete.
Closing ticket.
I'm not so sure. I had to do some manual tweaking, as I recall.
Well, in that case we should enter a new ticket as a bug fix.
Elapsed: 0:00:00.001793