https://github.com/kosli-dev/jira-multi-repo-back
Example of jira release process for a multi repo project. Backend.
https://github.com/kosli-dev/jira-multi-repo-back
Last synced: about 1 month ago
JSON representation
Example of jira release process for a multi repo project. Backend.
- Host: GitHub
- URL: https://github.com/kosli-dev/jira-multi-repo-back
- Owner: kosli-dev
- License: mit
- Created: 2025-06-19T05:04:24.000Z (9 months ago)
- Default Branch: main
- Last Pushed: 2025-08-28T12:03:05.000Z (7 months ago)
- Last Synced: 2025-08-28T19:26:37.686Z (7 months ago)
- Size: 19.5 KB
- Stars: 0
- Watchers: 0
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# jira-multi-repo-back
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 and also instructions for
running a demo.