# \#released

**URL:** https://discuss.bitrise.io/tag/released/153.md

[Latest](https://discuss.bitrise.io/latest.md) · [Categories](https://discuss.bitrise.io/categories.md) · [Tags](https://discuss.bitrise.io/tags.md)

---

## [What will be best approach to trigger a job running on on-premises just after completing a build on bitrise?](https://discuss.bitrise.io/t/what-will-be-best-approach-to-trigger-a-job-running-on-on-premises-just-after-completing-a-build-on-bitrise/24527)

<div class="topic-metadata">

**Author:** [@shubham.mishra](https://discuss.bitrise.io/u/shubham.mishra)\
**Replies:** 1\
**Last updated:** [September 24, 2024, 1:56pm UTC](https://discuss.bitrise.io/t/what-will-be-best-approach-to-trigger-a-job-running-on-on-premises-just-after-completing-a-build-on-bitrise/24527 "2024-09-24T13:56:08Z")

</div>

Just after completing build on bitrise i have to send apk and ipa file to a on-premises server and trigger a script on that on-premises server. What will be best approach for this?

---

## [AWS Device Farm Steps need new maintainer](https://discuss.bitrise.io/t/aws-device-farm-steps-need-new-maintainer/24516)

<div class="topic-metadata">

**Author:** [@eliot\_pear](https://discuss.bitrise.io/u/eliot_pear)\
**Replies:** 1\
**Last updated:** [September 23, 2024, 1:17pm UTC](https://discuss.bitrise.io/t/aws-device-farm-steps-need-new-maintainer/24516 "2024-09-23T13:17:23Z")

</div>

I am looking for a new maintainer for the AWS device farm steps. I have been unable to maintain these steps for years and the company that was originally sponsoring me to work on these steps no longer exists. I am actual…

---

## [Deploying to External Testers on TestFlight Using Bitrise](https://discuss.bitrise.io/t/deploying-to-external-testers-on-testflight-using-bitrise/24081)

<div class="topic-metadata">

**Author:** [@zura](https://discuss.bitrise.io/u/zura)\
**Replies:** 3\
**Last updated:** [May 27, 2024, 12:57pm UTC](https://discuss.bitrise.io/t/deploying-to-external-testers-on-testflight-using-bitrise/24081 "2024-05-27T12:57:37Z")

</div>

Hello everyone, As many of you are aware, Bitrise allows us to upload iOS versions to TestFlight (internal). However, I haven’t been able to find a solution for uploading versions to TestFlight (external) using Bitrise. …

---

## [Ignore build requests when GitHub's Pull Request is a draft](https://discuss.bitrise.io/t/ignore-build-requests-when-githubs-pull-request-is-a-draft/9024)

<div class="topic-metadata">

**Author:** [@thierrylee](https://discuss.bitrise.io/u/thierrylee)\
**Replies:** 11\
**Last updated:** [October 18, 2023, 5:48pm UTC](https://discuss.bitrise.io/t/ignore-build-requests-when-githubs-pull-request-is-a-draft/9024 "2023-10-18T17:48:37Z")

</div>

It would be great to ignore build requests on draft PRs from GitHub. That would avoid busying the CI with builds that might not even compile. Even if it did, because we know we’ll have to push more commits later, why bo…

---

## [📱 Easily find your installable app packages](https://discuss.bitrise.io/t/easily-find-your-installable-app-packages/23297)

<div class="topic-metadata">

**Author:** [@kaushal.bitrise](https://discuss.bitrise.io/u/kaushal.bitrise)\
**Replies:** 0\
**Last updated:** [September 8, 2023, 12:08pm UTC](https://discuss.bitrise.io/t/easily-find-your-installable-app-packages/23297 "2023-09-08T12:08:50Z")

</div>

Hello :wave: Several users had suggested that it wasn’t straightforward to access installable app packages on Bitrise. It often took a while to find the builds that have installable app packages. Additionally, when you …

---

## [Use Apple's "Application Specific Password" feature for connecting Apple Developer Accounts](https://discuss.bitrise.io/t/use-apples-application-specific-password-feature-for-connecting-apple-developer-accounts/6979)

<div class="topic-metadata">

**Author:** [@dgraham](https://discuss.bitrise.io/u/dgraham)\
**Replies:** 4\
**Last updated:** [August 20, 2022, 10:04pm UTC](https://discuss.bitrise.io/t/use-apples-application-specific-password-feature-for-connecting-apple-developer-accounts/6979 "2022-08-20T22:04:16Z")

</div>

Description of the feature request Allow users to connect Bitrise to their Apple Developer Account using Apple’s provided App-Specific password feature. Sign in to apps with your Apple Account using app-specific password…

---

## [Request to please add Firebase build deployment in Bitrise](https://discuss.bitrise.io/t/request-to-please-add-firebase-build-deployment-in-bitrise/10458)

<div class="topic-metadata">

**Author:** [@sathish2111](https://discuss.bitrise.io/u/sathish2111)\
**Replies:** 6\
**Last updated:** [August 20, 2022, 10:01pm UTC](https://discuss.bitrise.io/t/request-to-please-add-firebase-build-deployment-in-bitrise/10458 "2022-08-20T22:01:33Z")

</div>

Request to please add Firebase build deployment in Bitrise Hi Team, We are using Fabrics to deploy our build so far. But Fabrics is going out by Mar 31, 2020 and Fabrics is asking us to use Firebase. When i search for …

---

## [Support APK Signature Scheme V2](https://discuss.bitrise.io/t/support-apk-signature-scheme-v2/14224)

<div class="topic-metadata">

**Author:** [@Connor.jackson](https://discuss.bitrise.io/u/Connor.jackson)\
**Replies:** 6\
**Last updated:** [August 20, 2022, 9:58pm UTC](https://discuss.bitrise.io/t/support-apk-signature-scheme-v2/14224 "2022-08-20T21:58:53Z")

</div>

Description of the feature request Android apps targeting Android 11 are now required to sign APKs with APK Signature Scheme V2, otherwise the build will be invalid. See: https://developer.android.com/about/versions/11/b…

---

## [Update Carthage to 0.37.0](https://discuss.bitrise.io/t/update-carthage-to-0-37-0/15648)

<div class="topic-metadata">

**Author:** [@mathiasemil](https://discuss.bitrise.io/u/mathiasemil)\
**Replies:** 6\
**Last updated:** [August 20, 2022, 9:54pm UTC](https://discuss.bitrise.io/t/update-carthage-to-0-37-0/15648 "2022-08-20T21:54:35Z")

</div>

Hi When are you planning to update Carthage to version 0.37.0? Thx

---

## [Bitrise Public API](https://discuss.bitrise.io/t/bitrise-public-api/37)

<div class="topic-metadata">

**Author:** [@david.everlof.knowit](https://discuss.bitrise.io/u/david.everlof.knowit)\
**Replies:** 87\
**Last updated:** [August 20, 2022, 9:53pm UTC](https://discuss.bitrise.io/t/bitrise-public-api/37 "2022-08-20T21:53:03Z")

</div>

I’d very much like an API for bitrise. For configuring applications etc. For example, upload/read workflow, update/read stack, read build list, etc. I guess there isnt something like this, because I havent found it. Is…

---

## [Add Expiring Download URL to Env Variables for IPA/APK files](https://discuss.bitrise.io/t/add-expiring-download-url-to-env-variables-for-ipa-apk-files/12712)

<div class="topic-metadata">

**Author:** [@YishaiInv](https://discuss.bitrise.io/u/YishaiInv)\
**Replies:** 7\
**Last updated:** [August 20, 2022, 8:47pm UTC](https://discuss.bitrise.io/t/add-expiring-download-url-to-env-variables-for-ipa-apk-files/12712 "2022-08-20T20:47:37Z")

</div>

Description of the feature request In the deploy to bitrise build step there should be an environmental variable with a link to directly download the IPA/APK. Use case / for what or how I would use it This would allow o…

---

## [Expose url to artifact outside of Build page / public install page for non app artifacts (.pkg, .zip, ...)](https://discuss.bitrise.io/t/expose-url-to-artifact-outside-of-build-page-public-install-page-for-non-app-artifacts-pkg-zip/2330)

<div class="topic-metadata">

**Author:** [@fred-adda](https://discuss.bitrise.io/u/fred-adda)\
**Replies:** 7\
**Last updated:** [August 20, 2022, 8:42pm UTC](https://discuss.bitrise.io/t/expose-url-to-artifact-outside-of-build-page-public-install-page-for-non-app-artifacts-pkg-zip/2330 "2022-08-20T20:42:39Z")

</div>

Description of the feature request In addition to be able to view the artifact generated by bitrise in the build page, I’d like to have it exposed to (for example) Slack. Use case / for what or how I would use it I have…

---

## [Parallel Builds: trigger multiple workflows (builds) at the same time - build stages - fan-out fan-in support](https://discuss.bitrise.io/t/parallel-builds-trigger-multiple-workflows-builds-at-the-same-time-build-stages-fan-out-fan-in-support/410)

<div class="topic-metadata">

**Author:** [@streaka](https://discuss.bitrise.io/u/streaka)\
**Replies:** 39\
**Last updated:** [August 20, 2022, 8:26pm UTC](https://discuss.bitrise.io/t/parallel-builds-trigger-multiple-workflows-builds-at-the-same-time-build-stages-fan-out-fan-in-support/410 "2022-08-20T20:26:57Z")

</div>

Useful for cordova repos, so I don’t have to configure two bitrise apps for one client

---

## [Build dashboard / Build Time Trend / Stats / Analytics](https://discuss.bitrise.io/t/build-dashboard-build-time-trend-stats-analytics/1927)

<div class="topic-metadata">

**Author:** [@bootstraponline](https://discuss.bitrise.io/u/bootstraponline)\
**Replies:** 29\
**Last updated:** [August 20, 2022, 6:24pm UTC](https://discuss.bitrise.io/t/build-dashboard-build-time-trend-stats-analytics/1927 "2022-08-20T18:24:41Z")

</div>

A dashboard view containing average build duration, % successful, and other metrics would be nice. https://github.com/rouanw/build-window

---

## [Automatically abort repeating/identical ongoing workflows](https://discuss.bitrise.io/t/automatically-abort-repeating-identical-ongoing-workflows/20439)

<div class="topic-metadata">

**Author:** [@arthur.geron-work](https://discuss.bitrise.io/u/arthur.geron-work)\
**Replies:** 2\
**Last updated:** [June 27, 2022, 1:29pm UTC](https://discuss.bitrise.io/t/automatically-abort-repeating-identical-ongoing-workflows/20439 "2022-06-27T13:29:22Z")

</div>

Description of the feature request It’s common for workflows automatically triggered by github to overlap, if for example a user opens a PR from dev to main It’ll trigger the workflow “dev —\> main” which is fine but if t…

---

## [Pull Request support for AzureDevOps (VSTS)](https://discuss.bitrise.io/t/pull-request-support-for-azuredevops-vsts/6992)

<div class="topic-metadata">

**Author:** [@aladdinG](https://discuss.bitrise.io/u/aladdinG)\
**Replies:** 13\
**Last updated:** [June 15, 2022, 1:49pm UTC](https://discuss.bitrise.io/t/pull-request-support-for-azuredevops-vsts/6992 "2022-06-15T13:49:48Z")

</div>

Description of the feature request For the moment Bitrise webhooks integration with VSTS is only limited for Code Push and Tag Push event. I’ts very appreciable to have support for Pull Request Created/Updated as well …

---

## [Trigger selective builds based on diff, instead of touched files](https://discuss.bitrise.io/t/trigger-selective-builds-based-on-diff-instead-of-touched-files/18647)

<div class="topic-metadata">

**Author:** [@pierpo](https://discuss.bitrise.io/u/pierpo)\
**Replies:** 1\
**Last updated:** [November 29, 2021, 2:01pm UTC](https://discuss.bitrise.io/t/trigger-selective-builds-based-on-diff-instead-of-touched-files/18647 "2021-11-29T14:01:42Z")

</div>

Description of the feature request Suppose I enable selective builds for ./A/\* . In my PR from my branch into master, I only touch ./B/index.js . At some point, I do a merge commit of master into my branch to update my b…

---

## [Bitrise step or configuration for switching Java version](https://discuss.bitrise.io/t/bitrise-step-or-configuration-for-switching-java-version/15828)

<div class="topic-metadata">

**Author:** [@thoutbeckers](https://discuss.bitrise.io/u/thoutbeckers)\
**Replies:** 3\
**Last updated:** [September 10, 2021, 9:47am UTC](https://discuss.bitrise.io/t/bitrise-step-or-configuration-for-switching-java-version/15828 "2021-09-10T09:47:47Z")

</div>

Description of the feature request For a long time most of the Java eco system coalesced around JDK8 (certainly in the mobile space). However that time is now over, with tools like Gradle moving to a JDK11 minimum. Whil…

---

## [Add an abort button in the app's build items & dashboard build items](https://discuss.bitrise.io/t/add-an-abort-button-in-the-apps-build-items-dashboard-build-items/467)

<div class="topic-metadata">

**Author:** [@nikos](https://discuss.bitrise.io/u/nikos)\
**Replies:** 4\
**Last updated:** [August 31, 2021, 9:42am UTC](https://discuss.bitrise.io/t/add-an-abort-button-in-the-apps-build-items-dashboard-build-items/467 "2021-08-31T09:42:26Z")

</div>

Add a button in the task ribbon to abort the build, thus there is no need to open the build and do the abort from there

---

## [Turning off auto watching of apps by default](https://discuss.bitrise.io/t/turning-off-auto-watching-of-apps-by-default/4217)

<div class="topic-metadata">

**Author:** [@adamapplab](https://discuss.bitrise.io/u/adamapplab)\
**Replies:** 18\
**Last updated:** [August 25, 2021, 11:38am UTC](https://discuss.bitrise.io/t/turning-off-auto-watching-of-apps-by-default/4217 "2021-08-25T11:38:35Z")

</div>

Right now, whenever we add a new app it automatically adds us as a watcher to that app. Is there an organisation wide setting that allows us to turn this off? It’s annoying to have to unwatch every new app we add. Thanks…

---

## [Use connected Apple Developer account in workflow steps](https://discuss.bitrise.io/t/use-connected-apple-developer-account-in-workflow-steps/4044)

<div class="topic-metadata">

**Author:** [@matthias.buchetics](https://discuss.bitrise.io/u/matthias.buchetics)\
**Replies:** 6\
**Last updated:** [August 25, 2021, 11:32am UTC](https://discuss.bitrise.io/t/use-connected-apple-developer-account-in-workflow-steps/4044 "2021-08-25T11:32:55Z")

</div>

Description of the feature request iOS Auto Provisioning works great with a connected Apple Developer Account. However, we still need to provide an iTunes user and password for workflow steps such as “Deploy to iTunes Co…

---

## [Rolling Builds specific to workflow](https://discuss.bitrise.io/t/rolling-builds-specific-to-workflow/4138)

<div class="topic-metadata">

**Author:** [@thon](https://discuss.bitrise.io/u/thon)\
**Replies:** 6\
**Last updated:** [August 25, 2021, 11:16am UTC](https://discuss.bitrise.io/t/rolling-builds-specific-to-workflow/4138 "2021-08-25T11:16:47Z")

</div>

In Settings, there is a feature called: ROLLING BUILDS, described as “Auto-cancel on-hold builds if a new build is triggered on the same branch” There’s a couple other options that can also be enabled: Pull Requests …

---

## [Allow bitrise.yml to be pulled from project source code](https://discuss.bitrise.io/t/allow-bitrise-yml-to-be-pulled-from-project-source-code/154)

<div class="topic-metadata">

**Author:** [@viktorbenei](https://discuss.bitrise.io/u/viktorbenei)\
**Replies:** 20\
**Last updated:** [August 25, 2021, 11:04am UTC](https://discuss.bitrise.io/t/allow-bitrise-yml-to-be-pulled-from-project-source-code/154 "2021-08-25T11:04:33Z")

</div>

From @viktorbenei on Thu Jun 16 2016 07:27:46 GMT-0400 (EDT) Related UserVoice link: https://bitrise.uservoice.com/forums/235233-general/suggestions/10481289-allow-bitrise-yml-to-be-pulled-from-project-source Summary a…

---

## [Check if last build failed/status changed (e.g. only Slack notify if build failed or fixed)](https://discuss.bitrise.io/t/check-if-last-build-failed-status-changed-e-g-only-slack-notify-if-build-failed-or-fixed/1781)

<div class="topic-metadata">

**Author:** [@rajit](https://discuss.bitrise.io/u/rajit)\
**Replies:** 13\
**Last updated:** [August 10, 2021, 9:40am UTC](https://discuss.bitrise.io/t/check-if-last-build-failed-status-changed-e-g-only-slack-notify-if-build-failed-or-fixed/1781 "2021-08-10T09:40:54Z")

</div>

Currently we notify Slack on build failures only but we’d like to see when the build gets fixed. We don’t want to see every successful build, though, as it’s not useful information when it’s just repetitive.

---

## [Support test retries in the Xcode Test Step](https://discuss.bitrise.io/t/support-test-retries-in-the-xcode-test-step/17134)

<div class="topic-metadata">

**Author:** [@laszlo.pusok](https://discuss.bitrise.io/u/laszlo.pusok)\
**Replies:** 3\
**Last updated:** [July 7, 2021, 10:42am UTC](https://discuss.bitrise.io/t/support-test-retries-in-the-xcode-test-step/17134 "2021-07-07T10:42:13Z")

</div>

Description of the feature request Would like to request an option to retry failed tests in the Xcode Test Step if the test is flaky or the Simulator crashes. This allows for more reliable test runs and avoids having to …

---

## [Automatic signing via \`xcodebuild\`](https://discuss.bitrise.io/t/automatic-signing-via-xcodebuild/17133)

<div class="topic-metadata">

**Author:** [@godreikrisztian](https://discuss.bitrise.io/u/godreikrisztian)\
**Replies:** 0\
**Last updated:** [June 8, 2021, 2:03pm UTC](https://discuss.bitrise.io/t/automatic-signing-via-xcodebuild/17133 "2021-06-08T14:03:37Z")

</div>

Description of the feature request xcodebuild now supports the use of App Store Connect API keys for authentication with the Apple Developer website. This enables the use of automatic signing via xcodebuild in headles…

---

## [Allow to see the minor version of XCode in reports](https://discuss.bitrise.io/t/allow-to-see-the-minor-version-of-xcode-in-reports/11206)

<div class="topic-metadata">

**Author:** [@joao.jesus](https://discuss.bitrise.io/u/joao.jesus)\
**Replies:** 1\
**Last updated:** [December 5, 2019, 5:50pm UTC](https://discuss.bitrise.io/t/allow-to-see-the-minor-version-of-xcode-in-reports/11206 "2019-12-05T17:50:55Z")

</div>

Currently the builds gives the stack report without seeing the minor version like this: Stack used: Xcode 11.2.x, on macOS 10.14.6 (Mojave) In some cases is important to know if the build is using a specific type of XC…

---

## [GitHub checks / GitHub App](https://discuss.bitrise.io/t/github-checks-github-app/5088)

<div class="topic-metadata">

**Author:** [@bernat](https://discuss.bitrise.io/u/bernat)\
**Replies:** 13\
**Last updated:** [October 22, 2019, 2:05pm UTC](https://discuss.bitrise.io/t/github-checks-github-app/5088 "2019-10-22T14:05:32Z")

</div>

Description of the feature request Hi. As github created new checks support, it could be cool to have them on bitrise

---

## [Update Docker to 18.09](https://discuss.bitrise.io/t/update-docker-to-18-09/8597)

<div class="topic-metadata">

**Author:** [@ambientlight](https://discuss.bitrise.io/u/ambientlight)\
**Replies:** 3\
**Last updated:** [September 2, 2019, 11:53am UTC](https://discuss.bitrise.io/t/update-docker-to-18-09/8597 "2019-09-02T11:53:24Z")

</div>

The latest base Bitrise Docker image has a bit outdated docker, it would great to have it updated to 18.09 to take advantage of buildkit builds. I’ve create a pull request for it: https://github.com/bitrise-docker/bitri…

---

## [Make step optional for complete build to pass](https://discuss.bitrise.io/t/make-step-optional-for-complete-build-to-pass/9944)

<div class="topic-metadata">

**Author:** [@artyom\_ok](https://discuss.bitrise.io/u/artyom_ok)\
**Replies:** 3\
**Last updated:** [August 15, 2019, 12:27pm UTC](https://discuss.bitrise.io/t/make-step-optional-for-complete-build-to-pass/9944 "2019-08-15T12:27:05Z")

</div>

Description of the feature request Please add an option for making steps optional. If the step fails, and no one depends on it, it will not make the complete build to fail. Use case / for what or how I would use it That…

[Next page](https://discuss.bitrise.io/tag/released/153.md?match_all_tags=true&page=1&tags%5B%5D=released)
