Seeing old complete runs rather than runs in progress, when a run hasn't started yet #8
Comments
|
This cli doesn’t support tags, I would need to change the api endpoint I am using |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
I have a script that pushes a tag, and then immediately calls
actions-clito watch the deploy workflow triggeredon: createof that tag.Right now, I need to insert a
sleepin my script, because without it,actions-clijust finds the newest existing run (the one from the last deploy), shows it, and exits.Although my tag has already been pushed, the relevant workflow-run gets created asynchronously on Github's side, and it seemingly takes a few seconds. So if I invoke
actions-cliright away, the new run isn't available yet. Instead, it just sees the old runs, and assumes I wanted to see the newest of those.But of course, I actually want to see the new run; and if hasn't been created yet, I want
actions-clito wait around until it does get created, and then show its progress.Proposed fix
actions-cli, which will tell it to ignore or avoid matching any workflow-runs that were created before the passed timestamp.actions-clithat if it fails to discover any non-ignored runs (as could happen with the above time-filter in place), it should not exit, but rather should poll the workflow-runs API endpoint until it does successfully find a workflow run that passes the filter.With these two switches together, I wouldn't need the
sleepin my script; instead, I could run e.g.actions-cli --runs-since=... --block-until-found, and it would just sit there until a new workflow-run starts, at which point it would then start logging the progress of that workflow-run.The text was updated successfully, but these errors were encountered: