OpenMRS Core Master

Stages & jobs

  1. Build

  2. Test

  3. Deploy

  4. Release

    Requires a user to start manually

Build result summary

Details

Completed
Queue duration
< 1 second
Duration
30 minutes
Labels
None
Revisions
openmrs-core
648881adc8b5b8782c9fb199346bbe977d562934
openmrs-standalone
885ad10c3e56ae11105727bb801f2f04042a18d9
Release scripts
c4475a9228b197817dce78683d9da8a1e2c4e3a5
Failing since
#2973 (Changes by dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>)
Fixed in
#2985 (Rebuilt by Rafal Korytkowski)
No failed test found. A possible compilation error occurred.

Responsible

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

Code commits

openmrs-core
Author Commit Message Commit date
Wikum Weerakutti <wikum@linuxdeveloper.space> Wikum Weerakutti <wikum@linuxdeveloper.space> 648881adc8b5b8782c9fb199346bbe977d562934 TRUNK-6066 Rename host.url global property (#4121)
* TRUNK-6066 Rename host.url global property

The host.url global property is inconsistent with usage in password reset API. This renames host.url to security.passwordResetUrl .

* TRUNK-6066 Rename and deprecate host.url global property

The host.url global property is inconsistent with usage in password reset API. This copy over existing value from host.url to security.passwordResetUrl. Then host.url get deprecated.

* TRUNK-6066 Rename and deprecate host.url

The host.url global property is inconsistent with usage in password reset API. This renames host.url to security.passwordResetUrl. Then deprecate host.url.

* TRUNK-6066 Adding a logic to assign a value to OpenmrsConstants.GP_PASSWORD_RESET_URL

For backwards compatibility, Adding a logic to assign the value of OpenmrsConstants.GP_HOST_URL to OpenmrsConstants.GP_PASSWORD_RESET_URL when there is value to OpenmrsConstants.GP_HOST_URL and OpenmrsConstants.GP_PASSWORD_RESET_URL is empty.

Configuration changes

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

Jira issues

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