Add Resolute jobs to pipleline - #2802
Conversation
Declares the four Concourse resources a Resolute test line needs: the GCP and warden stemcells from bosh.io, the Resolute stemcell container image used to compile releases, and the bucket location for Resolute-compiled candidate releases. Each sits beside its Noble equivalent. Also adds a comment explaining that the compiled-release resources pick the newest tarball by a timestamp embedded in its filename, which only works because make-candidate.sh generates timestamped versions.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
WalkthroughAdded Ubuntu Resolute CI coverage. The pipeline defines Resolute stemcell and compiled-release resources, candidate-release compilation, BATS, BRATS, BDRATS, and cleanup jobs. Resolute jobs use Resolute stemcells, environment names, and OS parameters. Delivery gating remains Noble-only. Suggested reviewers: Mergeability Score: ⚪ Minimal · up to This change adds optional Resolute pipeline jobs without making them release-blocking; no actionable merge-blocking risk remains after normal checks and review. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 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 |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@ci/pipeline.yml`:
- Line 2183: Adjust the comment immediately above the resource entry to use two
leading spaces, matching the surrounding resource-level indentation and
resolving the YAML lint comments-indentation violation.
🪄 Autofix
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: ASSERTIVE
Plan: Pro Plus
Run ID: 494df7a4-a1a9-4653-9b47-0ab0c4012aa8
📒 Files selected for processing (1)
ci/pipeline.yml
The bosh pipeline tested the director on Ubuntu Noble and Jammy-FIPS only. Ubuntu Resolute (26.04) is coming, and nothing exercised it. Add a resolute stemcell line: compile the candidate bosh release on a resolute image, then boot a real director on GCP (bats), an inner director in a container (brats-acceptance), and a backup/restore run (bdrats) against the resolute stemcell. Each job is a copy of its noble twin with the stemcell, the compiled release and the stemcell-OS settings swapped, plus a daily sweeper for the GCP resources bats leaves behind. They are collected in a new "stemcell-resolute" group. Nothing depends on these jobs, so a failing resolute job cannot block a bosh release. bdrats does not build on resolute yet and is expected to be red for now.
1c33e5a to
158f11e
Compare
2 participants
What is this change about?
Add a resolute stemcell line: compile the candidate bosh release on a
resolute image, then boot a real director on GCP (bats), an inner
director in a container (brats-acceptance), and a backup/restore run
(bdrats) against the resolute stemcell. Each job is a copy of its noble
twin with the stemcell, the compiled release and the stemcell-OS
settings swapped, plus a daily sweeper for the GCP resources bats
leaves behind. They are collected in a new "stemcell-resolute" group.
Nothing depends on these jobs, so a failing resolute job cannot block a
bosh release. bdrats does not build on resolute yet and is expected to
be red for now; a comment in the job says so.
What tests have you run against this PR?
It's been flown, jobs are running. It's OK if they go red, that will be useful information.
Does this PR introduce a breaking change?
No