Set up CI
Opened this issue · 6 comments
Use a CI system - or several CI systems, if it comes to that - to do very basic acceptance criteria for new commits and to generate artifacts like PDF files ( #10 ) in an automated, repeatable fashion.
One example Markdown-to-HTML and Markdown-to-PDF pipeline is from the resume of Damir Dulic, at https://github.com/ddulic/resume ; it uses Travis CI.
A second example Markdown-to-PDF workflow using Pandoc is at https://gitlab.com/oddcoder/GP_Template - because it's on Gitlab it offers integrated CI, which has proven handy. I'm temporarily working in a fork at https://gitlab.com/vielmetti/GP_Template .
https://www.npmjs.com/package/markdown-pdf looks like the most promising tooling of the moment, and I'll plan to set up Drone Cloud for CI.
OK, working on this in a fork of the project.
What ended up working was Pandoc https://pandoc.org/ and Drone Cloud https://cloud.drone.io/
Drone config has been merged. Still TBD is turning on Drone Cloud in the Drone UI.