Conversation
|
@blueorangutan package |
|
@Spaceman1984 a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. |
|
Packaging result: ✖centos6 ✔centos7 ✔debian. JID-1061 |
|
Trillian test result (tid-1254)
|
|
I have tested this upgrade path like this:
|
borisstoyanov
left a comment
There was a problem hiding this comment.
LGTM,
2020-03-24 12:28:06,703 INFO [c.c.u.DatabaseUpgradeChecker] (main:null) (logid:) DB version = 4.13.0.0 Code Version = 4.13.1.0
2020-03-24 12:28:06,704 INFO [c.c.u.DatabaseUpgradeChecker] (main:null) (logid:) Database upgrade must be performed from 4.13.0.0 to 4.13.1.0
2020-03-24 12:28:06,712 DEBUG [c.c.u.DatabaseUpgradeChecker] (main:null) (logid:) Running upgrade Upgrade41300to41310 to upgrade from 4.13.0.0-4.13.1.0 to 4.13.1.0
2020-03-24 12:28:06,727 INFO [c.c.u.DatabaseUpgradeChecker] (main:null) (logid:) Cleanup upgrade Upgrade41300to41310 to upgrade from 4.13.0.0-4.13.1.0 to 4.13.1.0
2020-03-24 12:28:06,740 DEBUG [c.c.u.DatabaseUpgradeChecker] (main:null) (logid:) Upgrade completed for version 4.13.1.0
|
tests passing, 2 x LGTMS - merging |
Description
This PR adds the 4.13.0.0 to 4.13.1.0 upgrade path
Types of changes
Screenshots (if appropriate):
How Has This Been Tested?
This has been tested by starting up the client and checking the version table in the db.