-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
implement upgrade path from 4.6.0 to 4.6.1 #1067
Conversation
looks good, let's run a test anyway. the jenkins should run it but it it's running on a INFRA-10703 host so it will most likely fail. |
7536fb1
to
e0ac9df
Compare
@DaanHoogland I rebased it, as it needs the |
merged with 4.6 branch and:
LGTM |
This is an upgrade from 4.6.0 to 4.6.1:
The database shows:
I'd say this works as expected :-) Pinging @DaanHoogland |
so, you have my lgtm, need a second one? |
Yes, let's stick to the rules :-) |
LGTM 2015-11-15 19:52:41,711 DEBUG c.c.u.DatabaseUpgradeChecker Cleanup script /usr/share/cloudstack-management/setup/db/schema-460to461-cleanup.sql is executed successfully |
implement upgrade path from 4.6.0 to 4.6.1The 4.6 branch needs an upgrade path to 4.6.1. I looked at how this was done before and think this will do. Can you give it a second pair of eyes please @DaanHoogland ? When this is indeed OK, I'll do the same for master for the 4.6.0 -> 4.7.0 path. I've tried a build and that works: `mvn clean install` ``` [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESS [INFO] ------------------------------------------------------------------------ [INFO] Total time: 07:33 min [INFO] Finished at: 2015-11-15T13:45:58+01:00 [INFO] Final Memory: 120M/1591M [INFO] ------------------------------------------------------------------------ ``` Once this is a PR, I'll try an actual upgrade from 4.6.0 to 4.6.1-SNAPSHOT. * pr/1067: implemented upgrade path from 4.6.0 to 4.6.1 Signed-off-by: Remi Bergsma <github@remi.nl>
Hi, @remibergsma and @DaanHoogland tested this PR and I reviewed the code. it LGTM 👍 Cheers, |
The 4.6 branch needs an upgrade path to 4.6.1. I looked at how this was done before and think this will do. Can you give it a second pair of eyes please @DaanHoogland ?
When this is indeed OK, I'll do the same for master for the 4.6.0 -> 4.7.0 path.
I've tried a build and that works:
mvn clean install
Once this is a PR, I'll try an actual upgrade from 4.6.0 to 4.6.1-SNAPSHOT.