Details
-
Bug
-
Status: Open (View Workflow)
-
Major
-
Resolution: Unresolved
Description
When trying to manually build a Multi-configuration project with parameters the build never gets past the Queue phase. Attempted to create a 2nd project that will trigger the multi-configuration project on a different node from master and same result. If parameters are removed the build will run on all nodes selected without issue.
Job Config:
Checked -> Parameterized
Name: HOST_NAME
Default Nodes: master
Possible Nodes: [Selected Nodes]
Allow multi node selection concurrent builds
Node eligibility: Ignore Offline Nodes
Checked -> Execute concurrent builds if necessary
No Advanced Project Options (Restrict, Quiet, Retry, Blocking, Custom)
Source Code Management: GIT
Configuration Matrix
Slaves ->
Name: label
Node/Label: Individual Nodes (Valid Nodes selected)
Build:
Powershell Scripts
Post Build:
Editable Email Notification (Default Settings)
Queue Message:
#4 (pending—Waiting for next available executor on [Node Name]) [NodeParameterValue: HOST_NAME=[Node Name]
All the Executors are open and other jobs can be ran on the selected Nodes.
Attachments
Issue Links
- is related to
-
-
- Resolved
-
Activity
Justin Huot
created issue -
ikedam
made changes -
| Field | Original Value | New Value |
|---|---|---|
| Component/s | parameterized-trigger [ 15592 ] |
The issue is in LabelParameterValue.java:112
The code sets the warning text instead of the label value, hence the job won't be ever executed due to the non-existent label. Such issue appears if a NodeEligibility extension returns false for the selected node.
if (StringUtils.isBlank(getLabel()))
Unknown macro: { // these artificial label will cause the job to stay in the queue and the user will see this label setLabel(Messages.LabelParameterValue_triggerWithoutValidOnlineNode(StringUtils.join(labels, ','))); }
Reproduction steps:
1) Disable a node
2) Run job on the node by specifiing the NodeLabelParameter
– The job should hang in queue
3) Enable the node
Expected result: node takes the job
Actual result: job infinitely hangs, because it cannot find the label "Not valid node for label X"
The issue has been caused by https://github.com/jenkinsci/nodelabelparameter-plugin/commit/c84f71466823c726420ab2f6af7dd989cf766bf7 from Domi
| Link |
This issue is duplicated by |
| Link |
This issue is duplicated by |
| Link |
This issue is related to |
| Assignee | Dominik Bartholdi [ domi ] | Oleg Nenashev [ oleg_nenashev ] |
| Status | Open [ 1 ] | In Progress [ 3 ] |
Jenkins IRC Bot
made changes -
| Component/s | core [ 15593 ] | |
| Component/s | parameters [ 15594 ] |
Appears to not be a core issue, only auto-assigned by component deletion.
| Component/s | core [ 15593 ] |
Is there a workaround without restarting jenkins to get the job from the queue?
Donald Kwakkel
added a comment - - edited Is there a workaround without restarting jenkins to get the job from the queue? 
Heiko Böttger
added a comment - I also suffer from this problem. Any solution? | Workflow | JNJira [ 154306 ] | JNJira + In-Review [ 185496 ] |
Here is my old pull request: https://github.com/jenkinsci/nodelabelparameter-plugin/pull/5 with a test.
| Assignee | Oleg Nenashev [ oleg_nenashev ] |
| Status | In Progress [ 3 ] | Open [ 1 ] |
Sounds not related to parameterized-trigger plugin.
Removed parameterized-trigger from components.