| Issue Number | 4857 |
|---|---|
| Summary | [Internal] Update Publishing Document (GK changes) |
| Created | 2020-08-06 21:14:37 |
| Issue Type | Improvement |
| Submitted By | Englisch, Volker (NIH/NCI) [C] |
| Assigned To | Englisch, Volker (NIH/NCI) [C] |
| Status | Closed |
| Resolved | 2020-08-27 14:18:07 |
| Resolution | Fixed |
| Path | /home/bkline/backups/jira/ocecdr/issue.272064 |
With the elimination of the Gatekeeper use from our publishing process there are now a few unused variables which we can eliminate from our publishing document. The variables that aren't needed anymore are:
GKPushJobDescription
GKServer
GKPubTarget
IgnoreGKJobIDMismatch
~volker did I miss some?
Maybe you missed putting the updated document in place? When I'm running a publishing job I see these parameters listed.
Or maybe it got wiped out and not restored by a refresh from PROD. Does the document in the repository match https://github.com/NCIOCPL/cdr-publishing/blob/retire-gk/Publishing/Primary.xml?
No, it doesn't.
Does that mean I should be testing on STAGE rather than QA because we know STAGE hadn't been refreshed?
Or maybe just install the right publishing control document.
I figure STAGE has been updated more recently than QA and should reflect what PROD will look like after the installation. If you're certain the Primary.xml is the only difference between QA and STAGE in regard to these tests and other pieces haven't been affected by a refresh I'll go ahead and install it on QA.
It's possible that my assumption that the publishing control documents are installed as part of the deployment is wrong.
I have installed Primary.xml on DEV, QA, and STAGE.
Bob has installed the document Primary.xml on all servers.
Closing ticket.
Elapsed: 0:00:00.002071