-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Set up CI #13
Comments
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/ |
#13 sets up CI so that we can automatically produce PDF files from the original files.
Drone config has been merged. Still TBD is turning on Drone Cloud in the Drone UI. |
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.
The text was updated successfully, but these errors were encountered: