feat(deployments): expose native build server option in build settings

[myftija]

Adds a build setting about using our build server for remote builds.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 0002859

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[coderabbitai]

Walkthrough

This pull request adds a new "Use native build server" option to the build settings feature. The implementation spans two files: updating the build settings schema to include an optional boolean field, and extending the build settings form component to add a checkbox UI element with corresponding form state, validation, and submission handling for the new field.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

• The schema addition is straightforward, but the route file contains multiple interconnected changes (UI component, form state, validation schema transformation, submission handling)
• Key areas requiring careful attention:
  • Verify the string "on" to boolean transformation in the validation schema functions as intended
  • Confirm that useNativeBuildServer is properly propagated through the form submission to the action handler and service call
  • Ensure change detection logic correctly identifies when useNativeBuildServer toggles
  • Validate that error handling and helper text for the new field align with existing patterns in the form

Pre-merge checks and finishing touches

❌ Failed checks (2 warnings)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The PR description is incomplete. It lacks required sections from the template including Testing, Changelog, Screenshots, and the Checklist, providing only a minimal overview.	Complete all required template sections: add Testing steps, a Changelog entry describing the change, any Screenshots, and complete the Checklist items.
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	You can run @coderabbitai generate docstrings to improve docstring coverage.

✅ Passed checks (1 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and specifically describes the main change: exposing a native build server option in build settings, which directly aligns with the changeset's primary objective.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch native-remote-builds

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 19fa669 and 965901c.

📒 Files selected for processing (2)

• apps/webapp/app/routes/_app.orgs.$organizationSlug.projects.$projectParam.env.$envParam.settings/route.tsx (5 hunks)
• apps/webapp/app/v3/buildSettings.ts (1 hunks)

🧰 Additional context used

🧠 Learnings (1)

📚 Learning: 2025-08-14T18:35:44.370Z

Learnt from: nicktrn
Repo: triggerdotdev/trigger.dev PR: 2390
File: apps/webapp/app/env.server.ts:764-765
Timestamp: 2025-08-14T18:35:44.370Z
Learning: The BoolEnv helper in apps/webapp/app/utils/boolEnv.ts uses z.preprocess with inconsistent default value types across the codebase - some usages pass boolean defaults (correct) while others pass string defaults (incorrect), leading to type confusion. The helper should enforce boolean-only defaults or have clearer documentation.

Applied to files:

• apps/webapp/app/v3/buildSettings.ts

🧬 Code graph analysis (1)

apps/webapp/app/routes/_app.orgs.$organizationSlug.projects.$projectParam.env.$envParam.settings/route.tsx (2)

apps/webapp/app/components/primitives/Checkbox.tsx (1)

• CheckboxWithLabel (68-177)

apps/webapp/app/components/primitives/Hint.tsx (1)

• Hint (3-9)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (23)

• GitHub Check: units / internal / 🧪 Unit Tests: Internal (8, 8)
• GitHub Check: units / internal / 🧪 Unit Tests: Internal (7, 8)
• GitHub Check: units / internal / 🧪 Unit Tests: Internal (6, 8)
• GitHub Check: units / internal / 🧪 Unit Tests: Internal (4, 8)
• GitHub Check: units / internal / 🧪 Unit Tests: Internal (3, 8)
• GitHub Check: units / internal / 🧪 Unit Tests: Internal (2, 8)
• GitHub Check: units / internal / 🧪 Unit Tests: Internal (5, 8)
• GitHub Check: units / webapp / 🧪 Unit Tests: Webapp (8, 8)
• GitHub Check: units / webapp / 🧪 Unit Tests: Webapp (7, 8)
• GitHub Check: units / webapp / 🧪 Unit Tests: Webapp (1, 8)
• GitHub Check: units / internal / 🧪 Unit Tests: Internal (1, 8)
• GitHub Check: units / webapp / 🧪 Unit Tests: Webapp (4, 8)
• GitHub Check: units / webapp / 🧪 Unit Tests: Webapp (6, 8)
• GitHub Check: units / webapp / 🧪 Unit Tests: Webapp (3, 8)
• GitHub Check: units / webapp / 🧪 Unit Tests: Webapp (2, 8)
• GitHub Check: units / webapp / 🧪 Unit Tests: Webapp (5, 8)
• GitHub Check: units / packages / 🧪 Unit Tests: Packages (1, 1)
• GitHub Check: e2e / 🧪 CLI v3 tests (windows-latest - npm)
• GitHub Check: e2e / 🧪 CLI v3 tests (ubuntu-latest - pnpm)
• GitHub Check: e2e / 🧪 CLI v3 tests (windows-latest - pnpm)
• GitHub Check: e2e / 🧪 CLI v3 tests (ubuntu-latest - npm)
• GitHub Check: typecheck / typecheck
• GitHub Check: Analyze (javascript-typescript)

🔇 Additional comments (6)

apps/webapp/app/v3/buildSettings.ts (1)

7-7: LGTM!

The optional boolean field follows the existing schema pattern and correctly types the new build server setting.

apps/webapp/app/routes/_app.orgs.$organizationSlug.projects.$projectParam.env.$envParam.settings/route.tsx (5)

33-33: LGTM!

The import is correctly added to support the new checkbox UI component.

---

184-187: LGTM!

The string-to-boolean transform correctly handles checkbox input. HTML checkboxes send "on" when checked and omit the field when unchecked, so the val === "on" transform appropriately produces true or false.

---

415-416: LGTM!

The field is correctly extracted from the submission and passed to the service. Unlike the string fields, the boolean value doesn't need conversion to undefined since false is a meaningful value.

Also applies to: 422-422

---

1145-1145: LGTM!

The initial state correctly defaults to false when the setting is undefined, treating the absence of the setting as "disabled".

---

1152-1153: LGTM!

Change detection for the new field is implemented correctly and consistently with the field initialization.