-
Notifications
You must be signed in to change notification settings - Fork 636
Allow inclusion of repository in the tag name, so ghcr and dockerub c… #345
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.
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
Conversation
…an be used, including in the same experiment
Codecov ReportBase: 48.40% // Head: 48.37% // Decreases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## v0.34.x #345 +/- ##
===========================================
- Coverage 48.40% 48.37% -0.04%
===========================================
Files 280 280
Lines 49887 49908 +21
===========================================
- Hits 24150 24145 -5
- Misses 23878 23900 +22
- Partials 1859 1863 +4
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
…ersions. Uses multiversion to set UpgradeVersion.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for this!
#345) * Allow inclusion of repository in the tag name, so ghcr and dockerub can be used, including in the same experiment * Moves UpgradeVersion to Node, so nodes can be upgraded to different versions. Uses multiversion to set UpgradeVersion. * Updates the path for the local-version image. * Do not use yoda conditions. * Use the right code coverage definitions * Revert use of . We will only do a maximum of 2 versions per run
#345) * Allow inclusion of repository in the tag name, so ghcr and dockerub can be used, including in the same experiment * Moves UpgradeVersion to Node, so nodes can be upgraded to different versions. Uses multiversion to set UpgradeVersion. * Updates the path for the local-version image. * Do not use yoda conditions. * Use the right code coverage definitions * Revert use of . We will only do a maximum of 2 versions per run
#345) (#362) * Allow inclusion of repository in the tag name, so ghcr and dockerub can be used, including in the same experiment * Moves UpgradeVersion to Node, so nodes can be upgraded to different versions. Uses multiversion to set UpgradeVersion. * Updates the path for the local-version image. * Do not use yoda conditions. * Use the right code coverage definitions * Revert use of . We will only do a maximum of 2 versions per run
#345) (#362) * Allow inclusion of repository in the tag name, so ghcr and dockerub can be used, including in the same experiment * Moves UpgradeVersion to Node, so nodes can be upgraded to different versions. Uses multiversion to set UpgradeVersion. * Updates the path for the local-version image. * Do not use yoda conditions. * Use the right code coverage definitions * Revert use of . We will only do a maximum of 2 versions per run (cherry picked from commit 45a08f3)
#345) (#362) (#363) * Allow inclusion of repository in the tag name, so ghcr and dockerub can be used, including in the same experiment * Moves UpgradeVersion to Node, so nodes can be upgraded to different versions. Uses multiversion to set UpgradeVersion. * Updates the path for the local-version image. * Do not use yoda conditions. * Use the right code coverage definitions * Revert use of . We will only do a maximum of 2 versions per run (cherry picked from commit 45a08f3) Co-authored-by: Lasaro <lasaro@informal.systems>
…an be used, including in the same experiment
Should be ported to 0.37 and main.
PR checklist
.changelog
(we useunclog to manage our changelog)
docs/
orspec/
) and code comments