You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
the current monitoring scripts test the minor versions of the deployed actions,
eg: dispatch@v3.2
Helix internally always uses the major version. so we are testing something that is not actually used.
The following problem can arise:
assume dispatcher@v3.2.1 is the latest version
v3 -> v3.2.1
v3.2 -> v3.2.1
now, we release the next minor version:
v3 -> v3.3.0
v3.3 -> v3.3.0
v3.2 -> v3.2.1
the monitoring scripts get automatically updated during the release and now test @v3.3.
Assume, that the new version causes problems, and we need to immediately switch the v3 link back to v3.2.1. without updating the monitoring scripts, they will continue to test v3.3 (hence v3.3.0) and keep reporting errors.
Proposed Actions
Use the major version only for monitoring scripts.
The text was updated successfully, but these errors were encountered:
Overview
the current monitoring scripts test the minor versions of the deployed actions,
eg:
dispatch@v3.2
Helix internally always uses the major version. so we are testing something that is not actually used.
The following problem can arise:
dispatcher@v3.2.1
is the latest versionv3
->v3.2.1
v3.2
->v3.2.1
now, we release the next minor version:
v3
->v3.3.0
v3.3
->v3.3.0
v3.2
->v3.2.1
the monitoring scripts get automatically updated during the release and now test
@v3.3
.Assume, that the new version causes problems, and we need to immediately switch the
v3
link back tov3.2.1
. without updating the monitoring scripts, they will continue to testv3.3
(hencev3.3.0
) and keep reporting errors.Proposed Actions
Use the major version only for monitoring scripts.
The text was updated successfully, but these errors were encountered: