Build #2,276

Plan branch:
OpenMRS Core Master

Build: #2276 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
2 seconds
Duration
24 minutes
Labels
None
Revisions
openmrs-core
20cec90a006e5bd9d7a0884ee98bdbd8d405564b 20cec90a006e5bd9d7a0884ee98bdbd8d405564b
openmrs-standalone
8af748fdb6fe93f74ebb4b89e03b262fcd37b5c0 8af748fdb6fe93f74ebb4b89e03b262fcd37b5c0
Release scripts
1969d1c2650fc66ab14f5edb4052a329a196f370 1969d1c2650fc66ab14f5edb4052a329a196f370
Total tests
4406
Successful since
#2258 ()

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-2277 created from build #2277

Code commits

openmrs-core
Author Commit Message Commit date
teleivo <teleivo@users.noreply.github.com> teleivo <teleivo@users.noreply.github.com> 20cec90a006e5bd9d7a0884ee98bdbd8d405564b 20cec90a006e5bd9d7a0884ee98bdbd8d405564b TRUNK-5816 Move helpers into org.openmrs.test.jupiter
Junit 5 allows us to easily migrate to it also because classes,
annotations replacing the ones in Junit 4 have the same name but are
simply in another package called org.junit.jupiter. This is why the
IntelliJ migration tool only needs to change imports for example for the
@Test

We can follow the same approach end provide BaseContext... classes in a
new package called jupiter. When api tests or module tests migrate they
just need to update the import and everything else should work as before

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-5816Could not obtain issue details from Jira