From 397f1669b8da3b534f596677a40f958e6f57dcfa Mon Sep 17 00:00:00 2001
From: Chad Wilson <chadw@thoughtworks.com>
Date: Thu, 15 Sep 2022 23:14:33 +0800
Subject: [PATCH] Document release steps

---
 DEVELOPMENT.md   | 10 ++++++++++
 build.gradle.kts |  4 ++++
 2 files changed, 14 insertions(+)

diff --git a/DEVELOPMENT.md b/DEVELOPMENT.md
index 14132453..9aeffa59 100644
--- a/DEVELOPMENT.md
+++ b/DEVELOPMENT.md
@@ -101,3 +101,13 @@ Due to the config-driven nature of the tool, there are a number of tests which l
 
 Currently, core maintainer privileges are only available to Thoughtworkers. A setup guide is available [here (internal only)](https://docs.google.com/document/d/1r56rDyGOnRQAAMyHtUHflML1szdvQJMi8p3bzMNB_8A/edit#).
 
+## Releasing
+
+Needs to be more automated. Current we are experimenting with using [Reckon](https://github.com/ajoberstar/reckon) to determine versions from flags.
+
+Current release process looks like
+1. Tag locally and push
+    ```shell
+    ./gradlew -Preckon.stage=final reckonTagPush
+    ```
+2. This will trigger a build on GitHub Actions and push to GHCR. Create a new elease on Github via https://github.com/ThoughtWorks-SEA/recce/releases
diff --git a/build.gradle.kts b/build.gradle.kts
index 4d7682cc..e650147c 100644
--- a/build.gradle.kts
+++ b/build.gradle.kts
@@ -288,3 +288,7 @@ tasks.jibDockerBuild.configure {
         }
     }
 }
+
+tasks.reckonTagCreate {
+    dependsOn(tasks.check)
+}