test: add automated build environment display to RC and production builds.#29390
Conversation
|
CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes. |
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 2b8119e. Configure here.
🔍 Smart E2E Test Selection
click to see 🤖 AI reasoning detailsE2E Test Selection:
None of these changes affect:
Running E2E tests would provide zero validation value for these changes. No performance tests are needed either as no performance-sensitive code paths are touched. Performance Test Selection: |
|




Description
Adds automated build environment display to RC and production builds. Captures actual environment values used during builds (METAMASK_ENVIRONMENT, METAMASK_BUILD_TYPE, API URLs, etc.) and displays them:
Changes:
prod)
Changelog
CHANGELOG entry: null
Related issues
Fixes:
https://consensyssoftware.atlassian.net/browse/MMQA-1108
Manual testing steps
Screenshots/Recordings
Before
After
Pre-merge author checklist
Performance checks (if applicable)
trace()for usage andaddTokenfor an exampleFor performance guidelines and tooling, see the Performance Guide.
Pre-merge reviewer checklist
Note
Medium Risk
Changes CI build workflows and the RC PR-comment pipeline to generate, upload, download, and parse a new
build-env.jsonartifact; misconfiguration could break build jobs or PR comment posting. Risk is limited to CI/reporting paths and is largely non-blocking (continue-on-error/|| true) but still touches release build automation.Overview
Adds generation of a
build-env.jsonfile during CI builds (viascripts/apply-build-config.js --write-build-env) and uploads it as a build artifact for each platform.Updates RC automation to download these artifacts and extends
scripts/build-announceto parse them and include a Build Environment section (env/build type, remote FF mapping, key API URLs/flags) in the RC PR comment, with a fallback “not available” section on extraction failure.Introduces a new
Prod Build Env Notifyworkflow that triggers on successful production workflow runs, downloads thebuild-envartifact, extracts key values withjq, and currently prints a placeholder for a future Slack notification; also ignores localbuild-env.jsonvia.gitignore.Reviewed by Cursor Bugbot for commit 0f0c4b5. Bugbot is set up for automated code reviews on this repo. Configure here.