We’re working on getting the FHIR module included in Platform 2.0 (Q4 2015).
As part of this, we would like to have the configuration settings on the CI platform for FHIR be upgraded so that it runs all the tests that are required of a module that will be part of platform 2.0.
I think that a reasonable plan would be to see what configs are used on the rest webservices module, and then run the same settings on the FHIR module as well?
Is there a reason you want it to “be upgraded” as opposed to just upgrading it? Can you do this?
Actually, after I wrote this, I realized that I probably had the permissions to do this by myself; soI guess the question is, is what i’m proposing to do (copying the webservices CI plan to make sure that i’m running all the tests needed for platform 2.0 release) the right way for me to proceed?
So I reviewed the CI plan configurations for webservices and FHIR at: https://ci.openmrs.org/chain/admin/config/defaultStages.action?buildKey=FHIR-FM and
The default jobs under stages both look similar, but the dependencies are very very different. I wonder if someone (maybe @cintiadr) can advise me on what I specifically need to configure
Ok, I was finally able to update the CI plan thanks to @wyclif’s advice.
You can see the updated plan here: https://ci.openmrs.org/browse/FHIR-FM
I also ran it once, and everything seems to pass: see https://ci.openmrs.org/browse/FHIR-FM-JOB1-53/test/case/77602861
So as far as I can see, everything’s well, and we’re on track to releasing FHIR as part of platform 2.0
I believe there must also be a CI plan that generates the standalone for
the Platform release (e.g. with the REST module). This also needs to be
updated to include the FHIR module.