
How to Schedule Jobs in GitHub Actions and CI the Right Way
Schedule jobs in CI: GitHub Actions cron and the 60 day rule, GitLab pipeline schedules, manual runs, concurrency control and failure alerts.
Tag
8 posts

Schedule jobs in CI: GitHub Actions cron and the 60 day rule, GitLab pipeline schedules, manual runs, concurrency control and failure alerts.

Use OIDC in CI to get short lived cloud credentials instead of stored keys: GitHub id-token permission, AWS trust policy conditions and least privilege roles.

Fix GitHub Actions permission denied on a script: the executable bit, git update-index, shebang and line endings, noexec mounts, and how to call with bash.

Choose between self hosted and hosted CI runners: cost at scale, speed and caching, special hardware, network access, security risks and maintenance duties.

Build multi arch images in CI for amd64 and arm64: QEMU versus native runners, cross compiling in the Dockerfile, manifest lists and verification.

Compare GitHub Actions, GitLab CI and Jenkins for a small team: setup effort, runners, pricing model, maintenance and the situations that decide it.

Produce CI build artifacts you can trust: checksums, retention, signed attestations, SLSA provenance, reproducible builds and verifying before deploy.

Use branch protection and required status checks so nothing merges red: required checks, reviews, linear history, admin bypass, CODEOWNERS and gotchas.