Skip to content

Doc/build cache nano pico warning#954

Open
Juju-archy wants to merge 1 commit into
mainfrom
doc/build-cache-nano-pico-warning
Open

Doc/build cache nano pico warning#954
Juju-archy wants to merge 1 commit into
mainfrom
doc/build-cache-nano-pico-warning

Conversation

@Juju-archy
Copy link
Copy Markdown
Contributor

📝 What does this PR do?

Adds a notice in the CC_DISABLE_BUILD_CACHE_UPLOAD callouts to warn that Nano and Pico plans always use a dedicated build, which requires the build cache. Setting this environment variable on these plans causes deployment to fail.

The notice has been added in two places:

  • doc/develop/build-hooks.md (Post Build hook section)
  • doc/administrate/apps-management.md (Start/Stop/Restart section)

🔗 Related Issue (if applicable)

  • Closes #
  • Related to #

🧪 Type of Change

  • ⚠️ Bug fix
  • 📅 Changelog update
  • 📚 Documentation update
  • ✨ New content/feature
  • 🔧 Technical/maintenance

✅ Quick Checklist


👥 Reviewers

@CleverCloud/reviewers


📋 For major changes (click to expand)

Additional testing performed

Describe any specific testing done for complex changes

Screenshots

Add screenshots for visual/layout changes

Breaking changes

List any breaking changes or migration notes

@github-actions
Copy link
Copy Markdown

github-actions Bot commented May 19, 2026

✅ Review app deployed

Check how your changes look like!

ℹ️ Name 🔗 Infos & links
🌱 Latest deployed commit ee8ba77
👁️ Preview https://documentation-PR-954.cleverapps.io/developers

@Juju-archy Juju-archy requested a review from Kirbeerus May 19, 2026 09:55
@davlgd
Copy link
Copy Markdown
Collaborator

davlgd commented May 19, 2026

@Juju-archy can you rebase ?

@Juju-archy Juju-archy force-pushed the doc/build-cache-nano-pico-warning branch from b592db5 to fbb2745 Compare May 21, 2026 14:06
Setting this variable on Nano/Pico plans causes an infinite build loop
as these plans always use a dedicated build requiring the build cache.
@Juju-archy Juju-archy force-pushed the doc/build-cache-nano-pico-warning branch from fbb2745 to ee8ba77 Compare May 21, 2026 14:12
Copy link
Copy Markdown
Collaborator

@davlgd davlgd 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 this. It's more a bug we'll fix, but LGTM to document it until it is.

Also please rework the commit message.

Comment on lines 32 to +34
If you set [`CC_DISABLE_BUILD_CACHE_UPLOAD`](/doc/develop/env-variables/#settings-you-can-define-using-environment-variables) environment variable to `true`, the cache archive won't be created nor uploaded.

Nano and Pico plans always use a dedicated build, which requires the build cache. Setting this environment variable on these plans causes deployment to fail.
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Suggested change
If you set [`CC_DISABLE_BUILD_CACHE_UPLOAD`](/doc/develop/env-variables/#settings-you-can-define-using-environment-variables) environment variable to `true`, the cache archive won't be created nor uploaded.
Nano and Pico plans always use a dedicated build, which requires the build cache. Setting this environment variable on these plans causes deployment to fail.
If you set [`CC_DISABLE_BUILD_CACHE_UPLOAD`](/doc/develop/env-variables/#settings-you-can-define-using-environment-variables) environment variable to `true`, the cache archive won't be created nor uploaded. Don't use it with `nano` and `pico` plans which always use a build instance to create the build cache.

Comment on lines 101 to +103
If you set [\`CC_DISABLE_BUILD_CACHE_UPLOAD\`](/doc/develop/env-variables/#settings-you-can-define-using-environment-variables) environment variable to `true`, the cache archive won't be created nor uploaded.

Nano and Pico plans always use a dedicated build, which requires the build cache. Setting this environment variable on these plans causes deployment to fail.
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Suggested change
If you set [\`CC_DISABLE_BUILD_CACHE_UPLOAD\`](/doc/develop/env-variables/#settings-you-can-define-using-environment-variables) environment variable to `true`, the cache archive won't be created nor uploaded.
Nano and Pico plans always use a dedicated build, which requires the build cache. Setting this environment variable on these plans causes deployment to fail.
If you set [`CC_DISABLE_BUILD_CACHE_UPLOAD`](/doc/develop/env-variables/#settings-you-can-define-using-environment-variables) environment variable to `true`, the cache archive won't be created nor uploaded. Don't use it with `nano` and `pico` plans which always use a build instance to create the build cache.

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