Continuous Integration

AutoOps+ · 48 questions

• A city CI pipeline needs API tokens for a 311 chatbot deploy job. Where should those secrets live?
• County cloud deploys should avoid long-lived static access keys in CI. Which secrets practice best matches that goal?
• A parks CI pipeline token may have been exposed in a job log. What secrets action should the team take first?
• Housing and public-health CI fixtures must exercise workflows without storing raw resident identifiers. Which practice supports that requirement?
• Municipal CI service accounts should follow a Zero Trust-aligned secrets stance. Which choice best reflects that?
• City platform teams need a controlled place to store container images produced by CI. What fulfills that role?
• Tax-portal releases must ensure production always pulls the exact build that was tested. Which artifact practice supports that?
• Permits-portal CI must record which components shipped in each build for later vulnerability response. What should the pipeline generate?
• School-district CI pulls packages through an external open-source cache. What control should guard that access?
• Elections tooling builds must start from clean machines each run to avoid leftover credentials and packages. What CI environment approach fits?
• EMS automation jobs retrieve vault credentials that stop working after a configured interval even though nobody revoked them. What CI secrets concept explains this?
• School applications accidentally promoted a nonprod image tag into the production pull path. How should artifact registries be organized to reduce that mistake?
• Housing authority CI must prevent unsigned build outputs from entering the production promote path. Which control belongs there?
• Public-works IaC jobs fail because runners lack Terraform and cloud CLIs. What CI environment practice fixes that?
• Clerk automation CI must stop merges when a pull request embeds an API key. Which pipeline control does that?
• The city library catalog release must keep an inventory of shipped components with each versioned artifact. What practice meets that need?
• Utilities NOC builders are air-gapped and cannot reach the public Internet for packages. How should CI obtain approved dependencies?
• Municipal CI secrets for parks, clerk, and public health must stay isolated. Which vault design supports that?
• 311 API unit suites are independent and CI wall-clock time is too long. Which orchestration choice helps?
• Courts CI must apply a schema migration before integration tests that query the new tables. How should the workflow be ordered?
• Transit CI should deploy only from tagged builds on the main branch, not from feature branches. Which workflow concept applies?
• Parks deploy stage completes but post-deploy smoke checks fail. What workflow response should CI take?
• Open-data integration tests occasionally flake on transient timeouts. Which failure-handling approach is appropriate?
• Transit mobile-backend pull requests must not merge until security findings are reviewed. Which pipeline enhancement belongs there?
• Public-health CI jobs produce different results on different agents because tool versions drift. What practice improves consistency?
• City IaC repositories keep regressing on style and complexity rules. Which CI enhancement should block those merges?
• Municipal CI agents keep failing with intermittent out-of-memory errors that are hard to spot in raw logs. What enhancement helps?
• City chatbot CI must lint, then unit-test, then package—never package before tests finish. How should the pipeline express that?
• County PowerShell automation must be verified on multiple supported OS images. Which orchestration approach fits?
• Fire/EMS CI scans a container base image and finds a critical CVE. What should the pipeline do?
• A canary release for the assessor portal burns the error budget. Which CI workflow action should follow?
• Elections build pipelines fail overnight with nobody watching the CI UI. What failure-handling practice helps?
• Documentation-only PRs for the permits portal still trigger expensive load tests. What workflow change is appropriate?
• Permits automation scripts accumulate duplicated logic that slows future changes. Which CI enhancement flags that before merge?
• City Jenkins should start a pipeline automatically when developers push to the municipal Git remote. Which trigger mechanism fits?
• Library staff need a quick way to re-run a failed CI pipeline from chat without opening the CI console. What trigger helps?
• Open-data validators should rebuild every night even when no one pushed that day. Which trigger type fits?
• Tax-portal production deploy stages must not start until an authorized operator confirms. Which pipeline trigger practice applies?
• A public-health lab pipeline must load staging credentials on feature branches and production credentials only on main. Which Git variable practice applies?
• County release jobs must name permits-portal artifacts from the SemVer Git tag that triggered the build. What should drive that naming?
• City 311 builds must record immutable provenance so support can map a production binary to exact source. Which metadata should be stamped?
• City infrastructure lint and test stages for the water-utility repo should live as versioned pipeline code in Jenkins. Where should that definition live?
• County GIS tile builds need a versioned GitLab CI pipeline with build and publish stages. Which definition format fits?
• Parks reservation automated tests must run as a GitHub Actions workflow versioned with the app. Which file defines that pipeline?
• A hot clerk-portal bug fix was just pushed and must be validated immediately—not after tonight's nightly job. Which trigger choice is correct?
• Municipal CI receives Git webhooks for the housing portal. How should the pipeline reject forged start requests?
• A change to the elections-office CI pipeline definition is proposed. What municipal change-control practice applies?
• Library documentation-only commits still run full site deploys. What controlled approach should operators use?