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

Anchore plugin does not use default policy to evaluate gates when policy configuration is left blank in the build step

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Minor Minor
    • anchore-container-scanner-plugin
    • None
    • Jenkins version: 2.32.1
      Anchore plugin version: 1.0.4
      Jenkins running in a container

      As per the help for "Policy file" parameter in the Anchore Container Image Scanner build step, the plugin uses a default policy if the field is left blank/empty. The actual behavior observed was the plugin evaluates the gate with an empty policy document resulting in no gate output

        1. screenshot-2.png
          screenshot-2.png
          70 kB
        2. screenshot-1.png
          screenshot-1.png
          199 kB

          [JENKINS-41081] Anchore plugin does not use default policy to evaluate gates when policy configuration is left blank in the build step

          Swathi Gangisetty created issue -
          Swathi Gangisetty made changes -
          Status Original: Open [ 1 ] New: In Progress [ 3 ]
          Swathi Gangisetty made changes -
          Status Original: In Progress [ 3 ] New: In Review [ 10005 ]
          Swathi Gangisetty made changes -
          Resolution New: Fixed [ 1 ]
          Status Original: In Review [ 10005 ] New: Resolved [ 5 ]

            swathigangisetty Swathi Gangisetty
            swathigangisetty Swathi Gangisetty
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: