So how is this controlled atm? I don't see anything to this effect in
the templates I modified. I've really just replaced table based layouts
with div based layouts.
On 19/07/2014 07:04, Mirko Friedenhagen wrote:
+1 for completely collapsing the whole stuff (or even make this a
separate page?) maybe when a job takes longer as expected the
collapsed build queue should give a hint.
Regards
Mirko
--
Sent from my mobile
On Jul 19, 2014 7:00 AM, "domi" <d...@fortysix.ch
<mailto:d...@fortysix.ch>> wrote:
Not only collaps after a number of executers, but actually make
the whole thing disappear and only show the ones currently
executing a build. ...and some people don't even wanna see the
executing ones...
Am 19.07.2014 um 02:30 schrieb Stephen Connolly
<stephen.alan.conno...@gmail.com
<mailto:stephen.alan.conno...@gmail.com>>:
I want to set these to be collapsed by default if the number of
executors is above some threshold (as this will improve
responsiveness)
As long as you don't interfere with that aim, I'm good
On Friday, 18 July 2014, Tom Fennelly <tom.fenne...@gmail.com
<mailto:tom.fenne...@gmail.com>> wrote:
Hi.
I've been looking to see if we could replace the current
<l:pane> based panels with <div> based alternatives. I think
this will help us style the panels better + I think they will
work better (Vs tables) with the new layout.
Basically what I've done so far
(https://github.com/tfennelly/jenkins/compare/JENKINS-23810) is:
1. Created a new set of tags (<l:divpane>, <l:divpaneRow>
and <l:divpaneCell>) to replace the current <l:pane> tag.
2. Updated the Build Queue, Executors and History panes to
use this approach.
3. Can see it here: http://166.78.9.27:8080/
Examples of what they look like...
<https://lh6.googleusercontent.com/-EdhWclL9x9c/U8lQPZKr83I/AAAAAAAABJY/9_8rrwy4BJM/s1600/Screenshot+2014-07-18+17.07.24.png>
<https://lh3.googleusercontent.com/-xRJoi1se6AA/U8lQZdvoBZI/AAAAAAAABJg/Ip35Cs0OAE4/s1600/Screenshot+2014-07-18+17.08.29.png>
Intentionally looks fairly similar to current panes but we
can sex them up some more if we want (easier with divs).
I can see at least 22 plugins/components using this tag atm.
Do we try migrate them all (then we'd need a "shim" type
tagset to support BC), or leave them using the current pane?
Comments/feedback please.
Regards,
T.
--
You received this message because you are subscribed to the
Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from
it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
Sent from my phone
--
You received this message because you are subscribed to the
Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it,
send an email to jenkinsci-dev+unsubscr...@googlegroups.com
<mailto:jenkinsci-dev+unsubscr...@googlegroups.com>.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google
Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it,
send an email to jenkinsci-dev+unsubscr...@googlegroups.com
<mailto:jenkinsci-dev+unsubscr...@googlegroups.com>.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to a topic in the
Google Groups "Jenkins Developers" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/jenkinsci-dev/jzTgl9hEdPM/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
jenkinsci-dev+unsubscr...@googlegroups.com
<mailto:jenkinsci-dev+unsubscr...@googlegroups.com>.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Jenkins
Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
