Stream: IG creation
Topic: IG build / github hook
Jose Costa Teixeira (Jul 22 2019 at 20:09):
Hi. Is there any advice /instructions on how to get our own IG build from github?
Lloyd McKenzie (Jul 22 2019 at 20:11):
You mean a CI build?
Lloyd McKenzie (Jul 22 2019 at 20:11):
You could steal Josh's code and host it in your own VM
Jose Costa Teixeira (Jul 22 2019 at 20:28):
next question is precisely where is Josh's code
and the question after that is - do I want to document as I go at this for e.g. IHE, so that others can have it easier (presuming there is a learning curve)
Jose Costa Teixeira (Jul 22 2019 at 20:30):
thanks for the answer, @Lloyd McKenzie.
@Josh Mandel will you please let me know how I could get started?
Josh Mandel (Jul 22 2019 at 20:40):
All the relevant code is at https://github.com/fhir/auto-ig-builder -- though there's a fair bit of infrastructure behind it (k8s, etc).
Grahame Grieve (Jul 22 2019 at 20:40):
why would you do your own?
Grahame Grieve (Jul 22 2019 at 20:40):
I actively encourage you not to do that
Lloyd McKenzie (Jul 22 2019 at 20:41):
I think @Jose Costa Teixeira is asking about doing CI build for IHE - and that might be reasonable to host separately
Grahame Grieve (Jul 22 2019 at 20:41):
why? That's what I think is a bad idea
Josh Mandel (Jul 22 2019 at 20:41):
Is this for IGs? Would be easy enough to use shared infrastructure if IHE is comfortable.
Jose Costa Teixeira (Jul 22 2019 at 20:45):
well, this is based on my broad ignorance.
We should deploy the result to an IHE site. To achieve this, whether we use the same build or we need to replicate, does not really matter (I guess?..).
Jose Costa Teixeira (Jul 22 2019 at 20:47):
Yes, this is for IGs. IHE will have some additional governance, templates, perhaps pre- and post-processing, but if we can reuse the same build, that is good.
Grahame Grieve (Jul 22 2019 at 20:48):
why should you deploy the CI build to an IHE site? The publication, sure... of course.
Grahame Grieve (Jul 22 2019 at 20:49):
as for pre- and post- processing.... if we can't build what is needed into the IG publisher + templates, then sure, you will need your own build infrastructure
Jose Costa Teixeira (Jul 22 2019 at 20:50):
That is it.
I did not know if, in order to have a separate hosting location, we would need another build infrastructure
Jose Costa Teixeira (Jul 22 2019 at 20:50):
pre-and post-processing might be needed, but I can't see that far ahead
Lloyd McKenzie (Jul 22 2019 at 20:52):
IHE probably doesn't want their interim stuff hosted under build.fhir.org. Though I guess it's not problematic. (In reality, not everyone who wants a CI environment will necessarily want to have a relationship w/ fhir.org)
Jose Costa Teixeira (Jul 22 2019 at 20:54):
as long as we don't have to copy the HTML content to ihe.net web server, we should be ok.
Jose Costa Teixeira (Jul 22 2019 at 20:58):
The build process for IHE will likely start with IHE's github repo, and should (somehow) end on www.ihe.net
Grahame Grieve (Jul 23 2019 at 00:58):
Well, we have two build processes - the ci build, which I think one should just use exactly as we do, and then the publication build process which is down manually when we decide to do a release, has all sorts of check processes, and registry maintenance steps. Ihe needs it’s own variant process of the second, but I strongly recommend you just use the first process, the ci build, as is
Jose Costa Teixeira (Jul 23 2019 at 09:46):
Then we start with what we have, and we see how to add any enhancement needed.
How do we start (esp the publication release)?
Grahame Grieve (Jul 23 2019 at 10:42):
setting up the CI build is documented for the ig publisher, and you should not need anything special
Grahame Grieve (Jul 23 2019 at 10:42):
managing publishing .... that's something we should talk face to face on. but the process is here:
Grahame Grieve (Jul 23 2019 at 10:43):
http://wiki.hl7.org/index.php?title=Process_for_Publishing_a_FHIR_IG
Grahame Grieve (Jul 23 2019 at 10:44):
I would recommend that IHE adopt an extremely similar process, but I'd have to do some coding to make the tools handle IHE variations - which I'll be happy to do
Jose Costa Teixeira (Oct 14 2019 at 15:45):
I guess we have until Sydney to come up with requirements and ideas...
Grahame Grieve (Oct 15 2019 at 08:29):
yes. I have worked if over last week to make it more flexible.
Grahame Grieve (Oct 15 2019 at 08:30):
I have to document it this week
Jose Costa Teixeira (Oct 15 2019 at 09:44):
If useful, I can help with documenting (it may help me understanding)
Grahame Grieve (Oct 15 2019 at 09:47):
ok thx
Last updated: Apr 12 2022 at 19:14 UTC
