Amusingly, Peter and I disagree on the suitability of reusing the Jenkins image for simple building and testing, but it really doesn’t matter which one you use. You may find the directions in http://teic.github.io/TCW/testing_and_building.html a bit more step-by-step and easier to follow. But again, you’ll be doing the same things, so it doesn’t matter. I am strongly, and perhaps pathologically biased in favor of limiting complexity where possible and it colors my decisions 🙂.HughSent from my phone.On Dec 17, 2019, at 02:33, Peter Stadler <stadler@edirom.de> wrote:Dear all,
tomorrow we’ll be having our little workshop on how to build the TEI Guidelines (and Stylesheets) locally and although I’m quite late, may I ask you to prepare your computers by installing Docker (Community Edition) [1] and download (aka ‚pull‘) the teic/jenkins image?
That is, once you have Docker installed (and the Docker daemon is running; you can tell when the little Docker whale stops loading in your system tray) you simply hit
`docker pull teic/jenkins`
on the command line. This will take some minutes (depending on your connection) since the image is about 800 MB!
Oh, and of course you will need to have a clone of the TEI [2] and the Stylesheets repo [3] on your machine.
Best
Peter
[1] https://docs.docker.com/v17.09/engine/installation/
[2] https://github.com/TEIC/TEI
[3] https://github.com/TEIC/Stylesheets
_______________________________________________
Tei-council mailing list
Tei-council@lists.tei-c.org
http://lists.lists.tei-c.org/mailman/listinfo/tei-council