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

Add support to Pipeline API

    XMLWordPrintable

Details

    Description

      This is a placeholder for an upcoming feature to support cascade parameters without the HTML/DOM.

      This feature will enable Jenkinsfile, pipelines, cron-scheduled, and jobs triggered via other ways without using the GUI/HTML of Jenkins.

      No estimated release date, as I will have to find spare time to work on this feature (not using the plug-in at my current $work, so have no sponsor for this). Happy to review pull requests though.

      ioannis I will close other issues related to Pipelines/Jenkinsfile, as we never implemented that feature in the plug-in (I read somewhere users reporting they were able to use it, but this feature was not intentional and may be broken depending of the Jenkins or plug-in versions).

      Attachments

        Issue Links

          Activity

            kinow Bruno P. Kinoshita created issue -
            kinow Bruno P. Kinoshita made changes -
            Field Original Value New Value
            Link This issue is duplicated by JENKINS-59033 [ JENKINS-59033 ]
            kinow Bruno P. Kinoshita made changes -
            Link This issue is duplicated by JENKINS-61117 [ JENKINS-61117 ]
            kinow Bruno P. Kinoshita made changes -
            Link This issue is duplicated by JENKINS-50739 [ JENKINS-50739 ]
            kinow Bruno P. Kinoshita made changes -
            Link This issue is duplicated by JENKINS-62438 [ JENKINS-62438 ]
            kinow Bruno P. Kinoshita made changes -
            Link This issue is duplicated by JENKINS-29407 [ JENKINS-29407 ]
            kinow Bruno P. Kinoshita made changes -
            Link This issue is duplicated by JENKINS-63282 [ JENKINS-63282 ]
            schtefan Stefan added a comment - - edited

            We really like the Active Choice Parameters using Groovy scripts and use them a lot, but are suffering from the drawback that the configured default values are not propagated into the build when a job is triggered by a time schedule or by the SCM polling in free-style jobs. Any chance to estimate when this can be fixed, or any hints or description what has to be fixed in the code?

            schtefan Stefan added a comment - - edited We really like the Active Choice Parameters using Groovy scripts and use them a lot, but are suffering from the drawback that the configured default values are not propagated into the build when a job is triggered by a time schedule or by the SCM polling in free-style jobs. Any chance to estimate when this can be fixed, or any hints or description what has to be fixed in the code?
            mraone Alexey Nikitin added a comment - - edited

            kinow I started related work with PR#47.

            Please help with the review.

            mraone Alexey Nikitin added a comment - - edited kinow  I started related work with  PR#47 . Please help with the review.

            People

              kinow Bruno P. Kinoshita
              kinow Bruno P. Kinoshita
              Votes:
              18 Vote for this issue
              Watchers:
              29 Start watching this issue

              Dates

                Created:
                Updated: