Publish command

[vogel]

Description

Resolves #1814

Add new command publish which publishes all (or almost all) remaining checkpoints to history archives. I may leave one unpublished in case LCL is equal to last ledger in last checkpoint, in which case we must wait for next ledger from network before progressing. Publishing of that last checkpoint is postponed to normal stellar-core run.

This PR requires #1732 to be merged first

Checklist

• Reviewed the contributing document
• Rebased on top of master (no merge commits)
• Ran clang-format v5.0.0 (via make format or the Visual Studio extension)
• Compiles
• Ran all tests
• If change impacts performance, include supporting evidence per the performance document

[MonsieurNicolas]

This needs to be rebased @vogel

[vogel]

Rebased

[MonsieurNicolas]

it would be cleaner to just set the right config elements so that app->start() does what you want (in this case, I think you just need to set STANDALONE to true)

[vogel]

STANDALONE is set before - in CommandLine.cpp:runPublish function, by calling to Config::setNoListen.

Maintenance job is normally started in ApplicationImpl::start, which we don't use in command-line catchup and publish. I think we could move calling maintenance to the end of catchup/publish process, or just ignore that and postpone the maintenance itself to normal stellar-core runs (but we can't be sure there will be no instances of stellar-core used only for command-line catchup and publish).

[MonsieurNicolas]

You didn't understand my question: why not calling start if standalone is already set?

[vogel]

Updated

[MonsieurNicolas]

r+ ce473a1