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

Configure screen stack traces on me

    Details

    • Similar Issues:

      Description

      Some king of Jelly NPE exception I think. But it renders the configure screen useless, though Jenkins never crashes.

        Attachments

          Activity

          Show
          aheritier Arnaud Héritier added a comment - Fixed by https://github.com/jenkinsci/fortify-on-demand-uploader-plugin/pull/14 Should be in 2.0.5
          Hide
          wilson_ds_net Brian Wilson added a comment -

          The 2.0.6 revision of the HP FoD plugin (https://wiki.jenkins-ci.org/display/JENKINS/Fortify+On+Demand+Uploader+Plugin) seems to stabilize this issue for both the http://<jenkins_url>/configure and the individual job configuration screen saves.

          Show
          wilson_ds_net Brian Wilson added a comment - The 2.0.6 revision of the HP FoD plugin ( https://wiki.jenkins-ci.org/display/JENKINS/Fortify+On+Demand+Uploader+Plugin ) seems to stabilize this issue for both the http://<jenkins_url>/configure and the individual job configuration screen saves.
          Hide
          aheritier Arnaud Héritier added a comment -

          Great Brian Wilson Thx

          Show
          aheritier Arnaud Héritier added a comment - Great Brian Wilson Thx
          Hide
          wilson_ds_net Brian Wilson added a comment - - edited

          The 2.0.9 version of this plugin is also stable, and we do see all the data fields with pull down menus. Unfortunately, the menus are empty and don't populate, or take 30+ minutes to populate on our test systems. I'm in contact with HP and have been told they have some systems where they can duplicate this issue. We have a conference call in the near future to address our concerns.

          OS: RHEL 5 & 7 (mostly 7)
          Jenkins: 2.44
          Plugin: 2.09
          Java: 1.8

          Show
          wilson_ds_net Brian Wilson added a comment - - edited The 2.0.9 version of this plugin is also stable, and we do see all the data fields with pull down menus. Unfortunately, the menus are empty and don't populate, or take 30+ minutes to populate on our test systems. I'm in contact with HP and have been told they have some systems where they can duplicate this issue. We have a conference call in the near future to address our concerns. OS: RHEL 5 & 7 (mostly 7) Jenkins: 2.44 Plugin: 2.09 Java: 1.8
          Hide
          wilson_ds_net Brian Wilson added a comment - - edited

          I had a conference with HP's development team and was able to demonstrate the issues we were seeing with the HP FoD 2.0.9 plugin not populating the pull down menu's even after a long wait (~10 Minutes) At the suggestion of HP, we changed the Key-Secret values in the Jenkins Configuration screen and retried configuring a Jenkins Task to use the FoD Plugin.

          While there was still a significant delay of a few minutes, the pull down menu's did populate and cascade properly on the next test. HP and our team did agree that the delay was significant and annoying; but generating and installing a new key pair for the HP FoD account, did appear to resolve the immediate issue of the plugin not working.

          HP also said they are working on another plugin release to be available soon. The UI would be somewhat different, and that they would see if they could address the speed issue in this new release or the next. At this point, we ended the conference with our thanks to HP for working closely with us. I also applied a few small updates to the Jenkins Wiki plugin page referencing notes from the HP documentation and including hyperlinks to the documentation. It appears HP is not maintaining the Jenkins Wiki plugin description as well as might be hoped.

          Show
          wilson_ds_net Brian Wilson added a comment - - edited I had a conference with HP's development team and was able to demonstrate the issues we were seeing with the HP FoD 2.0.9 plugin not populating the pull down menu's even after a long wait (~10 Minutes) At the suggestion of HP, we changed the Key-Secret values in the Jenkins Configuration screen and retried configuring a Jenkins Task to use the FoD Plugin. While there was still a significant delay of a few minutes, the pull down menu's did populate and cascade properly on the next test. HP and our team did agree that the delay was significant and annoying; but generating and installing a new key pair for the HP FoD account, did appear to resolve the immediate issue of the plugin not working. HP also said they are working on another plugin release to be available soon. The UI would be somewhat different, and that they would see if they could address the speed issue in this new release or the next. At this point, we ended the conference with our thanks to HP for working closely with us. I also applied a few small updates to the Jenkins Wiki plugin page referencing notes from the HP documentation and including hyperlinks to the documentation. It appears HP is not maintaining the Jenkins Wiki plugin description as well as might be hoped.

            People

            • Assignee:
              mtgibbs Matt Gibbs
              Reporter:
              glowrimore Gregg Lowrimore
            • Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: