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

Snippet Generator no longer includes global variables

    XMLWordPrintable

Details

    • Bug
    • Status: Resolved (View Workflow)
    • Major
    • Resolution: Fixed
    • pipeline
    • None

    Description

      Since moving the Snippet Generator outside of jobs, it no longer includes the help docs from global variables.

      Attachments

        Issue Links

          Activity

            abayer Andrew Bayer added a comment -

            Actually got merged a while back.

            abayer Andrew Bayer added a comment - Actually got merged a while back.
            jglick Jesse Glick added a comment -

            The docker variable is a different case, and to deal with that properly really requires a separate API: JENKINS-32731.

            jglick Jesse Glick added a comment - The docker variable is a different case, and to deal with that properly really requires a separate API: JENKINS-32731 .
            rtyler R. Tyler Croy added a comment -

            I'll second what bitwiseman is saying, as a Pipeline user, the distinction between different flavors of API reference documentation is not really relevant to me. With the docker variable, for example, there are methods hanging off of that which I think of, and work with, like other "steps".

            rtyler R. Tyler Croy added a comment - I'll second what bitwiseman is saying, as a Pipeline user, the distinction between different flavors of API reference documentation is not really relevant to me. With the docker variable, for example, there are methods hanging off of that which I think of, and work with, like other "steps".
            bitwiseman Liam Newman added a comment -

            In my experience of Groovy the distinction between different ways to getting at things is pretty vague. I understand that a properties, methods, fields, and instances are diffent, but from a usage standpoint, the language seems to be designed to minimize one's awareness of those differences. From an end-user/pipeline-writer perspective, treating the global variables differently than we treat method is more confusing that helpful.

            bitwiseman Liam Newman added a comment - In my experience of Groovy the distinction between different ways to getting at things is pretty vague. I understand that a properties, methods, fields, and instances are diffent, but from a usage standpoint, the language seems to be designed to minimize one's awareness of those differences. From an end-user/pipeline-writer perspective, treating the global variables differently than we treat method is more confusing that helpful.
            abayer Andrew Bayer added a comment - Latest PR - https://github.com/jenkinsci/workflow-cps-plugin/pull/18

            People

              abayer Andrew Bayer
              abayer Andrew Bayer
              Votes:
              2 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: