Systems | Development | Analytics | API | Testing

Bitrise

DevOps CI/CD Pipeline and Workflow: A Bitrise CI/CD Pipeline and Workflow walkthrough

This Mobile DevOps tutorial takes you through what is a Pipeline, what is workflows, and how you can build and test in parallel to build better apps, faster, all tailored specifically for mobile development with Bitrise. Dive into the world of Bitrise Mobile DevOps, learning how to leverage the power of our software to build and test in parallel, enabling you to develop apps, quicker than ever before. In this video we cover the key components of a Bitrise DevOps pipeline - an integral toolset and automated processes that allow software teams to compile, build, and roll out codes seamlessly.

Ship sooner to Google Play: Release Management now supports Android production releases

Ship Android apps faster than ever. Our new features allow you to effortlessly integrate with your Google Account, create production releases and release directly to the Google Play Store. Read more on this, and what's coming next.

Bitrise at TNW Conference | Ironclad Mobile Commerce for Safe and Secure Experiences

Bitrise Sales Engineering Tech Lead, Tamás Bazsonyi joined a panel on the Discover Stage at TNW Conference in Amsterdam for a thought-provoking discussion around building a more resilient mobile commerce ecosystem that prioritizes safety, user privacy, and seamless experiences for customers worldwide.

Bitrise named in Europe's most promising startups 2023

The Titans of Tech report analyzed more than 100 European startups for scale, velocity and sentiment, and surveyed their GP. Bullhound network of more than 120 VC and growth investors to rank the top 50 companies with the most potential to become billion-dollar companies in the next two years and Bitrise has made that list!

How to reduce flaky tests in mobile development with Bitrise Insights

In mobile development, flaky tests are a persistent issue. They’re frustrating because a test is ‘flaky’ when it produces both ‘passing’ and ‘failing’ results from the same code. This wastes developers’ time by triggering unnecessary investigations and delays the integration of their code.