CI: stop using spot-instance BATs directors#2729
Conversation
|
|
|
ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (2)
💤 Files with no reviewable changes (2)
WalkthroughThis pull request removes the Suggested reviewers
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Pull request overview
Removes GCP spot/preemptible configuration from the BATs director setup to avoid unreliable spot-instance behavior in CI.
Changes:
- Remove
preemptible: truefrom the generated BATs config YAML for GCP. - Remove
"preemptible": truefrom the director vars JSON produced viajq.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
ci/bats/iaas/gcp/prepare-bats-config.sh |
Stops injecting preemptible: true into bats-config.yml properties for GCP BATs. |
ci/bats/iaas/gcp/director-vars |
Stops emitting the preemptible field in director vars JSON consumed by the GCP BATs pipeline. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
NOTE: EasyCLA is currently broken. See cloudfoundry/cloud_controller_ng#5089 (comment) Re-trigger EasyCLA via: |
|
/easycla |
Remove
preemptible: truefrom BATs director configurations. This flag causes GCP spot-instances to be used which are unreliable.