docs: verify that Linux release artifacts run in Docker #747
Conversation
Signed-off-by: Miroslav Bajtoš <[email protected]>
Signed-off-by: Miroslav Bajtoš <[email protected]>
Signed-off-by: Miroslav Bajtoš <[email protected]>
bajtos
changed the title
Signed-off-by: Miroslav Bajtoš <[email protected]>
| @@ -35,3 +35,42 @@ refer to `X.Y.Z` as _major_, _minor_ and _patch_ version. | |||
| changes. | |||
|
|
|||
| 1. Click on the green button `Publish release` | |||
|
|
|||
| ## Testing the release build pipeline | |||
There was a problem hiding this comment.
Is this already part of CI? Or is this something we're expected to perform manually before publishing?
There was a problem hiding this comment.
Great question!
This is not part of CI, we're expected to perform this manually when making changes to the release build pipeline (the GitHub Actions workflow).
I.e. this is a manual check to verify that the release build pipeline works as expected.
Do you think it's worth automating this check and running it for every release?
There was a problem hiding this comment.
I think it's fine to keep it manual, but can you please document that this is to be performed when working on the pipeline? That wasn't clear to me
There was a problem hiding this comment.
Ie "testing the release build pipeline" could also mean it's something you're supposed to do after every release, to verify the release build pipeline worked
Capturing the comment #172 (comment)
Related to: