[JIRA] (JENKINS-27498) Configure screen stack traces on me

10 views
Skip to first unread message

wilson@ds.net (JIRA)

unread,
Dec 14, 2016, 9:38:05 AM12/14/16
to jenkinsc...@googlegroups.com
Brian Wilson commented on Bug JENKINS-27498
 
Re: Configure screen stack traces on me

I'm seeing a similar issue.

When I open the <ServerURL:port>/configure screen then click on the "Apply" or "Save" buttons, The configuration appears to be saved, but I get a Stack Trace as follows. Jenkins itself seems to be working well otherwise.

I'm using Jenkins 2.35 and 2.36 on RHEL5. Both of these versions have exhibited the issue.

============= Stack Trace Follows ======================
Oops!

A problem occurred while processing the request. Please check our bug tracker to see if a similar problem has already been reported. If it is already reported, please vote and put a comment on it to let us gauge the impact of the problem. If you think this is a new issue, please file a new issue. When you file an issue, make sure to add the entire stack trace, along with the version of Jenkins and relevant plugins. The users list might be also useful in understanding what has happened.

Stack trace

javax.servlet.ServletException: java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649)
at org.kohsuke.stapler.Stapler.service(Stapler.java:238)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:812)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1669)
at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:135)
at com.cloudbees.jenkins.support.slowrequest.SlowRequestFilter.doFilter(SlowRequestFilter.java:37)
at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:132)
at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:59)
at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:132)
at jenkins.metrics.impl.MetricsFilter.doFilter(MetricsFilter.java:125)
at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:132)
at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:126)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652)
at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:49)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84)
at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at jenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java:93)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249)
at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76)
at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:171)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652)
at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:49)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652)
at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:82)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652)
at org.kohsuke.stapler.DiagnosticThreadNameFilter.doFilter(DiagnosticThreadNameFilter.java:30)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652)
at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:585)
at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)
at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:553)
at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:223)
at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1127)
at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:515)
at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185)
at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1061)
at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)
at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:97)
at org.eclipse.jetty.server.Server.handle(Server.java:499)
at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:311)
at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:257)
at org.eclipse.jetty.io.AbstractConnection$2.run(AbstractConnection.java:544)
at winstone.BoundedExecutorService$1.run(BoundedExecutorService.java:77)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
at java.util.ArrayList.rangeCheck(ArrayList.java:653)
at java.util.ArrayList.get(ArrayList.java:429)
at org.jenkinsci.plugins.fodupload.FodUploaderPlugin$DescriptorImpl.loadPluginOptions(FodUploaderPlugin.java:496)
at org.jenkinsci.plugins.fodupload.FodUploaderPlugin$DescriptorImpl.configure(FodUploaderPlugin.java:307)
at jenkins.model.Jenkins.configureDescriptor(Jenkins.java:3642)
at jenkins.model.Jenkins.doConfigSubmit(Jenkins.java:3605)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:335)
at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:175)
at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:108)
at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:124)
at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746)
... 60 more
Help us localize this page Page generated: Dec 14, 2016 9:18:57 AM ESTREST APIJenkins ver. 2.36
Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
Atlassian logo

wilson@ds.net (JIRA)

unread,
Dec 14, 2016, 9:42:02 AM12/14/16
to jenkinsc...@googlegroups.com
Brian Wilson edited a comment on Bug JENKINS-27498
I'm seeing a similar issue.

When I open the http:// <ServerURL:port>/configure screen then click on the "Apply" or "Save" buttons, The configuration appears to be saved, but I get a Stack Trace as follows.  Jenkins itself seems to be working well otherwise.   This behavior happens on all five of our Jenkins instances very consistently.

wilson@ds.net (JIRA)

unread,
Dec 14, 2016, 9:45:01 AM12/14/16
to jenkinsc...@googlegroups.com
Brian Wilson edited a comment on Bug JENKINS-27498
I'm seeing a similar issue.

When I open the http://<ServerURL:port>/configure screen then click on the "Apply" or "Save" buttons, The configuration appears to be saved, but I get a Stack Trace as follows.  Jenkins itself seems to be working well otherwise.  This behavior happens on all five of our Jenkins instances very consistently.

I'm using Jenkins 2.35 and 2.36 on RHEL5.  Both of these Jenkins versions have exhibited the this issue.

wilson@ds.net (JIRA)

unread,
Dec 14, 2016, 9:45:01 AM12/14/16
to jenkinsc...@googlegroups.com
Brian Wilson edited a comment on Bug JENKINS-27498
I'm seeing a similar issue.

When I open the http://<ServerURL:port>/configure screen then click on the "Apply" or "Save" buttons, The configuration appears to be saved, but I get a Stack Trace as follows.  Jenkins itself seems to be working well otherwise.  This behavior happens on all five of our Jenkins instances very consistently.

I'm using Jenkins 2.35 and 2.36 on RHEL5.  Both of these Jenkins versions have exhibited the issue.

wilson@ds.net (JIRA)

unread,
Dec 14, 2016, 9:51:01 AM12/14/16
to jenkinsc...@googlegroups.com
Brian Wilson edited a comment on Bug JENKINS-27498
I'm seeing a similar issue.

When I open the http://<ServerURL:port>/configure screen then click on the "Apply" or "Save" buttons, The configuration appears to be saved, but I get a Stack Trace as follows.  Jenkins itself seems to be working well otherwise.  This behavior happens on all five of our Jenkins instances very consistently.

I'm using Jenkins 2.35 and 2.36 on RHEL5.  Both of these Jenkins versions have exhibited this issue.   This does not appear to be the result of adding any new plugins (which we haven't done in a while), but may be the result of recent plugin updates (we have quite a few of these which are updated daily).

wilson@ds.net (JIRA)

unread,
Dec 14, 2016, 9:52:02 AM12/14/16
to jenkinsc...@googlegroups.com

================== Jenkins Log =================
Dec 14, 2016 9:13:34 AM INFO org.eclipse.jetty.util.log.JavaUtilLog info
Started w.@3c77d488

{/,file:/data/jenkins/war/,AVAILABLE} {/data/jenkins/war}

Dec 14, 2016 9:13:34 AM INFO org.eclipse.jetty.util.log.JavaUtilLog info
Started ServerConnector@470734c3

{HTTP/1.1} {0.0.0.0:8080}

Dec 14, 2016 9:13:34 AM INFO org.eclipse.jetty.util.log.JavaUtilLog info
Started @3647ms
Dec 14, 2016 9:13:34 AM INFO winstone.Logger logInternal
Winstone Servlet Engine v2.0 running: controlPort=disabled
Dec 14, 2016 9:13:34 AM INFO jenkins.InitReactorRunner$1 onAttained
Started initialization
Dec 14, 2016 9:13:36 AM INFO jenkins.InitReactorRunner$1 onAttained
Listed all plugins
Dec 14, 2016 9:13:36 AM INFO jenkins.bouncycastle.api.SecurityProviderInitializer addSecurityProvider
Initializing Bouncy Castle security provider.
Dec 14, 2016 9:13:36 AM INFO jenkins.bouncycastle.api.SecurityProviderInitializer addSecurityProvider
Bouncy Castle security provider initialized.
Dec 14, 2016 9:13:37 AM INFO com.youdevise.hudson.slavestatus.SlaveListenerInitiator init
Initialising slave-status plugin
Dec 14, 2016 9:13:37 AM INFO hudson.plugins.ansicolor.PluginImpl start
AnsiColor: eliminating boring output (https://github.com/dblock/jenkins-ansicolor-plugin)
Dec 14, 2016 9:13:45 AM INFO jenkins.InitReactorRunner$1 onAttained
Prepared all plugins
Dec 14, 2016 9:13:47 AM INFO com.brsanthu.googleanalytics.GoogleAnalytics
Initializing Google Analytics with config=GoogleAnalyticsConfig [threadNameFormat=googleanalytics-thread-

{0}

, enabled=true, maxThreads=1, useHttps=true, validate=true, httpUrl=http://www.google-analytics.com/collect, httpsUrl=https://ssl.google-analytics.com/collect, userAgent=java/1.8.0_72-b15/Oracle Corporation/Java HotSpot(TM) 64-Bit Server VM/Linux/2.6.18-402.el5/amd64, proxyPort=80, deriveSystemParameters=true, gatherStats=false] and defaultRequest=Request [parms=

{TRACKING_ID=UA-79358556-1, PROTOCOL_VERSION=1, HIT_TYPE=pageview, USER_LANGUAGE=en-US, CLIENT_ID=510c6a17-1782-493e-902d-2c273993c54f, DOCUMENT_ENCODING=UTF-8}

, customDimensions={}, customMetrics={}]
Dec 14, 2016 9:13:48 AM INFO hudson.ExtensionFinder$GuiceFinder$FaultTolerantScope$1 error
Failed to instantiate optional component hudson.plugins.build_timeout.operations.AbortAndRestartOperation$DescriptorImpl; skipping
Dec 14, 2016 9:13:48 AM INFO jenkins.InitReactorRunner$1 onAttained
Started all plugins
Dec 14, 2016 9:13:48 AM INFO jenkins.InitReactorRunner$1 onAttained
Augmented all extensions
Dec 14, 2016 9:13:49 AM INFO jenkins.InitReactorRunner$1 onAttained
Loaded all jobs
Dec 14, 2016 9:13:49 AM INFO hudson.model.AsyncPeriodicWork$1 run
Started Download metadata
Dec 14, 2016 9:13:50 AM WARNING org.jenkinsci.plugins.parameterizedscheduler.Cron getRecurrencePeriod
period set to 60000
Dec 14, 2016 9:13:50 AM WARNING org.jenkinsci.plugins.parameterizedscheduler.Cron getRecurrencePeriod
period set to 60000
Dec 14, 2016 9:13:50 AM INFO hudson.model.AsyncPeriodicWork$1 run
Finished Download metadata. 162 ms
Dec 14, 2016 9:13:50 AM INFO org.jenkinsci.main.modules.sshd.SSHD start
Started SSHD at port 51248
Dec 14, 2016 9:13:50 AM INFO jenkins.InitReactorRunner$1 onAttained
Completed initialization
Dec 14, 2016 9:13:50 AM INFO org.springframework.context.support.AbstractApplicationContext prepareRefresh
Refreshing org.springframework.web.context.support.StaticWebApplicationContext@40d14cce: display name [Root WebApplicationContext]; startup date [Wed Dec 14 09:13:50 EST 2016]; root of context hierarchy
Dec 14, 2016 9:13:50 AM INFO org.springframework.context.support.AbstractApplicationContext obtainFreshBeanFactory
Bean factory for application context [org.springframework.web.context.support.StaticWebApplicationContext@40d14cce]: org.springframework.beans.factory.support.DefaultListableBeanFactory@613ce4c2
Dec 14, 2016 9:13:50 AM INFO org.springframework.beans.factory.support.DefaultListableBeanFactory preInstantiateSingletons
Pre-instantiating singletons in org.springframework.beans.factory.support.DefaultListableBeanFactory@613ce4c2: defining beans [authenticationManager,activeDirectory]; root of factory hierarchy
Dec 14, 2016 9:13:50 AM INFO org.springframework.context.support.AbstractApplicationContext prepareRefresh
Refreshing org.springframework.web.context.support.StaticWebApplicationContext@1f948092: display name [Root WebApplicationContext]; startup date [Wed Dec 14 09:13:50 EST 2016]; root of context hierarchy
Dec 14, 2016 9:13:50 AM INFO org.springframework.context.support.AbstractApplicationContext obtainFreshBeanFactory
Bean factory for application context [org.springframework.web.context.support.StaticWebApplicationContext@1f948092]: org.springframework.beans.factory.support.DefaultListableBeanFactory@540e0360
Dec 14, 2016 9:13:50 AM INFO org.springframework.beans.factory.support.DefaultListableBeanFactory preInstantiateSingletons
Pre-instantiating singletons in org.springframework.beans.factory.support.DefaultListableBeanFactory@540e0360: defining beans [filter,legacy]; root of factory hierarchy
Dec 14, 2016 9:13:51 AM INFO com.youdevise.hudson.slavestatus.SlaveListenerInitiator onOnline
Starting slave-status listener on
Dec 14, 2016 9:13:51 AM INFO jenkins.plugins.slack.SlackNotifier$Migrator onLoaded
Starting Settings Migration Process
Dec 14, 2016 9:13:51 AM INFO com.youdevise.hudson.slavestatus.SlaveListener call
Slave-status listener starting
Dec 14, 2016 9:13:51 AM INFO com.youdevise.hudson.slavestatus.SocketHTTPListener waitForConnection
Slave-status listener ready on port 3141
Dec 14, 2016 9:13:51 AM INFO jenkins.plugins.slack.SlackNotifier$Migrator onLoaded
processing Job: Turbot_Build
Dec 14, 2016 9:13:51 AM INFO jenkins.plugins.slack.SlackNotifier$Migrator onLoaded
Configuration is already up to date for "Turbot_Build", skipping migration
Dec 14, 2016 9:13:52 AM INFO hudson.WebAppMain$3 run
Jenkins is fully up and running
Dec 14, 2016 9:14:30 AM INFO hudson.ivy.IvyBuildTrigger$DescriptorImpl configure
IvyConfigurations: 0
Dec 14, 2016 9:14:48 AM WARNING org.eclipse.jetty.util.log.JavaUtilLog warn
Error while serving http://taxi49427:8080/configSubmit
java.lang.reflect.InvocationTargetException

... 70 more

Dec 14, 2016 9:18:40 AM INFO hudson.ivy.IvyBuildTrigger$DescriptorImpl configure
IvyConfigurations: 0
Dec 14, 2016 9:18:57 AM WARNING org.eclipse.jetty.util.log.JavaUtilLog warn
Error while serving http://taxi49427:8080/configSubmit
java.lang.reflect.InvocationTargetException

... 70 more

Dec 14, 2016 9:19:48 AM WARNING okhttp3.internal.platform.Platform log
A connection to https://hpfod.com/ was leaked. Did you forget to close a response body?
Dec 14, 2016 9:36:12 AM INFO hudson.ivy.IvyBuildTrigger$DescriptorImpl configure
IvyConfigurations: 0
Dec 14, 2016 9:36:30 AM WARNING org.eclipse.jetty.util.log.JavaUtilLog warn
Error while serving http://taxi49427:8080/configSubmit
java.lang.reflect.InvocationTargetException

... 70 more

Dec 14, 2016 9:38:57 AM WARNING okhttp3.internal.platform.Platform log
A connection to https://hpfod.com/ was leaked. Did you forget to close a response body?
Feed All > SEVERE > WARNING
Help us localize this page Page generated: Dec 14, 2016 9:47:34 AM ESTJenkins ver. 2.36

wilson@ds.net (JIRA)

unread,
Dec 20, 2016, 8:41:02 AM12/20/16
to jenkinsc...@googlegroups.com

This issue seems to be related to the use of the Fortify on Demand Uploader Plugin version 2.0.4. When I upgrade to this version I get the Configure stack dump. When I reverted back to the previous 1.10 version the stack dump didn't occur.

I've opened a ticket, 25102 - Fortify on Demand Uploader Plugin Version 2.0.4 causes a Java stack dump when a Jenkins configuration screen is saved of applied, with HP on this issue.

wilson@ds.net (JIRA)

unread,
Dec 20, 2016, 8:55:01 AM12/20/16
to jenkinsc...@googlegroups.com
Brian Wilson edited a comment on Bug JENKINS-27498
This issue seems to be related to the use of the [Fortify on Demand Uploader Plugin|https://wiki.jenkins-ci.org/display/JENKINS/Fortify+On+Demand+Uploader+Plugin] version 2.0.4.  When I upgrade to this version I get the Configure stack dump.  When I reverted back to the previous 1.10 version the stack dump didn't occur.

I've opened a ticket, 25102 - [ Fortify on Demand Uploader Plugin Version 2.0.4 causes a Java stack dump when a Jenkins configuration screen is saved of applied |https://support-us.hpfod.com/hc/en-us/requests/25102] , with HP on this issue.

aheritier@apache.org (JIRA)

unread,
Dec 27, 2016, 3:35:01 PM12/27/16
to jenkinsc...@googlegroups.com

Hi Brian Wilson I think it should be better to open a different case for your issue. This one had the component cloudformation-plugin which isn't related at all to the Fortify on Demand Uploader Plugin
I cannot (sadly) clone the issue and keep all your comments (where there are the interesting informations)
Could you open a new issue and copy all your informations in it please ?

aheritier@apache.org (JIRA)

unread,
Jan 4, 2017, 5:46:03 AM1/4/17
to jenkinsc...@googlegroups.com
Arnaud Héritier updated an issue
 
Jenkins / Bug JENKINS-27498
Change By: Arnaud Héritier
Component/s: fortify-on-demand-uploader-plugin
Component/s: jenkins-cloudformation

aheritier@apache.org (JIRA)

unread,
Jan 4, 2017, 5:48:02 AM1/4/17
to jenkinsc...@googlegroups.com
Arnaud Héritier assigned an issue to Matt Gibbs
Change By: Arnaud Héritier
Assignee: Matt Gibbs

aheritier@apache.org (JIRA)

unread,
Jan 4, 2017, 5:48:03 AM1/4/17
to jenkinsc...@googlegroups.com
Arnaud Héritier resolved as Fixed
Change By: Arnaud Héritier
Status: Open Resolved
Resolution: Fixed

aheritier@apache.org (JIRA)

unread,
Jan 4, 2017, 5:48:05 AM1/4/17
to jenkinsc...@googlegroups.com

wilson@ds.net (JIRA)

unread,
Jan 10, 2017, 9:46:02 AM1/10/17
to jenkinsc...@googlegroups.com

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.

aheritier@apache.org (JIRA)

unread,
Jan 10, 2017, 10:03:03 AM1/10/17
to jenkinsc...@googlegroups.com

Great Brian Wilson Thx

wilson@ds.net (JIRA)

unread,
Feb 8, 2017, 1:01:02 PM2/8/17
to jenkinsc...@googlegroups.com

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
Jenkins: 2.44
Plugin: 2.09
Java: 1.8

wilson@ds.net (JIRA)

unread,
Feb 8, 2017, 1:02:02 PM2/8/17
to jenkinsc...@googlegroups.com
Brian Wilson edited a comment on Bug JENKINS-27498
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

wilson@ds.net (JIRA)

unread,
Feb 10, 2017, 9:11:04 AM2/10/17
to jenkinsc...@googlegroups.com

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 second 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 issue of the plugin not working.

HP also said they are working on another release to be available soon, and that they would see if they could address the speed issue in this 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 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.

wilson@ds.net (JIRA)

unread,
Feb 10, 2017, 9:12:03 AM2/10/17
to jenkinsc...@googlegroups.com
Brian Wilson edited a comment on Bug JENKINS-27498
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 second 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 issue of the plugin not working.


HP also said they are working on another release to be available soon, and that they would see if they could address the speed issue in this 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 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.

wilson@ds.net (JIRA)

unread,
Feb 10, 2017, 9:12:04 AM2/10/17
to jenkinsc...@googlegroups.com
Brian Wilson edited a comment on Bug JENKINS-27498
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 release to be available soon, and that they would see if they could address the speed issue in this 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 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.

wilson@ds.net (JIRA)

unread,
Feb 10, 2017, 9:13:02 AM2/10/17
to jenkinsc...@googlegroups.com
Brian Wilson edited a comment on Bug JENKINS-27498
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 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 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.

wilson@ds.net (JIRA)

unread,
Feb 10, 2017, 9:14:01 AM2/10/17
to jenkinsc...@googlegroups.com
Brian Wilson edited a comment on Bug JENKINS-27498
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 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.

wilson@ds.net (JIRA)

unread,
Feb 10, 2017, 9:15:01 AM2/10/17
to jenkinsc...@googlegroups.com
Brian Wilson edited a comment on Bug JENKINS-27498
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.
Reply all
Reply to author
Forward
0 new messages