← Back to issue list

dotnet plugin: Support `disable-parallel` parameter

View original Github issue

Metadata

Project
craft-parts
Number
#1235
Type
issue
State
open
Author
lengau
Labels
Type: Enhancement Status: Needs information
Created
Updated
Closed
—

Current evaluation

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.

Suggested action: keep open

Reason: The request is valid and not obsolete: `disable_parallel` is a real PartSpec field (craft_parts/parts.py:248) and a documented build-step key (docs/common/craft-parts/reference/part_properties.rst:94), and DotnetPluginProperties (craft_parts/plugins/dotnet_plugin.py) simply omits it. Only autotools implements it (autotools_plugin.py:49,133 via PR #1167), so this stays a valid open enhancement. However, the author himself writes it is "extremely low priority until someone shows us a real-world use case", the "Status: Needs information" label reflects that unresolved ask, and no use case has arrived in 395 days with zero comments — hence modest impact and only mid actionability, since the exact dotnet/MSBuild flag to use is unspecified (dotnet_plugin.py's `dotnet build` never references parallel_build_count at all).

Evaluated by: mr-cal-bot

Impact: 18 Quick Win: 7 Complexity: 30 Confidence: 85 Actionability: 55

Issue body

### What needs to get done Support the [disable-parallel](https://canonical-craft-parts.readthedocs-hosted.com/latest/common/craft-parts/reference/part_properties/#disable-parallel) part property in the dotnet plugin. ### Why it needs to get done All of our plugins should theoretically support this. In practice though, this is extremely low priority until someone shows us a real-world use case for it. If someone can bring us a real-world use case that we can test against (especially a case of "this application simply does not build with parallel"), that would be ideal. The [autotools plugin](https://github.com/canonical/craft-parts/pull/1167) required this for OpenJDK builds, for example.

Evaluation history

Date Model Scores Action Summary
stealth/space-bunny-alpha
Impact: 18
Quick Win: 7
Complexity: 30
Confidence: 85
Actionability: 55
keep 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.
qwen/qwen3.6-35b-a3b
Impact: 30
Quick Win: 11
Complexity: 40
Confidence: 80
Actionability: 60
keep open Request to add disable-parallel part property to the dotnet plugin. Labeled Needs information; maintainer marked it low priority pending a real-world use case, which has not been provided in 384 days.
qwen/qwen3.8-27b
Impact: 15
Quick Win: 10
Staleness: 80
Complexity: 30
Confidence: 75
Support Request: 5
close stale Request to add the disable-parallel part property to the dotnet plugin. Labeled Needs information; the maintainer marked it extremely low priority pending a real-world use case, which has not been provided in 363 days.
qwen/qwen3.6-35b-a3b
Staleness: 78
Complexity: 15
Confidence: 75
Support Request: 0
keep open Enhancement request to add disable-parallel parameter support to the dotnet plugin. Labeled needs information, inactive for over 10 months with no use cases provided.
qwen3.6-35b-a3b-mtp-q6
Staleness: 85
Complexity: 30
Confidence: 80
Support Request: 10
close stale Enhancement request to add disable-parallel parameter support to the dotnet plugin. Open for 309 days with no maintainer response or comments, awaiting a real-world use case to justify implementation.

Update history

No update history recorded yet.

Related work

  • Related To: canonical/craft-parts#1167 (confidence 92%)

    Cited in the issue body as the existing reference implementation (autotools) that needed disable-parallel for OpenJDK builds; pattern to follow is autotools_plugin.py:133.

  • Related To: craft-parts#1236 (confidence 88%)

    Same request for the dotnet (v2) plugin; one of ~9 sibling disable-parallel issues, all open and all awaiting a use case.

  • Related To: craft-parts#1242 (confidence 80%)

    make plugin issue with the identical code pattern (unconditional -j"N") and same maintainer deferral rationale.

Related issues

Issue Project State Summary Similarity
#1236 dotnet (v2) plugin: Support `disable-parallel` parameter craft-parts open dotnet v2 ignores disable-parallel, but maintainers labeled it Needs information and requested a real-world failure case; none was provided in 395 days.
90%
#1251 scons plugin: Support `disable-parallel` parameter craft-parts open Maintainer-filed enhancement (lengau) asking the scons plugin to honour the disable-parallel part property, like autotools; explicitly deferred as "extremely low priority" pending a real-world use case. Labeled Needs information, no comments.
79%
#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.
79%
#1244 maven-use plugin: Support `disable-parallel` parameter craft-parts open Maintainer-filed request to add the disable-parallel part property to the maven-use plugin. Marked Enhancement/Needs information; maintainer states it is extremely low priority pending a real-world use case, none supplied in ~395 days.
77%
#1241 jlink plugin: Support `disable-parallel` parameter craft-parts open Maintainer-filed, triaged enhancement to honour the disable-parallel part property in the jlink plugin. Labeled Needs information; jlink never uses parallel_build_count, so the property would likely be a no-op. Open 395 days, no comments.
77%
#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.
76%
#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).
76%
#1245 meson plugin: Support `disable-parallel` parameter craft-parts open Enhancement request to add `disable-parallel` support to the meson plugin. Open, labelled Enhancement/Needs information by maintainer lengau; explicitly deprioritized until someone provides a real-world use case to test against.
76%
#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.
76%
#1237 go plugin: Support `disable-parallel` parameter craft-parts open 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.
76%