Build #503

Plan branch:

Build: #503 failed Changes by OpenMRS Administrator

Stages & jobs

  1. Update versions

  2. Build

  3. Push docker image

  4. Validate

  5. Release

    Requires a user to start manually

  6. Release 2nd stage

  7. Release 3rd stage

Build result summary

Details

Completed
Queue duration
2 minutes
Duration
191 minutes
Labels
None
Revisions
OpenMRS Platform
84d3cd9de4de399813618b8535b27810da622d2e 84d3cd9de4de399813618b8535b27810da622d2e
Release scripts
ab83775184d5fb0f928388fa25ee675b855dd53c ab83775184d5fb0f928388fa25ee675b855dd53c
Standalone
57fffee4aa3fe0d23653f28781db49dcfc15dbe1 57fffee4aa3fe0d23653f28781db49dcfc15dbe1
openmrs-module-webservices.rest
cc34d86cf1e7a2fcb34e6cf723840d7d900770e0 cc34d86cf1e7a2fcb34e6cf723840d7d900770e0
Failing since
#502 (Changes by jwnasambu <33891016+jwnasambu@users.noreply.github.com> – )
Fixed in
#504 (Child of TRUNK-MASTER-2131)
No failed test found. A possible compilation error occurred.

Responsible

This build has been failing since #502
No one has taken responsibility

Comments on Build standalone

  1. Anonymous user

    Detected hung build state. Attempting to generate stack trace and terminate spawned sub-processes.

Code commits

OpenMRS Platform
Author Commit Message Commit date
OpenMRS Administrator OpenMRS Administrator 84d3cd9de4de399813618b8535b27810da622d2e 84d3cd9de4de399813618b8535b27810da622d2e "Updated versions
Standalone
Author Commit Message Commit date
jwnasambu <33891016+jwnasambu@users.noreply.github.com> jwnasambu <33891016+jwnasambu@users.noreply.github.com> 57fffee4aa3fe0d23653f28781db49dcfc15dbe1 m 57fffee4aa3fe0d23653f28781db49dcfc15dbe1 STAND-86:Consistently use CIEL (not MVP) in the UI and under the… (#37)
Co-authored-by: jwamalwa <julietwamalwa@yahoo.com>

Configuration changes

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

Restarting failed/incomplete builds only is not possible as some of the affected jobs no longer exist.

Jira issues

IssueDescriptionStatus
Unknown Issue TypeSTAND-86Could not obtain issue details from Jira