When requesting an installation url for a build artifact using the api:
curl -X GET “https://api.bitrise.io/v0.1/apps//builds//artifacts/” -H “accept: application/json” -H “Authorization: THE-ACCESS-TOKEN”
The returned google storage url is signed with an expiration token of 1 hour.
Add an “expiration” parameter to the request of the artifact so that we can specify a longer expiration for the returned url
Use case / for what or how I would use it
Automating the flow so that the public url can be shared with our QA team without it expiring so soon.
Hey @alessio.lapenna ,
thanks for the detailed feature request.
Until we have this implemented, I think you could use the BITRISE_PERMANENT_DOWNLOAD_URL_MAP generated by the Deploy to Bitrise.io Step.
These download URLs should not expire, and you could automate the sharing flow with a Slack Step or e-mail Step.
You may need to parse the URL map first to find the right artifact in the map, as it contains all the deployed artifacts, not just the APK/IPA/AAB.
Thank you for your reply @BirmacherAkos we tried using that, but since the permanent url is under bitrise authentication, it cannot be used on automated workflow with katalon, that’s why we want to use the public url.
I hope one day this will be possible, in the meantime thank you for your time.
Cheers,
Alessio
1 Like