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

Active Choices plugin doesn't work with Workflow Plugin

    Details

    • Similar Issues:

      Description

      When configuring a workflow job and adding a active-choices parameter to the job, the script section is blank/empty. This also seems to happen when the active-choices plugin is used with another plugin that has a groovy script textarea.

        Attachments

          Issue Links

            Activity

            Hide
            kinow Bruno P. Kinoshita added a comment -

            Previous comment was also a memory note, as I tend to forget things after a while but if you've read it and have another alternative, please let me know. So far the only other ways I can think of fixing it is by modifying the Jenkins core, which would require a longer time to design the change and get its approval (if approved) by core-devs.

            Show
            kinow Bruno P. Kinoshita added a comment - Previous comment was also a memory note, as I tend to forget things after a while but if you've read it and have another alternative, please let me know. So far the only other ways I can think of fixing it is by modifying the Jenkins core, which would require a longer time to design the change and get its approval (if approved) by core-devs.
            Hide
            kmagomedov Kamil Magomedov added a comment -

            Hello, Bruno P. Kinoshita

            Started by fixing the variables jenkinsBuild and jenkinsProject for pipeline builds (which also removes one deprecated method call at least). Then created a few pipeline jobs to test the plug-in. As expected, when you add "This build is parameterized", everything works as expected.

            This doesn't match my experience — groovy.lang.Binding only has the jenkinsParameter variable for any pipeline job that I test, "This build is parameterized" option is checked on each one. Is this fix not included in the official releases yet? I'm using Active Choices plugin version 2.2.1

            Show
            kmagomedov Kamil Magomedov added a comment - Hello, Bruno P. Kinoshita Started by fixing the variables jenkinsBuild and jenkinsProject for pipeline builds (which also removes one deprecated method call at least). Then created a few pipeline jobs to test the plug-in. As expected, when you add "This build is parameterized", everything works as expected. This doesn't match my experience — groovy.lang.Binding only has the jenkinsParameter variable for any pipeline job that I test, "This build is parameterized" option is checked on each one. Is this fix not included in the official releases yet? I'm using Active Choices plugin version 2.2.1
            Hide
            kinow Bruno P. Kinoshita added a comment -

            Hi , once released the issue will be marked as closed or fixed here. I have no bandwidth to work on this right now, but happy to review/merge pull requests.

            Bruno

            Show
            kinow Bruno P. Kinoshita added a comment - Hi , once released the issue will be marked as closed or fixed here. I have no bandwidth to work on this right now, but happy to review/merge pull requests. Bruno
            Hide
            ioannis Ioannis Moutsatsos added a comment - - edited

            Bruno P. Kinoshita thanks for the interesting comment/memory dump above! As of now (OCT-25-2019), there are at least 13 different active-choice Jira related tickets referencing the use of this plugin in pipeline jobs/Jenkinsfile. Given that this plugin was designed to be used interactively on freestyle job build forms (clearly stated in the plugin documentation) is there a point to keep looking for solutions in this space especially if there are no convenient Jenkins extension points to support this approach?  Should we just close all these issues as will not be done. It seems no-one is reading the plugin documentation any longer. Perhaps these AC shortcomings could be addressed in a different plugin designed specifically for pipeline jobs.

            Show
            ioannis Ioannis Moutsatsos added a comment - - edited Bruno P. Kinoshita thanks for the interesting comment/memory dump above! As of now (OCT-25-2019), there are at least 13 different active-choice Jira related tickets referencing the use of this plugin in pipeline jobs/Jenkinsfile. Given that this plugin was designed to be used interactively on freestyle job build forms (clearly stated in the plugin documentation) is there a point to keep looking for solutions in this space especially if there are no convenient Jenkins extension points to support this approach?  Should we just close all these issues as will not be done. It seems no-one is reading the plugin documentation any longer. Perhaps these AC shortcomings could be addressed in a different plugin designed specifically for pipeline jobs.
            Hide
            kinow Bruno P. Kinoshita added a comment -

            Moving work to JENKINS-63284. This way it will be easier for me to triage issues, and keep track of requests for pipelines (this issue will be linked).

            Show
            kinow Bruno P. Kinoshita added a comment - Moving work to JENKINS-63284 . This way it will be easier for me to triage issues, and keep track of requests for pipelines (this issue will be linked).

              People

              • Assignee:
                kinow Bruno P. Kinoshita
                Reporter:
                analogj Jason Kulatunga
              • Votes:
                9 Vote for this issue
                Watchers:
                20 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: