What is the difference between CI and CD?
Continuous integration brings changes together frequently and verifies them with automated build and test feedback. Continuous delivery keeps eligible changes ready for controlled release; continuous deployment automatically publishes changes that pass the required gates. Explain which meaning of CD you are using.
Design a pull-request pipeline
Use a reproducible environment, restore dependencies safely, run fast static and unit checks early, and add integration, security, or contract tests based on risk. Report results to the review. Avoid rebuilding the release artifact differently after approval.
How should artifacts move between environments?
Build once when practical, attach version and provenance, store the immutable artifact in a controlled registry, and promote that artifact through environments with configuration supplied separately. Explain how you identify exactly what is running and trace it back to reviewed source.
How do you handle secrets?
Use an approved secret store and narrowly scoped short-lived credentials where possible. Restrict environment access, prevent secrets from entering logs or artifacts, rotate them, and audit use. A masked value can still leak through files, commands, or derived output, so test the whole path.
Rolling, blue-green, or canary deployment?
Choose based on blast radius, capacity, state, compatibility, observability, and recovery needs. A rolling update gradually replaces instances; blue-green uses separate environments; a canary exposes a limited audience first. None is automatically safest without reliable health criteria.
How do database changes remain compatible?
Prefer staged, backward-compatible changes: add before using, move application behavior, migrate or backfill safely, then remove only after old code no longer depends on it. Account for mixed application versions during rollout. Test both rollback and roll-forward constraints.
The pipeline is green but production is broken
A green pipeline proves only the checks it ran. Protect users, stop or reverse the rollout, inspect production signals, compare configuration and dependencies, and add a targeted check after understanding the gap. Do not add a flaky end-to-end test merely to say coverage increased.
Sources checked
These official references support the guide. Product details and technical documentation can change; check the linked source for current information.
Where Cluegent helps
Cluegent supports permitted live workflows with transcript context, typed prompts, screenshot-aware answers, resume context, custom response behavior, quick action buttons, and a private desktop overlay. It is most useful when you already understand the subject and need help staying structured under pressure.
Frequently asked questions
What should I draw in a CI/CD system-design answer?
Show trigger, build, checks, artifact storage, promotion, environment controls, deployment, verification, and recovery. Mark secrets and approvals.
Does a passing pipeline mean a release is safe?
It means the configured checks passed. Safe delivery also depends on test relevance, environment differences, rollout controls, observability, and recovery.