Build #3,285

Plan branch:
More details of the release in https://wiki.openmrs.org/x/i4DTAw

Build: #3285 was successful Changes by Michael Seaton <mseaton@pih.org>

Stages & jobs

  1. Default Stage

  2. Release

    Requires a user to start manually

Build result summary

Details

Completed
Queue duration
< 1 second
Duration
2 minutes
Labels
None
Revisions
Git
f03603888100d996ba1b58e4d2706261944e6c48
Release scripts
ced9ff00825ca1cb8c744547be4ba8ff994bd71b
Total tests
496
Successful since
#3275 ()

Tests

Code commits

Git
Author Commit Message Commit date
Michael Seaton <mseaton@pih.org> Michael Seaton <mseaton@pih.org> f03603888100d996ba1b58e4d2706261944e6c48 EA-182 - Update minimum OpenMRS version to 2.2.1 and consolidate legacy code
* Increase OpenMRS version requirement to 2.2.1 (minimum required by code in web-2.2)
* Update reporting module dependencies to reflect increased OpenMRS platform dependency
* Removed api-1.10 which was only loaded used for 1.10
* Removed api-1.11 which was only loaded used for 1.11
* Removed api-pre2.2, which was only loaded for versions < 2.2.0
* Removed fhir-condition, which was only loaded for versions 2.0-2.1
* Moved / consolidated code from api-1.12 and api-2.2 into api
* Moved / consolidated code from web-2.2 into omod
* Consolidated different versions of EmrOrderService, ObservationMapper, ObsBuilder, DrugMapper, OrderMapper that were only needed to support Order API differences between 1.9 and 2.2
* Update REST supported versions
* Removed provider name tests that are not supported in OpenMRS 2.2+
* Fix failing unit tests and upgraded for compatibility with 2.2+
* Removed/conslidated EmrVisitService in favor of DiagnosisService as all methods are diagnosis related
* Ignore out unit test that fails due to multi-threading and configuration
* Remove custom CareSettingType in favor of the core version

Configuration changes

Some of the jobs or stages referenced by this result no longer exist.

Jira issues

IssueDescriptionStatus
Unknown Issue TypeEA-182Could not obtain issue details from Jira