[upgrade] add verbosity check and show repair info & steps

[MorrisJobke]

cc @LukasReschke @DeepDiver1975 @nickvergessen @PVince81

I would like to have this at least in 8.1.x. This help to find issues during a upgrade more easiely. I'm also open to backport this to older branches, but that decision is up to @karlitschek

• add documentation once this is merged

Now you can add the -v option and it will be more verbose (shows repair info and repair steps):

$ ./occ upgrade -v
ownCloud or one of the apps require upgrade - only a limited number of commands are available
Turned on maintenance mode
Repair step: Repair MySQL database engine
Repair info: Not a mysql database -> nothing to do
Repair step: Repair MySQL collation
Repair info: Not a mysql database -> nothing to no
Repair step: Repair SQLite autoincrement
Repair step: Repair duplicate entries in oc_lucene_status
Repair info: lucene_status table does not exist -> nothing to do
Repair step: Repair config
Checked database schema update
Checked database schema update for apps
Updated database
Repair step: Repair mime types
Repair step: Repair legacy storages
Repair step: Repair config
Repair step: Clear asset cache after upgrade
Repair info: Asset pipeline disabled -> nothing to do
Repair step: Generate ETags for file where no ETag is present.
Repair info: ETags have been fixed for 0 files/folders.
Repair step: Clean tags and favorites
Repair info: 0 tags for delete files have been removed.
Repair info: 0 tag entries for deleted tags have been removed.
Repair info: 0 tags with no entries have been removed.
Repair step: Drop old database tables
Repair step: Drop old background jobs
Update successful
Turned off maintenance mode

Also the old way works:

$ ./occ upgrade       
ownCloud or one of the apps require upgrade - only a limited number of commands are available
Turned on maintenance mode
Checked database schema update
Checked database schema update for apps
Updated database
Update successful
Turned off maintenance mode

[MorrisJobke]

cc @rullzer @Xenopathic

[nickvergessen]

Sounds useful to me 👍

[MorrisJobke]

@DeepDiver1975 @cmonteroluque Decide on this if this should go into 8.1 or 8.2. In either case I would at least propose a backport to stable8 and stable8.1

[MorrisJobke]

I added a repair info for the collation change to this PR because it is related to that change.

[RobinMcCorkell]

Cool! 👍

[nickvergessen]

@MorrisJobke the branch is dead:

13:14:36 ERROR: Error fetching remote repo 'origin'
13:14:36 hudson.plugins.git.GitException: Failed to fetch from https://github.com/owncloud/core.git
13:14:36    at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:735)
13:14:36    at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:983)
13:14:36    at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1016)
13:14:36    at hudson.scm.SCM.checkout(SCM.java:485)
13:14:36    at hudson.model.AbstractProject.checkout(AbstractProject.java:1282)
13:14:36    at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:610)
13:14:36    at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
13:14:36    at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:532)
13:14:36    at hudson.model.Run.execute(Run.java:1744)
13:14:36    at hudson.matrix.MatrixRun.run(MatrixRun.java:146)
13:14:36    at hudson.model.ResourceController.execute(ResourceController.java:98)
13:14:36    at hudson.model.Executor.run(Executor.java:374)

[scrutinizer-notifier]

A new inspection was created.

[MorrisJobke]

Jenkins succeeded: #17126 (comment)

[MorrisJobke]

stable8.1 is created -> merge

[MorrisJobke]

Backport see #17429