Charles N Wyble
bb5a6e21e1
- Script gathers data from Redmine API and processes it. - Includes robust error handling and detailed logging. - Test suite verifies data gathering functionality. |
||
---|---|---|
dsr-input | ||
dsr-joplin-create | ||
endstops | ||
local | ||
microservices/DSRInstrumentedCTORedmineGather | ||
vendor/git.knownelement.com | ||
.gitignore | ||
DSRVariables.env | ||
LICENSE | ||
README.md |
DailyStakeholderReport-Pipeline
Introduction
I publish a daily stakeholder report to the TSYS Group discourse every day. Up until 11/29 I was performing the publishing step manually. On 11/29 I automated the pdf creation and publishing to discourse procedure.
I also begin work on automated gathering of data going into the new version of the report that is in development.
Scripts
Start a new day
Start a new day. See the script: endstops/start-day.sh
Create a new (blank) DSR
See the script: dsr-joplin-create/dsr-new.sh
Populate the new DSR with objectives for the day
See the script: dsr-joplin-create/dsr-populate-objectives.sh
End the day
End the day. See the script: endstops/end-day.sh
Collating and Publishing the report
Publishing the report involves three steps:
-
Exporting the markdown from Joplin (and any attachments (i often take screenshots throughout the day)) I am still doing this manually due to having issues installing the Joplin CLI.
-
Creating a (formatted/styled) PDF from the exported markdown/attachments. See the script: dsr-publish/create-dsr-pdf.sh.
-
Uploading the PDF to discourse and creating a new topic in the appropriate category. See the script: dsr-publish/publish-dsr.sh