Windows build fails: R2 private bucket dependency missing from contributor setup docs

[JEEVANANTHAMV]

Issue Type

Agent Issue

Operating System

Windows

Description of the bug

When i try to build after changes made in BrowserOS I faced a major challenge in yaml file everyehere R2 Dependency how can i build or will you provide those files required seperately

Steps to Reproduce

Just folow readme the files for windows build is missing

Screenshots / Videos

No response

BrowserOS Version

No response

Additional Context

No response

[shadowfax92]

Hey Jeevanantham V (@JEEVANANTHAMV) — thanks for flagging this! The R2 bucket references are for internal build infra and aren't needed for a local build. The README should document how to skip or stub those — added this to our backlog to improve the contributor build docs.

[JEEVANANTHAMV]

`
def r2_account_id(self) -> Optional[str]:
return os.environ.get("R2_ACCOUNT_ID")

def r2_access_key_id(self) -> Optional[str]:
return os.environ.get("R2_ACCESS_KEY_ID")

def r2_secret_access_key(self) -> Optional[str]:
return os.environ.get("R2_SECRET_ACCESS_KEY")

def has_r2_config(self) -> bool:
return bool(
self.r2_account_id and self.r2_access_key_id and self.r2_secret_access_key
)
`

download_resources.yaml defines 5 R2 download operations:

• BrowserOS server resources (Linux/Windows/macOS, arm64/x64)
• All downloads are mandatory for the build

Build Configuration (release.windows.yaml, debug.yaml):

• Explicit module execution order: download_resources runs BEFORE other modules
• If R2 download fails, entire build fails

[shadowfax92]

Hey Jeevanantham V (@JEEVANANTHAMV) — thanks for digging into this further. This confirms the blocker: download_resources.yaml runs first in the build pipeline, the R2 downloads are mandatory (not optional), and the has_r2_config guard doesn't gate anything in the actual build flow.

This is a real contributor onboarding issue — the R2 credentials are internal build infra that open-source contributors can't access, yet the build fails hard without them. The fix should either: (a) make the download step conditional and provide stubs/mirrors for the resources that external contributors can use, or (b) document clearly in the README that contributors need to skip or mock the resource download step and explain how. We'll escalate this to the team — it's blocking anyone who wants to build from source.