SAML SSO and manual approve for PR builds landed on Bitrise

We've introduced two new features: one to keep your secrets during PR builds, and one to enhance access control for Bitrise organization. Read the details.

We've introduced two new features: one to keep your secrets during PR builds, and one to enhance access control for Bitrise organization. Read the details below.

Manual approval for PR builds

Not all Pull Requests need to be built, right? For most projects, anyone can create a fork of the repository and submit a Pull Request, but if an app on Bitrise is set up with Secrets that are exposed for Pull Request builds, then you probably don’t want just anyone to be able to access them.

That is why you have the option to require approval for a Pull Request build before it can start.

  • For private apps: By default, Pull Requests submitted from a fork require approval if any Secrets are marked to be exposed for Pull Requests. The setting can be changed. If your secrets are NOT exposed to PRs, the build will run without asking for approval.
  • For public apps: Pull Requests submitted from a fork require approval by default and it cannot be changed. Public apps CANNOT opt out of this feature.

SAML SSO for Bitrise Orgs

As SAML provides a single point of authentication, we're introducing this secure gateway to your Bitrise organization. From now on, it'll be simpler for companies to control who has access to what, plus once set up, the members of your Bitrise organization won't need to remember another username and password anymore.

SAML SSO is only available for a Workspace with the Velocity or Enterprise Build plans.

Workspace members can log in to a Bitrise Workspace using their own SAML SSO provider’s system, but pnly the Workspace owner can set up SAML SSO to a Bitrise Workspace.

We support the following providers:

For the detailed guides on the specific SAML SSO providers, please follow the links above.

Basically, you have to make the following steps:

  1. Adding Bitrise to your SAML SSO provider
  2. Setting up SAML SSO for your Bitrise organization (on the Security tab)
  3. Enabling SAML SSO on Bitrise (by org members)
  4. Enforcing SAML SSO on the organization (by the org owner): before that, users can choose to use SAML SSO or the regular login

Once setup is done by the Bitrise Organization's owner and users are added to the SAML SSO provider too, users will get an email notification with a link, they approve it and that's it, they can log in via SSO.

undefined
No items found.
The Mobile DevOps Newsletter

Explore more topics

App Development

Learn how to optimize your mobile app deployment processes for iOS, Android, Flutter, ReactNative, and more

Bitrise & Community

Check out the latest from Bitrise and the community. Learn about the upcoming mobile events, employee spotlights, women in tech, and more

Bitrise Insights

Cache | Caching

Mobile App Releases

Learn how to release faster, better apps on the App Store, Google Play Store, Huawei AppGallery, and other app stores

Mobile DevOps

Learn Mobile DevOps best practices such as DevOps for iOS, Android, and industry-specific DevOps tips for mobile engineers

Mobile Testing & Security

Learn how to optimize mobile testing and security — from automated security checks to robust mobile testing and more.

Product Updates

Check out the latest product updates from Bitrise — Build Insights updates, product news, and more.

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.