Feature Request Friday: April 26 – May 17

Let's check out all the feature requests we've received in the past 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. Let’s take a look at all the feature requests that we have received in the past two weeks!

Allow workflow-specific secrets

Our first feature request comes from Roboteam, who would like to see workflow-specific secrets, similar to secret environment variables. These would come in handy when dealing with several workflows that each upload to different places, essentially eliminating the need to constantly have to change upload scripts.

Support Latest Ruby Versions in Stack Updates

Next up, we have a request from Josh Kaplan, who would like to see support for the latest Ruby versions in stack updates. In addition to the security fixes the new version included, having the same versions both locally and on the CI service would mean that there’s no additional build time due to having to build the separate versions.

Fully compatibility for custom steps using GitLab instead GitHub

We also saw a request from Jorge Gironda, who would like to see full compatibility for custom steps using GitLab instead of GitHub. This would mean that the Workflow Editor would able to retrieve step.yml information, and that users could edit input fields through the GUI instead of having to go to the bitrise.yml file.

Ability to download/see full logs during build

Dominik Roszkowski submitted a feature request for having the ability to see and download full logs while running builds. This would allow users to take a look at the steps they’ve used while they’re waiting for longer builds to finish.

Support of artifacts subfolders

We also saw a feature request for artifact subfolder support from Dzmitry Kotsik. In Dzmitry’s case, this support would mean that the images placed in subfolders upon snapshot testing are also recognized as artifacts, instead of only the ones which are in the main folder.

Ignore build requests when GitHub’s Pull Request is a draft

Last but not least, we had a feature request from Thierry LEE, who would like to see the possibility of ignoring build requests for draft pull requests on GitHub. This would help users avoid putting further, unnecessary pressure on CI systems with builds that might not even compile.

kim kardashian twitter GIF

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.