Skip to content

Set version 4.6.3-SNAPSHOT in 4.6 branch#1265

Merged
asfgit merged 2 commits into
apache:4.6from
remibergsma:463_version
Dec 21, 2015
Merged

Set version 4.6.3-SNAPSHOT in 4.6 branch#1265
asfgit merged 2 commits into
apache:4.6from
remibergsma:463_version

Conversation

@remibergsma
Copy link
Copy Markdown
Contributor

@remibergsma remibergsma commented Dec 21, 2015

  • setnextversion.sh
  • upgrade path

Build succeeds:

[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 08:44 min
[INFO] Finished at: 2015-12-21T14:13:29+01:00
[INFO] Final Memory: 123M/1578M
[INFO] ------------------------------------------------------------------------

Will try upgrade soon.

@DaanHoogland
Copy link
Copy Markdown
Contributor

DaanHoogland commented Dec 21, 2015

looks good

@rafaelweingartner
Copy link
Copy Markdown
Member

rafaelweingartner commented Dec 21, 2015

LGTM,
BTW: Looking at that database upgrade checker that does not just check but also upgrade the ACS schema, I got me thinking that there has to be a better way to do that. Have we started any discussions about how to improve and facilitate that process?

@remibergsma
Copy link
Copy Markdown
Contributor Author

remibergsma commented Dec 21, 2015

@rafaelweingartner True story, the faster we release versions the harder it becomes. It needs to be changed, preferably in a tool outside of CloudStack. We should investigate what's already available, because we aren't the only one with this problem. For now, I'll just do the monkey work ;-)

I can do 4.7 and master once the 4.7 branch gets mirrored to Github. Will check again tonight.

@rafaelweingartner
Copy link
Copy Markdown
Member

rafaelweingartner commented Dec 21, 2015

I understand you; I will have a look at that, to see how other projects deal with that kind of problem. If I find something interesting I will bring that to the dev list

@remibergsma
Copy link
Copy Markdown
Contributor Author

remibergsma commented Dec 21, 2015

And it works:

INFO  [o.a.c.s.l.CloudStackExtendedLifeCycle] (main:null) Running system integrity checker com.cloud.upgrade.DatabaseUpgradeChecker@847ca9d
INFO  [c.c.u.DatabaseUpgradeChecker] (main:null) Grabbing lock to check for database upgrade.
INFO  [c.c.u.DatabaseUpgradeChecker] (main:null) DB version = 4.6.2 Code Version = 4.6.3-SNAPSHOT
INFO  [c.c.u.DatabaseUpgradeChecker] (main:null) Database upgrade must be performed from 4.6.2 to 4.6.3-SNAPSHOT
INFO  [c.c.u.DatabaseUpgradeChecker] (main:null) Cleaning upgrades because all management server are now at the same version
INFO  [c.c.u.DatabaseUpgradeChecker] (main:null) Cleanup upgrade Upgrade462to463 to upgrade from 4.6.2-4.6.3 to 4.6.3
INFO  [o.a.c.s.l.CloudStackExtendedLifeCycle] (main:null) Configuring CloudStack Components
INFO  [o.a.c.s.l.CloudStackExtendedLifeCycle] (main:null) Done Configuring CloudStack Components

@asfgit asfgit merged commit 6646c7d into apache:4.6 Dec 21, 2015
asfgit pushed a commit that referenced this pull request Dec 21, 2015
@remibergsma
Merge pull request #1265 from remibergsma/463_version
451ae2b 
Set version 4.6.3-SNAPSHOT in 4.6 branch- setnextversion.sh
- upgrade path

Build succeeds:
```
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 08:44 min
[INFO] Finished at: 2015-12-21T14:13:29+01:00
[INFO] Final Memory: 123M/1578M
[INFO] ------------------------------------------------------------------------
```

Will try upgrade soon.

* pr/1265:
  Implement upgrade path 4.6.2 -> 4.6.3
  Updating pom.xml version numbers for release 4.6.3-SNAPSHOT

Signed-off-by: Remi Bergsma <github@remi.nl>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

4 participants

@remibergsma @DaanHoogland @rafaelweingartner @asfgit