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

Details

    • Bug
    • Status: Resolved (View Workflow)
    • Minor
    • Resolution: Fixed
    • None
    • Jenkins version: 2.32.1
      Anchore plugin version: 1.0.4
      Jenkins running in a container

    Description

      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

      Attachments

        Activity

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

          People

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

            Dates

              Created:
              Updated:
              Resolved: