Skip to content

CI: Use precompiled Director release - #341

Draft
neddp wants to merge 5 commits into
masterfrom
speed-up-bats-director
Draft

CI: Use precompiled Director release#341
neddp wants to merge 5 commits into
masterfrom
speed-up-bats-director

Conversation

@neddp

@neddp neddp commented Aug 28, 2026

Copy link
Copy Markdown
Member

No description provided.

@coderabbitai

coderabbitai Bot commented Aug 28, 2026

Copy link
Copy Markdown

Important

Draft PR not reviewed

Draft PRs are not automatically reviewed by default.

  • Trigger a manual review

To automatically review draft PRs, update your CodeRabbit configuration:

reviews:
  auto_review:
    drafts: true

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.

@neddp neddp changed the title CI: Use compiled Director release CI: Use precompiled Director release Aug 28, 2026
@neddp
neddp force-pushed the speed-up-bats-director branch 5 times, most recently from 53cae42 to 5a1c8cc Compare August 31, 2026 10:43
neddp added 3 commits August 31, 2026 14:38
The BATS director previously deployed on a jammy stemcell with the bosh
and bpm releases pulled from source (via misc/source-releases/bosh.yml
plus a file:// override), so create-env recompiled every director
package on the VM (~25 min).

Let the director use bosh-deployment's compiled bosh/bpm releases
instead. These are built for noble, and bosh-deployment/openstack/cpi.yml
already pins a matching noble stemcell at /resource_pools/name=vms/
stemcell, kept in lockstep with the compiled releases by bosh-deployment
CI. So:

- Drop the source-releases/bosh.yml overlay and the file:// bosh
  override; bosh and bpm now resolve to the compiled noble URLs in
  bosh-deployment/bosh.yml.
- Narrow deployment-configuration.yml to patch only cloud_properties,
  letting cpi.yml's noble stemcell stand as the director host OS.
- Drop the now-unused stemcell-director input/get, the source-release
  fallback (prepare_bosh_release / find_bosh_compiled_release, which
  queried a bucket that no longer exists), and the bosh-release input.

The stemcell under test (BATS/lifecycle) stays jammy. The director host
OS tracks bosh-deployment's compiled release automatically, so there is
no stemcell version to pin here.
bosh-deployment/openstack/cpi.yml wires the Ruby openstack_cpi job,
whose openstack-ruby-3.1 package compiles at create-env time (~9 min
on the worker plus ~5 min on the director VM).

Add use-golang-cpi.yml, applied after cpi.yml, to point the director's
cpi_job, cloud_provider template, and bosh instance-group job at
openstack_cpi_golang instead. The Go job takes the same openstack.*
properties and only needs the golang-1-linux package, so create-env no
longer builds the Ruby runtime. BATS now exercises the Go CPI
end-to-end against DevStack.
The bosh-release resource_type (dpb587/bosh-release-resource) is not
referenced by any resource, and teardown-director.{yml,sh} is not
referenced by the pipeline. Remove them.
@neddp
neddp force-pushed the speed-up-bats-director branch from 5a1c8cc to b0ec870 Compare August 31, 2026 11:39
neddp added 2 commits August 31, 2026 14:41
Drop 'set -x', which dumped the whole command trace before BATS — including
the jumpbox SSH key, admin password, and CA cert. Also fix shellcheck:
split the secret exports (SC2155), quote expansions (SC2086), read
bats_rspec_tags into an array, and annotate the runtime-exported vars.
@neddp
neddp force-pushed the speed-up-bats-director branch from b0ec870 to cf8e35f Compare August 31, 2026 11:44
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.

1 participant