|
|
dcda5be0dd
|
docs: update deployment checklist for ITSulu K8s cluster
Updated PHASE3_DEPLOYMENT_CHECKLIST.md to reflect K8s-based E2E testing
instead of external Runboat:
CI/CD Variable:
- Changed from 3 Runboat variables to 1 KUBE_CONFIG variable
- KUBE_CONFIG: base64-encoded kubeconfig for itsulu-testing namespace
- Must have Job create permissions and pod access
Deployment Steps:
- Step 1: Get kubeconfig from infrastructure team
- Step 2: Base64 encode and set KUBE_CONFIG variable
- Removed GitLab bot token creation (no MR comments needed)
- Removed Runboat account verification
K8s Cluster Verification:
- Check cluster connectivity with kubectl cluster-info
- Verify itsulu-testing namespace exists
- Check for required services: test-db-svc
- Verify secrets: test-db-info, gitlab-docker-creds
Pipeline Timing:
- Lint: 2 min (unchanged)
- Test: 10 min (unchanged)
- Build: 3 min (unchanged)
- E2E: 30-45 min (K8s job setup + Odoo init + tests)
- Total: ~50 minutes
Note: E2E stage removed as separate stage, now runs inline during build phase
via kubectl job creation.
Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
|
2026-05-30 00:59:31 -04:00 |
|
|
|
124d9308c7
|
docs: add Phase 3 deployment checklist with CI/CD variable setup
Created comprehensive deployment guide for Phase 3 Runboat E2E testing:
Pre-Deployment Checklist:
- Code readiness verification (all Phase 3 artifacts listed)
- CI/CD variables setup with exact requirements:
* RUNBOAT_API_URL (from infrastructure team)
* RUNBOAT_TOKEN (from infrastructure team)
* GITLAB_BOT_TOKEN (create locally via GitLab access tokens)
- Runboat account verification script
- E2E test dry-run instructions
- Performance test dry-run instructions
Deployment Steps (Step-by-step):
1. Create GitLab bot token (copy/paste walkthrough)
2. Set CI/CD variables in GitLab UI (protected, masked)
3. Push Phase 3 code to feature branch
4. Create MR with standard description
5. Verify pipeline runs (expected stages + timing)
6. Review pipeline artifacts (reports + traces)
Troubleshooting Guide:
- Runboat preview fails: Authorization, timeout, connectivity
- E2E selector failures: Form field mismatches
- Performance test failures: Network time vs mocked
- With fixes and verification steps for each
Post-Deployment:
- Weekly monitoring procedures
- Annual token renewal reminder
- Success criteria checklist
- Approval sign-off section
Expected Pipeline Timeline:
- Lint: 2 min
- Test (parallel): 10 min
- Build: 3 min
- Preview: 5 min
- E2E: 15 min
- Total: ~35 minutes
Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
|
2026-05-30 00:55:38 -04:00 |
|
