Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: update runbooks/backporting-changes-to-older-version.md #334

Merged
merged 1 commit into from
Sep 10, 2024
Merged

docs: update runbooks/backporting-changes-to-older-version.md #334

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions runbooks/backporting-changes-to-older-version.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -43,4 +43,10 @@ This runbook shows a real example of backporting changes correlated to `ta-autom
- click `Publish release`
- check if the release is available, and it points at the proper version - https://github.com/splunk/addonfactory-workflow-addon-release/tags tag `v4.16` should point to the same commit as tag `v4.16.15`
<img src="images/backporting/compare-tags.png" alt="tags"/>
Backporting changes will cause that the tag `v4` will point at the same commit as `v4.16`. To make it proper one has to either re-trigger the workflow which produced the latest tag (`v4.17.1`) or resolve that manually:
```
git fetch --tags -f
git tag -f v4 v4.17.1
git push -f --tags
```
- run the workflow for some TA using v4.16 to verify if the pipeline works as expected.
Loading