# CircleCI Published articles for CircleCI. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## CircleCI is now available on Cursor Origin DevFeed: [CircleCI is now available on Cursor Origin]() Original publisher: [Read original article]() Author: Nathan Fish Published: 2026-09-01T18:45:00Z Content type: release Language: en Sources: [The CircleCI Blog Feed | CircleCI]() Topics: [CI/CD](), [Testing](), [AI-assisted coding](), [Pull Request]() Tags: [agentic-ci-cd](), [ai-coding-agents](), [ai-development](), [ci](), [ci-cd](), [circleci](), [circleci-cursor-origin](), [circleci-news](), [cursor-origin](), [cursor-origin-ci-cd](), [integrations](), [mcp](), [origin-ci-cd-integration](), [pull-request](), [testing]() ### AI overview CircleCI has released a beta integration with Cursor Origin, allowing teams to connect Origin-hosted repositories and run CI/CD pipelines on pushes and pull requests. The integration supports agent-oriented validation through parallel execution, targeted testing, and feedback via the CircleCI CLI and MCP. ### Source excerpt CircleCI now integrates with Cursor Origin in beta. Connect an Origin repo, keep your existing .circleci/config.yml, and add agent-friendly CI/CD to your Origin projects. ## CircleCI Smarter Testing: Stop running tests that don't matter DevFeed: [CircleCI Smarter Testing: Stop running tests that don't matter]() Original publisher: [Read original article]() Author: Nathan Fish Published: 2026-08-26T19:00:00Z Content type: article Language: en Sources: [The CircleCI Blog Feed | CircleCI]() Topics: [Testing](), [CI/CD]() Tags: [accelerate](), [auto-rerun-failed-tests](), [ci-cd](), [circleci](), [circleci-news](), [developer-productivity](), [dynamic-test-splitting](), [engineering-productivity](), [flaky](), [intelligent-test-selection](), [parallel](), [pipeline](), [quality](), [reduce](), [smarter-testing](), [test-impact-analysis](), [testing](), [tests](), [time]() ### AI overview CircleCI describes Smarter Testing, a set of features designed to reduce CI/CD test execution time by skipping tests unaffected by changes, balancing parallel nodes, and retrying flaky tests. The article says early users have seen test runs up to four times faster. ### Source excerpt Testing eats up to half your pipeline time. See how CircleCI Smarter Testing skips unaffected tests, rebalances parallel nodes, and retries flaky tests. ## Pushing container images to China: what we learned the hard way DevFeed: [Pushing container images to China: what we learned the hard way]() Original publisher: [Read original article]() Author: Team Honey Badger Published: 2026-08-06T15:34:42Z Content type: article Language: en Sources: [Giant Swarm Blog]() Topics: [container images](), [ACR](), [Azure](), [Kubernetes](), [AI Infrastructure](), [Inference](), [Cloud]() Tags: [acr](), [ai-infrastructure](), [azure](), [china](), [circleci](), [container](), [container-image-building](), [container-images](), [firewall](), [inference](), [kubernetes]() ### AI overview This article explains why container image pushes to China can be much slower than elsewhere. It attributes the problem to China's separate registry infrastructure and cross-border transfer throttling, and says Giant Swarm cut delivery time to under two minutes with a split push through Singapore. ### Source excerpt Why container pushes to China take 30 minutes, and how Giant Swarm cut it to under 2 with a split push through Singapore. ## Best GitLab Alternatives in 2026 DevFeed: [Best GitLab Alternatives in 2026]() Original publisher: [Read original article]() Author: Pete Miloravac Published: 2026-07-30T12:04:04Z Content type: comparison Language: en Sources: [Semaphore Engineering]() Topics: [GitLab](), [CI/CD](), [DevSecOps](), [GitHub Actions]() Tags: [2026](), [alternatives](), [ci-cd](), [circleci](), [compare](), [cost](), [devsecops](), [enterprise-deployment](), [evaluation](), [github](), [github-actions](), [gitlab](), [gitlab-ci](), [self-hosted]() ### AI overview A comparison of Semaphore, GitHub Actions, CircleCI, and Buildkite as alternatives to GitLab for CI/CD-focused decisions. It examines execution, deployment, pricing, support, and operating models while explaining when retaining GitLab repositories may be more practical than replacing GitLab entirely. ### Source excerpt GitLab is a capable, integrated DevSecOps platform--but it is not the only sensible way to run CI/CD. Teams comparing GitLab alternatives are often trying to improve pipeline execution, simplify operations, get clearer support and cost options, or adopt a CI/CD tool that fits their existing source-control strategy. That does not automatically mean moving repositories out [...] The post Best GitLab Alternatives in 2026 appeared first on Semaphore. ## Best Bitbucket Alternatives in 2026 DevFeed: [Best Bitbucket Alternatives in 2026]() Original publisher: [Read original article]() Author: Pete Miloravac Published: 2026-07-29T11:54:28Z Content type: comparison Language: en Sources: [Semaphore Engineering]() Topics: [bitbucket](), [CI/CD](), [GitHub Actions](), [GitLab](), [Self-hosted](), [Cloud](), [Deployment](), [DevSecOps]() Tags: [2026](), [alternatives](), [bitbucket](), [ci-cd](), [circleci](), [cloud](), [compare](), [github](), [github-actions](), [gitlab](), [gitlab-ci](), [linux](), [macos](), [pipelines](), [self-hosted]() ### AI overview This comparison guide examines Bitbucket Pipelines and four alternatives--Semaphore, GitHub Actions, GitLab CI/CD, and CircleCI--to help teams choose a CI/CD platform based on source-control ecosystem, visibility, deployment control, hosting model, and operational requirements. ### Source excerpt Bitbucket Pipelines is a logical starting point for teams already using Bitbucket Cloud. It is built into the source-control experience, configured in a bitbucket-pipelines.yml file, and offers both Atlassian-hosted execution and self-hosted runners. But convenience at the repository level is not always the same thing as the best long-term CI/CD operating model. Teams evaluating Bitbucket [...] The post Best Bitbucket Alternatives in 2026 appeared first on Semaphore. ## Best Jenkins Alternatives in 2026 DevFeed: [Best Jenkins Alternatives in 2026]() Original publisher: [Read original article]() Author: Pete Miloravac Published: 2026-07-24T09:56:00Z Content type: article Language: en Sources: [Semaphore Engineering]() Topics: [CI/CD](), [Jenkins](), [Groovy](), [GitHub Actions](), [GitLab](), [Vulnerabilities](), [DevOps](), [Open Source]() Tags: [ci-cd](), [circleci](), [compare](), [devsecops](), [github-actions](), [gitlab](), [groovy](), [jenkins](), [open-source](), [security](), [security-vulnerabilities](), [self-hosted]() ### AI overview A 2026 guide compares Jenkins alternatives and explains why teams migrate away from Jenkins, citing maintenance overhead, plugin conflicts, Groovy pipeline complexity, and security-patch concerns. It highlights Semaphore, GitHub Actions, GitLab CI/CD, and CircleCI for different use cases. ### Source excerpt Jenkins earned its place as the default CI server of the 2010s: it was free, endlessly extensible, and available before any serious managed CI/CD competitor existed. More than a decade later, that same flexibility has become the thing teams complain about most -- plugin sprawl, Groovy pipeline scripts nobody wants to maintain, and infrastructure that [...] The post Best Jenkins Alternatives in 2026 appeared first on Semaphore. ## Fault Injection in your release automation DevFeed: [Fault Injection in your release automation]() Original publisher: [Read original article]() Author: Sam Rossoff Published: 2024-03-18T00:00:00Z Content type: article Language: en Sources: [Gremlin Blog]() Topics: [CI/CD](), [Chaos Engineering](), [Resilience](), [Testing](), [Automation](), [sdlc]() Tags: [automation](), [ci-cd](), [circleci](), [concurrency](), [deployment](), [engineering](), [latency](), [parallel](), [resilience](), [sdlc](), [testing]() ### AI overview The article explains how Fault Injection and resilience testing can be incorporated into CI/CD and release automation. It describes three strategies: scheduling tests independently of release cadence, running them after production deployments, and gating release candidates on test results. It also explains why these experiments usually require longer runtimes and controlled concurrency. ### Source excerpt A Gremlin Principal Engineer goes over Fault Injection and resilience testing in the CI/CD and release automation portion of an SDLC. ## Shared Secrets in CI Systems Create Security Risks DevFeed: [Shared Secrets in CI Systems Create Security Risks]() Original publisher: [Read original article]() Author: info@goteleport.com (Noah Stride) Published: 2023-03-08T00:00:00Z Content type: article Language: en Sources: [Teleport]() Topics: [ci](), [Security](), [GitHub Actions](), [API keys](), [CircleCI](), [ssh]() Tags: [api-keys](), [ci](), [circleci](), [github-actions](), [heroku](), [security](), [ssh](), [travis-ci](), [vercel]() ### AI overview The article explains how shared secrets in CI systems and CD pipelines can enable attackers to access production systems and steal customer data. It discusses replacing long-term shared secrets with short-lived, scoped certificates. ### Source excerpt Shared secrets in CI systems like GitHub Actions and CircleCI pose serious risks. Hackers can exploit secrets to access production systems and steal information. ## Apollo Changelog: March 6, 2023 DevFeed: [Apollo Changelog: March 6, 2023]() Original publisher: [Read original article]() Author: Dylan Anthony Published: 2023-03-06T19:38:51Z Content type: release Language: en Sources: [Apollo Blog]() Topics: [changelog](), [GraphQL](), [apollo-client](), [CircleCI](), [monorepo](), [Kotlin](), [Terraform]() Tags: [apollo-client](), [changelog](), [circleci](), [community](), [graphql](), [kotlin](), [monorepo](), [news](), [terraform]() ### AI overview The March 6, 2023 Apollo Changelog highlights Apollo GraphOS monorepo deployment work using CircleCI, Kotlin, and Terraform; upcoming Rust and TypeScript subgraph content; GraphQL documentation updates; new videos; Kotlin client guidance; and several Apollo tooling releases and improvements. ### Source excerpt Welcome back to the Apollo Changelog. After taking a week off, we're back with a fresh batch of news for you! A glimpse into Apollo's monorepo Ever wonder how GraphOS works under the hood? A big chunk of it lives in a monorepo that Apollo engineer Ryan Wilcox has shared details about in a recent blog post. Check out "How we deploy the Apollo GraphOS monorepo" to learn how we use CircleCI, Kotlin, Terraform, and more! ## How we deploy the Apollo GraphOS monorepo DevFeed: [How we deploy the Apollo GraphOS monorepo]() Original publisher: [Read original article]() Author: Ryan Wilcox Published: 2023-02-23T11:32:34Z Content type: tutorial Language: en Sources: [Apollo Blog]() Topics: [monorepo](), [CI/CD](), [CircleCI](), [Deployment]() Tags: [circleci](), [continuous-deployment](), [continuous-integration](), [deployment](), [engineering](), [graphos](), [guide](), [monorepo](), [workflow]() ### AI overview Apollo describes how it moved deployment of its Apollo GraphOS monorepo to continuous deployment in its staging environment using CircleCI. The article outlines the workflow triggered when developers push, approve, and merge code, including CircleCI dynamic configuration and change-scope detection. ### Source excerpt Did you know that the majority of Apollo GraphOS's features are shipped via a monorepo? Yes, these mythic beasts still roam the earth. Ours is a humble but temperamental creature that, until recently, required Apollo engineers to do a lot of manual deployment to get the fleet entirely rolled. This year our team undertook the effort to get things continuously deployed to our staging environment using our continuous integration (CI) provider, CircleCI. ## Application Security Roundup - January DevFeed: [Application Security Roundup - January]() Original publisher: [Read original article]() Author: Adam Published: 2023-01-30T00:00:00Z Content type: article Language: en Sources: [Shostack & Friends Blog]() Topics: [Application Security](), [Security](), [incident](), [CircleCI](), [Artificial Intelligence]() Tags: [ai-assistants](), [application-security](), [article](), [circleci](), [incident](), [security]() ### AI overview An application security roundup covering threat modeling, security incident retrospectives involving CircleCI and Uber, research on AI assistants and insecure code, sociotechnical harms, vulnerability remediation under the CFAA, and the history of attack trees. ### Source excerpt So many interesting articles from AI to an organizatoion of socio-technical harms, fascinating incident reports about Uber and Circle CI and some history of attack trees. ## Run your Maestro Flows on CircleCI DevFeed: [Run your Maestro Flows on CircleCI]() Original publisher: [Read original article]() Author: Arthur Published: 2023-01-18T08:00:00Z Content type: tutorial Language: en Sources: [mobile.dev - Medium]() Topics: [ci](), [Cloud](), [API keys](), [API](), [Command-line interface](), [Android](), [iOS](), [cURL](), [APK]() Tags: [android](), [api](), [apk](), [ci](), [circleci](), [cli](), [cloud](), [curl](), [environment-variables](), [ios](), [maestro]() ### AI overview A guide to integrating Maestro Cloud with CircleCI. It explains how to upload application builds and Maestro flows, securely provide an API key through project environment variables, and retrieve flow results in CI jobs for Android and iOS projects. ### Source excerpt Maestro Cloud is compatible with all CI systems including CircleCI. ## The Appsec Landscape in 2023 DevFeed: [The Appsec Landscape in 2023]() Original publisher: [Read original article]() Author: Adam Published: 2023-01-05T00:00:00Z Content type: article Language: en Sources: [Shostack & Friends Blog]() Topics: [Application Security](), [Security](), [Requirements](), [open-source-security]() Tags: [appsec](), [changes](), [circleci](), [driving](), [external](), [government](), [legacy](), [requirements](), [secure-software](), [ssdf](), [supply-chain]() ### AI overview This article examines how economic conditions, new regulations, and engineering considerations may shape application security decisions in 2023. It emphasizes threat modeling, secure software development requirements, legacy code, and software supply-chain concerns. ### Source excerpt External changes will be driving appsec in 2023. It's time to frame the decisions in front of you. ## Parallelizing Jest and Cypress.io Tests on CircleCI DevFeed: [Parallelizing Jest and Cypress.io Tests on CircleCI]() Original publisher: [Read original article]() Published: 2022-09-07T00:00:00Z Content type: tutorial Language: en Sources: [Artsy]() Topics: [Jest](), [Cypress](), [ci](), [Developer experience]() Tags: [ci](), [circleci](), [cypress](), [developer-experience](), [jest](), [tests](), [unit-tests]() ### AI overview This tutorial explains how to parallelize CI test workloads using Jest sharding and CircleCI's split command for Cypress.io integration tests. It describes dividing Jest tests into buckets so separate processes can run subsets concurrently, reducing overall test execution time and developer wait time. ### Source excerpt At Artsy, exploring ways to improve the developer experience is part of our makeup. Whether it's implementing hot-swapping for Express.js or integrating the Rust-based SWC compiler into our front-end build pipeline, we're always trying to reduce the amount of time it takes for a code cycle to take place. CI is no exception. When a developer opens a PR, we want to ensure they get timely feedback. Do their unit tests pass? Does the app build correctly? And how about smoke tests? Each of these jobs are complex processes that take time, and the more one can parallelize said tasks the less devs will need to wait. Scaled out to a whole engineering org, minor improvements to CI can be radical. In this regard, two things came across our radar recently that we'd like to share: sharding via Jest, and a (free) way to parallelize Cypress.io integration tests via CircleCI's split command. Sharding in Jest "What is sharding?" Good question! In short, it means "a small part of a whole". The database community has employed sharding techniques for decades, where a large database is split up into smaller, more manageable chunks, usually to improve performance at scale. The same idea can be applied to any process or task involving a lot of data, including tests. Think about it like this. Imagine an app that has thousands of tests. One can open up their terminal and run yarn test and execute all of the tests at once in a single process, or one can open two terminal tabs and run yarn test src/utils and yarn test src/routes, and have both processes allocate a pool of memory to complete each (smaller) subset of tasks. Because each process has its own memory pool the performance characteristics are generally better, and thus the overall time required to run our tests is reduced / decreased. Running each of these commands scoped to a particular folder is easy enough, but in a CI environment this is somewhat cumbersome; we'd need to define two new jobs and then the conditions in which they r ## CI CD Solution From CircleCI and ionir DevFeed: [CI CD Solution From CircleCI and ionir]() Original publisher: [Read original article]() Author: ionir Team Published: 2022-03-01T14:52:22Z Content type: release Language: en Sources: [ionir]() Topics: [CI/CD](), [DevOps](), [Cloud]() Tags: [ci-cd](), [circleci](), [cloud](), [cloud-native](), [devops](), [latest-news](), [partner](), [partnership](), [pipeline]() ### AI overview ionir announced a technology partnership with CircleCI to offer customers a streamlined CI/CD solution for cloud-native workflows. The partnership is intended to support DevOps needs and accelerate CI/CD deployments. ### Source excerpt ionir announced it has become a technology partner with CircleCI to offer customers a streamlined CI/CD solution. This effort aligns with ionir's initiative to meet market needs and accommodate customers' DevOps needs with cloud-native CI/CD solutions The post CI CD Solution From CircleCI and ionir appeared first on ionir. ## Android Worldwide: April 2021 DevFeed: [Android Worldwide: April 2021]() Original publisher: [Read original article]() Author: Siddhesh Patil Published: 2021-05-06T17:29:25Z Content type: article Language: en Sources: [Sid Patil - Android Engineer and Kotlin Advocate]() Topics: [Android](), [Development](), [Kotlin](), [API](), [Compose](), [Testing](), [CI/CD](), [CircleCI]() Tags: [android](), [android-developer-communities](), [android-development](), [android-worldwide-event-talks](), [api](), [best-android-developer-communities](), [ci-cd](), [circleci](), [compose](), [development](), [event](), [gde-talks](), [gdg-groups](), [honey-sonwani-android-lint](), [jetpack-compose](), [julien-salvi-talks](), [karan-dhillon](), [kotlin](), [kotlin-user-groups](), [marton-braun-gde-android](), [merab-tato-kutalia-gdg-tbilisi](), [mohit-sarveiya-kotlin-talks](), [preview-driven-development-with-jetpack-compose](), [rikin-marfatia](), [siddhesh-patil-android-engineer](), [testing](), [wajahat-karim-jetpack-compose]() ### AI overview The article provides details of the April 2021 Android Worldwide event, including its participating communities, schedule, speakers, and sessions on Android development, Kotlin, Jetpack Compose, API visibility, testing, app bundles, and CI/CD. ### Source excerpt As the second event of the series unfolds, Julien Salvi, Honey Sonwani, Marton Braun, Karan Dhillon, Mohit Sarveiya, Rikin Marfatia and Wajahat Karim talk about the latest in Android development. ## Searching for RH Counterexamples -- Productionizing DevFeed: [Searching for RH Counterexamples -- Productionizing]() Original publisher: [Read original article]() Published: 2021-03-06T10:08:59Z Content type: tutorial Language: en Sources: [Jeremy Kun]() Topics: [CI/CD](), [CircleCI](), [Testing](), [GitHub](), [Docker](), [Containers](), [scaling]() Tags: [ci](), [circleci](), [containers](), [coverage](), [error-handling](), [github]() ### AI overview A tutorial on productionizing an application that searches for counterexamples to the Riemann Hypothesis. It covers automated tests for pull requests, error handling, cleanup after failed worker jobs, type-hint and test-coverage checks, static analysis, failure alerting, and automated updates, using CircleCI and containers. ### Source excerpt We're ironically searching for counterexamples to the Riemann Hypothesis. Setting up Pytest Adding a Database Search Strategies Unbounded integers Deploying with Docker Performance Profiling Scaling up In the last article we rearchitected the application so that we could run as many search instances as we want in parallel, and speed up the application by throwing more compute resources at the problem. This is good, but comes with a cost. The complexity of this new architecture requires us to manage many different containers and AWS instances. ## Aircall Journey to Android App Bundle DevFeed: [Aircall Journey to Android App Bundle]() Original publisher: [Read original article]() Author: Julien Salvi Published: 2021-02-18T15:12:51Z Content type: tutorial Language: en Sources: [Stories by Julien Salvi on Medium]() Topics: [Android](), [APK](), [Gradle](), [Optimization](), [CircleCI](), [feature flags](), [ci]() Tags: [android](), [android-app-bundle](), [androiddev](), [apk](), [ci](), [circleci](), [continuous-integration](), [feature-flags](), [gradle](), [optimization](), [play-store]() ### AI overview Aircall describes migrating its Android app from APK distribution to Android App Bundle to deliver optimized APKs. The article covers APK size reduction, language, density, and ABI splits, Gradle configuration, and planned Play Feature Delivery, with CircleCI and fastlane mentioned for release automation. ### Source excerpt A couple months, we decided to use Android App Bundle (AAB) to distribute Aircall's Android app in Play Store. After analyzing the Aircall Android application package (APK), we found we could deliver optimized APKs to our users -- an overall size reduction of 60%! In this article, we are going to expose our journey to Android App Bundle from our own motivations to the development within the application and the CI with CircleCI and fastlane to release on the Play Store. Why move to App Bundle? Moving to App Bundle had many advantages. The first and main reason was the APK size optimization, to deliver only what the user needs. After looking at our application file, we found that we embedded all native libraries (.so files) of all supported architectures! We could have used the abi split in our main build.gradle but we would have managed 4 APKs with different version code. We also saw we could reduce the resource assets to match the density of the device where the app is installed. Here is what the Aircall universal APK looks like on the inside: APK analysis with Android Studio Optimizing size was not the only advantage we saw. Migrating to AAB will allow us (a little bit) to save the planet! Indeed, with all the MB saved from the downloads and updates, we are using less storage space and consuming fewer energy resources. You can see our MAD Score below. If it hits 1 million downloads we could save 22 TB of data -- really a huge impact. MAD Score data from the Aircall project We were also excited by our future ability to enable Play Feature Delivery to push features to specific users. Since we are already using feature flags inside our applications, this would let us develop features on-the-go for our users. Gradle configuration Moving to AAB was a very smooth process and did not require a lot of configuration code. To replicate this move, on your build.gradle of your application, add the following block to build an AAB file. You will be able to add the language, densit ## Hello8Ball: Exploring Coroutine Testing with a Kotlin Sampler App DevFeed: [Hello8Ball: Exploring Coroutine Testing with a Kotlin Sampler App]() Original publisher: [Read original article]() Published: 2019-11-23T21:36:11Z Content type: tutorial Language: en Sources: [maiatoday]() Topics: [Coroutines](), [Testing](), [test](), [CircleCI](), [test-coverage](), [App]() Tags: [circleci](), [code](), [code-coverage](), [coroutine-testing](), [coroutines](), [detekt](), [jacoco](), [kotlinx](), [test](), [testing](), [tests]() ### AI overview Hello8Ball is a toy sampler app for exploring coroutine testing in Kotlin. It simulates an 8 Ball and includes examples involving network calls, calculations, password generation, synonym lookup, and prime-number checks. The repository includes tests using kotlinx-coroutine-test, CircleCI test execution, detekt, JaCoCo coverage, and a branch converted to JUnit 5. ### Source excerpt A sampler app to explore Coroutine testing. This is a toy app that simulates an 8 Ball. It can answer questions, find synonmyms, generate a password or check if a number is prime. It was created to make a situation where it makes sense to use coroutines to e.g. go on the network or make a calculation. Then I added tests for all the pieces using kotlinx-coroutine-test. As a bonus the repo is set up to run the tests on CircleCi. It has detekt setup and jacoco code coverage. There is also a branch where all the tests are converted to junit5. Devfest 2019 video This is the companion repo to the KotlinEveryWhereZA 2019 and DevFestZa 2019 talk. Slides are in the repo. code ## Publish a Docker container from Bitbucket to Google Cloud Container Registry DevFeed: [Publish a Docker container from Bitbucket to Google Cloud Container Registry]() Original publisher: [Read original article]() Published: 2019-08-07T00:00:00Z Content type: tutorial Language: en Sources: [Juri Strumpflohner]() Topics: [Docker](), [bitbucket](), [Google Cloud Platform (GCP)](), [Docker Hub](), [Automation](), [Git](), [Jenkins](), [GitLab]() Tags: [automation](), [bitbucket](), [circleci](), [container-registry](), [docker](), [git](), [gitlab](), [google-cloud](), [jenkins](), [registry]() ### AI overview This tutorial explains how to configure a Bitbucket pipeline to automatically build and publish Docker container images to a private repository in Google Cloud Container Registry. It covers triggering builds from commits and Git tags, setting required environment variables, authenticating with Google Cloud, and tagging images. ### Source excerpt Lorem ipsum dolor sit amet ## Hugo, Firebase Hosting and CircleCI DevFeed: [Hugo, Firebase Hosting and CircleCI]() Original publisher: [Read original article]() Published: 2019-04-28T09:34:57Z Content type: tutorial Language: en Sources: [Posts on Adam Bennett]() Topics: [Hugo](), [Firebase](), [hosting](), [CircleCI](), [Google]() Tags: [algorithms](), [android](), [blog](), [career](), [circleci](), [compose](), [continuous-deployment](), [continuous-integration](), [development](), [domain](), [engineering](), [finance](), [firebase](), [functional](), [google](), [growth](), [guides](), [hosting](), [how-to](), [hugo](), [java](), [jetpack](), [kotlin](), [money](), [opinions](), [software](), [startups](), [thoughts](), [training](), [tutorial](), [web]() ### AI overview A practical guide to setting up a Hugo blog with Firebase Hosting and CircleCI, including domain configuration and DNS verification through Google Domains. ### Source excerpt Domain setup First thing's first - go buy your domain on domains.google.com. They're only GBP 10 a year, but if I remember correctly there's a GBP 120 initial fee. Your mileage may vary depending on the popularity of your domain name. The process is pretty user friendly, even for a web noob like myself. ## Google Cloud Build for Android DevFeed: [Google Cloud Build for Android]() Original publisher: [Read original article]() Published: 2018-12-21T20:27:21Z Content type: tutorial Language: en Sources: [Blogs on Ryan Harter]() Topics: [Google Cloud Platform (GCP)](), [Android](), [CI/CD](), [CircleCI](), [Docker]() Tags: [android](), [circleci](), [continuous-integration](), [delivery](), [docker](), [google-cloud]() ### AI overview This introductory post examines Google Cloud Build as a continuous integration and delivery option for Android projects. It explains the author's limitations with CircleCI, including container memory constraints and projected costs, and introduces a series on configuring Google Cloud Build for Android. ### Source excerpt As I've written before, I'm always on the lookout for a great continuous integration and delivery system. For a long time I used CircleCI, but in the last month or so I've started hitting some limitations that I needed to work around. My requirements are pretty standard, I need something that works well with Android, requires minimal maintenance, and can handle somewhat larger projects. After a souring experience with CircleCI, and a short search for other hosted providers, I stumbled upon an early solution from Google that intrigued me. ## Continuous Delivery for Android DevFeed: [Continuous Delivery for Android]() Original publisher: [Read original article]() Published: 2018-05-24T20:15:03Z Content type: tutorial Language: en Sources: [Blogs on Ryan Harter]() Topics: [Android](), [CI/CD](), [CircleCI](), [releases](), [Testing](), [Jenkins]() Tags: [android](), [android-development](), [circleci](), [continuous-delivery](), [continuous-integration](), [jenkins](), [releases](), [testing]() ### AI overview An Android developer describes moving from continuous integration to continuous delivery, where app changes are automatically built and released to appropriate channels. The article discusses release targets, separate debug and release builds, and a CircleCI 2.0 workflow, with Jenkins mentioned as a previous option. ### Source excerpt For a long time I've been in search of a good continuous integration server for Android. I've even written about one that I used years ago, which is no longer suited to Android development, in my opinion. As the Android community has grown, so has the wealth of tools available. In that time I've also moved from simply wanting continuous integration, to wanting continuous delivery. Continuous Delivery you say? Continuous delivery builds on continuous integration, but instead of just testing your source code when you commit, it is also published to the appropriate channels. This takes the burden from the developer by automatically releasing a new version of the app any time changes are made, and also creates a reliable, repeatable release pipeline. ## Automating a CI workflow for a Python serverless app with CircleCI DevFeed: [Automating a CI workflow for a Python serverless app with CircleCI]() Original publisher: [Read original article]() Author: Rupak Ganguly Published: 2018-04-27T00:00:00Z Content type: tutorial Language: en Sources: [Serverless Blog]() Topics: [ci](), [Python](), [Serverless](), [App]() Tags: [app](), [aws](), [aws-lambda](), [ci](), [circleci](), [cloud-computing](), [continuous-integration](), [engineering](), [faas](), [function-as-a-service](), [infrastructure-as-code](), [python](), [serverless](), [serverless-architecture](), [serverless-framework](), [workflow]() ### AI overview An end-to-end overview of continuous integration for a Python serverless app using CircleCI. ### Source excerpt An end-to-end look at continuous integration with Python, Serverless and CircleCI. [Next page]()