[Backport 2.10] Fixing Duplicate Pipeline Versions [CORE-2252] (#10024) #10038
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary:
This change adds a migration step to 2.10 that detects whether pipeline versions with colliding version numbers exist. If detected, the migration proceeds to renumber all of the pipeline versions for the offending pipelines, updates the corresponding Job objects in the collections.jobs table, and finally adds a UNIQUE index onto the Pipelines table so that we prevent the database from entering a bad state in the future.
TODO