Can somebody review jenkinsci/jenkins#6285 please. I think it is a UX issue. It causes confusion that
built-in node is called builtin in one place.
I've released theme manager with the previews support: https://github.com/jenkinsci/theme-manager-plugin/releases/tag/theme-manager-1.0
:tada:
PRs are open to all the theme plugins on the update center to migrate to the new API:
requires Jenkins 2.336
Re jenkinsci/jenkins#6338, I wonder whether we'd want to visually highlight newly added
divs in a running build's log, so it's easier to tell which log output is fresh. Like a colored background that quickly fades away or something. Thoughts?
Hi, I’d like to use the newer Jenkins build status icons as emojis in Slack notifications. I found https://github.com/jenkinsci/jenkins/blob/master/war/src/main/webapp/images/build-status/build-status-sprite.svg but I’m unable to open the SVG in photoshop / illustrator to export the various layers for each icon as a .png file. Does anyone more familiar with this kind of workflow have any suggestions?
Though afaik illustrator should handle SVG easily. You could try inkscape
Oh is that why github has trouble? Some sort of nested SVG?
Svgs are XML. You could just grab the symbol into its own file
https://github.com/jenkinsci/jenkins/blame/master/war/src/main/webapp/images/build-status/build-status-sprite.svg#L2 take that symbol block, change symbol to SVG in a new file
1 reply
I need a volunteer to run next week's UX SIG meeting (Wednesday at 16:00 UTC). I won't be available.
Request for volunteer has also been posted to https://groups.google.com/g/jenkinsci-ux/c/bqLPocQJt3Y/m/iwxMCKdOHgAJ . Person running the meeting needs access to the Jenkins Zoom account.
2 replies
I filed https://issues.jenkins.io/browse/JENKINS-68001 the other day after the recent release added a ton of padding to the project overview. I'm all for spacing things properly to make it easy to read and not slip a column or row when looking or clicking things, but it's a bit excessive, especially since that is already using the compact overview version of the project list. It makes more sense to add alternating row colors or stronger borders than whitespace around every cell.
Think the columns are part of the standard dashboard view plugin, I just added them all creating a custom dashboard view as default view. I install simple theme at some point to change some css already to remove padding and margin from the test result table and other widgets further down the page. .bigtable td, .bigtable th {
padding: 0.0rem 0.0rem; for example. Perhaps just an option to go between normal and "compact views" would suffice in this case
padding: 0.0rem 0.0rem; for example. Perhaps just an option to go between normal and "compact views" would suffice in this case
1 reply
UI considered part of UX or just general jenkinsci/jenkins chatter?
I opted for a Solarized Dark theme and the spinner GIF while watching the console log of a build is black with a white background. looks rough on a blueish background
oof, exploring static analysis warnings on a dark style is tough... they're listing file linenumbers with a dark font
Where? In the source code view? You can change the theme of the source code view to the dark theme.
:D
I was watching the pipeline job console and it had the spinner at the bottom of the screen.
I'll grab a screen shot when I get back home
re the demo today @janfaracik Perhaps you could look into considering the 'new view' and 'new agent' dialogs when redesigning the 'new item/job' dialog? They diverged in 2.0 and that's something I think was a mistake. They all have the same basic structure (select name and either type or copy source), except only items/jobs has categories grouping types. Might be good idea to make them consistent? Unsure though, perhaps groups make them too different.
If anyone wants to see how we're getting on with UI samples take a look here:
jenkinsci/ui-samples-plugin#12
You want these branches:
https://github.com/janfaracik/ui-samples-plugin/tree/overhaul
https://github.com/janfaracik/jenkins/tree/scalable-icon-support-3-custom-symbols
@timja Re https://github.com/jenkinsci/jenkins/pull/5897#issuecomment-1072129042 it would be nice if there also were some guidance when to use which. We are very weak when it comes to UI standards, and we can probably improve a lot with some basic guidance :)
