Build #179

Plan branch:

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
23 minutes
Duration
77 minutes
Labels
None
Revisions
OpenMRS Platform
5e399ddd0a7ec494e985cbf0b4698f0e3b128c07 5e399ddd0a7ec494e985cbf0b4698f0e3b128c07
Release scripts
681f3bff12454842e7e4fae01a15ce2827d75dc7 681f3bff12454842e7e4fae01a15ce2827d75dc7
Standalone
f57e133a631aae82a1cb920ac82db02a50508515 f57e133a631aae82a1cb920ac82db02a50508515
openmrs-module-webservices.rest
3e8657b7d7544942f599227ba4a2888d510774d5 3e8657b7d7544942f599227ba4a2888d510774d5
Failing since
#115 (Changes by jwnasambu <33891016+jwnasambu@users.noreply.github.com> – )
No failed test found. A possible compilation error occurred.

Responsible

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

Code commits

Release scripts
Author Commit Message Commit date
Burke Mamlin <burke@openmrs.org> Burke Mamlin <burke@openmrs.org> 681f3bff12454842e7e4fae01a15ce2827d75dc7 681f3bff12454842e7e4fae01a15ce2827d75dc7 Fix sourceforge rsync transfers
Sourceforge key is now under a sourceforge subfolder. Use "openmrs" username.
Standalone
Author Commit Message Commit date
Wolf Schlegel <wolf.schlegel@thoughtworks.com> Wolf Schlegel <wolf.schlegel@thoughtworks.com> f57e133a631aae82a1cb920ac82db02a50508515 f57e133a631aae82a1cb920ac82db02a50508515 Trunk-4830 split pom into modules so that different Liquibase versions can be used (#52)
* TRUNK-4830-AC upgrade Liquibase maven plugin to 3.10.2 and refactor liquibase-ciel-data.xml

* TRUNK-4830 split pom into modules so that different Liquibase versions can be used

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