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

ZAP Settings Environment Variable does not populate Drop Down Lists

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Minor Minor
    • zap-plugin
    • ZAP Jenkins: 1.0.8
      ZAP UI: 2.6.0

      If you set a windows environment variable such as %ZAPROXY_SETTINGS% and enter that as the Path for ZAP Settings in the Jenkins ZAP configurations, then the drop down lists for policy, authentication script and alert filters will not populate since the variable is not yet evaluated.

          [JENKINS-43384] ZAP Settings Environment Variable does not populate Drop Down Lists

          Code changed in jenkins
          User: JordanGS
          Path:
          src/main/java/org/jenkinsci/plugins/zap/ZAPBuilder.java
          src/main/java/org/jenkinsci/plugins/zap/ZAPDriver.java
          src/main/resources/org/jenkinsci/plugins/zap/ZAPDriver/help-zapSettingsDir.html
          http://jenkins-ci.org/commit/zap-plugin/45733233e9ccd48f8f76350c8433059f345fe827
          Log:
          FIX JENKINS-43384

          -removed support from the ZAP Settings Variable for System Environment Variables, Build Variables as well as Environment Inject Plugin Variables since the Job Configuration page is ONLY run on the master and has no access to the slave
          -updated help file to refelect the changes made

          SCM/JIRA link daemon added a comment - Code changed in jenkins User: JordanGS Path: src/main/java/org/jenkinsci/plugins/zap/ZAPBuilder.java src/main/java/org/jenkinsci/plugins/zap/ZAPDriver.java src/main/resources/org/jenkinsci/plugins/zap/ZAPDriver/help-zapSettingsDir.html http://jenkins-ci.org/commit/zap-plugin/45733233e9ccd48f8f76350c8433059f345fe827 Log: FIX JENKINS-43384 -removed support from the ZAP Settings Variable for System Environment Variables, Build Variables as well as Environment Inject Plugin Variables since the Job Configuration page is ONLY run on the master and has no access to the slave -updated help file to refelect the changes made

          RESOLVED: PR#7

           

          RELEASE: 1.1.0 or newer.

           

          NOTE: if the release is not published yet, feel free to checkout the associated development branch for the latest version. Be aware that if it's not released yet, it's in development for a reason.

          Goran Sarenkapa added a comment - RESOLVED: PR#7   RELEASE : 1.1.0 or newer .   NOTE : if the release is not published yet, feel free to checkout the associated development branch for the latest version. Be aware that if it's not released yet, it's in development for a reason.

            jordangs Goran Sarenkapa
            jordangs Goran Sarenkapa
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: