FHIR Chat · Local core builds are now requiring Jekyll

Stream: committers

Topic: Local core builds are now requiring Jekyll

Lloyd McKenzie (Oct 12 2018 at 16:44):

@Michelle (Moseman) Miller is running into issues with her local build yelling because she doesn't have Jekyl installed. That's because the build process now builds all of the test IGs. If this is a new requirement, we should broadcast it. But I'm not sure it's totally reasonable. I'm also concerned about the local builds now taking even longer. @Grahame Grieve ?

Grahame Grieve (Oct 12 2018 at 18:56):

it takes 1:30 on my system

Grahame Grieve (Oct 12 2018 at 18:57):

as for why.. it's part of a general thrust on my part to stabilise the build and validation systems.

Grahame Grieve (Oct 12 2018 at 18:57):

I agree we should document the requirement - I overlooked that

Lloyd McKenzie (Oct 12 2018 at 18:57):

So the expectation is that anyone who's committing to the core spec must now install both Ruby & Jekyll?

Grahame Grieve (Oct 12 2018 at 18:59):

yes

Melva Peters (Oct 12 2018 at 23:44):

Is there instructions on where/how to install? I haven't run into my build complaining at this point, but may happen on my next branch.

Melva Peters (Oct 12 2018 at 23:44):

Never mind...see Lloyd's instruction on another stream

John Moehrke (Oct 29 2018 at 16:53):

where?

John Moehrke (Oct 29 2018 at 18:13):

stream:committers/announce topic:Requirement+for+Jekyll

Hugh Glover (Nov 06 2018 at 13:21):

Installing Jekyll is defeating me for Windows 10. The guidance notes on the wiki discuss an install of Ruby that is v 2.0 to 2.3 - but clearly there are later versions. There are comments about the incompatibility of Jekyll with Windows. So which versions are we supposed to use - is the usual "latest is best" mantra correct?

Lloyd McKenzie (Nov 06 2018 at 13:36):

I'm running Windows 10 and it works fine for me. I grabbed the latest at the time, though that's a while ago now. My version is: ruby 2.3.3p222 (2016-11-21 revision 56859) [x64-mingw32]