# Continuous integration Continuous integration is a software development practice in which code changes are frequently merged into a shared repository and automatically built and tested. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Google joins the OpenROAD Initiative as principal member to accelerate open source silicon innovation DevFeed: [Google joins the OpenROAD Initiative as principal member to accelerate open source silicon innovation]() Original publisher: [Read original article]() Author: Google Open Source (noreply@blogger.com) Published: 2026-08-11T18:30:00Z Content type: release Language: en Sources: [Google Open Source Blog]() Topics: [Google](), [Chip design](), [Open Source](), [toolchains](), [Continuous integration]() Tags: [chip-design](), [ci-cd](), [eda](), [google](), [open-source](), [openroad](), [semiconductors](), [toolchains](), [user-experience]() ### AI overview Google has joined the OpenROAD Initiative as a principal member and appointed Aaron Cunningham to its Governing Board. The partnership supports OpenROAD's open-source electronic design automation ecosystem through governance, ecosystem growth, workforce development, and technical improvements. ### Source excerpt by Ethan Mahintorabi & Aaron Cunningham, Hardware Toolchains Team Google is committed to advancing open source silicon innovation. We are excited to share that we have formally joined the OpenROAD Initiative (ORI), Inc. as a principal member. ORI is a nonprofit public benefit corporation dedicated to the open source electronic design automation (EDA) ecosystem. As part of this commitment, Aaron Cunningham has been appointed to the ORI Governing Board to represent Google and help drive the foundation's strategic direction, financial sustainability, and technical stewardship. Driving long-term open source sustainability The OpenROAD Initiative's mission is to advance and sustain the open source EDA ecosystem by fostering collaborative innovation across research, education, and industry--transforming ideas into silicon. Google's membership aligns directly with ORI's multi-year sustainability goals, supported by the US National Science Foundation's (NSF) Pathways to Enable Open-Source Ecosystems (POSE) program. With Google's participation and membership commitment, ORI will continue to strengthen, grow, and sustain its open source ecosystem through key vectors: Neutral Stewardship: Fostering transparent governance where no single company has outsized control over the code, ensuring the project remains inspectable, accessible, and community-driven. Ecosystem Growth: Supporting open and reproducible silicon research, developing robust design flows, and hosting global design contests. Workforce Development: Supporting global silicon skilling initiatives by expanding open source chip design curricula and collaborating with academic institutions and industrial training networks. Technical Strengthening: Enhancing continuous integration and deployment (CI/CD) pipelines, expanding PDK enablement, and improving user experience. Leadership perspectives "The OpenROAD Initiative is built on the vision of making chip design open and accessible to all--building a collaborative ecosyst ## Software Delivery Platform: Key Features & How to Evaluate DevFeed: [Software Delivery Platform: Key Features & How to Evaluate]() Original publisher: [Read original article]() Author: Eric Minick Published: 2026-08-11T00:00:00Z Content type: article Language: en Sources: [Harness Blog]() Topics: [Software](), [CI/CD](), [Continuous Delivery (CD)](), [Continuous integration]() Tags: [audit](), [automation](), [blog](), [ci-cd](), [ci-cd-pipeline](), [governance](), [how-to](), [progressive-delivery](), [rollback](), [scalability](), [security](), [software-delivery](), [visibility]() ### AI overview This article explains how a software delivery platform differs from a standalone CI/CD tool. It describes a platform as an integrated system covering the full after-code lifecycle, including continuous integration, continuous delivery, security, governance, insights, coordination, and rollback, then outlines criteria for evaluating vendors. ### Source excerpt A software delivery platform isn't just a CI/CD tool. Get the must-have feature checklist and the demo questions to use when evaluating vendors. | Blog ## The Electron browser is being deprecated in Cypress DevFeed: [The Electron browser is being deprecated in Cypress]() Original publisher: [Read original article]() Published: 2026-07-10T15:15:58Z Content type: article Language: en Sources: [Cypress Blog]() Topics: [Cypress](), [Electron](), [Testing](), [browsers](), [Chromium](), [Continuous integration]() Tags: [browser](), [browsers](), [chrome](), [chromium](), [continuous-integration](), [cypress](), [edge](), [firefox](), [testing]() ### AI overview Cypress is deprecating its bundled Electron browser starting with Cypress 16.0.0 and plans to remove it in a future major version. The article explains that tests can produce inconsistent results in Electron compared with users' installed browsers, and recommends moving local and CI runs to installed browsers such as Chrome for Testing, Chrome, Firefox, or Edge. ### Source excerpt We're deprecating the Electron browser in Cypress, starting in Cypress 16.0.0, with removal in a future major version. After years of seeing inconsistent results between Electron and the browsers people actually use, we are standardizing on installed browsers for more reliable test results. ## A miniguide to AI Product Management DevFeed: [A miniguide to AI Product Management]() Original publisher: [Read original article]() Author: Raphaël Hoogvliets Published: 2024-02-07T09:23:52Z Content type: tutorial Language: en Sources: [Raphaël Hoogvliets]() Topics: [Artificial Intelligence](), [Product Management](), [MLOps](), [Continuous integration](), [Requirements](), [Data Quality](), [Testing](), [Deployment]() Tags: [ai](), [data-quality](), [deployment](), [management](), [mlops](), [product-management](), [requirements](), [testing]() ### AI overview A practical guide for aspiring AI product managers covering MLOps processes, business alignment, requirements gathering, iterative development, governance, data privacy, and data quality. ### Source excerpt Navigate the challenges of tech innovation in a multi-stakeholder landscape ## Evolution of Developer Productivity at Square - Part Two DevFeed: [Evolution of Developer Productivity at Square - Part Two]() Original publisher: [Read original article]() Author: Korhan Bircan Published: 2024-01-29T09:00:00Z Content type: article Language: en Sources: [Square Corner Blog RSS Feed]() Topics: [code productivity](), [build times](), [Android](), [remote-development](), [Continuous integration](), [Optimization](), [Caching](), [Gradle](), [Amazon EC2](), [ide](), [benchmarking]() Tags: [android](), [benchmarking](), [build-times](), [caching](), [cloud](), [continuous-integration](), [developer-productivity](), [development](), [engineering](), [gradle](), [ide](), [optimization](), [remote-development](), [velocity]() ### AI overview Square describes efforts to improve developer productivity and development velocity by reducing build, installation, IDE synchronization, and continuous integration times. The article reports development apps, remote Android development environments, configuration caching, CI shard skipping, emulator optimization, Gradle changes, and modularization work. ### Source excerpt Accelerating development velocity ## Schema Checks: Introducing the New GraphQL CI Tool In Apollo Studio DevFeed: [Schema Checks: Introducing the New GraphQL CI Tool In Apollo Studio]() Original publisher: [Read original article]() Author: Caydie Tran Published: 2020-10-01T16:44:29Z Content type: release Language: en Sources: [Apollo Blog]() Topics: [GraphQL](), [Continuous integration](), [Command-line interface](), [configuration]() Tags: [backend](), [ci](), [cli](), [configuration](), [graphql](), [release](), [schema]() ### AI overview Apollo introduces redesigned GraphQL schema checks in Apollo Studio. The Apollo CLI can check schema changes against real production traffic for backward compatibility, with improved visibility, overrides, user experience, and centralized configuration. ### Source excerpt A Better Way to do CI For GraphQL When deploying code, you want to be sure that nothing will blow up when things go live. To prevent downtime, it's a good practice to use CI (continuous integration) to run tests, checks, and ensure your app is fully ready to hit production. If you're running GraphQL in production, the last thing you want is a schema change to break things for your users. ## Living on the Edge of Rails DevFeed: [Living on the Edge of Rails]() Original publisher: [Read original article]() Author: Edouard CHIN Published: 2019-08-21T18:39:00Z Content type: article Language: en Sources: [Shopify Engineering](), [Shopify Engineering - Shopify Engineering]() Topics: [Rails](), [Shopify](), [Continuous integration](), [Bot]() Tags: [blog](), [blog-post](), [ci](), [edge](), [framework](), [production](), [ruby](), [shopify]() ### AI overview Shopify describes running the latest revision of Rails in production and continuously integrating upstream changes into its Core monolith. This approach reduces upgrade effort, exposes edge cases through a large CI test suite, and encourages contributions to Rails and related projects. A bot named Solid Track automates weekly Rails updates. ### Source excerpt Shopify's Core monolith has been running the latest revision of the Rails framework in production since Feb 2019. ## Continuous Integration of Vanilla C Programs for Intel, ARM, and MIPS Architecture DevFeed: [Continuous Integration of Vanilla C Programs for Intel, ARM, and MIPS Architecture]() Original publisher: [Read original article]() Published: 2019-07-22T22:33:34Z Content type: tutorial Language: en Sources: [Ariya Hidayat]() Topics: [Continuous integration](), [C](), [cross-platform](), [Azure](), [C++](), [gcc](), [make]() Tags: [architectures](), [azure](), [c](), [c-plus-plus](), [continuous-integration](), [cpu](), [cross-platform](), [free](), [gcc](), [yaml]() ### AI overview This tutorial demonstrates continuous integration for a small ANSI C/C90 program across multiple CPU architectures, operating systems, and C/C++ compilers. It uses Azure Pipelines with YAML jobs for supported architecture, operating-system, and compiler combinations, and describes native builds, compiler installation, and executable verification. ### Source excerpt Developing cross-platform applications presents a major challenge:, how to ensure that every commit does not break some combinations of operating systems and CPU architectures. Fortunately, thanks an array of online services and open-source tools, this challenge becomes easier to tackle. ## Validating OAS 3 specification in your CI build DevFeed: [Validating OAS 3 specification in your CI build]() Original publisher: [Read original article]() Published: 2019-02-15T17:29:41Z Content type: tutorial Language: en Sources: [Miro Cupak]() Topics: [OpenAPI Specification](), [Continuous integration](), [YAML](), [GitHub](), [Swagger](), [Testing](), [pull-requests]() Tags: [ci](), [continuous-integration](), [github](), [openapi](), [pull-requests](), [specifications](), [swagger](), [swagger-validator-badge](), [testing](), [travis](), [travis-ci](), [yaml]() ### AI overview This tutorial explains how to validate an OpenAPI 3 specification on every pull request as part of continuous integration. It uses the Swagger Validator Badge tool in Travis CI, building version 2.0.0 locally because hosted support for OpenAPI 3 was incomplete at the time of writing. ### Source excerpt As part of my work on standards under GA4GH, I frequently deal with API specifications, most often written in OpenAPI 3 (OAS 3). The setup is always similar - there's a public GitHub repository containing an OAS 3 YAML file and a few common auxiliary files (.gitignore, LICENSE, CONTRIBUTING.md, and README.md). Reference implementations of... ## Announcing new versions of our client SDKs DevFeed: [Announcing new versions of our client SDKs]() Original publisher: [Read original article]() Author: Tristan Sokol Published: 2017-04-28T22:18:28Z Content type: release Language: en Sources: [Square Corner Blog RSS Feed]() Topics: [SDK](), [OpenAPI Specification](), [Code generation](), [Continuous integration](), [Slack](), [ASGI]() Tags: [apis](), [authorization](), [c-sharp](), [ci](), [developers](), [github](), [gradle](), [java](), [maven](), [openapi](), [php](), [python](), [request](), [ruby](), [sdks](), [slack](), [travis-ci](), [update]() ### AI overview Square announces updated first-party client SDKs, a new Slack community for developer feedback, and its first Java SDK. The SDKs are generated from the OpenAPI Specification and support PHP, Python, Ruby, C#, and Java, with expanded endpoint coverage and revised authorization and API naming. ### Source excerpt We are releasing a big update to our first-party SDKs, as well as a new Slack community for developers! ## Android Makers FR recap DevFeed: [Android Makers FR recap]() Original publisher: [Read original article]() Author: info@jeroenmols.com (Jeroen Mols) Published: 2017-04-11T00:00:00Z Content type: article Language: en Sources: [Jeroen Mols]() Topics: [Android](), [Development](), [Kotlin](), [React](), [Continuous integration]() Tags: [android](), [androidmakers](), [blogs](), [conference](), [continuous-integration](), [droidcon](), [kotlin](), [pull-requests](), [react](), [recap]() ### AI overview A recap of Android Makers FR, a conference that followed the organizers' move from Droidcon Paris to a new format. The article covers themes and highlights including Android app quality, launch performance, engineering practices, continuous integration, Kotlin, React Native, Android Things, and collected conference slides. ### Source excerpt After organizing Droidcon Paris for several year, the organizers decided to move on and experiment with a new format. This didn't just result in a well organized conference, but also in a fresh new vibe whilst still feeling familiar. ## Best Practices and Common Mistakes with Travis CI DevFeed: [Best Practices and Common Mistakes with Travis CI]() Original publisher: [Read original article]() Author: Kevin Deisz Published: 2017-01-10T13:46:39Z Content type: tutorial Language: en Sources: [Localytics]() Topics: [Travis CI](), [Continuous integration](), [Testing](), [build performance](), [GitHub]() Tags: [best-practices](), [continuous-integration](), [github](), [parallelism](), [speed](), [testing](), [travis-ci]() ### AI overview This article presents five internal best practices for using Travis CI, focusing on continuous integration, efficient testing, and reducing build time. It explains how Travis CI integrates with GitHub and supports configurable build environments, build matrices, and test parallelism. ### Source excerpt What is Travis At Localytics, we've worked hard to ensure that all of our services are built and deployed using our own internal best practices. One of those core best practices is that the service in question is using continuous integration (CI). CI greatly reduces the amount of ## Continuous Delivery - Automating the Release Process DevFeed: [Continuous Delivery - Automating the Release Process]() Original publisher: [Read original article]() Author: umer Published: 2016-06-18T00:00:00Z Content type: article Language: en Sources: [Code Ahoy - Articles]() Topics: [Continuous Delivery (CD)](), [Continuous integration](), [Software Engineering](), [DevOps]() Tags: [automated](), [ci](), [configuration](), [continuous-delivery](), [release](), [tests]() ### AI overview The article explains how manual release processes can be slow, error-prone, and stressful, then introduces Continuous Delivery as an approach for automating releases. It describes production-like environments, extensive automated testing, fast developer feedback, and Continuous Integration as a prerequisite. ### Source excerpt For many software developers, release days are stressful events. There's always some risk that things might go wrong in the process or that a bug would surface in production. At my previous company, we had a manual release process that was very human intensive; hence, error prone. On release days, DevOps would load binaries on a staging environment and perform user acceptance tests (UAT) manually. If the tests were successful, the software was copied to production servers and verified with smoke tests and occasionally, a trimmed down version of the UAT was run again. Here are the common problems we faced: 2 out 3 times when we had to roll back a release because of an issue, it was due to a configuration mismatch between staging and production environments. The release process was slow and it took a long time to put new features in the hands of our users. It wasn't uncommon for the release process to take days or sometimes even weeks. The slow release process and the manual UAT had another side-effect: the developers didn't get timely feedback. By the time feedback arrived, they were often in the middle of another feature. This incurred additional overhead because their memories were no longer fresh and on rare occasions, the error got re-introduced due to mix-up between branches. In short, manual and ad-hoc release processes are suboptimal and the release day is fraught with stress. In our case, it was tolerable until releases became more frequent and the team grew. To improve and automate the release process, there's a software engineering approach know as Continuous Delivery (CD). Continuous delivery makes it possible to release new features quickly and reliably. It provides fast feedback to developers. The software is built in a way where it can be automatically and safely released to production at any time. This is ensured by delivering every change to a production-like environment and running extensive automated tests on it. According to Martin Fowler, you are ## Lint your shell scripts DevFeed: [Lint your shell scripts]() Original publisher: [Read original article]() Author: Carlos Alexandro Becker Published: 2014-12-15T00:00:00Z Content type: tutorial Language: en Sources: [Carlos Becker]() Topics: [Bash](), [Shell](), [Command-line interface](), [Continuous integration]() Tags: [bash](), [command-line](), [continuous-integration](), [shell](), [zsh]() ### AI overview The article discusses improving shell-script quality with ShellCheck, a Haskell executable that lints Bash, Zsh, and other shell scripts. It explains how to integrate ShellCheck into continuous integration with the shell-travis-build project and Travis CI, including use as a Git submodule. ### Source excerpt I will start this by quoting the bashstyle's readme: ## A Modern CI Server for Android DevFeed: [A Modern CI Server for Android]() Original publisher: [Read original article]() Published: 2014-07-02T07:00:00Z Content type: opinion Language: en Sources: [Blogs on Ryan Harter]() Topics: [Continuous integration](), [Android](), [Jenkins]() Tags: [android](), [android-studio](), [ci](), [continuous-integration](), [jenkins](), [opinion]() ### AI overview A freelance Android developer explains why continuous integration servers improve build reliability, test feedback, and build standardization. The article discusses shortcomings the author sees in Jenkins, including web-only configuration and limited build isolation, and describes the search for a modern, open-source CI server with Android support. ### Source excerpt As a freelance Android developer, I've gotten the opportunity to work with many different client environments when it comes to building and releasing Android (and other) apps. One of the things that I've learned over the years is the importance of a good build server. Why CI? Continuous Integration servers, or CI servers, are designed to checkout your code after each push and build your project, including any tests you might have. This allows you to be notified immediately if and when you commit code that doesn't compile or fails tests. Especially when working in teams, this can offer increased reliability and peace of mind. ## Writing your own Karma adapter DevFeed: [Writing your own Karma adapter]() Original publisher: [Read original article]() Published: 2013-09-09T00:00:00Z Content type: tutorial Language: en Sources: [SoundCloud Backstage Blog]() Topics: [JavaScript](), [Web app](), [Continuous integration](), [browsers](), [Web Development](), [Chrome]() Tags: [browsers](), [chrome](), [ci](), [html](), [javascript](), [mobile-web](), [testing](), [web-app]() ### AI overview This tutorial explains how to write a custom Karma adapter for the Tyrtle JavaScript unit testing framework. It covers connecting test results and completion status to the Karma API, creating a renderer or reporter, configuring the test files and runner, and handling Karma's browser-serving and caching behavior, including use with an AMD loader. ### Source excerpt Background When we started to work on the new version of our mobile web app, we knew we wanted to run unit tests on a wide variety of... ## Objective-C on Travis-CI DevFeed: [Objective-C on Travis-CI]() Original publisher: [Read original article]() Author: Keith Smiley Published: 2013-04-11T22:58:00Z Content type: tutorial Language: en Sources: [Keith Smiley]() Topics: [Objective-C](), [Continuous integration](), [iOS](), [Xcode](), [Testing](), [GitHub](), [Jenkins](), [Open Source]() Tags: [apple](), [ci](), [configuration](), [continuous-integration](), [dependencies](), [github](), [ios](), [jenkins](), [objective-c](), [open-source](), [self-hosted](), [submodules](), [testing](), [travis](), [travis-ci](), [xcode]() ### AI overview A practical guide to configuring Travis CI for Objective-C projects targeting OS X and iOS. It covers repository setup, the .travis.yml configuration file, Xcode shared schemes and test targets, dependency handling, and additional scripts for projects using CocoaPods or submodules. ### Source excerpt Recently Travis added support for Objective-C and there for OS X and iOS projects for continuous integration testing. I gather that people have previously done this with self-hosted dedicated Jenkins machines but since Apple is so aggressive about dropping support for previous versions of the OS it seems like a pain to have to replace your build server every few years. Enter Travis, a great hosted continuous integration server that hosts a huge amount of open source projects. I figured with this new support I could host some of my smaller libraries just to set how well it worked. The initial setup process was a bit tedious but I eventually got it to work. Assumtions: You have a test framework already integrated with your project (I like Specta/Expecta) You have your project on Github in a public repository. Travis offers a pro account if you'd rather Steps Create a .travis.yml file in the root of your repository (leading dot is intentional). For many projects a file may just look like: language: objective-c By default Travis runs this script for Objective-C projects I was informed on Twitter that the current script that runs Objective-C projects is actually located here. It was originally created by Justin Spahr-Summers here. This script seems to run my projects without any issue, they just occasionally require more initial setup (we'll get to that). Enable your repository in Travis' settings. From your Travis profile page (after signing in with Github) you should see a list of your repositories, you may have to press 'Sync now', where you can switch on the repository you're planning on adding. Configure your project within Xcode. As I assumed above you already have a test target setup. You do have to do a few things in Xcode to make everything work correctly. Go to 'Manage Schemes' in Xcode. Check the 'Shared' box for the scheme that needs to be run. Click 'Edit...' in the bottom left and go to your build action. On the row of your Tests target check the box in the ' ## iOS Integration Testing, Part 2 DevFeed: [iOS Integration Testing, Part 2]() Original publisher: [Read original article]() Author: Square Engineering Published: 2011-11-04T16:00:00Z Content type: release Language: en Sources: [Square Corner Blog RSS Feed]() Topics: [Integration testing](), [Testing](), [Continuous integration](), [iOS](), [Jenkins](), [Git](), [Open Source](), [RSS]() Tags: [continuous-integration](), [engineering](), [git](), [integration-testing](), [ios](), [jenkins](), [open-source](), [rss](), [testing]() ### AI overview This article announces Zapp, an open-source continuous integration server for running KIF iOS integration tests on each commit. It describes its setup, Xcode requirement, Jenkins-compatible RSS output, repository polling, build queuing, and test-result status. ### Source excerpt A continuous integration server for running your tests on every commit.