Your browser was unable to load all of the resources. They may have been blocked by your firewall, proxy or browser configuration.
Press Ctrl+F5 or Ctrl+Shift+R to have your browser try again.

QuickBuild

QB3.0.3: Click trigger step to go to triggered build #1113

#1
scastria ·
Would it be possible to enhance the trigger step so that when I click on it, it takes me directly to the build that it triggered? It would make it so much easier to navigate a trigger build hierarchy that way.
  • replies 14
  • views 4829
  • stars 0
#2
robinshen ADMIN ·
Track this as improvement request: http://track.pmease.com/browse/QB-620
Will try to deliver it in a patch release of 3.0
#3
robinshen ADMIN ·
Implemented in 3.0.4 now.
#4
scastria ·
This feature is wonderful. However, can you make a little better and have the overview page show this extra information as soon as the triggered configuration gets assigned a build object? In other words, can you make this new information available DURING a build instead of only AFTER a build. I would like to walk the trigger hierarchy while the build is running.
#5
robinshen ADMIN ·
This is now possible in 3.0.14
#6
scastria ·
PERFECT!

Now here is an enhancement request to add to your list:

Keeping with trigger chains, it would be nice to see a graphical representation of a trigger chain with circles and lines connecting them showing the hierarchy. In addition, each circle will contain the build links to go that build and it will be colored yellow for in progress and green for successful and red for failure. At the end of a big trigger chain, I could look at this graph and see at a glance the status of all modules in the trigger chain with links to go to each one. I have written my own plugin to walk the trigger chain and present this information in tabular form so I am in no hurry for this, but having a graphical representation would be truly AWESOME!
#7
robinshen ADMIN ·
This has been filed as feature request http://track.pmease.com/browse/QB-695
#8
scastria ·
I think there may be a bug somewhere. The more I use these new links to the triggered build, the more I get the exceptions below. All I have to do is go back to dashboard and everything is fine so I would much rather have these exceptions then not having the trigger build links.


WicketMessage: Cannot find the rendered page in session [pagemap=null,componentPath=112:ajaxRefreshLink,versionNumber=0]

Root cause:

org.apache.wicket.protocol.http.PageExpiredException: Cannot find the rendered page in session [pagemap=null,componentPath=112:ajaxRefreshLink,versionNumber=0]
at org.apache.wicket.protocol.http.WebRequestCycleProcessor.resolve(WebRequestCycleProcessor.java:197)
at org.apache.wicket.RequestCycle.step(RequestCycle.java:1310)
at org.apache.wicket.RequestCycle.steps(RequestCycle.java:1428)
at org.apache.wicket.RequestCycle.request(RequestCycle.java:545)
at org.apache.wicket.protocol.http.WicketFilter.doGet(WicketFilter.java:479)
at org.apache.wicket.protocol.http.WicketServlet.doGet(WicketServlet.java:138)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:596)
at com.pmease.quickbuild.web.WebServlet.handleWebRequest(WebServlet.java:141)
at com.pmease.quickbuild.web.WebServlet.service(WebServlet.java:104)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
at com.pmease.quickbuild.web.HttpServiceProvider$1$1.service(HttpServiceProvider.java:86)
at org.eclipse.equinox.http.servlet.internal.ServletRegistration.handleRequest(ServletRegistration.java:90)
at org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:111)
at org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:59)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
at org.eclipse.equinox.http.jetty.internal.HttpServerManager$InternalHttpServiceServlet.service(HttpServerManager.java:318)
at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:502)
at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:380)
at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765)
at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
at org.mortbay.jetty.Server.handle(Server.java:324)
at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:535)
at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:865)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:540)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:213)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:404)
at org.mortbay.jetty.bio.SocketConnector$Connection.run(SocketConnector.java:228)
at org.mortbay.thread.QueuedThreadPool$PoolThread.run(QueuedThreadPool.java:520)
#9
robinshen ADMIN ·
Are you able to get it reproduced?
#10
robinshen ADMIN ·
Also is this only happening for running builds?
#11
scastria ·
It happens quite frequently, not sure what causes it though. No it happens when inspecting finished builds. It may have nothing to do with these new trigger links and maybe it is timing out at a regular interval as if nothing is ever resetting the timer, not sure.
#12
robinshen ADMIN ·
Do you mean this also happens when build is finished?
#13
scastria ·
yes. If I look at a build from yesterday and start walking the trigger chain with the new links, eventually, I will get the exception shown below. Let me see if I can narrow down what causes this before you worry about it.
#14
robinshen ADMIN ·
That will be of great help, as I tried but can not get it reproduced so far...
#15
robinshen ADMIN ·
I get this reproduced by opening up to 7 browser tabs. It is a Wicket limitation that at most 6 tabs can be opened in the same web session.
Log in to reply