April 2024 Summaries

Apple's latest privacy change requires app developers to describe the data they collect in their apps, either on their own or through third-party SDKs, and provide reasons for accessing certain APIs. This is achieved through a `plist` file called a Privacy Manifest file, which records the types of data collected and provides justification for its usage. The deadline for initial compliance is March 13th, 2024, with new apps not accepted by App Store Connect starting May 1st, 2024, unless they meet these requirements. This change expands to include the entire app binary in the future, aiming to standardize privacy disclosures and enable users to make informed decisions, aligning with global privacy trends and setting a benchmark for other platforms.

The Bitrise Runner is a new capability that allows developers to use their own machine within their own infrastructure to run Bitrise builds, providing enhanced security, geolocation flexibility, and control over build environments. This introduces a paradigm shift in how build environments are managed compared to Bitrise-managed machines, with maintenance and setup effort involved but offering benefits such as faster builds, prewarming machines, and larger free disk space. The Runner is compatible with Linux and macOS platforms and offers a range of benefits including enhanced security, geolocation flexibility, in-house control, bare metal setup, and seamless transition to Bitrise for teams looking to scale their development processes.

Jenkinsfile and bitrise.yml are configuration files used to define CI/CD pipelines, with Jenkinsfile using Groovy and bitrise.yml using YAML. Both share similar functionalities such as code-based definition, modular structure, declarative nature, structure and hierarchy, phases, tasks, steps, parallelization, input instructions, and a hierarchical structure. However, their approaches differ in flexibility, simplicity, readability, and customization options. Jenkinsfile offers more granular control through Groovy scripting, making it suitable for complex workflows, while bitrise.yml prioritizes simplicity with a user-friendly YAML syntax, catering to mobile app development workflows and offering built-in integrations for common tools. Ultimately, the choice between Jenkinsfile and bitrise.yml depends on specific needs and preferences, with no clear-cut winner.

CI/CD has transformed software development, testing, and delivery processes, making them efficient, reliable, and faster. Release management plays a critical role in managing software builds through different stages and environments. However, traditional release management methods are plagued by inefficiencies, including outdated information, manual tracking, and collaboration challenges. These issues lead to delays, errors, and inconsistencies, ultimately affecting the end product. The need for streamlined and automated release management processes is evident, as modern tools can provide real-time updates, faster time-to-market, and promote collaboration. However, simply automating traditional spreadsheets may not be enough, and a shift towards more sophisticated tools is necessary to overcome challenges such as limited visibility, platform-specific requirements, human errors, and manual processes. Integrated release management tools offer features like version control, change management, automated testing, and deployment orchestration, making tracking changes and systematizing documentation easier. Automation eliminates errors, boosts efficiency, and speeds up delivery, ensuring consistent deployment and reducing downtime, ultimately enhancing productivity and effectiveness.

The Gradle Critical Path Analyzer and Diagnostic Builds feature helps identify bottlenecks in Gradle commands, allowing developers to optimize their build processes and reduce overall execution time. By analyzing the critical path of tasks executed during a Gradle command invocation, developers can pinpoint slow tasks and apply optimizations to improve efficiency. The Diagnostic Builds feature provides insights into why specific tasks are being executed, enabling developers to make informed decisions about their build configuration. By leveraging these features, developers can significantly reduce the duration of their Gradle builds and tests, leading to improved productivity and better engineering practices.

Bazel is an open-source build and test automation tool designed for large, multi-language projects with complex dependencies. Its remote caching capabilities allow it to store and retrieve build outputs from a remote server, enhancing build times through cache reuse across different environments. The Bazel remote caching API specification outlines how clients and remote servers interact, defining entities such as Action, Command, platform, and ActionResult. The client-side implementation in Bazel v7.0.2 involves checking for cached results, downloading missing blobs, writing local results to the cache, and persisting results for given Actions. Bitrise's server-side implementation of the remote cache API will be explored in a subsequent post.

Mobile apps are integral to our daily tasks, and their development teams must ensure seamless user interaction through efficient development processes. Poor release management practices can lead to suboptimal procedures, insufficiently reviewed distribution, and poor incident traceability, all of which diminish the end-user experience. The Android app release lifecycle involves development, testing, and deployment phases, where adopting an agile release management strategy improves quality assurance, efficiency, and reduces risks. A well-planned, executed, and monitored release process is crucial for staged rollouts and ensuring device compatibility. Google Play Console offers a comprehensive array of tools that supports every stage of an app's lifecycle, addressing DevOps teams' major concerns in app release and management. Thorough testing before release is essential to prevent bugs, poor user experience, and system failures, while utilizing pre-release tracks for testing can provide targeted feedback and robust app validation. Effective deployment strategies, such as gradual or staged releases, ensure smooth application transition, user satisfaction, and tangible value, while monitoring the deployment process and handling rollbacks in case of issues are critical to a successful app launch.

The introduction of connected apps by Bitrise aims to improve the efficiency and precision of mobile development workflows by providing a more organized release management strategy for store apps. The new system allows each app version to be managed independently, offering precise management and tracking of releases with tailored presets and feature flag configuration. This approach distinguishes between staying ahead of the competition and playing catch-up by enabling streamlined release processes. With connected apps, developers can oversee and handle releases for different app versions more effectively, ensuring that each one gets the attention it deserves.

Developers cry too`: Engineering Managers and team leaders can now measure developer satisfaction using the new metric "Developer Tears Saved" within Bitrise Insights. This feature aims to streamline operations, enhance productivity, and celebrate milestones in mobile development teams. The traditional metrics like DORA are important but don't replace the need for measuring happiness among developers. By monitoring "Developer Tears Saved", managers can pinpoint where their team is succeeding and celebrate those moments.