-
Notifications
You must be signed in to change notification settings - Fork 9
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
Disable publishing of stable labels #62
Comments
Stable versions are still flip-flopping between Updated the
Using this method no label should ever regress to an older version. |
Similar problem observed on change pushed to DWSpectrum RC build on 3 June 2023. Before {
"Product": "DWSpectrum",
"Versions": [
{
"Version": "5.1.0.36830",
"Uri": "https://updates.networkoptix.com/digitalwatchdog/36830/dwspectrum-server_update-5.1.0.36830-linux_x64-rc.zip",
"Labels": [
"RC"
]
},
{
"Version": "5.0.0.36871",
"Uri": "https://updates.networkoptix.com/digitalwatchdog/36871/dwspectrum-server_update-5.0.0.36871-linux_x64.zip",
"Labels": [
"Latest"
]
},
{
"Version": "4.2.0.32842",
"Uri": "https://updates.networkoptix.com/digitalwatchdog/32842/dwspectrum-server_update-4.2.0.32842-linux64.zip",
"Labels": []
}
]
} After {
"Product": "DWSpectrum",
"Versions": [
{
"Version": "5.1.0.36751",
"Uri": "https://updates.networkoptix.com/digitalwatchdog/36751/dwspectrum-server_update-5.1.0.36751-linux_x64-rc.zip",
"Labels": [
"RC"
]
},
{
"Version": "5.0.0.36871",
"Uri": "https://updates.networkoptix.com/digitalwatchdog/36871/dwspectrum-server_update-5.0.0.36871-linux_x64.zip",
"Labels": [
"Latest"
]
},
{
"Version": "4.2.0.32842",
"Uri": "https://updates.networkoptix.com/digitalwatchdog/32842/dwspectrum-server_update-4.2.0.32842-linux64.zip",
"Labels": []
}
]
} |
And around 1 July 2023 5.1 was promoted to release, then two days later reverted to RC then a day later back to release again, arggg. |
Build tooling will now not let tagged versions regress. |
Publishing of
stable
labels to docker images are temporarily disabled.The problem scenario:
stable
tag was added to4.2
versioned releases in docker.5.0
to "released" status. (per my interpretation of the data)stable
tag was added to the5.0
versioned releases in docker.4.2
the "released" version.4.2
to5.0
is a Nx supported scenario, downgrading from5.0
to4.2
is not a Nx supported scenario.stable
tag would have automatically upgraded their4.2
build to the5.0
build.stable
tag cannot be re-applied to the4.2
builds.Publishing of
stable
labels will resume when5.0
is again promoted to a "released" status.P.s. Refer to best practices and use case studies for "fix forward vs. roll back".
The text was updated successfully, but these errors were encountered: