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

Zap plugin fails when configuring job with Jenkins 2.277.1 or later

    XMLWordPrintable

Details

    • Bug
    • Status: Open (View Workflow)
    • Blocker
    • Resolution: Unresolved
    • zap-plugin

    Description

      Steps to reproduce:

      1. This is a fresh install, the installation method is mentioned in the environment details.
      2. Installed all the recommended plugins
      3. Install plugin https://plugins.jenkins.io/zap/ 
      4. Added an Environment variable 'ZAPROXY_HOME' for the install directory.
      5.  Create a job
      6. Add a build step 'Execute ZAP`
      7. Just change the port for ZAP 
      8. Apply and save

      Expected:

      The Job to be saved successfully

       

      Actual:

      A problem occurred while processing the request.

       

      Attachments

        Issue Links

          Activity

            rakil Akil added a comment -

            Any updates on this?

             

            rakil Akil added a comment - Any updates on this?  
            markewaite Mark Waite added a comment -

            rakil since that plugin was last released 4 years ago and includes table elements in its configuration form, it is not compatible with the configuration form modernization in Jenkins 2.277.1 and later. See the Jenkins 2.277.1 changelog, Jenkins 2.277.1 upgrade guide, and Jenkins 2.277.1 webinar for more details.

            Your choices include:

            • Adopt the plugin and use the tables to divs migration guide to fix the issue
            • Remove the plugin and find another way to accomplish your objective
            • Use a Jenkins version prior to 2.277.1
            markewaite Mark Waite added a comment - rakil since that plugin was last released 4 years ago and includes table elements in its configuration form , it is not compatible with the configuration form modernization in Jenkins 2.277.1 and later. See the Jenkins 2.277.1 changelog , Jenkins 2.277.1 upgrade guide , and Jenkins 2.277.1 webinar for more details. Your choices include: Adopt the plugin and use the tables to divs migration guide to fix the issue Remove the plugin and find another way to accomplish your objective Use a Jenkins version prior to 2.277.1
            rakil Akil added a comment -

            Thank You markewaite for your response. I Will try to use a prior version of Jenkins, would you recommend me a version?

             

            rakil Akil added a comment - Thank You markewaite  for your response. I Will try to use a prior version of Jenkins, would you recommend me a version?  
            rakil Akil added a comment -

            Hope this Jenkins 2.263.x will work. As mentioned in https://www.jenkins.io/doc/developer/views/table-to-div-migration/

            rakil Akil added a comment - Hope this Jenkins 2.263.x will work. As mentioned in  https://www.jenkins.io/doc/developer/views/table-to-div-migration/
            adityafaircent ADITYA added a comment -

            can there be a video reference available ? I am using 2.375.3 and receiving the same issue. I am not able to understand how to set up prior version of the jenkin

             

            adityafaircent ADITYA added a comment - can there be a video reference available ? I am using 2.375.3 and receiving the same issue. I am not able to understand how to set up prior version of the jenkin  
            markewaite Mark Waite added a comment -

            adityafaircent I'm not aware of any video reference on installing and configuring Jenkins 2.263.x.

            I think it is a mistake to invest effort installing a badly outdated version of Jenkins in order to configure the unmaintained ZAProxy plugin. If your company needs that specific plugin, propose to your management that they assign someone a day or two a month to maintain it. Adopt the plugin, fix the tables to divs issue, and release a new version of the plugin with the fix. That will resolve the issue for you and resolve the issue for others.

            Alternately, replace the use of the plugin with command line calls to start and stop the ZAproxy in the cases where you are using it.

            markewaite Mark Waite added a comment - adityafaircent I'm not aware of any video reference on installing and configuring Jenkins 2.263.x. I think it is a mistake to invest effort installing a badly outdated version of Jenkins in order to configure the unmaintained ZAProxy plugin. If your company needs that specific plugin, propose to your management that they assign someone a day or two a month to maintain it. Adopt the plugin, fix the tables to divs issue, and release a new version of the plugin with the fix. That will resolve the issue for you and resolve the issue for others. Alternately, replace the use of the plugin with command line calls to start and stop the ZAproxy in the cases where you are using it.

            People

              jordangs Goran Sarenkapa
              rakil Akil
              Votes:
              2 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated: