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

linter for Jenkinsfile doesn't detect misspelled parameter names

      On a busy Jenkins system it can take up to 30 minutes before your job gets executed, then take several minutes to get to the step you've just added where you accidentally misspelled a parameter name to a Groovy command (sh in my case).  The declarative-linter idea is great but something that can pick up any errors that are guaranteed to break your build when it finally executed would make a huge difference.

       

          [JENKINS-55092] linter for Jenkinsfile doesn't detect misspelled parameter names

          Andrew Bayer added a comment -

          Can you give me an example? It should be doing this for steps - not for shared library functions, but it should be verifying parameter names for step classes invoked from the Jenkinsfile.

          Andrew Bayer added a comment - Can you give me an example? It should be doing this for steps - not for shared library functions, but it should be verifying parameter names for step classes invoked from the Jenkinsfile.

          Dylan Nicholson added a comment - - edited

              return sh(scrip: "./myScript.sh", returnStatus: true) != 0

           

          Doesn't detect that "scrip" is misspelled.

          Dylan Nicholson added a comment - - edited     return sh(scrip: "./myScript.sh", returnStatus: true) != 0   Doesn't detect that "scrip" is misspelled.

            Unassigned Unassigned
            wizofaus Dylan Nicholson
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: