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

active choices reactive parameter cant load shared library

    Details

    • Similar Issues:

      Description

      In groovy script in parameter i havent access into Groovy shared library.

      I use version 1.5.3 of Active Choices Plugin.

      In job workflow works same include.

        Attachments

          Activity

          Hide
          ashwinpai1981 Ashwin Pai added a comment -

          I too would vote in favour of this feature. It would be very useful to have a single shared groovy lib that can be used across. 

          Show
          ashwinpai1981 Ashwin Pai added a comment - I too would vote in favour of this feature. It would be very useful to have a single shared groovy lib that can be used across. 
          Hide
          roercik Robert Grądzki added a comment -

          The same case - I need this feature !!!

          Show
          roercik Robert Grądzki added a comment - The same case - I need this feature !!!
          Hide
          kinow Bruno P. Kinoshita added a comment -

          Looks like this is something useful for users. Next development cycle will start looking into ways other plugins are using to support that. I really want to avoid the plugin being blacklisted again due to security issues/CVE's. So my plain is

          1. learn how other plugins are working
          2. create a branch with the solution
          3. upload here a .hpi file with the proposed solution, and also try to release to the experimental update site (not sure if that still exists)
          4. release only, and really only, if there's enough testing from users that also took into consideration possible attack vectors created by this feature (i.e. giving some thought to what issues this feature could cause... do they have a security permission model that could allow users to use dangerous libraries? did we implement in a way that the administrator him/herself could shoot his own foot and accidentally introduce a security problem in their jenkins/etc)

          And once we pass step 4, and we are confident this won't introduce a security bug, cut a release. Let me know if anyone has any other suggestions, or if interested in helping with the testing/development.

          Cheers
          Bruno

          Show
          kinow Bruno P. Kinoshita added a comment - Looks like this is something useful for users. Next development cycle will start looking into ways other plugins are using to support that. I really want to avoid the plugin being blacklisted again due to security issues/CVE's. So my plain is 1. learn how other plugins are working 2. create a branch with the solution 3. upload here a .hpi file with the proposed solution, and also try to release to the experimental update site (not sure if that still exists) 4. release only, and really only, if there's enough testing from users that also took into consideration possible attack vectors created by this feature (i.e. giving some thought to what issues this feature could cause... do they have a security permission model that could allow users to use dangerous libraries? did we implement in a way that the administrator him/herself could shoot his own foot and accidentally introduce a security problem in their jenkins/etc) And once we pass step 4, and we are confident this won't introduce a security bug, cut a release. Let me know if anyone has any other suggestions, or if interested in helping with the testing/development. Cheers Bruno
          Hide
          roercik Robert Grądzki added a comment - - edited

          I can help with the testing.

          Show
          roercik Robert Grądzki added a comment - - edited I can help with the testing.
          Hide
          mpechner michael pechner added a comment -

          Very interested in accessing a  json file in the resources directory as defined from this facility:

          https://jenkins.io/doc/book/pipeline/shared-libraries/

          My use case is to read a json file and present part of the data in a active choice parameter.

          Show
          mpechner michael pechner added a comment - Very interested in accessing a  json file in the resources directory as defined from this facility: https://jenkins.io/doc/book/pipeline/shared-libraries/ My use case is to read a json file and present part of the data in a active choice parameter.

            People

            • Assignee:
              kinow Bruno P. Kinoshita
              Reporter:
              paveto Tomas Pavelka
            • Votes:
              15 Vote for this issue
              Watchers:
              23 Start watching this issue

              Dates

              • Created:
                Updated: