MRJP-27 Renamed flow from release to tagged. Updated README

Author: ToreMerkely

.github/workflows/build-app.yml

@@ -27,8 +27,8 @@ jobs:
         id: begin-trail
         uses: kosli-dev/jira-multi-repo-release/.github/actions/kosli-begin-trail-commit-or-release@main
         with:
-          kosli-release-flow: "jira-multi-repo-back-release"
-          kosli-release-template: "kosli-flow-templates/release-template.yml"
+          kosli-release-flow: "jira-multi-repo-back-tagged"
+          kosli-release-template: "kosli-flow-templates/tagged-template.yml"
           kosli-commit-flow: "jira-multi-repo-back-app"
           kosli-commit-template: "kosli-flow-templates/app-template.yml"
 

.github/workflows/setup-kosli.yml

@@ -37,8 +37,8 @@ jobs:
             --description "Track jira multi repo back attestations for application"
             --template-file kosli-flow-templates/app-template.yml
 
-      - name: Create jira-multi-repo-back-release flow
+      - name: Create jira-multi-repo-back-tagged flow
         run:
-          kosli create flow jira-multi-repo-back-release
-            --description "Track jira multi repo back attestations for releases"
-            --template-file kosli-flow-templates/release-template.yml
+          kosli create flow jira-multi-repo-back-tagged
+            --description "Track jira multi repo back attestations for tagged versions"
+            --template-file kosli-flow-templates/tagged-template.yml

README.md

@@ -1,2 +1,43 @@
 # jira-multi-repo-back
-Example of jira release process for a multi repo project. Backend.
+
+This is part of a collection of 3 repos
+jira-multi-repo-back
+jira-multi-repo-front
+jira-multi-repo-release
+
+The purpose is to show an example of the release of multiple services
+together to production using tagged versions and Jira.
+
+## Normal Development
+This is a helper repo that shall simulate a micro-service that has its own repo.
+Changes to the source code and new versions of the SW is simulated by updating
+the `counter=` variable in
+```shell
+app/backend/backend-content.txt
+```
+The tracking of application builds when merging to main is tracked in
+[jira-multi-repo-back-app](https://app.kosli.com/kosli-public/flows/jira-multi-repo-back-app/trails/)
+flow with a trail naming matching git commit.
+
+The team use Pull-requests and always have a reference to a
+Jira Issue. The tracking of these attestations are done in the
+[jira-multi-repo-back-source](https://app.kosli.com/kosli-public/flows/jira-multi-repo-back-source/trails/)
+flow.
+
+
+## Tagged version of SW ready for release
+When the team is of the opinion that the SW is ready to the next release to
+production they make a tagged version of the SW. This is done by pushing a tag
+of the format `v.*.*.*`.
+
+Tagged SW versions are tracked in the 
+[jira-multi-repo-back-tagged](https://app.kosli.com/kosli-public/flows/jira-multi-repo-back-tagged/trails/)
+flow
+
+For each tagged version of the SW we attest a list of Jira Issues since previous tagged version.
+An example for version v2.0.11 can be found [here](https://app.kosli.com/kosli-public/flows/jira-multi-repo-back-tagged/trails/v2.0.11?attestation_id=c32734cf-ccd6-4f8b-baaa-6b790a0a)
+
+At this point the SW team has done their job and the release manager will now orchestrate
+the next release and approval of SW to production.
+
+Please see the README of `jira-multi-repo-release` for details.