Bitrise Build Issue Report template
Description of the issue
When we trigger a large amount of builds, some of them get triggered after hour because we only have 3 concurrent builds. When they get triggered, the key based cache restoration step fails with:
Input:
- verbose: false
- key: {{ .OS }}-{{ .Arch }}-carthage-cache-{{ checksum "/Users/vagrant/git/Cartfile.resolved" }}
- retries: 3
Evaluating key template: {{ .OS }}-{{ .Arch }}-carthage-cache-{{ checksum "/Users/vagrant/git/Cartfile.resolved" }}
Build trigger doesn't have an explicit git commit hash, using the Git Clone Step's output for the .CommitHash template variable (value: 44040bbdf78b3b0490841cf5b22dcfa157adb41a)
Cache key: darwin-arm64-carthage-cache-3d0e637e339efc3a9b6724742a66aba30fbcfba64f3a4a780e7fbdfa4e22c53b
Downloading archive...
download failed:
failed to get download URL:
HTTP 401: Jwt is expired
What token is this and how can we prevent the issue?
Environment:
In the Cache restoration step. Xcode 16.3 stack.
Reproducibility
When scheduled e.g. 70 builds, the 60th gets triggerd after some hours and lets say the cache restauration fauils with the mentioned error. Then it also can happen that succeeding builds run though just fine again. This is what we do not fullly understand.
Local reproduction
Not tested. our workflows only run in the cloud.
Build log
See Description of the issue on top