Stream: IG creation
Topic: Publisher build without generation
Sarah Gaunt (Feb 04 2020 at 02:35):
@Grahame Grieve I presume a flag that prevents the generation of the html would just leave whatever had already be generated in place? This would also be useful in helping to stop the IG from disappearing from the CI build page if there is an issue with the Publisher/template. So I could set the flag and rebuild the IG after a publisher/template release without worrying that the IG would disappear...
Grahame Grieve (Feb 04 2020 at 02:54):
no I'm afraid that the flag is not relevant for this
Grahame Grieve (Feb 04 2020 at 02:55):
but @Josh Mandel this is actually the core issue that generates such pain when a build fails: you lose what you already had from the last build. This is not the IG Publisher's doing, it's the way the ci-build works. Is this something we can do anything about?
Grahame Grieve (Feb 05 2020 at 20:31):
@Josh Mandel ping on this
Josh Mandel (Feb 05 2020 at 20:35):
Discussion from https://chat.fhir.org/#narrow/stream/179255-questionnaire/topic/SDC.20IG.20build.20down.3F -- does the layout I proposed make sense? (Paul was talking about a "staging server" and I wasn't entirely sure what this meant.)
Grahame Grieve (Feb 05 2020 at 21:11):
I didn't entirely follow the structure, I guess. So if you have a successful build, you overwrite the root, but if it fails, you write what you have into failure? I think that works for me
There's one weird thing now - if the build fails, you see the source, I think. I've never understood that - it doesn't seen useful; only the output log is relevant.
Also, in your scheme, what would happen with branches? just reproduce that scheme?
Josh Mandel (Feb 05 2020 at 21:12):
Yes, that's the idea. The reason all "source" is included is just to provide full details on failure, including any inputs, any partially-generated outputs, etc.
Josh Mandel (Feb 05 2020 at 21:12):
I'll go ahead and give this a shot.
Josh Mandel (Feb 05 2020 at 21:17):
(For example, http://build.fhir.org/ig/IHTSDO/snomed-ig/branches/master/failure/output/qa.json is a partial output that's relevant, outsie the build.log.)
Josh Mandel (Feb 05 2020 at 21:18):
OK, this is up and running -- probably needs some testing to work out any kinks.
Josh Mandel (Feb 05 2020 at 21:22):
I see in teh https://fhir.github.io/auto-ig-builder/builds.html page, failures and successes are now showing up as distinct rows. An unintended consequence... will see what I can do about that!
Grahame Grieve (Feb 05 2020 at 21:58):
great thanks.
Grahame Grieve (Feb 05 2020 at 21:59):
on the subject of all source... only the output folder matters
Grahame Grieve (Feb 05 2020 at 21:59):
anything else in any other directory... people can run their own local copy if they want to browse the temp etc
Lloyd McKenzie (Feb 05 2020 at 22:05):
Actually, the temp and template folders would be useful too if we're trying to debug
Josh Mandel (Feb 05 2020 at 22:06):
Yeah, I don't see a reason not to include the full state... is it causing an issue?
Josh Mandel (Feb 05 2020 at 22:07):
And OK, cleaned up the the report at https://fhir.github.io/auto-ig-builder/builds.html a bit -- should only be showing the relevant stuff, now, with correct links to logs in case of failure.
Grahame Grieve (Feb 05 2020 at 22:37):
wonderful
Last updated: Apr 12 2022 at 19:14 UTC
