Skip to content

Limit goreleaser parallel builds to 2 - #955

Merged
dustman9000 merged 1 commit into
openshift:masterfrom
dustman9000:fix-goreleaser-parallelism
Aug 28, 2026
Merged

Limit goreleaser parallel builds to 2#955
dustman9000 merged 1 commit into
openshift:masterfrom
dustman9000:fix-goreleaser-parallelism

Conversation

@dustman9000

@dustman9000 dustman9000 commented Aug 28, 2026

Copy link
Copy Markdown
Member

The v0.64.0 release workflow has failed twice with GitHub's runner receiving a shutdown signal ~11 minutes into goreleaser's cross-compilation phase. By default goreleaser runs all 4 build targets (linux/amd64, linux/arm64, darwin/amd64, darwin/arm64) concurrently, which puts heavy parallel load on the runner.

This caps parallelism at 2 to reduce peak resource usage and avoid triggering runner preemption, while still being faster than fully sequential builds.

Testing

Re-running the release workflow after this merges will validate the fix.

Summary by CodeRabbit

  • Chores
    • Adjusted the release build configuration to use controlled parallelism for osdctl.
    • Existing build environment settings remain unchanged.

GitHub-hosted runners are being killed mid-build with a shutdown signal
when all 4 cross-compilation targets run concurrently. Capping at 2
reduces peak resource usage without making the build excessively long.
@coderabbitai

coderabbitai Bot commented Aug 28, 2026

Copy link
Copy Markdown

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Repository: openshift/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: 7c4d00b7-acc9-4a02-9544-726fbc33ed03

📥 Commits

Reviewing files that changed from the base of the PR and between 190332b and 47adba1.

📒 Files selected for processing (1)
  • .goreleaser.yml

Cache: Disabled due to data retention organization setting

Knowledge base: Disabled due to data retention organization setting


Walkthrough

GoReleaser now limits osdctl build parallelism to 2. Existing build environment settings remain unchanged.

Changes

Build configuration

Layer / File(s) Summary
Parallel build configuration
.goreleaser.yml
GoReleaser sets build parallelism to 2 and retains the existing environment settings.

Estimated code review effort: 1 (Trivial) | ~2 minutes

✨ Finishing Touches 💡 1
🛠️ Fix failing CI checks 💡
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests

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

@openshift-ci

openshift-ci Bot commented Aug 28, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dustman9000

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@dustman9000
dustman9000 merged commit bf52a07 into openshift:master Aug 28, 2026
11 of 17 checks passed
@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Aug 28, 2026
@dustman9000 dustman9000 added the lgtm Indicates that a PR is ready to be merged. label Aug 28, 2026
@fullsend-ai-review

fullsend-ai-review Bot commented Aug 28, 2026

Copy link
Copy Markdown

🤖 Finished Review · ✅ Success · Started 12:47 PM UTC · Completed 12:52 PM UTC

Commit: 47adba1 · View workflow run →

Runtime: claude · Model: opus → claude-opus-4-6 · Effort: high · Cost: $1.59

@fullsend-ai-review

Copy link
Copy Markdown

Review skipped — this PR is already merged.

The /fs-review command only reviews open PRs/MRs.

Posted by fullsend pre-review check

@fullsend-ai-review

Copy link
Copy Markdown

Review skipped — this PR is already merged.

The /fs-review command only reviews open PRs/MRs.

Posted by fullsend post-review check

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant