-
Notifications
You must be signed in to change notification settings - Fork 212
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
Attempt to ensure that we download the latest artifact #241
base: master
Are you sure you want to change the base?
Conversation
Hm, unfortunately, it looks like there's one test failure :-/ |
…hat are a couple days old
Testing this for a little while, it seems to occasionally still pull an artifact that's a couple days old, even though there may be like ~40 newer ones. Adding a new 'ensure_latest' configuration has seemed to fix it in early testing - let's see how this goes! |
There is still some regression here. Look at the failed job. Any ideas? |
This turned out to be user error on our part, I have no comment on the issue at hand. |
@dsnopek are you still working on that? |
Can this be picked up again? |
+1 on wanting this feature! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍🏾
This fixes issue #240 for me!
When switching from 'listWorkflowRuns' to the 'listWorkflowRunsForRepo' end-point, it's returning the workflow runs in reverse chronological order (ie. newest to oldest), which means that newer artifacts are favored over older ones.