Skip to content

Clarify build cache troubleshooting #1162

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
radiantjade wants to merge 1 commit into from
Closed

Clarify build cache troubleshooting #1162

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions content/docs/builds/build-configuration.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -123,6 +123,12 @@ in your service:
NO_CACHE=1
```

This forces Railway to rebuild layers instead of reusing cached build output.
It does not change which repository, branch, root directory, or Dockerfile is
used for the deployment. If a build appears to use stale or unexpected files,
also check the service's linked repository, branch, [root directory](#set-the-root-directory),
Dockerfile path, and watch paths before redeploying.

## Why isn't my build using cache?

Since Railway's build system scales up and down in response to demand, cache hit
Expand Down
Loading