CI: ensure that the correct resource is used when running tasks

[aramprice]

It is important that code-under-test, and tasks-in-use come from the non-CI resource bosh-linux-stemcell-builder and not bosh-stemcells-ci (current naming) so that code executed has satisfied the expected pass constraints.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: 3bdc8cc0-3edc-4710-b58b-602085bf9fa4

📥 Commits

Reviewing files that changed from the base of the PR and between 9348552 and 0dedb6a.

📒 Files selected for processing (8)

• ci/tasks/build-docker-args.sh
• ci/tasks/build-release-metadata.sh
• ci/tasks/build.sh
• ci/tasks/bump-bosh-agent.sh
• ci/tasks/bump-bosh-blobstore-cli.sh
• ci/tasks/commit-build-time.sh
• ci/tasks/os-images/build.sh
• ci/tasks/test-unit.sh

---

Walkthrough

This pull request updates multiple CI task scripts to reference the bosh-linux-stemcell-builder repository located under a parent directory structure instead of the repository root. Changes include adjusting working directory paths for build, test, and artifact handling operations; updating file lookup paths for configuration files like .ruby-version, bosh-agent-version, and metadata; and modifying git clone sources and destination directories. The modifications affect scripts for Docker argument generation, release metadata building, stemcell compilation, dependency updates, version management, and unit testing.

Suggested reviewers

• mkocher
• ystros
• neddp

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately summarizes the main change: updating CI tasks to use the correct resource path (bosh-linux-stemcell-builder) instead of the current naming (bosh-stemcells-ci).
Description check	✅ Passed	The description is directly related to the changeset, explaining that code-under-test and tasks must come from bosh-linux-stemcell-builder to satisfy expected pass constraints.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ 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 fix-relative-path-access

---

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

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}