Make buildID persistent for multiarch build #2709
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description and Related Issue(s)
This PR implements custom build ID generation in our Next.js configuration.
This should resolve the issue of having different buildIDs in Docker images built for different architectures under the same tag. That inconsistency has prevented us from scaling the frontend across both amd64 and arm64 nodes.
Proposed Changes
Support environment-based build IDs via NEXT_BUILD_ID
Provide a fallback unique ID when no env var is specified (using timestamp + random string)
Breaking or Incompatible Changes
Additional Information
Checklist for PR author