Issue Number | 3570 |
---|---|
Summary | Rerun Previous Publishing Run |
Created | 2012-12-08 13:32:41 |
Issue Type | Improvement |
Submitted By | Englisch, Volker (NIH/NCI) [C] |
Assigned To | Englisch, Volker (NIH/NCI) [C] |
Status | Closed |
Resolved | 2013-09-25 18:45:22 |
Resolution | Fixed |
Path | /home/bkline/backups/jira/ocecdr/issue.107898 |
BZISSUE::5268
BZDATETIME::2012-12-08 13:32:41
BZCREATOR::Volker Englisch
BZASSIGNEE::Volker Englisch
BZQACONTACT::Margaret Beckwith
When we are pushing documents to Gatekeeper we first compare the new
files created as part of the current publishing job with the files send
to GK last. All files that differ are entered into the table
pub_proc_cg_work.
Seeding the pub_proc_cg_work table can take some time and therefore
we've created an option that allows us to rerun a failed push job
without having to run the diff portion again.
Last night's push job failed and I was restarting the push trying to
use this option but it appears that it is not working anymore and the
push process is rerunning the diff portion.
I need to look into this and find out why the option isn't working.
It appears that I didn't remember correctly. The ability to re-run a
push job was only setup for a Full-Load publishing job but not for a
regular Export or Reload job.
I will have to go back to the old issue to find out if there was a
reason why it hadn't been setup for the Export/Reload as well.
I went back through the different versions. There was no reason why this was only implemented for a full load. I'm guessing that I had only tested it for a full load since I was using this feature when the new Gatekeeper was setup and I probably didn't have time for additional testing.
That testing will be done now.
The following program has been modified:
R12052: cdrpub.py
In order for the changes to work properly the publishing document CDR178 will need to be updated to include the parameter 'RerunFailedPush' for the Interim, Export, and Full push jobs.
The publishing document is now included in subversion under
/Filters/178.xml trunk
R12108: 178.xml
I was just assuming this was a filter, with such a low CDR ID, but since it's actually a publishing control document, it would probably be better to move it to trunk/Publishing, if we're going to keep it under version control (which isn't a bad idea). At any rate, we don't need to include this in the build materials given to Wenling, as we can just install it (like any other CDR document) from the bastion host.
The publishing document has been moved to the
\cdr\publishing
directory in subversion.
The document has been updated on PROD. We're not testing the new functionality until we need to rerun a publishing job, so I'm setting the status of the issue to 'QA Verified' for now and will close it after the weekly publishing job finished.
Elapsed: 0:00:00.000905