3 ms·
I have a wierd urge to add Gitlab CI to this so that any tagged commit creates a release containing all assets (PDF, ePub, HTML), and a manual job on any commit
by rpigab 3y ago
I have a wierd urge to add Gitlab CI to this so that any tagged commit creates a release containing all assets (PDF, ePub, HTML), and a manual job on any commit does the same without a release (stored in Gitlab Generic Package Registry or job artifacts), and the HTML version is built and deployed to the repository's Gitlab Pages on all master pipelines.
I know it's of little use since you usually install all dependencies on a dev machine and simply run fast scripts locally, but Gitlab CI is really a nice tool to use, and you've got some free build minutes you can use on the Saas instance.
Then you can make edits on any machine using the Web IDE, and easily share the result hosed on Gitlab pages.
- Leo_Germond 3y agoI've been using pandoc + rst + beamer for producing very large (1000's) training slide decks, and pdf2latex is so slow that using a CI to generate the 10's of decks configurations in parallel makes for a very valid use case, so I implemented just that... I don't know what I'm getting at with this little story of mine, but if you actually scratch that urge at some point I'd be interested in seeing the result, especially regarding distribution, which I didn't set out to implement.
- rpigab 3y agoNot sure I'll try that anytime soon, but here's what I would check out to start: https://gitlab.com/pandoc/pandoc-ci-example https://gitlab.com/pandoc/pandoc-ci-example