Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-53917

choice parameter no longer supports choices in pipeline

    • 1.17

      Current releases of all plugins, notably Struct 1.16, result in the choice parameter no longer having a legal choices argument. https://github.com/jenkinsci/structs-plugin/pull/41 perhaps?

      Reproduce: docker run -p 8080:8080 jenkins/jenkins:2.138.1, install workflow-aggregator only, create a Pipeline and consult the Snippet Generator.

      Originally reported on IRC by ctcpme (siigna):

      [2018-10-05 07:58:19]  <ctcpme>		i just did an upgrade to 2.138.1, and updated plugins.  i'm getting an error "WorkflowScript: 80: Invalid parameter "choices", did you mean "name"?" with choice parameters in my pipelines.  like pipeline { parameters { choice(name: "test", choices: "1\n2", description: "test") } }.  anyone have a clue what could cause this?
      [2018-10-05 08:02:23]  <@danielbeck>		ctcpme are you on structs plugin 1.16?
      [2018-10-05 08:02:38]  <ctcpme>		yes
      [2018-10-05 08:03:51]  <@danielbeck>		ctcpme is there a way for you to ignore the error, if so, what happens?
      [2018-10-05 08:04:41]  <ctcpme>		i don't believe so.  i get a MultipleCompilationErrorsException and the job immediately fails.	 

          [JENKINS-53917] choice parameter no longer supports choices in pipeline

          Daniel Beck created issue -
          Daniel Beck made changes -
          Description Original: Current releases of all plugins, notably Struct 1.16, result in the {{choice}} parameter no longer having a legal {{choices}} argument. [https://github.com/jenkinsci/structs-plugin/pull/41] perhaps?

          Reproduce: {{docker run -p 8080:8080 jenkins/jenkins:2.138.1}}, install workflow-aggregator only, create a Pipeline and consult the Snippet Generator.

          Originally reported on IRC by ctcpme:
          {noformat}
          [2018-10-05 07:58:19] <ctcpme> i just did an upgrade to 2.138.1, and updated plugins.  i'm getting an error "WorkflowScript: 80: Invalid parameter "choices", did you mean "name"?" with choice parameters in my pipelines.  like pipeline { parameters { choice(name: "test", choices: "1\n2", description: "test") } }.  anyone have a clue what could cause this? [2018-10-05 08:02:23] <@danielbeck> ctcpme are you on structs plugin 1.16? [2018-10-05 08:02:38] <ctcpme> yes [2018-10-05 08:03:51] <@danielbeck> ctcpme is there a way for you to ignore the error, if so, what happens? [2018-10-05 08:04:41] <ctcpme> i don't believe so.  i get a MultipleCompilationErrorsException and the job immediately fails. {noformat}
          New: Current releases of all plugins, notably Struct 1.16, result in the {{choice}} parameter no longer having a legal {{choices}} argument. [https://github.com/jenkinsci/structs-plugin/pull/41] perhaps?

          Reproduce: {{docker run -p 8080:8080 jenkins/jenkins:2.138.1}}, install workflow-aggregator only, create a Pipeline and consult the Snippet Generator.

          Originally reported on IRC by ctcpme:
          {noformat}
          [2018-10-05 07:58:19] <ctcpme> i just did an upgrade to 2.138.1, and updated plugins.  i'm getting an error "WorkflowScript: 80: Invalid parameter "choices", did you mean "name"?" with choice parameters in my pipelines.  like pipeline { parameters { choice(name: "test", choices: "1\n2", description: "test") } }.  anyone have a clue what could cause this?
          [2018-10-05 08:02:23] <@danielbeck> ctcpme are you on structs plugin 1.16?
          [2018-10-05 08:02:38] <ctcpme> yes
          [2018-10-05 08:03:51] <@danielbeck> ctcpme is there a way for you to ignore the error, if so, what happens?
          [2018-10-05 08:04:41] <ctcpme> i don't believe so.  i get a MultipleCompilationErrorsException and the job immediately fails. {noformat}
          Daniel Beck made changes -
          Assignee Original: Kohsuke Kawaguchi [ kohsuke ] New: Jesse Glick [ jglick ]
          Steve Bouché made changes -
          Description Original: Current releases of all plugins, notably Struct 1.16, result in the {{choice}} parameter no longer having a legal {{choices}} argument. [https://github.com/jenkinsci/structs-plugin/pull/41] perhaps?

          Reproduce: {{docker run -p 8080:8080 jenkins/jenkins:2.138.1}}, install workflow-aggregator only, create a Pipeline and consult the Snippet Generator.

          Originally reported on IRC by ctcpme:
          {noformat}
          [2018-10-05 07:58:19] <ctcpme> i just did an upgrade to 2.138.1, and updated plugins.  i'm getting an error "WorkflowScript: 80: Invalid parameter "choices", did you mean "name"?" with choice parameters in my pipelines.  like pipeline { parameters { choice(name: "test", choices: "1\n2", description: "test") } }.  anyone have a clue what could cause this?
          [2018-10-05 08:02:23] <@danielbeck> ctcpme are you on structs plugin 1.16?
          [2018-10-05 08:02:38] <ctcpme> yes
          [2018-10-05 08:03:51] <@danielbeck> ctcpme is there a way for you to ignore the error, if so, what happens?
          [2018-10-05 08:04:41] <ctcpme> i don't believe so.  i get a MultipleCompilationErrorsException and the job immediately fails. {noformat}
          New: Current releases of all plugins, notably Struct 1.16, result in the {{choice}} parameter no longer having a legal {{choices}} argument. [https://github.com/jenkinsci/structs-plugin/pull/41] perhaps?

          Reproduce: {{docker run -p 8080:8080 jenkins/jenkins:2.138.1}}, install workflow-aggregator only, create a Pipeline and consult the Snippet Generator.

          Originally reported on IRC by ctcpme ([~siigna]):
          {noformat}
          [2018-10-05 07:58:19] <ctcpme> i just did an upgrade to 2.138.1, and updated plugins.  i'm getting an error "WorkflowScript: 80: Invalid parameter "choices", did you mean "name"?" with choice parameters in my pipelines.  like pipeline { parameters { choice(name: "test", choices: "1\n2", description: "test") } }.  anyone have a clue what could cause this?
          [2018-10-05 08:02:23] <@danielbeck> ctcpme are you on structs plugin 1.16?
          [2018-10-05 08:02:38] <ctcpme> yes
          [2018-10-05 08:03:51] <@danielbeck> ctcpme is there a way for you to ignore the error, if so, what happens?
          [2018-10-05 08:04:41] <ctcpme> i don't believe so.  i get a MultipleCompilationErrorsException and the job immediately fails. {noformat}

          Steve Bouché added a comment -

          Downgrading to structs 1.15 resolves the error.

          Steve Bouché added a comment - Downgrading to structs 1.15 resolves the error.
          Jesse Glick made changes -
          Status Original: Open [ 1 ] New: In Progress [ 3 ]
          Jesse Glick made changes -
          Component/s Original: workflow-aggregator-plugin [ 21710 ]
          Component/s Original: workflow-cps-plugin [ 21713 ]
          Labels New: regression

          Jesse Glick added a comment -

          Regression caused by trying to work around an evil effect of the fix of JENKINS-26143.

          Jesse Glick added a comment - Regression caused by trying to work around an evil effect of the fix of JENKINS-26143 .
          Jesse Glick made changes -
          Link New: This issue relates to JENKINS-26143 [ JENKINS-26143 ]
          Jesse Glick made changes -
          Remote Link New: This issue links to "structs PR 42 (Web Link)" [ 21902 ]

            jglick Jesse Glick
            danielbeck Daniel Beck
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: