This repository has been archived by the owner on Jan 8, 2024. It is now read-only.
Backport of Feature: Reattach to a pipeline run by latest or sequence id into release/0.10.x #4104
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
hc-github-team-waypoint
force-pushed
the
backport/feat/pipelines/reattach-pipeline-run/manually-sacred-drum
branch
from
ba0b90b to
ed6dbc2
Compare
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Backport
This PR is auto-generated from #4042 to be assessed for backporting due to the inclusion of the label backport/0.10.x.
WARNING automatic cherry-pick of commits failed. Commits will require human attention.
The below text is copied from the body of the original PR.
This pull request introduces a new CLI flag for
pipeline runto enable the CLI to reattach to an existing pipeline run, either by the latest known run, or by a specific sequence id. It will attempt to reply the job ids in the order defined in the pipeline run message.Fixes #4010