You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm trying to understand how to reliably access the latest artifacts generated by a particular task.
At first glance it seems straightforward (as per docs): https://api.cirrus-ci.com/v1/artifact/github/<USER OR ORGANIZATION>/<REPOSITORY>/<TASK NAME>/<ARTIFACTS NAME>/<PATH>.
But for more complex CI setup it turns out to be not so simple. If a more recent build for the same repo omits both the task that generated artifacts and *_artifacts instruction that saves the artifacts, the URL above will return 404 even though the artifacts are still there, they still are from the latest run of that task, just not from the latest build in this repo.
Artifact URL goes 404 after the next successful build (6045406209507328) even though there is neither build-packer-image task nor *_artifacts definition in that build.
Is there a way to construct an URL that will always point to the latest artifacts of build-packer-image task even after completing some newer builds without that task?
The text was updated successfully, but these errors were encountered:
URLs are per build so if you use skip_if for some tasks than the latest URL won't work as you described. At the moment there is no way to have a link pointing to the latest run of a task.
I'm trying to understand how to reliably access the latest artifacts generated by a particular task.
At first glance it seems straightforward (as per docs):
https://api.cirrus-ci.com/v1/artifact/github/<USER OR ORGANIZATION>/<REPOSITORY>/<TASK NAME>/<ARTIFACTS NAME>/<PATH>
.But for more complex CI setup it turns out to be not so simple. If a more recent build for the same repo omits both the task that generated artifacts and
*_artifacts
instruction that saves the artifacts, the URL above will return 404 even though the artifacts are still there, they still are from the latest run of that task, just not from the latest build in this repo.Example:
build-packer-image
task. That task generates some artifactsbuild-packer-image
task nor*_artifacts
definition in that build.Is there a way to construct an URL that will always point to the latest artifacts of
build-packer-image
task even after completing some newer builds without that task?The text was updated successfully, but these errors were encountered: