FHIR Chat · Requirement for Jekyll · committers/announce

Stream: committers/announce

Topic: Requirement for Jekyll


view this post on Zulip Lloyd McKenzie (Oct 12 2018 at 19:10):

The core build has been updated to run several test IGs to ensure the full suite of the publication process runs correctly after each commit. That means that if you're running a local build prior to pushing your commits to the core spec, you need to be set up to be able to publish FHIR implementation guides too. (Realisticly, any work group that isn't yet developing implementation guide content will need to do so in the next 1-2 years anyhow.) In practical terms, that means that all committers will need to install Ruby and Jekyll. Instructions are here: http://wiki.hl7.org/index.php?title=IG_Publisher_Documentation#Installing

view this post on Zulip John Moehrke (Oct 29 2018 at 16:54):

if this is now required of the core build... then it should be added to the core build requirements.

view this post on Zulip Lloyd McKenzie (Oct 29 2018 at 16:59):

Added

view this post on Zulip John Moehrke (Oct 29 2018 at 18:11):

I can confirm that was my build problem. A full build now takes 65 minutes... ouch

view this post on Zulip Cooper Thompson (Oct 30 2018 at 13:33):

Is there a simple way to validate that you have Jekyll installed correctly without attempting a full build? The windows docs for installing Jekyll is a bit out of sync with the (recent?) Ruby dev kit changes.

view this post on Zulip Eric Haas (Oct 30 2018 at 15:02):

besides jekyll -v ?

view this post on Zulip Eric Haas (Oct 30 2018 at 15:09):

otherwise you can clone my test IG run bash pub3.sh (on mac) for the root directory should work - takes about 5 minutes to run the first time.

view this post on Zulip John Moehrke (Oct 30 2018 at 15:54):

build should do the jekyll check and fail with appropriate message???

view this post on Zulip Cooper Thompson (Oct 30 2018 at 16:00):

I initially did a build without Jekyll (on me for not checking committers/announce). That failed ~120 minutes into the build with the IG tests, so there doesn't seem to be a startup check for Jekyll. After installing Jekyll, I still got the same build errors (again, ~120 minutes in). However prompted by Grahame's comment, I deleted the publish directory and rebuilt, and it seems to work now.

view this post on Zulip Josh Mandel (Oct 31 2018 at 00:46):

But wait, does it take 2h ??

view this post on Zulip Eric Haas (Oct 31 2018 at 00:50):

yep

view this post on Zulip Josh Mandel (Oct 31 2018 at 00:51):

Yikes.

view this post on Zulip Brian Postlethwaite (Oct 31 2018 at 02:03):

Same here for the full build. Considering an update on my hardware, even looking into using an Azure VM... But that's no use on a plane.

view this post on Zulip Grahame Grieve (Oct 31 2018 at 02:04):

full build takes me ~27min

view this post on Zulip Grahame Grieve (Oct 31 2018 at 02:05):

one way to speed it up is to set up a ram drive of ~2GB in size, and build to the RAM drive.

-output r:/fhir

view this post on Zulip Grahame Grieve (Oct 31 2018 at 02:06):

the other thing to do is to clean out your temp directory. if you're on windows, you could have >200k files in it, and run like a dog....

view this post on Zulip Brian Postlethwaite (Oct 31 2018 at 02:12):

Which RAM Drive tool are you using?

view this post on Zulip Grahame Grieve (Oct 31 2018 at 03:13):

lmDisk

view this post on Zulip Eric Haas (Oct 31 2018 at 03:26):

this is why I skip the local build and asked for the PR build but sometimes I need to use excel then I have to build locally. for simple stuff I just edit the excel file directly in a text editor.

view this post on Zulip Grahame Grieve (Oct 31 2018 at 03:31):

yes I mostly use notepad++ for editing the spreadsheets

view this post on Zulip Lloyd McKenzie (Oct 31 2018 at 03:45):

Note that this stream is for announcements, not discussion...


Last updated: Apr 12 2022 at 19:14 UTC