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

notifyCommit with sha1=0000000000000000000000000000000000000000

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Minor Minor
    • git-plugin

      If a notifyCommit is called with sha1=0000000000000000000000000000000000000000 results in the following error

      FATAL: Command "c:\Program Files\Git\bin\git.exe rev-parse "0000000000000000000000000000000000000000^{commit}"" returned status code 128:
stdout: 0000000000000000000000000000000000000000^{commit}

stderr: fatal: ambiguous argument '0000000000000000000000000000000000000000^{commit}': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git <command> [<revision>...] -- [<file>...]

      Shouldn't the plugin skip this trigger for an empty/null hash (0000000000000000000000000000000000000000)?

            Unassigned Unassigned
            bfcamara Bruno Camara
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: