• Type: Bug
• Resolution: Unresolved
• Priority: Major
• Component/s: matrix-project-plugin
• Labels:

  None
• Environment:

  OS: RHEL7.9
  Jenkins: 2.319.3 upgraded from 2.303.1
  Matrix Project plugin: 1.20 upgraded from 1.19
  Node and Label parameter plugin: 1.10.3 upgraded from 1.10.1

1. 

   NoConsoleErrorfromRenderinDevPlusCheckName.png

   142 kB

   2022-02-18 18:05

2. 

   renderDevelopmentShowsNodes.png

   148 kB

   2022-02-18 18:05

3. 

   renderProductionShowsLabels.png

   188 kB

   2022-02-18 18:05

4. 

   ConsoleErrorfromRender.png

   348 kB

   2022-02-18 18:05

5. plugins-ver.txt

   3 kB

   2022-02-20 17:19

6. 

   screencapture-testing-a-markwaite-net-8080-manage-2022-02-20-11_58_13-edit.png

   71 kB

   2022-02-20 19:08

[JENKINS-67843] Matrix projects can't add Agents axis if a multi-line description is assigned to a label

Victoria created issue - 2022-02-18 18:10

Mark Waite made changes - 2022-02-20 04:03

Assignee

Original: Kohsuke Kawaguchi [ kohsuke ]

Victoria made changes - 2022-02-20 17:19

Attachment

New: plugins-ver.txt [ 57319 ]

Victoria made changes - 2022-02-20 17:21

Description

Original: After a Jenkins application and all plugins-update, new and existing multi-configuration projects have lost the ability to add an Agents axis.   This is occurring on two production servers, both of which have many nodes defined.  It is not occurring on two development servers, which only have three to six nodes defined. In the /configure screen, when I select "Add axis" and then "Agents", no window and no errors are displayed in the GUI.  (In the dev environment, when I do that I get the Agents/Name/Node\Label window.)  I also note in dev I see a checkName "step", but that does not occur in prod. Using Chrome to see what I could figure out, I captured some errors.  Attached. Please let me know what additional information I can provide.  This is impacting existing multi-configuration projects, which no longer have the agents available to them.

New: After a Jenkins application and all plugins-update, new and existing multi-configuration projects have lost the ability to add an Agents axis.   This is occurring on two production servers, both of which have many nodes defined.  It is not occurring on two development servers, -which only have three to six nodes defined.-  . I added all the nodes from one production server to one dev server, but that did not have an impact.   In the /configure screen, when I select "Add axis" and then "Agents", no window and no errors are displayed in the GUI.  (In the dev environment, when I do that I get the Agents/Name/Node\Label window.)  I also note in dev I see a checkName "step", but that does not occur in prod. Using Chrome to see what I could figure out, I captured some errors.  Attached. Please let me know what additional information I can provide.  This is impacting existing multi-configuration projects, which no longer have the agents available to them.

Victoria made changes - 2022-02-20 17:38

Environment

Original: OS: RHEL7.9 Jenkins: 2.319.3 Matrix plugin: 1.20

New: OS: RHEL7.9 Jenkins: 2.319.3 upgraded from 2.303.1 Matrix Project plugin: 1.20 upgraded from 1.19 Node and Label parameter plugin: 1.10.3 upgraded from 1.10.1

Mark Waite made changes - 2022-02-20 19:08

Attachment

New: screencapture-testing-a-markwaite-net-8080-manage-2022-02-20-11_58_13-edit.png [ 57320 ]

Victoria made changes - 2022-02-20 21:08

Description

Original: After a Jenkins application and all plugins-update, new and existing multi-configuration projects have lost the ability to add an Agents axis.   This is occurring on two production servers, both of which have many nodes defined.  It is not occurring on two development servers, -which only have three to six nodes defined.-  . I added all the nodes from one production server to one dev server, but that did not have an impact.   In the /configure screen, when I select "Add axis" and then "Agents", no window and no errors are displayed in the GUI.  (In the dev environment, when I do that I get the Agents/Name/Node\Label window.)  I also note in dev I see a checkName "step", but that does not occur in prod. Using Chrome to see what I could figure out, I captured some errors.  Attached. Please let me know what additional information I can provide.  This is impacting existing multi-configuration projects, which no longer have the agents available to them.

New: After a Jenkins application and all plugins-update, new and existing multi-configuration projects have lost the ability to add an Agents axis.   {code:java} Uncaught SyntaxError: Invalid or unexpected token   at eval (<anonymous>)   at geval (hudson-behavior.js:471:30) {code} This is occurring on two production servers, both of which have many nodes defined.  It is not occurring on two development servers, -which only have three to six nodes defined.-  . I added all the nodes from one production server to one dev server, but that did not have an impact.   In the /configure screen, when I select "Add axis" and then "Agents", no window and no errors are displayed in the GUI.  (In the dev environment, when I do that I get the Agents/Name/Node\Label window.)  I also note in dev I see a checkName "step", but that does not occur in prod. Using Chrome to see what I could figure out, I captured some errors.  Attached. Please let me know what additional information I can provide.  This is impacting existing multi-configuration projects, which no longer have the agents available to them.

Victoria made changes - 2022-02-20 21:08

Summary

Original: Multi-config projects unable to add Agents axis

New: Multi-config projects unable to add Agents axis (hudson.behavior.js:471:30)

Victoria made changes - 2022-02-20 21:10

Description

Original: After a Jenkins application and all plugins-update, new and existing multi-configuration projects have lost the ability to add an Agents axis.   {code:java} Uncaught SyntaxError: Invalid or unexpected token   at eval (<anonymous>)   at geval (hudson-behavior.js:471:30) {code} This is occurring on two production servers, both of which have many nodes defined.  It is not occurring on two development servers, -which only have three to six nodes defined.-  . I added all the nodes from one production server to one dev server, but that did not have an impact.   In the /configure screen, when I select "Add axis" and then "Agents", no window and no errors are displayed in the GUI.  (In the dev environment, when I do that I get the Agents/Name/Node\Label window.)  I also note in dev I see a checkName "step", but that does not occur in prod. Using Chrome to see what I could figure out, I captured some errors.  Attached. Please let me know what additional information I can provide.  This is impacting existing multi-configuration projects, which no longer have the agents available to them.

New: After a Jenkins application and all plugins-update, new and existing multi-configuration projects have lost the ability to add an Agents axis.  Running through Chrome's debugger, this error displays when the Agents button is selected under the "Add axis" option.   {code:java} Uncaught SyntaxError: Invalid or unexpected token   at eval (<anonymous>)   at geval (hudson-behavior.js:471:30)   [...]{code} This is occurring on two production servers, both of which have many nodes defined.  It is not occurring on two development servers, -which only have three to six nodes defined.-  . I added all the nodes from one production server to one dev server, but that did not have an impact.   In the /configure screen, when I select "Add axis" and then "Agents", no window and no errors are displayed in the GUI.  (In the dev environment, when I do that I get the Agents/Name/Node\Label window.)  I also note in dev I see a checkName "step", but that does not occur in prod. Using Chrome to see what I could figure out, I captured some errors.  Attached. Please let me know what additional information I can provide.  This is impacting existing multi-configuration projects, which no longer have the agents available to them.

Victoria made changes - 2022-02-28 14:31

Resolution		New: Cannot Reproduce [ 5 ]
Status	Original: Open [ 1 ]	New: Closed [ 6 ]

Justin Vallon made changes - 2022-08-31 19:58

Resolution	Original: Cannot Reproduce [ 5 ]
Status	Original: Closed [ 6 ]	New: Reopened [ 4 ]

Load more newer history items