Browse
Trending commands (last 30 days).
30 commands
Sorted by popularity, then recency
CI/CD Pipelines: Debugging and Troubleshooting · Find failures faster0 copies · 30d
Enable GitHub Actions step debug logging
Turn on runner debug logs for detailed troubleshooting.
CI/CD Pipelines: Debugging and Troubleshooting · Frequent CI/CD problems and fixes0 copies · 30d
Retry flaky network operations
Wrap downloads or package installs with bounded retries.
CI/CD Pipelines: Debugging and Troubleshooting · Frequent CI/CD problems and fixes0 copies · 30d
Cancel outdated duplicate runs
Keep only the latest run active for a branch or PR.
CI/CD Pipelines: Debugging and Troubleshooting · Frequent CI/CD problems and fixes0 copies · 30d
Missing secrets or permissions
Fail early when credentials or roles are unavailable.
CI/CD Pipelines: Debugging and Troubleshooting · Find failures faster0 copies · 30d
Replay Jenkins pipeline with edits
Retry a failed Jenkins pipeline with small script adjustments.
CI/CD Pipelines: Debugging and Troubleshooting · Find failures faster0 copies · 30d
Inspect GitLab job traces
Review the full job log and artifacts from failed jobs.
CI/CD Pipelines: Debugging and Troubleshooting · Frequent CI/CD problems and fixes0 copies · 30d
Use strict shell mode in scripts
Stop on errors and unset variables.
CI/CD Pipelines: Monorepos, Templates, and Maintainability · Make pipelines maintainable0 copies · 30d
Wrap repeated commands in repo scripts
Keep YAML small by moving logic into versioned scripts.
CI/CD Pipelines: Monorepos, Templates, and Maintainability · Make pipelines maintainable0 copies · 30d
Use predictable workflow names
Name workflows by concern or application area.
CI/CD Pipelines: Monorepos, Templates, and Maintainability · Make pipelines maintainable0 copies · 30d
Expose pipeline health publicly
Add workflow status badges to docs or README files.
CI/CD Pipelines: Monorepos, Templates, and Maintainability · Avoid running everything on every change0 copies · 30d
Generate jobs per package
Drive job fan-out from changed package lists or matrix inputs.
CI/CD Pipelines: Monorepos, Templates, and Maintainability · Avoid running everything on every change0 copies · 30d
GitLab rules with changes
Conditionally run jobs based on file changes.
CI/CD Pipelines: Monorepos, Templates, and Maintainability · Avoid running everything on every change0 copies · 30d
GitHub path filters
Run workflows only when selected folders change.
CI/CD Pipelines: Releases, Rollbacks, and Quality Gates · Stop bad builds from reaching users0 copies · 30d
Fail if test coverage drops below threshold
Enforce a minimum quality bar in CI.
CI/CD Pipelines: Releases, Rollbacks, and Quality Gates · Ship progressively0 copies · 30d
Rollback to the previous version
Keep a simple rollback command or job ready before each production deploy.
CI/CD Pipelines: Releases, Rollbacks, and Quality Gates · Stop bad builds from reaching users0 copies · 30d
Run smoke tests after deployment
Verify critical endpoints before marking a release healthy.
CI/CD Pipelines: Releases, Rollbacks, and Quality Gates · Ship progressively0 copies · 30d
Release from version tags
Trigger a release pipeline when a semver tag is pushed.
CI/CD Pipelines: Releases, Rollbacks, and Quality Gates · Stop bad builds from reaching users0 copies · 30d
Run database migrations during deploy
Apply migrations as an explicit pipeline stage.
CI/CD Pipelines: Releases, Rollbacks, and Quality Gates · Ship progressively0 copies · 30d
Canary deploy flow
Send a small portion of traffic to the new version before full rollout.
CI/CD Pipelines: Security, Secrets, and Governance · Reduce pipeline risk0 copies · 30d
Be careful with untrusted pull requests
Avoid exposing secrets to code from forks.
CI/CD Pipelines: Security, Secrets, and Governance · Harden pipeline credentials and permissions0 copies · 30d
Use least-privilege permissions in GitHub Actions
Explicitly scope the token for each workflow or job.
CI/CD Pipelines: Security, Secrets, and Governance · Harden pipeline credentials and permissions0 copies · 30d
Use OIDC instead of long-lived cloud keys
Exchange a short-lived identity token for cloud credentials.
CI/CD Pipelines: Security, Secrets, and Governance · Harden pipeline credentials and permissions0 copies · 30d
Protect production variables in GitLab
Restrict sensitive variables to protected branches or tags.
CI/CD Pipelines: Security, Secrets, and Governance · Reduce pipeline risk0 copies · 30d
Require approval for production release
Add environment rules or manual gates before prod deploys.
CI/CD Pipelines: Security, Secrets, and Governance · Reduce pipeline risk0 copies · 30d
Pin actions to a version or commit
Avoid floating references for critical workflow dependencies.
CI/CD Pipelines: Containers, Services, and Environments · Build and publish container images0 copies · 30d
Build and push Docker image with GitHub Actions
Authenticate, build, and push to a registry.
CI/CD Pipelines: Containers, Services, and Environments · Run with databases or environment-specific settings0 copies · 30d
Run deploy only on deployment-capable agents
Target jobs to specific Jenkins workers or labels.
CI/CD Pipelines: Containers, Services, and Environments · Run with databases or environment-specific settings0 copies · 30d
Use named environments
Attach production jobs to an environment with protection rules.
CI/CD Pipelines: Containers, Services, and Environments · Build and publish container images0 copies · 30d
Build image in GitLab CI
Use Docker-in-Docker or a compatible runner setup.
CI/CD Pipelines: Containers, Services, and Environments · Build and publish container images0 copies · 30d
Deploy a new image to Kubernetes
Update a deployment image and monitor rollout status.