# CircleCI CircleCI is CI/CD tooling that automates software builds, tests, and deployments. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## 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. ## 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 ## 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. ## 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. ## Setting up a Go build with Glide on CircleCI DevFeed: [Setting up a Go build with Glide on CircleCI]() Original publisher: [Read original article]() Author: Carlos Alexandro Becker Published: 2016-08-07T00:00:00Z Content type: tutorial Language: en Sources: [Carlos Becker]() Topics: [CircleCI](), [Go Language]() Tags: [build](), [circleci](), [go]() ### AI overview A quick tutorial on setting up a Go build with Glide on CircleCI. It provides configuration tips and notes that import paths may need adjustment for the project repository. ### Source excerpt I've lost a considerable amount of time trying to bind those things together, so I decided to write this quick post about it, so others could also benefit from it. ## Continuous Delivery with GitHub, CircleCI, Docker and AWS Elastic Beanstalk DevFeed: [Continuous Delivery with GitHub, CircleCI, Docker and AWS Elastic Beanstalk]() Original publisher: [Read original article]() Author: Carlos Alexandro Becker Published: 2015-09-29T00:00:00Z Content type: tutorial Language: en Sources: [Carlos Becker]() Topics: [Continuous Delivery (CD)](), [CI/CD](), [Docker](), [CircleCI](), [GitHub](), [Docker Hub](), [Deployment](), [Amazon Web Services](), [Environment Variables]() Tags: [aws](), [circleci](), [continuous-delivery](), [deployment](), [docker](), [docker-hub](), [environment-variables](), [github]() ### AI overview This tutorial explains a continuous delivery setup for a Go service using GitHub, CircleCI, Docker, Docker Hub, and Amazon Elastic Beanstalk. Commits pushed to the site repository are built into Docker images, tagged with the CircleCI build number, pushed to Docker Hub, and deployed to production so deployed commits can be traced through the image and build tags. ### Source excerpt This is just a quick overview of how I did it in antibody's homepage.