Skip to content

CI: Do the static build in a separate job#419

Merged
edolstra merged 1 commit intomainfrom
static-job
Apr 8, 2026
Merged

CI: Do the static build in a separate job#419
edolstra merged 1 commit intomainfrom
static-job

Conversation

@edolstra
Copy link
Copy Markdown
Collaborator

@edolstra edolstra commented Apr 8, 2026

Motivation

Context

Summary by CodeRabbit

  • Chores
    • Optimized CI/CD build workflow by restructuring build processes for improved efficiency.

@coderabbitai
Copy link
Copy Markdown

coderabbitai bot commented Apr 8, 2026

📝 Walkthrough

Walkthrough

The pull request refactors the GitHub Actions build workflow by extracting the nix-cli-static build into a separate, independently-conditioned job. The original build job no longer performs this static build; instead, a new build_static job handles it with its own conditional logic and runner configuration.

Changes

Cohort / File(s) Summary
Build Workflow Reorganization
.github/workflows/build.yml
Removed nix-cli-static build step from build job and created a new build_static job with conditional execution. The test job continues to depend only on build.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Poem

🐰 The static build now hops alone,
In its own job, separately shown,
While builders wait and testers cheer—
A cleaner workflow, crystal clear! ✨

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly and concisely describes the main change: moving the static build from the existing build job into a separate CI job, which aligns with the actual modifications shown in the file summary.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch static-job

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

@github-actions
Copy link
Copy Markdown

github-actions bot commented Apr 8, 2026

@github-actions github-actions bot temporarily deployed to pull request April 8, 2026 16:25 Inactive
Copy link
Copy Markdown

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)
.github/workflows/build.yml (1)

243-250: ⚠️ Potential issue | 🟠 Major

build_static is not included in the success job's dependencies.

The success job acts as the workflow status gate, but build_static is missing from its needs list. This means if the static build fails, the overall workflow can still report success.

If the static build should be required for CI to pass, add it to the needs list:

🔧 Proposed fix
   success:
     needs:
       - build
+      - build_static
       - test
       - vm_tests_smoke
       - vm_tests_all
       - flake_regressions
       - manual
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In @.github/workflows/build.yml around lines 243 - 250, The workflow's "success"
job is missing the "build_static" dependency in its needs list, so add
"build_static" to the array under the success job's needs (the same place where
"build", "test", "vm_tests_smoke", "vm_tests_all", "flake_regressions", and
"manual" are listed) so that the "success" job will wait for the build_static
job to complete and fail the workflow if the static build fails.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Outside diff comments:
In @.github/workflows/build.yml:
- Around line 243-250: The workflow's "success" job is missing the
"build_static" dependency in its needs list, so add "build_static" to the array
under the success job's needs (the same place where "build", "test",
"vm_tests_smoke", "vm_tests_all", "flake_regressions", and "manual" are listed)
so that the "success" job will wait for the build_static job to complete and
fail the workflow if the static build fails.

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 71579baa-23dc-4b05-9143-5b47520f7191

📥 Commits

Reviewing files that changed from the base of the PR and between e9b4735 and 04657d1.

📒 Files selected for processing (1)
  • .github/workflows/build.yml

@edolstra edolstra enabled auto-merge April 8, 2026 16:53
@edolstra edolstra added this pull request to the merge queue Apr 8, 2026
Merged via the queue into main with commit 0b5c51a Apr 8, 2026
31 checks passed
@edolstra edolstra deleted the static-job branch April 8, 2026 17:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants