As climate change has become a key global issue, software developers and DevOps experts reflect on their own industries to help reduce the climate impact of the industry. And, in our specific case, what can be done within static analysis tool development.
We are simplifying code signing on Bitrise. Now there are two ways to automate code signing on Bitrise: using Xcode Build/Archive Steps (with iOS Auto Provision Steps merged into them) and not using these Steps, but 'Manage iOS Code Signing' instead. In both cases, we've reduced the number of things that could go wrong. Let's see what has changed!
In this article, we will talk about continuous integration and continuous delivery for Flutter apps and compare features in GitHub Actions and Bitrise.
It’s easy to take continuous integration (CI) and continuous delivery/deployment (CD) for granted these days, but these have been transformational concepts that have drastically changed the face of software development over the past thirty years.
While CI/CD is synonymous with modern software development best practices, today’s machine learning (ML) practitioners still lack similar tools and workflows for operating the ML development lifecycle on a level on par with software engineers. For background, follow a brief history of transformational CI/CD concepts and how they’re missing from today’s ML development lifecycle.
A guide to understanding the concept behind DevSecOps and how you can inject security into your mobile CI/CD pipeline to deliver more secure mobile applications.
If you still rely on big-bang deployments or are ever afraid to break your production environment when you push changes, then it is seriously time to invest in building a strong CI/CD pipeline. Pushing changes quickly and often is critical. The best way to mitigate the risks of new releases is to have a strong deployment strategy in place. Continuous deployment automates the deployment process, which lets you deliver new features and improvements to your applications faster than before.
