Where communities thrive

Join over 1.5M+ people
Join over 100K+ communities
Free without limits
Create your own community

Explore more communities

jenkinsci/ux-sig

Special interest group for the Jenkins user experience

People

Repo info

Activity

Stuart Rowe

@stuartrowe

Hi, we’ve just upated to Jenkins LTS 2.235.1 and noticed an issue with the BFA plugin after the typography changes. The FailureCauseBuildAction Summary is using h2 and h3 tags making the failure indication text very large compared to everything else on the build summary page. I’m just curious how the typography changes affected h2 and h3 tags and what would be the proper way to fix this in case I want to submit a PR to BFA.

11 replies

Jeremy Hartley

@jphartley

The 16th edition of the Jenkins UX SIG took place yesterday. We are really starting to get to a core group and I am happy that it far from being all CloudBees folks.

This edition saw Félix Queiruga provide an overview of the work that has been going on integrating the table to div migration. There was also an overview and discussion about the table look-and-feel restyling. It finished with reviewing Tim Jacomb’s work on the Black Theme.
The recording of the Jenkins UX SIG meeting is available: https://youtu.be/43-sDEgbUwk as well as very detailed minutes: https://docs.google.com/document/d/1xA6UN7ORv3OFYBC3Kw6y4mtqDekAjwYVNhsrH4PBwBk/edit#heading=h.l9ztccigxec5.

Thanks @josephbrueggen_twitter and @FelixQueiruga_twitter for doing a great job leading the conversation and taking the minutes. As well as all of the other contributors of course such as @timja, @uhafner and @oleg-nenashev to name a few.

Stuart Rowe

@stuartrowe

Tim Jacomb

@timja

anyone able to review jenkinsci/jenkins#4820 please?

Félix Queiruga

@FelixQueiruga_twitter

Floating some widget ideas, how would you feel about a bigtable jelly widget?. Some variant styles would be applied as props instead of CSS classes from a user perspective. I was thinking something like

<l:bigtable sortable="true" striped="<odd | even>" headerColor="<dark | light | white>" compact="${iconSize == '16x16'}">

1 reply

Félix Queiruga

@FelixQueiruga_twitter

@uhafner I'm trying to build the bs4-api plugin locally playing with the etc/custom.scss file a bit. Do I understand correctly that we cannot really use that file and that we need to build bootstrap out of the project and then manually edit it?

5 replies

Félix Queiruga

@FelixQueiruga_twitter

Captura de pantalla 2020-07-14 a las 16.46.58.png

12 replies

Oleg Nenashev

@oleg-nenashev

Update for the Plugin Management UX roadmap item: jenkins-infra/jenkins.io#3524

Félix Queiruga

@FelixQueiruga_twitter

Captura de pantalla 2020-07-20 a las 10.37.02.png

5 replies

Captura de pantalla 2020-07-20 a las 10.37.15.png

Tim Jacomb

@timja

https://github.com/jenkinsci/jenkins/blob/5db90b704f27a8ffab79e0b317ce39aa0e485197/core/src/main/resources/hudson/model/AllView/noJob.properties#L34-L33

Jeremy Hartley

@jphartley

The recording of the UX SIG Meeting is now available on YouTube: https://youtu.be/IpJUT0Oqs9U

During the meeting we discussed the designs for the Welcome Screen which is showed to first time users. There was a short update on the Table and Tabs redesign which has just been merged as well as the table to div migration. There was quite some discussion about themes in general and their supportability. Tim Jacomb gave an update on the Black Theme which had just reached 0.0.5. The meeting finished with a short discussion about the future direction now that most of the generic components had been updated.

Full minutes are available at: https://docs.google.com/document/d/1xA6UN7ORv3OFYBC3Kw6y4mtqDekAjwYVNhsrH4PBwBk/edit#heading=h.1dgzdiri6rye

Ullrich Hafner

@uhafner

@FelixQueiruga_twitter The meeting time was quite limited yesterday so I did not have the time to ask why was Bootstrap not an option when your team started with the redesign. We already use the grid and some components (like alerts). I’m also using Bootstrap without problems in plugins that visualize build results. Fonts and colors and things like states have been carefully chosen by the Bootrap team. From my understanding they have quite a good experience on how to design good web UIs...

10 replies

Wadeck Follonier

@Wadeck

(Disclaimer: I have not followed recently the changes)
Is it expected to have a black color for the top header and a "close-to-be-black" color for the new table headers? It feels weird.

3 replies

gitlab-

@gitlab-_gitlab

will https://github.com/jenkinsci/dark-theme-plugin/releases/tag/0.0.5 become a default option or will that stay a plugin?

Tim Jacomb

@timja

@gitlab-_gitlab potentially it will move into Jenkins at some point

for now the ux-sig doesn't want to have to support the dark theme on it's ux rework of Jenkins

so it'll remain a separate plugin in the short term

and hopefully eventually be included by default

Félix Queiruga

@FelixQueiruga_twitter

and hopefully eventually be included by default

That's the endgoal IMO. Dark theme should be "productized" and integrate into Jenkins core proper for it to be robust

Tim Jacomb

@timja

ha just started an instance with no plugins, think the text might have got broken in the table re-work :p

"No plugins installed" is there but very faint

Félix Queiruga

@FelixQueiruga_twitter

Trying it right now, opening :thread:

5 replies

Félix Queiruga

@FelixQueiruga_twitter

@timja there's an ATH fork branch with tables to divs fixes on @alecharp 's repo: https://github.com/alecharp/acceptance-test-harness/tree/table-to-divs-fix

Is there any chance we can have a mainline branch on ATH's repo parallel to master to integrate these changes?

Tim Jacomb

@timja

@FelixQueiruga_twitter there shouldn't be a need to do that, all ATH changes need to work on both old and new versions

should just integrate the fixes as we go

Félix Queiruga

@FelixQueiruga_twitter

okk

Tim Jacomb

@timja

i.e. @alecharp 's change there isn't backwards compatible

this PR here does @alecharp 's fix in a backwards compatible way: https://github.com/jenkinsci/acceptance-test-harness/pull/598/files

Tim Jacomb

@timja

@FelixQueiruga_twitter out of the ATH failures I checked the plot plugin is the only one left that I found an issue in

i fixed a couple of issues in core, and the promoted-builds plugin

Félix Queiruga

@FelixQueiruga_twitter

Just saw it, quite some effort :muscle:

Tim Jacomb

@timja

they're mostly very small quick patches

fixes are all quite similar

at least the ones with tests failing

Félix Queiruga

@FelixQueiruga_twitter

So the conditional selectors for tables and divs work in both situations?

Tim Jacomb

@timja

yes

@FelixQueiruga_twitter ^^

it's a very common pattern in ATH

for there to be up to 4 selectors :p

which work across multiple versions

and the first match will be used

Félix Queiruga

@FelixQueiruga_twitter

didn't know that tbh

Tim Jacomb

@timja

Hi ya,
I'm planning to demo a backstage Jenkins plugin I've made at the sig meeting tomorrow:
spotify/backstage#673

Just posting in here in case anyone else might be interested in seeing it

18 replies

Félix Queiruga

@FelixQueiruga_twitter

oh cool

Baptiste Mathus

@batmat

I've created https://docs.google.com/spreadsheets/d/1cILB7gxxwx3FgVbujlEXx20HHVNC5fmEphWbn-F0_AY/edit?usp=sharing quickly, in case this can help looking at next potential candidates for UI/UX improvements. Rationale being: if it proves that the next biggest wins are not in Jenkins Core anymore with the work already delivered, it might be that improving the most installed plugins is the next right move. (because in the end, only experts know/care that this is a plugin. If a plugin is installed on 99.99% of instances phoning in, this plugin is Jenkins as much as its 'core' for what users are concerned about)