With the 2.0.7 version release of the “Deploy to Bitrise.io - Apps, Logs, Artifacts” Step, storing artifacts switch from AWS S3 to Google Cloud Storage. This means improvements in speed, especially for testing and deployment. We'll deprecate older version and this might be a breaking change.
TL;DR: We suggest locking the Step to the 2.x.x version as soon as possible
With the new 2.0.7 version, uploading and deploying test results or the generated IPAs and APKs (or any other deployed artifact) of the build happens faster.
Every build running on Bitrise will possibly end up with shorter build times but this change is particularly beneficial for your build times if
- you actively use Public Install pages and have bigger test result files
- you regularly deploy any bigger files to the Artifacts tab
The artifacts will be handled in the same secure way on GCS as they were on S3 and the level of security will not change.
Step versions and deprecation
For getting these improvements, please make sure you are using version 2.0.7 (or above) for the “Deploy to Bitrise.io - Apps, Logs, Artifacts” Step. We suggest locking the Step to the 2.x.x version as soon as possible to gain speed improvements instantly.
As for older Step versions,
- we plan to introduce this change in older versions of the “Deploy to Bitrise.io - Apps, Logs, Artifacts” Step where possible: we will switch to GCS for versions between 1.9.2 and 2.0.6.
- older versions (1.9.1 or prior) are not capable of supporting GCS, and in late July, we’ll deprecate the 1.9.1 or prior versions. Unless the steps are updated to at least 1.9.2+, those builds will fail.
The benchmarks
We ran some tests to compare older and newer Step versions to be able to give you an idea of the improvements in run times.
We hope you like this new improvement. Do you have any feedbacks? Do not hesitate to share it with us on Slack or Twitter. Happy building!
