FHIR Chat · Build failure in auto-build? · shorthand

Stream: shorthand

Topic: Build failure in auto-build?

Kevin Power (Oct 14 2020 at 13:50):

Seems like we are getting build failures because of the sushi version in the autobuild?
http://build.fhir.org/ig/HL7/genomics-reporting/branches/genomics-reporting-fsh/failure/build.log

CC: @Patrick Werner / @May Terry

Nick Freiter (Oct 14 2020 at 13:55):

Are you hoping to run the 1.0.0-beta version of SUSHI? Currently the IG autobuild doesn't allow you to use which version of SUSHI you want to use, it is locked in at the latest "official" version, which is 0.16.0, since 1.0.0 is still a beta. There is conversation happening here: https://chat.fhir.org/#narrow/stream/179252-IG-creation/topic/Selecting.20SUSHI.20Versions.20in.20AutoBuild on how this needs to change, and will hopefully be changed soon.

May Terry (Oct 14 2020 at 13:55):

Kevin Power said:

Seems like we are getting build failures because of the sushi version in the autobuild?
http://build.fhir.org/ig/HL7/genomics-reporting/branches/genomics-reporting-fsh/failure/build.log

CC: Patrick Werner / May Terry

Thanks @Kevin Power - to be precise, here's the relevant error message: Run Sushi on /scratch/ig-build-temp-U6MNU5/repo (00:00.0020) Sushi: info Running SUSHI v0.16.0 (implements FHIR Shorthand specification v0.13.x) (00:00.0493) Sushi: info SUSHI detected a "fsh" directory in the input path. As a result, SUSHI will operate in "IG Publisher integration" mode. This means: (00:00.0494)
Is this something the SUSHI team coordinates with the maintainers of the autobuild. I don't think our CG team has this ability right now.

May Terry (Oct 14 2020 at 13:57):

@Nick Freiter - yeh, we were encouraged by @Mark Kramer to upgrade to 1.0beta so we did. :smile:

Mark Kramer (Oct 14 2020 at 13:57):

You can run the publisher locally, no problem.

Mark Kramer (Oct 14 2020 at 13:57):

And every branch gets its own auto-build.

Nick Freiter (Oct 14 2020 at 13:58):

And should be able to autobuild soon, if you check out that linked conversation, I believe it was settled that the IG Publisher will soon support fsh.ini, which will allow you to specify the SUSHI version.

May Terry (Oct 14 2020 at 14:00):

@Nick Freiter - yeh, but going back to 0.16 will require that we reorganize our file structure and config file changes, only to change it back again. It's a rather suboptimal adjustment.

Mark Kramer (Oct 14 2020 at 14:01):

Same situation with mCODE, though, and the build.fhir.org version is still the latest under 0.16.0

May Terry (Oct 14 2020 at 14:03):

Yeh, but my concern is not mCODE, but the CG WG which has a migration workflow that leverages the autobuild for QA by subject matter experts, not all software engineers who will each have their own local build to run.

May Terry (Oct 14 2020 at 14:06):

It's kind of a catch-22 here. We're encouraged to test beta releases but the npm option for installing SUSHI makes this change globally on dev systems at the cost of losing a workflow that depends upon an autobuild environment which doesn't trust beta releases.

Mark Kramer (Oct 14 2020 at 14:07):

I apologize. I was interested in having you test the beta and the upgrade instructions, and neglected the autobuild breakage situation. My fault.

May Terry (Oct 14 2020 at 14:10):

Ok. we'll make it work somehow. @Kevin Power and @Patrick Werner - I think perhaps we can find a place to upload the IG as a zip file for SMEs to review until SUSHI 1.0 is production and we can go back to the autobuild QA workflow. It's a good note however for others doing migrations. Thanks!

Mark Kramer (Oct 14 2020 at 14:19):

Chris is going to ping Grahame again. This might be resolved very soon if we get Grahame's attention. You might want to just use local builds for today and wait and see.

Chris Moesel (Oct 15 2020 at 00:07):

OK. Grahame released a new IG Publisher today -- and you can now control the SUSHI version by placing a fsh.ini file in the root folder of your IG (sibling to the ig.ini). The contents of fsh.ini should be something like this:

[FSH]
sushi-version=beta

The above will force the publisher to download and use the SUSHI release tagged as beta. This is a good choice during the 1.0.0 beta because as we release new betas, we'll move the beta tag -- this way your IG always uses the latest beta. Once we get out of beta, you can remove fsh.ini (or comment out that line) to go back to the normal "latest official release" approach.

NOTE: You can also use specific versions as the value, so you could say sushi-version=1.0.0-beta.1 to lock it to that specific version, or once we officially release 1.0.0, you could say sushi-version=0.16.0 if you absolutely must use the older version of SUSHI.

May Terry (Oct 15 2020 at 00:09):

Thanks for the really quick turnaround @Chris Moesel !
cc: @Kevin Power and @Patrick Werner

Chris Moesel said:

OK. Grahame released a new IG Publisher today -- and you can now control the SUSHI version by placing a fsh.ini file in the root folder of your IG (sibling to the ig.ini). The contents of fsh.ini should be something like this:

[FSH]
sushi-version=beta

The above will force the publisher to download and use the SUSHI release tagged as beta. This is a good choice during the 1.0.0 beta because as we release new betas, we'll move the beta tag -- this way your IG always uses the latest beta. Once we get out of beta, you can remove fsh.ini (or comment out that line) to go back to the normal "latest official release" approach.

NOTE: You can also use specific versions as the value, so you could say sushi-version=1.0.0-beta.1 to lock it to that specific version, or once we officially release 1.0.0, you could say sushi-version=0.16.0 if you absolutely must use the older version of SUSHI.

May Terry (Oct 15 2020 at 03:06):

@Chris Moesel - quick update. easy change and verified the fix. we have our auto-build again. Thanks to you and @Grahame Grieve for the really quick turnaround on this. :smile:

Last updated: Apr 12 2022 at 19:14 UTC