On Mon, 2017-10-23 at 18:22 +0200, Konrad Windszus wrote: > Does anyone else have any idea how to enforce that publishing runs > only if the local master branch has no uncommitted changed and is > also up to date with the latest upstream repo.
We could move site publishing to a Jenkins job. That would guarantee that the latest changes are used. Another option would be to create a script which does the publishing, invoking the Maven commands, and that scripts check if the local checkout is up-to-date. I think we can even use some Maven magic to check e.g. for an environment variable which is set by the script to make it hard to publish without it. Robert
