go plugin: Support `disable-parallel` parameter
Metadata
Current evaluation
Adding disable-parallel support to the Go plugin remains open and low priority, pending a concrete real-world use case or application that fails with parallel builds.
Suggested action: needs triage
Reason: The Status: Needs information label and the author's explicit request for a real-world failing case show that implementation readiness is still blocked by missing evidence. The requested behavior is well understood and the Go plugin currently always passes parallel_build_count to go install -p, but its practical impact remains unclear without a reproducer.
Evaluated by: mr-cal-bot
Issue body
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha |
Impact:
25
Quick Win:
9
Complexity:
20
Confidence:
88
Actionability:
45
|
needs triage | Adding disable-parallel support to the Go plugin remains open and low priority, pending a concrete real-world use case or application that fails with parallel builds. | |
| stealth/space-bunny-alpha |
Impact:
15
Quick Win:
4
Complexity:
15
Confidence:
82
Actionability:
30
|
keep open | Request to add `disable-parallel` part property support to the go plugin. Maintainer-authored, labelled Status: Needs information, explicitly deferred as "extremely low priority until someone shows us a real-world use case". No implementation or comments for 395 days. | |
| qwen/qwen3.6-35b-a3b |
Impact:
30
Quick Win:
13
Complexity:
30
Confidence:
70
Actionability:
60
|
keep open | Add disable-parallel part property support to the go plugin. Low-priority enhancement awaiting a real-world use case. | |
| qwen/qwen3.8-27b |
Impact:
15
Quick Win:
11
Staleness:
85
Complexity:
25
Confidence:
85
Support Request:
10
|
close stale | Go plugin lacks disable-parallel support. Filed by maintainer as low-priority enhancement, labeled Needs information, explicitly awaiting a real-world use case that never arrived in 363 days of zero activity. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
85
Complexity:
30
Confidence:
80
Support Request:
10
|
close stale | Request to add disable-parallel support to the go plugin. Currently unaddressed and awaiting a real-world use case or test scenario from the community. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
85
Complexity:
25
Confidence:
80
Support Request:
0
|
close stale | Enhancement to add disable-parallel support to the go plugin. Labeled needs information, awaiting a real-world use case for testing. No activity in over 10 months. |
Update history
No update history recorded yet.
Related work
-
Related To:
canonical/craft-parts#1167
(confidence 95%)
The issue cites the autotools disable-parallel implementation, merged as commit 7dfd1bf7, as a precedent required for OpenJDK builds.
-
Related To:
craft-parts#1234
(confidence 90%)
A parallel enhancement tracks disable-parallel support for the CMake plugin and is likewise awaiting a real-world use case.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1238 go-use plugin: Support `disable-parallel` parameter | craft-parts | open | Support for disable-parallel in go-use remains open and is explicitly deferred pending a real-world Go project that fails under parallel builds. | |
| #1246 npm plugin: Support `disable-parallel` parameter | craft-parts | open | Add disable-parallel support to the npm plugin. It remains open and low priority, with the maintainer requesting a real-world npm build case before prioritizing implementation. | |
| #1242 make plugin: Support `disable-parallel` parameter | craft-parts | open | Enhancement: make plugin should honor the disable-parallel part property (currently always emits make -j"N"). Filed by a maintainer, labeled Triaged/Enhancement, and explicitly deferred as "extremely low priority" until a real-world non-parallel-build use case is supplied; autotools already has it via PR #1167. | |
| #1232 ant plugin: Support `disable-parallel` parameter | craft-parts | open | Ant plugin support for disable-parallel is unimplemented; the request remains open as Needs information, with maintainers requesting a real-world case that fails under parallel builds. | |
| #1239 gradle plugin: Support `disable-parallel` parameter | craft-parts | open | Feature request: add `disable-parallel` support to the gradle plugin. Maintainer labels it low-priority, 'Needs information', asking for a real-world use case that fails under parallel builds; design (None/False/True) sketched in a comment. | |
| #1250 rust plugin: Support `disable-parallel` parameter | craft-parts | open | Request to honor the documented `disable-parallel` part property in the rust plugin. Maintainer-opened, labeled Needs information, explicitly deprioritized pending a real-world use case; rust_plugin.py still builds with cargo defaults. | |
| #1247 python plugin: Support `disable-parallel` parameter | craft-parts | open | Python plugin support for compiled-wheel parallel control remains unimplemented; maintainers are awaiting a real-world case and resolution of tri-state semantics versus setting CRAFT_PARALLEL_BUILD_COUNT=1. | |
| #1249 qmake plugin: Support `disable-parallel` parameter | craft-parts | open | Enhancement: add disable-parallel support to the qmake plugin. Maintainer-filed, labeled Needs information; explicitly deferred as low priority pending a real-world use case. One of six sibling per-plugin issues (cmake, meson, make, go, rust). | |
| #1243 maven plugin: Support `disable-parallel` parameter | craft-parts | open | Maven plugin support for disable-parallel remains unimplemented; the open enhancement is maintainer-marked Needs information and deliberately low priority pending a real-world failing build. | |
| #1235 dotnet plugin: Support `disable-parallel` parameter | craft-parts | open | Maintainer-filed enhancement: dotnet plugin does not honor the existing `disable-parallel` part property. Labeled Needs information and explicitly deferred as "extremely low priority" pending a real-world use case; no comments in 395 days. |