| Issue Number | 5239 |
|---|---|
| Summary | [Internal] Add log message to Build Script |
| Created | 2023-05-15 17:08:57 |
| Issue Type | Improvement |
| Submitted By | Englisch, Volker (NIH/NCI) [C] |
| Assigned To | Kline, Bob (NIH/NCI) [C] |
| Status | Closed |
| Resolved | 2023-05-26 16:27:15 |
| Resolution | Fixed |
| Path | /home/bkline/backups/jira/ocecdr/issue.345899 |
The build script install.bat runs several individual steps in order. The last step - added in Pauling - installs the publishing control documents.
This script ( install-pub-control-documents.py ) doesn't add any information to the log file build.log to indicate that it actually ran. It would be nice to add a log message to the logfile even when the script finishes without error.
Installed on DEV.
https://github.com/NCIOCPL/cdr-tools/commit/e1eadb6
~volker You can verify by
viewing tail of d:/cdr/Log/deploy.log
running https://github.com/NCIOCPL/cdr-tools/blob/quinn/Build/install-pub-control-documents.py
I can see the log entries in the log file deploy.log.
Information about updating the publishing documents is written to the log files.
Confirming this ticket on QA.
I'll let you verify and close this one, @volker, since you filed the ticket.
Trying a second time to tag you, @volker, since JIRA ignored the first attempt.
Third time's the charm, they say. Adding the tag by editing the raw comment text, ~volker
I'm confirming that the log messages are now written to the logfile deploy.log.
Closing ticket.
Elapsed: 0:00:00.001686