CI/CD
- What is CI/CD?
CI/CD stands for Continuous Integration and Continuous Delivery/Deployment. It's a set of practices that automate building, testing, and releasing software so teams can ship changes quickly and reliably. - How do I set up a CI/CD pipeline?
Choose a CI/CD tool (GitHub Actions, GitLab CI, Jenkins), define stages (build, test, deploy) in a config file, connect your repo, and add deployment steps with secrets. Start simple and iterate. - What is the difference between continuous delivery and continuous deployment?
Continuous delivery means every change is automatically built and tested, but a human approves the final release to production. Continuous deployment means every change that passes tests goes to production automatically, with no manual gate. - How do I run tests in a CI pipeline?
Add a test step to your CI configuration that installs dependencies and runs your test command after checkout. The pipeline should fail if any test fails, blocking the build from moving forward. - What is a build artifact?
A build artifact is any file produced by a build process that you want to keep or deploy, such as a compiled binary, a JAR file, a Docker image, or a zip archive. It is the output of your CI pipeline that gets stored and promoted to environments. - How do I store secrets in CI/CD?
Use your CI/CD platform's built-in secret management (like GitHub Secrets, GitLab CI variables, or Jenkins credentials) to store sensitive values encrypted. Never hardcode secrets in code or config files; inject them as environment variables at runtime.