jenkinsci / jenkinsci/workflow-durable-task-step-plugin

[JENKINS-41940] Pipeline stages should be configurable with a weight property, corresponding to the number of executors the stage occupies

Open
#519 20 comments 0 reactions 0 assignees View on GitHub
component:workflow-durable-task-step-plugin imported-jira-issue priority:critical resolution:unresolved
Dominant language
Java
Stars
46
Forks
110
PR merge metrics
No merged PRs in 30d

Description

For Freestyle jobs, the Heavy Job plugin (see https://wiki.jenkins-ci.org/display/JENKINS/Heavy+Job+Plugin) can be used in order to configure the number of executors that a given job occupies. This is necessary in order to avoid CPU oversubscription when a single build consumes multiple HW threads (e.g. in case of "make -jN", "ninja -jN" etc.).

I have done some research and was not able to find a means to specify the number of executors consumed by a Pipeline stage.

Parallel builds are a necessity in case of large C++ builds, and the ability to specify the number of executors is a practical solution that can be used by the scheduler in order to avoid CPU oversubscription on a particular node.

---
Originally reported by gontsharuk, imported from: Pipeline stages should be configurable with a weight property, corresponding to the number of executors the stage occupies


  • assignee: goganchic
  • status: In Review
  • priority: Critical
  • component(s): workflow-durable-task-step-plugin
  • label(s): stalled-pr
  • resolution: Unresolved
  • votes: 33
  • watchers: 34
  • imported: 20251212-090250

Raw content of original issue

For Freestyle jobs, the Heavy Job plugin (see https://wiki.jenkins-ci.org/display/JENKINS/Heavy+Job+Plugin) can be used in order to configure the number of executors that a given job occupies. This is necessary in order to avoid CPU oversubscription when a single build consumes multiple HW threads (e.g. in case of "make -jN", "ninja -jN" etc.).

I have done some research and was not able to find a means to specify the number of executors consumed by a Pipeline stage.

Parallel builds are a necessity in case of large C++ builds, and the ability to specify the number of executors is a practical solution that can be used by the scheduler in order to avoid CPU oversubscription on a particular node.

  • environment: Jenkins 2.45, latest versions of all plugins installed

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.