Release automation #802

Done

• update script does not update gradle-plugin in kotlin example projects (addressed) ✔️
• update script does not update java11 pom and maven pom in example projects ✔️
• issues with checkout of gh-pages make script fail (addressed) ✔️
• git push fails due to missing rights, git release fails as well (addressed) ✔️
• script to publish release on github does not have an execution permission ✔️
• publishing on JGiven does not work because executor does not have jekyll installed ✔️
• no post was created on website -> post creation script does not commit and push.
• release script does not commit example projects (addressed) ✔️
• publish release to Github does not work -> script permissions? (addressed) ✔️
• jekyll does not terminate, because we told it not to. (adressed) ✔️
• issue with sign publication during release ✔️
• gh-pages change is not pushed to github (addressed) https://github.com/TNG-release/JGiven-Release/pull/8 (✔️ )

To Fix

• the new checkout version does not pull the branch but only the commit, hence pushing does not push to master (i
  • reason is insufficient rights for the bot see: https://github.com/TNG-release/JGiven-Release/issues/7
• gh-pages change is not pushed to github (addressed) https://github.com/TNG-release/JGiven-Release/pull/8
• Asciidoc was published with incorrect version (reason: publish scripts reset git to master instead of the current branch)
  ** scripts should return to original branch with git checkout - (addressed Issue-802: Release script return to previous branch #1394)

To Improve

• no check to see if there is already a release of the same version on github
• no check to see if there is already a release of the same version on maven central
• script does not fail if git push fails
• ensure that there is a changelog