Feature Request Friday: March 1–29

Check out all the feature request submissions we've received in the last few weeks!

Developing new features for our platform is one of the key ways we can make sure we are giving you the best service possible — and we wouldn’t be able to do it without your help. After a short hiatus, we’re back with a brand new collection of all the feature requests you submitted in the last few weeks. Let’s dig in!

App Store API - submit for Beta review (Testflight)

Our first feature request comes from Bill Ferrell, who would like to see an option for submitting a build for review at the end of his beta workflows when working with App Store API.

Python 3 - add feature - auto installed

Our next request comes from Daniel Meltzer, and is about having Python 3 installed by default.

Evaluate `run_if` before launching step

Next up, we have a feature request by Ghemmen Arh Spx for having run_if evaluated before running a step, which would save significant time for a build.

Treat xcode-analyze step warnings as errors

We also saw a feature request for treating Xcode-analyze step warnings as errors, submitted by Mike DiNicola.

Support automatic version upgrades

Next up is Gedw99’s feature request for the automatic option for checking whether all dependencies are up to date.

Filter pull request web-hooks from Github using labels

Next up, we have a request for filtering pull request web-hooks through the labels associated with them, submitted by Sourav Chandra.

Retry mechanism on tasks

Our next feature request is one about the option for users to choose an attempt count for a step in order to be able to retry it if it fails, and was submitted by Grégory Lureau.

Slack step: allow multiple recipients

Usmonster submitted a feature request about allowing Slack notifications to go to multiple recipients.

Build fail reason to an $ENVIRONMENT_VARIABLE

Next up, we have a request from Joaquim Ley about having a variable built into the Bitrise-CLI that states the actual reason why the build failed.

Abort rolling builds only if running < x minutes

We also saw a feature request for having the option of aborting rolling builds based on how much time has passed, submitted by John Mejia.

Simplified tester onboarding

Neutrino8 Build submitted a feature request about a simplified, separate tester onboarding process.

Running Instrumentation tests on Firebase using physical devices

Our next feature request was submitted by Moataz Nabil, and is about being able to run instrumentation tests on Firebase using physical devices.

Xcode-analyze report

Purvi Mehta added a feature request for having detailed reports about warnings, leaks, or logical errors when using Xcode-analyze.

Add the ability to set simulator location

This feature request was about having the ability to set a location for simulators, and was submitted by Daichi Sasaki.

Add google cloud cli (gcloud, gsutil) to default image

Last but not least, we saw a feature request by Tally Barak for having a default image installed with the Google Cloud CLI.


That’s it for now, folks! Make sure you go and vote on your favorite feature requests to help us see just what it is you'd really want to see on Bitrise. Have any ideas that you haven't seen mentioned? Post them on the feature request page — all you have to do is log into your account, click "New Topic" on the top right corner of the page, and you're good to go! See you in two weeks with a new Feature Request Friday!

No items found.
The Mobile DevOps Newsletter

Explore more topics

App development

Best practices from engineers on how to use Bitrise to build better apps, faster.

Community

Meet other Bitrise engineers, technology experts, power users, partners and join our BUGs.

Company

All the updates about Bitrise events, sponsorships, employees, and more.

Insights

Mobile development, latest tech, industry insights, and interviews with experts.

Mobile DevOps

Learn why mobile development is unique and requires a set of unique practices.

Releases

Stay tuned for the last updates, new features, and product improvements.

The Mobile DevOps Newsletter

Join 1000s of your peers. Sign up to receive Mobile DevOps tips, news, and best practice guides once every two weeks.