This website uses cookies to ensure you get the best experience.
Learn more.
An existing pipeline deploys schema-changing revisions. Concurrent executions can finish out of order and install an older revision last. Which control should be evaluated?
Published
- Retry older executions indefinitely after newer releases succeed.
- Allow unrestricted parallel execution and assume completion order equals commit order.
- Generate random release identities and discard all source revision metadata.
- Use an execution mode and deployment serialization strategy that preserves the required release order, with version-aware deployment checks.
Comments — 0
Sign in to comment