SoarGroup / Release-Support

3 stars 2 forks source link

Fully automate release #5

Open garfieldnate opened 1 year ago

garfieldnate commented 1 year ago

Current release process:

VisualSoar and Eaters_TankSoar must be built from their repositories (although I had to fix VisualSoar, see https://github.com/SoarGroup/VisualSoar/issues/1), and the others are in the lib/ directory in the VisualSoar repository. Note that the log4j one is not affected by the famous security bug.

export SOAR_RELEASE_VERSION=9.6.1
export SOAR_SHUFFLER_OUTPUT_DIR=./SoarRelease
export SOAR_WIN_X86_64_COMPILED_DIR=~/Downloads/Soar_windows-x86-64_out
export SOAR_LINUX_X86_64_COMPILED_DIR=~/Downloads/Soar_linux-x86-64_out
export SOAR_MAC_X86_64_COMPILED_DIR=~/Downloads/Soar_mac-x86-64_out
export SOAR_MAC_ARM64_COMPILED_DIR=~/dev/workspaces/c_workspace/Soar/out
export SOAR_GROUP_REPOS_HOME=~/dev/workspaces/c_workspace/

You'll get the release directories wherever you specified in the SOAR_SHUFFLER_OUTPUT_DIR env var.

garfieldnate commented 1 year ago

The release instructions are now detailed in the readme; they are even longer than the ones listed in my last comment XD This ticket still stands.

garfieldnate commented 4 months ago

The release process is now a sort of checklist in release.py; over time we can automate the individual steps (there are 20ish).