Plan for OpenMRS Core 1.12.x

Build: #57 failed Changes by Wyclif Luyima

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
3 minutes
Labels
None
Revisions
Git
1f0d912d0935307a25e3574786d3cc2afc98ac88 1f0d912d0935307a25e3574786d3cc2afc98ac88
Release scripts
a9c6b4741f415820e397e9b150cf80baca7f9368 a9c6b4741f415820e397e9b150cf80baca7f9368
Total tests
52
Fixed in
#61 (Rebuilt by Cintia Del Rio)

Tests

Responsible

Code commits

Git
Author Commit Message Commit date
Wyclif Luyima Wyclif Luyima 1f0d912d0935307a25e3574786d3cc2afc98ac88 1f0d912d0935307a25e3574786d3cc2afc98ac88 Upgrading to 1.9 requires new privileges for visits which are not added by default - TRUNK-3422

Tests

New test failures 1
Status Test View job Duration
Collapse Failed Database1_9_7UpgradeIT shouldSetValuesToNullIfUnitsOrFrequencyBlank History
Integration Test 4 secs
java.io.IOException: liquibase.exception.MigrationFailedException: Migration failed for change set liquibase-update-to-latest.xml::201401101647-TRUNK-4187::wyclif:      Reason:            liquibase-update-to-latest.xml : /tmp/appdir-for-unit-tests-2243897621366385613/order_entry_upgrade_settings.txt (No such file or directory) :           Caused By: Precondition Error
java.io.IOException: liquibase.exception.MigrationFailedException: Migration failed for change set liquibase-update-to-latest.xml::201401101647-TRUNK-4187::wyclif:
     Reason: 
          liquibase-update-to-latest.xml : /tmp/appdir-for-unit-tests-2243897621366385613/order_entry_upgrade_settings.txt (No such file or directory)
:
          Caused By: Precondition Error
	at org.openmrs.util.databasechange.DatabaseUpgradeTestUtil.upgrade(DatabaseUpgradeTestUtil.java:229)
	at org.openmrs.util.databasechange.Database1_9_7UpgradeIT.shouldSetValuesToNullIfUnitsOrFrequencyBlank(Database1_9_7UpgradeIT.java:443)
(55 more lines...)

Jira issues

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