Hi guys.
I've just started looking into ways in which we can refresh the look and
feel of the Jenkins UI, as well as looking at tackling some of the main
usability issues. I've really only started, but have committed a small bit
of code to a branch on github
at
to collaborate.
Em 26/05/2014 10:54, Tom Fennelly tom.fe...@gmail.com javascript:
escreveu:
Hi guys.
I've just started looking into ways in which we can refresh the look
and feel of the Jenkins UI, as well as looking at tackling some of the main
usability issues. I've really only started
On Monday, May 26, 2014 7:22:31 PM UTC+1, Daniel Beck wrote:
On 26.05.2014, at 15:54, Tom Fennelly tom.fe...@gmail.com javascript:
wrote:
• New more modern icons?
IMO the background makes the icons look blander than they are. And we
should use an icon style that allows
On Monday, May 26, 2014 8:08:28 PM UTC+1, Christopher wrote:
On 05/26/2014 03:54 PM, Tom Fennelly wrote:
Hi guys.
I've just started looking into ways in which we can refresh the look
and feel of the Jenkins UI, as well as looking at tackling some of the
main usability issues
On Tuesday, May 27, 2014 7:29:54 AM UTC+1, Dominik Bartholdi wrote:
Glad to see others coming up with this topic again!
We have talked about this on many occasions and some work has been done in
a separate branch too:
https://github.com/jenkinsci/jenkins/tree/ui-changes
In JIRA we also
Hi Tyler.
Did you ever commit your experiments to GitHub? I'd be keen to see what
you did and would also be keen to hear your thoughts on the API and it's
suitability. I started a related thread (wasn't aware of this one until
now) at
Boston meeting in June, I would love to touch base
and discuss this further.
Many thanks for the brave new world of Jenkins UI proposals out there!
best regards
--Ioannis--
On Monday, May 26, 2014 9:54:21 AM UTC-4, Tom Fennelly wrote:
Hi guys.
I've just started looking into ways in which
Thanks Tyler. I now understand what you mean about the API structure.
On Tuesday, May 27, 2014 10:46:45 PM UTC+1, R Tyler Croy wrote:
(replies inline)
On Tue, 27 May 2014, Tom Fennelly wrote:
Did you ever commit your experiments to GitHub? I'd be keen to see what
you did and would
On Tuesday, May 27, 2014 10:24:33 AM UTC+1, Tom Fennelly wrote:
On Monday, May 26, 2014 8:08:28 PM UTC+1, Christopher wrote:
As you may have seen, this is something Tyler did some work on during
FOSDEM last year. The basic prototype I saw at the time was pretty
decent
On 28/05/2014 22:12, Kohsuke Kawaguchi wrote:
On 05/28/2014 02:01 PM, Stephen Connolly wrote:
Let's work together on this --- getting rid of tables in favor of
divs. It sounds like that's a necessary step to enable other
people to do more aggressive experiments.
The config
On 28/05/2014 22:07, Kohsuke Kawaguchi wrote:
On 05/28/2014 01:49 PM, Jesse Glick wrote:
It would be nice (especially if we can finally kill Auto Refresh!),
but you have to be very careful about the performance impact.
ajaxBuildQueue and ajaxExecutors already impose a significant burden
on the
On 29/05/2014 02:57, Michael Neale wrote:
On Thu, May 29, 2014 at 11:33 AM, Christopher Orr ch...@orr.me.uk
mailto:ch...@orr.me.uk wrote:
It may also be worth considering Server Sent Events — basically
one-way push from the server, without all the handshaking and
protocol
should be there.
So I don't think the API necessarily has to be RESTful — from what I
understand, Backbone expects data to be structured in a certain
format; other JS frameworks like AngularJS don't make this distinction.
On 05/28/2014 11:08 AM, Tom Fennelly wrote:
Thanks Tyler. I now
On 29/05/2014 09:01, Michael Neale wrote:
On Thu, May 29, 2014 at 5:26 PM, Tom Fennelly tom.fenne...@gmail.com
mailto:tom.fenne...@gmail.com wrote:
AFAIK... any proxy/gateway between the websocket client and server
needs to be pretty much websocket aware. SSE would seem like
On 29/05/2014 17:51, Kevin Burke wrote:
Hi! I am the author of Doony http://github.com/kevinburke/doony, a
skin on top of Jenkins that's been downloaded/used by developers at
EBay, Instagram, Netflix, the BBC, Panic, and other web companies, and
starred by over 600 developers on Github. We
On 30/05/2014 07:06, Michael Neale wrote:
On Friday, May 30, 2014 2:51:15 AM UTC+10, Kevin Burke wrote:
Second, I use Travis CI for building most of my Github
projects, but one of my biggest frustrations with it is its
occasional ability to pin a CPU, render a completely blank
@googlegroups.com] *On Behalf Of *Tom Fennelly
*Sent:* den 29 maj 2014 10:27
*To:* jenkinsci-dev@googlegroups.com
*Subject:* Re: Refreshing the Jenkins UI
On 29/05/2014 09:01, Michael Neale wrote:
On Thu, May 29, 2014 at 5:26 PM, Tom Fennelly
tom.fenne...@gmail.com mailto:tom.fenne...@gmail.com
on the Jenkins API and they want to use
something like AngularJS ($resource + other bells and whistles). I
think this was the point that Tyler was making.
On 02/06/2014 21:23, Jesse Glick wrote:
On Thu, May 29, 2014 at 3:37 AM, Tom Fennelly tom.fenne...@gmail.com wrote:
These only work
On Monday, June 2, 2014 11:50:03 AM UTC+1, Tom Fennelly wrote:
As suggested by others, I think it would be a good idea to bite off
smaller chunks where we can so as to make progress. So, maybe we could
start by adding Doony and then look at making some of the above
improvements, right
On Wednesday, June 4, 2014 12:05:18 PM UTC+1, Tom Fennelly wrote:
On Monday, June 2, 2014 11:50:03 AM UTC+1, Tom Fennelly wrote:
As suggested by others, I think it would be a good idea to bite off
smaller chunks where we can so as to make progress. So, maybe we could
start by adding
On Thursday, May 29, 2014 7:31:35 PM UTC+1, Tom Fennelly wrote:
Hi guys.
As Kohsuke suggested, it would be a good idea for as many of us as
possible to hook up on google hangout to have a chat about this, maybe do
some hacking and bounce some ideas around. I'm aware there's a Jenkins
On Wednesday, June 4, 2014 12:05:18 PM UTC+1, Tom Fennelly wrote:
On Monday, June 2, 2014 11:50:03 AM UTC+1, Tom Fennelly wrote:
As suggested by others, I think it would be a good idea to bite off
smaller chunks where we can so as to make progress. So, maybe we could
start by adding
On Wednesday, June 4, 2014 8:53:59 PM UTC+1, Jesse Glick wrote:
On Wed, Jun 4, 2014 at 1:58 PM, Tom Fennelly tom.fe...@gmail.com
javascript: wrote:
I have a test instance running here: http://166.78.9.27:8080/
The added message
Build #5 created, you will be redirected when
On Friday, June 6, 2014 3:58:47 PM UTC+1, mambu wrote:
Hi,
I like the idea.
Talking about plugins... The dashboard-view-plugin requires the tables
that are currently created by Jenkins in order to work (i.e. I add tr
without a table because I am already rendering inside a table).
Just
All the icons in Jenkins are hardcoded as images in the Jelly scripts. We
were hoping to move away from this (ala Doony) by using CSS + some
Javascript (for the animation). Seems like this is not possible to do
without getting into screen-scraping hacks
On 07/06/2014 16:17, Daniel Beck wrote:
On 07.06.2014, at 13:14, domi d...@fortysix.ch wrote:
I'm sure plugins which do not look nice with the new style will be changed soon.
It'd be best if core provided CSS/JS equivalent images (it doesn't need to use
them itself) so plugins referencing
that plugin maintainers don't feel
the need to change anything ;) I guess we can always crawl the repos
for plugins that use img and open a generic ticket for each (or
something like that).
On Sun, Jun 8, 2014 at 4:56 AM, Tom Fennelly tom.fenne...@gmail.com
mailto:tom.fenne...@gmail.com wrote
I created a simple plunker to try test browser compatibility for the
specific CSS3 animation I'm looking to use to (to replace the JS version
from Doony).
If you have a few mins, please browse to the plunker using whatever
browsers you have and filling in the form:
Sorry... they must disable the run after a while
http://plnkr.co/O1KfxBES2nt1guhVMBty
On 09/06/2014 08:11, d...@fortysix.ch wrote:
Tom, the given plunker URL does not work anymore...
On 08 Jun 2014, at 16:10, Tom Fennelly tom.fenne...@gmail.com
mailto:tom.fenne...@gmail.com wrote:
I
Not sure if this is normally the place to mention stuff like this, but
*.jenkins-ci.org seem to be unstable for the last day
(updates.jenkins-ci.org etc). What normally happens to investigate +
rectify this?
Regards,
T.
--
You received this message because you are subscribed to the Google
It's a PITA :)
On 17/06/2014 15:07, Jesse Glick wrote:
On Tue, Jun 17, 2014 at 10:00 AM, Tom Fennelly tom.fenne...@gmail.com wrote:
Not sure if this is normally the place to mention stuff like this
Here or in the #jenkins-infra chat room. Yes the site has been having
a lot of problems. AFAIK
Posting back here again to solicit feedback.
We've already pushed some styling tweaks into upstream master. We don't
think they'll cause too much controversy (thanks to Kevin Burke):
1. Updated buttons styles
2. Friendlier/newer form control styles.
What might be the cause of some
On Wednesday, June 18, 2014 1:47:25 PM UTC+1, slide wrote:
Is there anything that can be done about the unaligned buttons that often
appear?
Are you saying this is an issue that has been introduced by these changes,
or is it a separate comment?
--
You received this message because you are
On Wednesday, June 18, 2014 2:12:47 PM UTC+1, mambu wrote:
Hi,
Just to clarify, what do you mean with upstream? Is it the main Jenkins
branch or is there a new branch for this changes?
The upstream Jenkins repo at https://github.com/jenkinsci/jenkins
Have you tried any plugins that
On Wednesday, June 18, 2014 2:13:27 PM UTC+1, Mark Waite wrote:
Thanks very much for hosting that server. I ran the git-client-plugin
from the new user interface and found no issues with Chrome, Firefox, or
Internet Explorer on Windows 8.1.
When I displayed the same job on Chrome on my
On Wednesday, June 18, 2014 2:42:52 PM UTC+1, slide wrote:
The issue has been around for a while, I just mentioned it since there
were updates to the layout.
Thanks for mentioning it. Hopefully we'll be able to tackle issues like
that once we've sorted out the basic structure of config
...@gmail.com mailto:michael.ne...@gmail.com wrote:
On Wed, Jun 18, 2014 at 10:25 PM, Tom Fennelly
tom.fenne...@gmail.com mailto:tom.fenne...@gmail.com wrote:
Posting back here again to solicit feedback.
Looks great - I tried on chrome, safari (both mac) and iphone
On 19/06/2014 03:00, Daniel Beck wrote:
On 19.06.2014, at 01:45, Gus Reiber gusrei...@gmail.com wrote:
As a possible remedy to that bit of awkwardness, I am looking at pulling some
of the 'action' link list items out and displaying them in a global toolbar
sort of context. Jenkins
I pulled your branch and had a peek. Comments inline...
On 19/06/2014 00:45, Gus Reiber wrote:
Following Tom's lead, I am also starting to poke around at the Jenkins
UI.
My initial branch is here:
https://github.com/gusreiber/jenkins/tree/gustables
What I am most excited about in what Tom
Awesome... thank you Daniel this is really useful information. I'm
still digesting it though ;) Thanks !!!
On 19/06/2014 11:31, Daniel Beck wrote:
I think your comments were primarily targeted at his experiments with the
navigation, right? Or maybe it was both the navigation and the
Moving away from img based icons to using CSS does not mean we have to
change the actual icons that are visible to the user, so I think maybe
we can avoid a debate on that for now. I'm currently working on the CSS
to back this up and, at the moment, the user still sees the same old icons.
Btw... we created a Trello board in an effort to help track this work a
bit: https://trello.com/b/RmlNnRxq/jenkins-ui-refresh
--
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,
Hi.
After making a series of Jelly script changes, I'm now getting regular OOM
failures from
AbstractProjectTest.testConfiguringBlockBuildWhenUpstreamBuildingRoundtrip
(in the test harness) Here's the branch
https://github.com/tfennelly/jenkins/tree/icons-via-css. I can solve by
setting
Yeah, I think it's just a simple case of these changes blowing the memory
profile of the test over the edge of what's available to the vm. As I
said... I saw a few random failures on this test in the last week.
I'll pull that change out into a separate fix.
--
You received this message
Sorry... here's the trace...
java.lang.OutOfMemoryError: Java heap space
at java.util.Arrays.copyOf(Arrays.java:2734)
at java.util.Vector.ensureCapacityHelper(Vector.java:226)
at java.util.Vector.addElement(Vector.java:573)
at org.apache.xml.dtm.ref.dom2dtm.DOM2DTM.addNode(DOM2DTM.java:246)
at
On Friday, June 20, 2014 11:20:29 PM UTC+1, Tom Fennelly wrote:
Moving away from img based icons to using CSS does not mean we have to
change the actual icons that are visible to the user, so I think maybe we
can avoid a debate on that for now. I'm currently working on the CSS to
back
On Tuesday, June 24, 2014 11:30:43 PM UTC+1, Jesse Glick wrote:
Is there some new JavaScript which is trying to load HTML content from
the page for some reason?
I was going to reply and say no, but decided to check and yes, there is a
call to layoutUpdateCallback.call() on that branch.
Hi.
There's the Refreshing the Jenkins UI
https://groups.google.com/forum/?hl=en#!topic/jenkinsci-dev/zDaX4yiWLLw%5B101-125-false%5D
thread that's been going. I decided to split out a new thread for this
because the other thread has long since become a bit unwieldy.
So I've been playing
Guys, I broke out a new thread for a discussion on icons
... https://groups.google.com/forum/?hl=en#!topic/jenkinsci-dev/GOiQdvctBB0
--
You received this message because you are subscribed to the Google Groups
Jenkins Developers group.
To unsubscribe from this group and stop receiving emails
On Friday, June 27, 2014 5:22:13 PM UTC+1, Stephen Connolly wrote:
I think we are still missing something in letting people backport this to
older plugins. So from what I can see in its current incarnation we'd be
waiting for plugins to pick up this version of core.
Ah yes... I forgot to
On Friday, June 27, 2014 3:11:07 PM UTC+1, Tom Fennelly wrote:
On Tuesday, June 24, 2014 11:30:43 PM UTC+1, Jesse Glick wrote:
Is there some new JavaScript which is trying to load HTML content from
the page for some reason?
I was going to reply and say no, but decided to check and yes
So... the whole idea of the shim plugin got me thinking a bit i.e. was
there an alternative that might be a bit easier to manage. I was wondering
why not just put the icon tag in a simple taglib of it's own (Vs putting
it in Jenkins Core + requiring the shim etc).
I quickly ran the idea by
smell as sweet?
On Monday, 30 June 2014, Tom Fennelly tom.fenne...@gmail.com
mailto:tom.fenne...@gmail.com wrote:
Hi.
We're in the process of creating a new icon in the hope of
allowing more control over icons in the UI [1]. As part of that,
we want to allow plugins that adopt
Engineer - SW Environment and Product Configuration
Sony Mobile Communications
*From:*jenkinsci-dev@googlegroups.com
[mailto:jenkinsci-dev@googlegroups.com] *On Behalf Of *Tom Fennelly
*Sent:* den 1 juli 2014 00:33
*To:* jenkinsci-dev@googlegroups.com
*Subject:* New Jelly tags - via Jenkins Core
@googlegroups.com] *On Behalf Of *Tom Fennelly
*Sent:* den 1 juli 2014 12:41
*To:* jenkinsci-dev@googlegroups.com
*Subject:* Re: New Jelly tags - via Jenkins Core + Plugin shim, or
via simple Java jar dependency ??
But wouldn't that be the case anyway if we defined the base tag in the
normal way inside
to get the changes into core to release your
module
On 1 July 2014 13:20, Tom Fennelly tom.fenne...@gmail.com
mailto:tom.fenne...@gmail.com wrote:
Thanks Robert. Good point!!
So maybe what we could do then is a cross between what I was
referring to, and shim plugin i.e. a jenkins
July 2014 16:18, Tom Fennelly tom.fenne...@gmail.com
mailto:tom.fenne...@gmail.com wrote:
OK after talking to Stephen again we're heading back in the
old shim direction (he has beaten me into submission lol).
On 01/07/2014 13:53, Stephen Connolly wrote:
yep... only now you
wrote:
Do you inform jenkins that you have a taglibrary?
On 2 July 2014 23:34, Tom Fennelly tom.fenne...@gmail.com
mailto:tom.fenne...@gmail.com wrote:
Hi.
Just wondering if anyone can guide me as to how I can write a Java
based TagLibrary and have it loadable from a plugin (without
of the TagLibrary
class or else it will not discover it. I am suspecting that there
is a plugin goal putting the requisite info somewhere on the
classpath. That plugin goal is probably working for jenkins core
but perhaps not by default in plugins
On 3 July 2014 09:56, Tom Fennelly
but perhaps not by default in plugins
On 3 July 2014 09:56, Tom Fennelly tom.fenne...@gmail.com
mailto:tom.fenne...@gmail.com wrote:
xmlns:myf=jelly:org.jenkins.x.y.MyFunkyTag is one way of
doing that and, as I said, that works when the TagLibrary
the
requisite info somewhere on the classpath. That plugin
goal is probably working for jenkins core but perhaps not
by default in plugins
On 3 July 2014 09:56, Tom Fennelly tom.fenne...@gmail.com
mailto:tom.fenne...@gmail.com wrote
is probably working for jenkins core but perhaps
not by default in plugins
On 3 July 2014 09:56, Tom Fennelly
tom.fenne...@gmail.com
mailto:tom.fenne...@gmail.com wrote:
xmlns:myf=jelly:org.jenkins.x.y.MyFunkyTag
it?
On 3 July 2014 12:01, Tom Fennelly tom.fenne...@gmail.com
mailto:tom.fenne...@gmail.com wrote:
Sure:
* Branch: https://github.com/tfennelly/jenkins/tree/icon-tag
* Taglib classes:
https://github.com/tfennelly/jenkins/tree/icon-tag/icon/src/main/java/org/jenkins
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
of jenkins just to get the icons using the
tag.
On 27 June 2014 16:51, Tom Fennelly tom.fe...@gmail.com javascript:
wrote:
Hi.
There's the Refreshing the Jenkins UI
https://groups.google.com/forum/?hl=en#!topic/jenkinsci-dev/zDaX4yiWLLw%5B101-125-false%5D
thread that's been going. I
There a PR for this now: https://github.com/jenkinsci/jenkins/pull/1336
Hopefully we can get it in or just decide to not do it at all... it's been
dragging on way too long.
--
You received this message because you are subscribed to the Google Groups
Jenkins Developers group.
To unsubscribe
Hi.
Kevin created a PR some time ago re tweaking the Console Output page to
make the default output look more like
terminal: https://github.com/jenkinsci/jenkins/pull/1272
There was a fair bit of discussion on the PR but consensus was not reached.
Some people felt the changes might effect
Hi all. Thanks for your feedback. We have closed this PR. Maybe we could
do it as part of a Themes type feature, where among other things people
could select their preferred Console Output theme.
--
You received this message because you are subscribed to the Google Groups
Jenkins
Hey Bruno.
We experimented with JS based animations a few weeks ago. Perhaps you
remember. There's a branch
here: https://github.com/tfennelly/jenkins/tree/orbs-with-plugin.
I think this work could be resurrected and combined with the work you've
been doing, now that we have the l:icon tag
]
https://issues.jenkins-ci.org/browse/JENKINS-14749?focusedCommentId=198375page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-198375
Emeric
Le jeudi 31 juillet 2014 14:26:05 UTC+2, Tom Fennelly a écrit :
In particular... how far back do we want to support Internet
Right, I think this is a good approach + the caveats Daniel suggests. I
think the policy around accepting patches should be along the lines of the
level of guarantee we plan to offer e.g. for no guarantee on support we
also offer no guarantee re accepting patches i.e. if we can reasonably
Okay... really sorry about that... I did make those changes on a branch but
I should have done it on a fork. I actually did create a fork after seeing
there was a build tracking branches. Let me know if I should delete the
branch I created - I won't touch anything until you let me know what
I added a v1 of this to the wiki
at https://wiki.jenkins-ci.org/display/JENKINS/Browser+Compatibility+Matrix
Of course, feel free to make comments and edits :)
--
You received this message because you are subscribed to the Google Groups
Jenkins Developers group.
To unsubscribe from this group
That's great, thanks Baptiste.
On Tuesday, August 26, 2014 2:26:18 PM UTC+1, Baptiste Mathus wrote:
Great, thanks Tom. I just reworked the page a bit into a table to help
make the information more quickly findable by readers.
Hope this suits you and others.
2014-08-26 15:06 GMT+02:00 Tom
Good question... no reason other than being hasty. I'll update it and make
it L1. In fact... is there a need to mention it specifically?
On Tuesday, August 26, 2014 6:14:05 PM UTC+1, Daniel Beck wrote:
On 26.08.2014, at 15:06, Tom Fennelly tom.fe...@gmail.com javascript:
wrote:
I
At yesterdays governance meeting on #jenkins we talked about configuring
JIRA to provide some helpful text wrt the Components and Labels fields
to help people file issues more consistently. We talked about doing it
using Javascript hacks.
I installed a trial JIRA and was able to configure the
One of the things I'm working on is trying to convert some of the plugins
to work with workflow. Workflow is different to other Job types in a
number of ways. Jobs can be paused, failed, restarted in the middle, can
have multiple SCMs and the whole concept of the build's workspace is
Hi.
A number of issues have been raised in JIRA over the last while regarding
the Build History Widget and how the layout can go a bit screwy as more
data gets cluttered in it. Here's a few of the JIRAs
I'll be pushing PR #1470 https://github.com/jenkinsci/jenkins/pull/1470/
if I don't hear anything. Would be good if people could try it and let us
know if there are any issues. Daniel Beck has already tested it loads
already (thanks Daniel).
On Tuesday, November 25, 2014 10:23:28 AM UTC, Tom
I'm seeing this locally and I also see the same failure on a recent PR
(https://jenkins.ci.cloudbees.com/job/core/job/jenkins-core/1870/console).
Is anyone fixing this?
--
You received this message because you are subscribed to the Google Groups
Jenkins Developers group.
To unsubscribe from
Hi Michael.
Feel free to share your findings here. From that we can decide what JIRAs
need to be created etc.
Regards,
T.
On Monday, January 19, 2015 at 8:15:59 PM UTC, Michael Rumpf wrote:
Hi,
the company I work for has conducted a professional usability check of
Jenkins.
How can
Hi Michael.
Sure, create a JIRA (https://issues.jenkins-ci.org/) of type Improvement
against component core and attach the user-experience label to it (and
of course attach your docs).
I tried translating the docs by viewing in google drive but that did not
work so I need to try something
Great stuff here guys.
Hopefully we can translate some of these ideas into here into JIRA feature
tasks (if not already in JIRA) for tracking (label user-experience).
--
You received this message because you are subscribed to the Google Groups
Jenkins Developers group.
To unsubscribe from
Hi Bobby.
What do you mean when you talk about moving it out into a separate widget?
Move which parts out? Are you saying have 2 widgets, one for
in-queue/running builds and one for completed builds?
Perhaps I don't know all the use case but I was thinking (as I said in the
original email)
about that widget,
I'm rather lifting some concerns :)
/B
On Mon, Jan 26, 2015 at 9:25 AM, Tom Fennelly tom.fe...@gmail.com
javascript: wrote:
Hi Bobby.
What do you mean when you talk about moving it out into a separate
widget? Move which parts out? Are you saying have 2 widgets, one
for a bit more info on this.
On 05/01/2015 21:59, Ulli Hafner wrote:
That looks very promising!
How would this concept integrate with plus-ins? Does a theme provide
icons for plug-ins, too? Or is each plug-in providing icons for each
available theme?
Am 05.01.2015 um 18:56 schrieb Tom Fennelly
I updated the PR associated with this
(https://github.com/jenkinsci/jenkins/pull/1524). Would appreciate any
comments/suggestions. Would like to get the required changes into Jenkins
core as soon as possible.
--
You received this message because you are subscribed to the Google Groups
implementations of the interface?
On 06.01.2015, at 12:41, Tom Fennelly tom.fenne...@gmail.com wrote:
Thanks Ulli.
Plugins can contribute to a theme implementation in the very same way as Jenkins Core does.
Therefore, it can contribute icon style definitions to multiple icon theme
I got back to doing a little bit of Jenkins Core UI work in the last few
weeks. I've evolved the uithemes-plugin
https://github.com/jenkinsci/uithemes-plugin a bit further in the last
few weeks, to a stage now where (on this branch) a user can perform
personalized theme configurations such as:
successful plugins?
As always, any feedback is good feedback.
I am eager to help keep this thread near the top of this Dev list.
Thanks Again,
Gus
On Wednesday, February 18, 2015 at 8:27:12 AM UTC-8, Gus Reiber wrote:
At the end of last summer, my friend and co-worker, Tom Fennelly
https
On Saturday, February 21, 2015 at 6:08:12 PM UTC, Kanstantsin Shautsou
wrote:
@Tom, divs, css and tab it's cool, but as not UI developer i will expect
building blocks that will allow me just to use form and databinding. This
will also allow enhance/fix problems only in this block that will
Thanks Ioannis.
On Saturday, February 21, 2015 at 5:09:27 PM UTC, Ioannis Moutsatsos wrote:
I know that the fear of the unexpected consequences is always an issue.
However, given the benefits of improved an Configuration UI I think we
should be willing to take on some breaking changes. I
Yes, I think everyone agrees that the config pages are a UX nightmare. We
looked at changing how they are rendered by introducing div sections that
are then collapsible. It was somewhat of a success but what frightened me
off taking it further was the fact that it was inevitably going to break
Hi.
I'm interested in hearing how people would feel about a change to how the
BuildHistory widget handles build histories where there are 100s or 1000s
of builds. As JENKINS-26445
https://issues.jenkins-ci.org/browse/JENKINS-26445 discusses, the
performance of this widget can stink if there
Hey Gus, these look really great and would be a huge step forward imo. I
can see new users having a much easier/happier time with this ux.
In terms of styling (colour, icons etc), what you have here is very
different to what's in Jenkins atm. What's the plan there?
On 20 April 2015 at 22:41, Gus
I created PR #1641 https://github.com/jenkinsci/jenkins/pull/1641 around
efforts to address the issue of huge build histories. Hopefully there'll be
a CI build available soon (from CI PR builder).
It's a WiP but please try it out and let us know what works, doesn't work,
is missing etc
--
On Wednesday, August 19, 2015 at 1:55:58 PM UTC+1, Jesse Glick wrote:
I thought I already proposed everything that was needed here.
You did for sure. Sorry about that. I should not post late at night.
The caveat: you actually know the last version in which global
configuration was saved
On Tuesday, August 18, 2015 at 10:01:28 PM UTC+1, Tom Fennelly wrote:
Something I was wondering in order to help with upgrades ... could we use
a simple plugin that needs to be installed that captures and records all
split plugin info from the instance. This info can then be used
Something I was wondering in order to help with upgrades ... could we use a
simple plugin that needs to be installed that captures and records all
split plugin info from the instance. This info can then be used on the
subsequent install so as to install the exact versions of split plugins. An
On Monday, August 17, 2015 at 9:11:25 PM UTC+1, Jesse Glick wrote:
On Fri, Aug 14, 2015 at 5:51 PM, Kohsuke Kawaguchi k...@kohsuke.org
javascript: wrote:
when a plugin is split from core in version X, people upgrading
from a version earlier will experiene functionality loss.
Well I
1 - 100 of 223 matches
Mail list logo
