โ† Back to Visual Guide Index

๐Ÿ”„ Complete PR Workflow Timeline

Watch a code change journey from PR to production through the entire Konflux CI/CD pipeline

๐Ÿ“š Related: Renovate/MintMaker Workflow | Testing Flow Details

๐Ÿ‘จโ€๐Ÿ’ป
1
Developer Opens PR
Time: 0 minutes
You make changes to a component (e.g., build-service) and open a Pull Request on GitHub.
What happens:
  • Code pushed to your branch
  • PR opened with description
  • CI automatically triggers
๐Ÿงช
2
Component CI Tests Run
Duration: 1-2 hours
GitHub Actions runs unit tests, integration tests, and e2e tests for your component.
Tests include:
  • Unit tests (5-10 min)
  • Integration tests (10-20 min)
  • E2E tests with paired changes (1 hour)
  • Code quality checks
โœ…
3
PR Approved & Merged
Time: Few hours to 1 day
After code review and approval, your PR merges to the main branch.
Triggers:
  • Postsubmit CI job starts
  • Container image build begins
  • Tests run one final time
๐Ÿ“ฆ
4
Container Image Built
Duration: 10-15 minutes
New container image is built and pushed to quay.io with multiple tags.
Image tags created:
  • :latest
  • :main-abc123d (branch-commit)
  • :sha-abc123def456 (full SHA)
๐Ÿค–
5
Renovate Creates PR
Duration: 2 hours (bot scanning interval)
Renovate bot detects the new image and automatically creates a PR in infra-deployments to update the image reference.
PR updates:
  • components/{service}/base/kustomization.yaml
  • Image tag: old456e โ†’ abc123d
  • Image digest for security
  • Links to your original PR
๐Ÿ”ฌ
6
infra-deployments Tests
Duration: 1.5 hours
OpenShift CI provisions a fresh cluster, installs Konflux with your new image, and runs the full e2e test suite.
Test phases:
  • Provision cluster (5-10 min)
  • Bootstrap Konflux (15-20 min)
  • Run e2e tests (30-60 min)
  • Report results (5 min)
๐Ÿš€
7
Deployed to Development
Duration: 3-5 minutes
After the infra-deployments PR merges, ArgoCD automatically syncs and deploys your changes to the development environment.
Deployment steps:
  • ArgoCD detects manifest change
  • Kubernetes rolling update
  • Health checks pass
  • Slack notification sent
๐ŸŽฏ
8
Staging โ†’ Production
Duration: 1-3 days
After soak time in development, changes are promoted to staging, then after approval and more soak time, to production.
Progression:
  • Development (immediate)
  • Staging (after 6-24 hours)
  • Production (manual approval)
๐ŸŽ‰ Total Time: Code โ†’ Production = 2-5 days (typical)