Skip to content

Add resolute test jobs - #522

Merged
mkocher merged 2 commits into
developfrom
add-resolute-test-jobs
Aug 11, 2026
Merged

Add resolute test jobs#522
mkocher merged 2 commits into
developfrom
add-resolute-test-jobs

Conversation

@mkocher

@mkocher mkocher commented Aug 7, 2026

Copy link
Copy Markdown
Member

Add test-resolute-gcp, test-resolute-warden and test-resolute-docker as clones of the noble test jobs, differing only in the stemcell resource and the DIRECTOR_OPS_FILES / STEMCELL_OS params introduced earlier.

These jobs ship without passed: constraints and are deliberately left out of promote for now. Garden does not yet compile on Resolute, so the warden job will be paused for now.

These have been flown and are starting to run now.

@coderabbitai

coderabbitai Bot commented Aug 7, 2026

Copy link
Copy Markdown

Review Change Stack

Walkthrough

Added Ubuntu Resolute stemcell resources, release-compilation jobs, stemcell-update jobs, and GCP, Warden, and Docker test jobs. Added a complete NATS deployment manifest. Updated Docker, GCP, and Warden test tasks to use NATS instead of Zookeeper. The GCP task now installs the DNS runtime configuration. Removed the integration-test script.

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly identifies the main change: adding Resolute test jobs.
Description check ✅ Passed The description explains the Resolute test jobs, configuration differences, promotion status, Warden limitation, and rollout state.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches
📝 Generate docstrings
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch add-resolute-test-jobs

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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`:
- Around line 235-255: Add paused: true to the test-resolute-warden pipeline job
definition so Concourse does not schedule this known-failing Resolute test job
while preserving the existing plan and configuration.
🪄 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: d1ef4258-da87-45a5-ae3e-9edcea49b6ba

📥 Commits

Reviewing files that changed from the base of the PR and between 0d84908 and bca311f.

📒 Files selected for processing (1)
  • ci/pipeline.yml

Comment thread ci/pipeline.yml
@github-project-automation github-project-automation Bot moved this from Inbox to Waiting for Changes | Open for Contribution in Foundational Infrastructure Working Group Aug 7, 2026
Add test-resolute-gcp, test-resolute-warden and test-resolute-docker as
clones of the noble test jobs, differing only in the stemcell resource and
the DIRECTOR_OPS_FILES / STEMCELL_OS params introduced earlier.

For GCP, DIRECTOR_OPS_FILES goes on the bbl-up step, where it drives
generation of the create/delete-director override scripts and the bbl ops
drift guard; STEMCELL_OS goes on test-gcp, which only uploads the stemcell
and deploys zookeeper. The warden and docker jobs stand up the director and
deploy in a single task, so both params go on that step. In every case
misc/use-compiled-resolute-releases.yml is applied last.

Resolute is early in its release series, so these jobs ship without passed:
constraints and are deliberately left out of promote, which still gates on
test-smoke and the three noble jobs only.
zookeeper-release is unsupported. Add ci/assets/nats.yml, a minimal
TLS-only nats deployment modeled on cf-deployment, and point the docker,
gcp, and warden test tasks at it.

test-gcp.sh also re-applies runtime-configs/dns.yml under bbl's "dns"
runtime config name. bbl builds that config from a vendored
bosh-deployment predating ubuntu-resolute, so bosh-dns went uninstalled
and the deployment's DNS aliases would not resolve.

Drop tests/run.sh: unreferenced since 2021, requires local VirtualBox,
superseded by virtualbox/create-env.sh and the CI test tasks.
@mkocher
mkocher force-pushed the add-resolute-test-jobs branch from bca311f to 4593b6b Compare August 11, 2026 02:42
@github-project-automation github-project-automation Bot moved this from Waiting for Changes | Open for Contribution to Pending Merge | Prioritized in Foundational Infrastructure Working Group Aug 11, 2026

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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/tasks/test-docker.sh`:
- Around line 36-46: Update the cleanup sequence in ci/tasks/test-docker.sh
lines 36-46 and ci/tasks/test-warden.sh lines 33-43: after recreating the nats
deployment, run bosh -n -d nats delete-deployment, then run the global bosh -n
clean-up --all command instead of cleaning up while the deployment remains
active.
🪄 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: 11db4c67-5684-403a-9f76-a9645da2904b

📥 Commits

Reviewing files that changed from the base of the PR and between bca311f and 4593b6b.

📒 Files selected for processing (5)
  • ci/assets/nats.yml
  • ci/tasks/test-docker.sh
  • ci/tasks/test-gcp.sh
  • ci/tasks/test-warden.sh
  • tests/run.sh
💤 Files with no reviewable changes (1)
  • tests/run.sh

Comment thread ci/tasks/test-docker.sh
@github-project-automation github-project-automation Bot moved this from Pending Merge | Prioritized to Waiting for Changes | Open for Contribution in Foundational Infrastructure Working Group Aug 11, 2026
@github-project-automation github-project-automation Bot moved this from Waiting for Changes | Open for Contribution to Pending Merge | Prioritized in Foundational Infrastructure Working Group Aug 11, 2026
@mkocher
mkocher merged commit 0ea181d into develop Aug 11, 2026
2 checks passed
@mkocher
mkocher deleted the add-resolute-test-jobs branch August 11, 2026 05:07
@github-project-automation github-project-automation Bot moved this from Pending Merge | Prioritized to Done in Foundational Infrastructure Working Group Aug 11, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Development

Successfully merging this pull request may close these issues.

2 participants