Build #2,295

Plan branch:
OpenMRS Core Master

Build: #2295 was successful Changes by teleivo <teleivo@users.noreply.github.com>

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
17 minutes
Labels
None
Revisions
openmrs-core
99a8057e52a899169d2a731111217eea11cff5a7 99a8057e52a899169d2a731111217eea11cff5a7
openmrs-standalone
8af748fdb6fe93f74ebb4b89e03b262fcd37b5c0 8af748fdb6fe93f74ebb4b89e03b262fcd37b5c0
Release scripts
1969d1c2650fc66ab14f5edb4052a329a196f370 1969d1c2650fc66ab14f5edb4052a329a196f370
Total tests
4406
Successful since
#2292 ()

Tests

Included in deployment project

Deploy Trunk Nightly

No release with the artifacts of this build exists.
The next release containing these commits is release openmrs-trunk-2299 created from build #2299

Code commits

openmrs-core
Author Commit Message Commit date
teleivo <teleivo@users.noreply.github.com> teleivo <teleivo@users.noreply.github.com> 99a8057e52a899169d2a731111217eea11cff5a7 99a8057e52a899169d2a731111217eea11cff5a7 Use assertThrows instead of try/catch in tests
this idiom seems to stem from the JUnit 3 times
https://github.com/junit-team/junit4/wiki/Exception-testing#trycatch-idiom
now with JUnit 4/5 the preferred approach is assertThrows
https://github.com/junit-team/junit4/wiki/Exception-testing#using-assertthrows-method
teleivo <teleivo@users.noreply.github.com> teleivo <teleivo@users.noreply.github.com> da4854a7a671d3add241e87787e4563953c3396e da4854a7a671d3add241e87787e4563953c3396e Use assertFalse instead of assertEquals(true, expression)
since assertTrue/assertFalse are specifically written for these assertions

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.