Yes, ultimately we donât want CI using any devtest machines, leaving those for developers to use as needed for experimentation, showcases, etc.
Making the aliases now letâs @cintiadr proceed using intârefapp.openmrs.org & qaârefapp.openmrs.org within CI plans/scripts independent of @ryan migrating those to new machines (or creating new devtest machines and renaming the existing ones).
devtest03 and demo should not be touched.
Other option, as @darius mentioned, is not rename them at all, just create new ones for int-refapp and qa-refapp
Create the following servers:
If that can be done quickly (e.g., within 24 hours), then letâs do it. @cintiadr will be unblocked and we can throw devtest01 & devtest02 back in the pool.
If creating six machines will take >24 hours, then please create the following aliases now (so we can move forward until those 6 new machines can be created):
Iâm done with demo-ing the qa01.openmrs.org server, and can hand it over for correct use. For the new machines, which should/could I use for our work on FHIR?
You can make a request to the helpdesk for a new machine and they can help assign a server based on the need:
Demo/playground: devtest
Integrated (automated) testing: int
Quality assurance (manual) testing: qa
User acceptance testing for a specific relase: uat
If youâre unsure, itâs probably a devtest server.
Ideally/alternatively, since you are aiming to get FHIR into Platform 2.0, get the FHIR module included in the distribution of the Platform (so it would be tested & deployed to intâplatform, qaâplatform, and, when we begin testing for the 2.0 release, uatâplatform.
For reference, I couldnât find any help desk cases from @surangak about being done with QA01, or any help desk cases from @burke about creating new instances.
Our near-term goal for Platform 2.0 Alpha release should be to get this automatically building on http://int-platform.openmrs.org. Once thatâs working (automatic build & redeploy on each commit) to support automated testing of the platform, then we can aim for getting http://qa-platform.openmrs.org configured such that we can manually trigger a new deployment on demand for quality assurance (manual) testing.
You should be able to coordinate with helpdesk at openmrs.org to get these environments working. If you have any questions/issues, donât hesitate to reach out to us.