Skip to content

Conversation

@mikemccracken
Copy link
Contributor

hacking.md told lies about setting CLONE_D and how to use it.

This actually adds the variable.

What type of PR is this?

documentation

What does this PR do / Why do we need it:

It fixes lies / We shouldn't lie

If an issue # is not available please add repro steps and logs showing the issue:

  1. look at hacking.md
  2. try the suggestion for running make docker-clone with CLONE_D
  3. observe that CLONE_D is undisturbed

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@codecov
Copy link

codecov bot commented Dec 3, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 60.92%. Comparing base (ad24357) to head (c3bc3fb).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #745      +/-   ##
==========================================
+ Coverage   51.67%   60.92%   +9.25%     
==========================================
  Files          59       57       -2     
  Lines        6491     5049    -1442     
==========================================
- Hits         3354     3076     -278     
+ Misses       2489     1323    -1166     
- Partials      648      650       +2     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@raharper
Copy link
Contributor

raharper commented Dec 3, 2025

Can you confirm this is needed? The github workflow uses things like this;

.github/workflows/build.yaml:          make docker-clone "STACKER_DOCKER_BASE=docker://ghcr.io/project-stacker/" CLONE_D="$PWD/.build/oci-clone"
.github/workflows/coverage.yaml:          make docker-clone "STACKER_DOCKER_BASE=docker://ghcr.io/project-stacker/" CLONE_D="$PWD/.build/oci-clone"

Why do those work without your change?

@mikemccracken
Copy link
Contributor Author

Can you confirm this is needed? The github workflow uses things like this;

.github/workflows/build.yaml:          make docker-clone "STACKER_DOCKER_BASE=docker://ghcr.io/project-stacker/" CLONE_D="$PWD/.build/oci-clone"
.github/workflows/coverage.yaml:          make docker-clone "STACKER_DOCKER_BASE=docker://ghcr.io/project-stacker/" CLONE_D="$PWD/.build/oci-clone"

Why do those work without your change?

Those work because the value they send for CLONE_D happens to be the same as the hardcoded value in the Makefile:

232   ./tools/oci-copy "$(BUILD_D)/oci-clone" $(STACKER_BUILD_IMAGES)

$(BUILD_D)/oci-clone is .build/oci-clone, so it doesn't matter that it ignores CLONE_D, until you try to use a different directory (say, one outside your source tree so you can keep the tree clean)

Copy link
Contributor

@raharper raharper left a comment

Choose a reason for hiding this comment

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

Thanks for cleanup here.

hacking.md told lies about setting CLONE_D and how to use it.

This actually adds the variable.

Signed-off-by: Michael McCracken <[email protected]>
@mikemccracken mikemccracken force-pushed the 2025.12.03/main/missing-clone-d branch from 4b8ec1f to c3bc3fb Compare December 11, 2025 20:16
@mikemccracken mikemccracken merged commit 6bdaf52 into project-stacker:main Dec 11, 2025
4 of 15 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants