Page History

...

• Recreate OpenHIE environment in Rwanda.
• Create a Web Demo for public use.
• Implement Continuous Integration for OpenHIE component interoperability
  • Nightly Builds
  • Automated deployments
  • Automated tests
  • Statistics on code quality and coverage

Environments

Development (

...

dev)

The dev environment of the sandbox is where automated builds are deployed.  The builds come from our CI server and are automatically deployed nightly.

...

Testing (

...

test)

The OpenHIE sandbox is the place to find all of the newest developments in the community.  This will serve as a place to experiment with new builds of software, new configurations and data. This is not stable and could change at any time. 

...

1. Code is committed to a community repo.
2. CI checks code repository for latest changes.
3. Code is compiled / packaged and made into an artifact.  Unit tests are also run if available.
4. Artifact is deployed to our dev environment.  Manual testing may occur, for functionality and interoperability. Test interoperability against staging (which should mirror prod).
5. Release artifact is deployed.  Bamboo build agent runs integration tests.  Users will do User Acceptance Testing to determine if all expected functionality works as expected.
6. If all tests pass, make a Release of OpenHIE, which specifies OpenHIE (e.g. v0.2.1 = OpenHIM 2.3, OpenEMPI 2.9.6, ...etc).  Deploy using automated scripts to demo environment. 

Status

...

Testing Environment

Demo

OpenHIE Demo