Stream: IG creation
Topic: How to prevent D.O.A. software?
Mark Kramer (Feb 03 2020 at 22:18):
What type of process should in place to prevent the release of templates of IG publisher versions that are dead on arrival?
Chris Moesel (Feb 03 2020 at 22:24):
For IGs using the templates, I think it makes sense to use a Pull Request workflow, even for commits to IGs that don't require review. That way if there is something broken in the framework/tools, it will kill the published branch of the IG, but the published master will remain. If a reviewer verifies the autobuild succeeded on the branch the PR points to, they can merge it and as long as the PR build was very recent, then the master build ought to succeed. This would help avoid situations like we have now where the FHIR Shorthand documentation is 404 because autobuilds are failing due to issues in the framework.
Chris Moesel (Feb 03 2020 at 22:26):
(I realize I did not answer your original questions -- but I think it's good to also think about how we can minimize our chances of being unwitting victims to these issues).
Jose Costa Teixeira (Feb 03 2020 at 22:30):
Won't the new version thing address that?
Grahame Grieve (Feb 03 2020 at 22:32):
the version thing + the new testing framework will make it more solid, but I have no way to test this particular error - this one exists in the interplay between versions, templates, and the way the IG publisher is launched on the ci-build
Jose Costa Teixeira (Feb 03 2020 at 22:38):
"this particular error" - D.O.A.? If "D.O.A" is "the new template does not work", and assuming we will have a "current" and a "dev" version, then I'd assume that this should solve it.
Grahame Grieve (Feb 03 2020 at 22:48):
this particular error is in the ci-build infrastructure itself, not any of the templates or content
Last updated: Apr 12 2022 at 19:14 UTC
