Build #25

Plan branch:

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

Stages & jobs

  1. Build and Test

  2. Deploy

  3. Release

    Requires a user to start manually

Build result summary

Details

Completed
Queue duration
< 1 second
Duration
16 minutes
Labels
None
Revisions
openmrs-core
ec6c6c5cb605655ff81496da81ade799a198948a ec6c6c5cb605655ff81496da81ade799a198948a
openmrs-standalone
f41bad710932f3ad84332b5996ecc0efb28f6ebc f41bad710932f3ad84332b5996ecc0efb28f6ebc
Release scripts
681f3bff12454842e7e4fae01a15ce2827d75dc7 681f3bff12454842e7e4fae01a15ce2827d75dc7
Total tests
4453
Successful since
#4 ()

Tests

Code commits

openmrs-core
Author Commit Message Commit date
Michael Seaton <mseaton@pih.org> Michael Seaton <mseaton@pih.org> ec6c6c5cb605655ff81496da81ade799a198948a ec6c6c5cb605655ff81496da81ade799a198948a TRUNK-5977 - getPatientOrPromotePerson leading to stack traces under … (#3631)
TRUNK-5977 - getPatientOrPromotePerson leading to stack traces under some conditions.  This changes the current approach by first loading the person with the given id, and then checking if the returned person is a patient or not.
 Unfortunately, none of the unit tests catch the error that this is fixing, but running the refapp with this fix + a related fix to idgen fixes the error case as described on the ticket.

Jira issues

IssueDescriptionStatus
Unknown Issue TypeTRUNK-5977Could not obtain issue details from Jira