Grief Prevention

Grief Prevention

Bukkit Plugins
1M Downloads

Establish release process

Closed this issue ยท 1 comments

commented

Current process is manual, would like to automate and formally standardize it.

Is mvn deploy a good process to use for automating build process? As mvn deploy has a lot of assumptions, and attempts to perform multiple commits (using 'SNAPSHOT' terminology and such).

Current manual process

Build process

The version number presented in-game is expected to include the commit hash only if the build was built on an untagged (and therefore unreleased) commit.

  • New commit is made with version number changed in pom.xml
  • This commit is git tagged with the version number
    • This often happens via pushing the new commit to GitHub, and then using GitHub Releases to create the tag
  • The commit is built with mvn clean package

Release process

  • Create GitHub Release
  • The resulting target/GriefPrevention.jar is uploaded to BukkitDev, with GitHub Release notes copied into description
  • GitHub release is published/updated with link to BukkitDev release
  • After BukkitDev approval, copy and paste GitHub release to spigot release
commented

I do intend for this to be a task, but I realize I'm still at the discussion/gathering info phase of this task, so am converting to discussion.