CI 2 minute window
Alright, I've got a Gitlab CI pipeline I'm reasonably pleased with as a result of yesterday's efforts.
There's 1 glaring problem with it though.
The pipeline is triggered by pushing or creating a new tag.
At this point in time in the codebase the manifest would have been updated with a new
The CI job takes ~2 minutes to complete.
During that 2 minute window, anyone who tries to update the package gets an error "Not Found" because the release has no assets yet.
I'm interested in peoples' workarounds for this issue.
There's 1 glaring problem with it though.
The pipeline is triggered by pushing or creating a new tag.
At this point in time in the codebase the manifest would have been updated with a new
versiondownloadThe CI job takes ~2 minutes to complete.
During that 2 minute window, anyone who tries to update the package gets an error "Not Found" because the release has no assets yet.
I'm interested in peoples' workarounds for this issue.
Similar Threads
Was this page helpful?
