521f88e159
This PR moves the instructions for configuring CI providers to preserve Next.js's build cache out of the _No Cache Detected_ error message and into ~the _Deployment_~ a new page within the _Advanced Features_ docs.
This change is beneficial because it makes the CI configuration examples visible in the context of other helpful documentation for deploying Next.js.
👉 **Prior to this change, these CI configuration examples didn't show up in the Next.js docs.**
The relocated instructions are now linked on the _No Cache Detected_ error message page.
## Documentation / Examples
- [x] Make sure the linting passes by running `yarn lint`
Co-authored-by: Lee Robinson <me@leerob.io>
Co-authored-by: Steven <steven@ceriously.com>
14 lines
653 B
Markdown
14 lines
653 B
Markdown
# No Cache Detected
|
|
|
|
### Why This Error Occurred
|
|
|
|
A Next.js build was triggered in a continuous integration environment, but no cache was detected.
|
|
|
|
This results in slower builds and can hurt Next.js' persistent caching of client-side bundles across builds.
|
|
|
|
### Possible Ways to Fix It
|
|
|
|
> **Note**: If this is a new project, or being built for the first time in your CI, you can ignore this error.
|
|
> However, you'll want to make sure it doesn't continue to happen and fix it if it does!
|
|
|
|
Follow the instructions in [CI Build Caching](https://nextjs.org/docs/advanced-features/ci-build-caching) to ensure your Next.js cache is persisted between builds.
|