OpenMRS Core Master

Build: #2545 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
15 minutes
Labels
None
Revisions
openmrs-core
4e583b698e6ed99200f3b8e82ff8557214c6d0a0 4e583b698e6ed99200f3b8e82ff8557214c6d0a0
openmrs-standalone
f41bad710932f3ad84332b5996ecc0efb28f6ebc f41bad710932f3ad84332b5996ecc0efb28f6ebc
Release scripts
681f3bff12454842e7e4fae01a15ce2827d75dc7 681f3bff12454842e7e4fae01a15ce2827d75dc7
Total tests
4456
Successful since
#2541 ()

Tests

Code commits

openmrs-core
Author Commit Message Commit date
Michael Seaton <mseaton@pih.org> Michael Seaton <mseaton@pih.org> 4e583b698e6ed99200f3b8e82ff8557214c6d0a0 4e583b698e6ed99200f3b8e82ff8557214c6d0a0 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.

Configuration changes

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

Manual stage Release cannot be run as it references jobs that no longer exist.

Jira issues

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