CI CD
84 bites tagged CI CD — interview questions with model answers, and 60-second explainers.
Optimizing Slow iOS CI Build Times
Profile the build, cache CocoaPods and DerivedData, use prebuilt frameworks, parallelize, scope to changed work. CI build optimization. buying faster runners without measuring the bottleneck first.
Designing a Fastfile for Versioning, match, and Uploads
Lanes bump versions, run match for signing, build with gym and gradle, upload via pilot and supply; secrets come from CI env or a vault. Fastlane lane design. committing the match passphrase or keys to the repo.
CI/CD Pipeline for React Native to TestFlight and Play
A triggered workflow installs deps, builds signed artifacts on macOS and Linux runners, uploads via Fastlane to TestFlight and the Play internal track. mobile CI/CD design. storing signing secrets in the repo.
Monorepo vs polyrepo for a product portfolio
Monorepo eases atomic shared-component changes and consistency but needs tooling; polyrepo gives autonomy but version drift; tie choice to deploy independence. Whether you reason about repo strategy via concrete tradeoffs.
Automating chaos in CI/CD for continuous verification?
Run codified experiments against staging or canary with pass/fail on steady-state SLIs; prerequisites are observability, automated abort, and isolation. Operationalizing chaos as a gate.
Design automated microservice provisioning workflow
Template scaffolding plus a pipeline that creates repo, CI/CD, and infra as code, with idempotent steps and rollback. Golden-path platform design.
Automating a recurring manual cache clear
Recognize the repetitive manual task, document the runbook, then automate it into the deploy pipeline as a post-deploy hook with monitoring. Eliminating toil.
What is a model registry and how does it enable CD?
A registry versions models with metadata, lineage, and stage tags; CD watches stage transitions to trigger deploys. model lifecycle governance. treating it as just blob storage with no versioning, stages, or lineage.
CI/CD for microservice-based ML systems
Independent per-service pipelines, contract testing to protect interfaces and schemas, and incremental deploys (canary, blue-green); manage data and model contracts, not just code. ML CI/CD at service granularity.
Fairness and robustness gates in CI/CD
Sliced fairness metrics across subgroups, robustness checks via perturbation and adversarial sets, all compared to thresholds that fail the build. automated model quality gates.
Automating design system standards enforcement
Custom ESLint and Stylelint rules for tokens and APIs, a11y testing with axe, editor and pre-commit hooks, blocking CI gates plus visual regression. Shift-left enforcement tooling.
Versioning and distributing multi-platform tokens
JSON source, Style Dictionary transforms per platform, semantic versioning, and per-platform package registries in CI. full token pipeline plus distribution. ignoring how each platform consumes and updates the packages.
Token build pipeline for multi-platform output
JSON source of truth, a tool like Style Dictionary with per-platform transforms and formats, and CI publishing. token transformation across platforms. hand-maintaining separate platform files in parallel.
Automated enforcement of deprecated component removal
Lint rule failing new usages, codemods for existing ones, and a usage dashboard gating removal. automating deprecation governance in CI. hard-failing builds day one with no migration path.
Designing a contribution model with quality gates
Define a federated model, branch-and-PR flow, required reviews, and automated gates for tests, a11y, and visual regression. Whether you can open contributions without losing quality.
Automated Release Pipeline
An automated release pipeline turns merged design-system changes into published, versioned packages without manual steps, using semantic versioning and changelogs so consumers can upgrade safely and the team ships small changes frequently and reliably.
ML CI/CD versus traditional software CI/CD
Validates code plus data plus the model, auto-trains and evaluates, adds continuous training and monitoring. MLOps pipeline understanding. describing only code CI/CD and ignoring data, model gates, and retraining.
CI/CD pipeline for a design system monorepo
Install and cache, then parallel lint, type-check, unit and visual tests, then build, and on main a release job bumps versions and publishes. Designing release automation for a monorepo. publishing before tests pass.
How would you build CI/CD for an ML model?
Data and model versioning, automated training plus evaluation gates, model registry, deployment with monitoring and retraining triggers. MLOps maturity beyond app deployment.
CI/CD pipeline for a container PaaS
Run tests, build the image, push the tag to a registry, then deploy it to Cloud Run. The registry is the build-to-deploy handoff. the build-push-deploy pipeline. skipping the registry or rebuilding on the deploy host.
Dynamically generate CI/CD pipelines
A detection step scans for marker files and maps them to reusable stage templates assembled at runtime; trade off convention/DRY against reduced transparency and harder debugging. designing pipeline-as-code that adapts to a repo.
Securely managing signing assets in CI/CD
Keep encrypted certificates and profiles in a controlled store or fastlane match repo, inject the decryption key and credentials via CI secrets, install into a temporary keychain per run. secret handling for CI signing.
Automatic signing: benefits and limitations on teams
Automatic signing creates certificates and profiles on demand and keeps them in sync, easing local setup; limits include proliferating certificates, weak CI fit, and less control for complex entitlements. managing signing across a team.
Diagnosing and stabilizing flaky XCUITests
Identify timing races, animations, network variance, and shared state; fix with expectations, controlled launch state, and isolation. handling nondeterminism in UI automation.
Get CI CD bites daily.
Five a day, five minutes, offline. With quizzes so it sticks.
Open testing — you’ll join as an early tester.