Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Gavin Mogan
    @halkeye
    side note, getting my demo site to install incrementals is exactly why the jenkins helm chart now has plugin manager cli tool working
    so its already paid off
    Félix Queiruga
    @FelixQueiruga_twitter
    I'd love to be able to build a react widget to list builds to replace pipeline-stageview, and i think graphql would help there
    Oleg Nenashev
    @oleg-nenashev
    It would be awesome @halkeye @cliffmeyers . Happy to try out any PoC. Such widgets could be also useful outside Jenkins, e.g. o dashboards or on a standalone UI (e.g. for Jenkinsfile Runner)
    @timja @FelixQueiruga_twitter would you be fine if I update https://issues.jenkins.io/browse/JENKINS-56109 and https://issues.jenkins.io/browse/JENKINS-64142 with big and visible issue reporting guidelines. It looks like current community ratings are not very helpful to discover and prioritize new compat issues
    1 reply
    Tim Jacomb
    @timja
    @oleg-nenashev go for it
    Tim Jacomb
    @timja
    @oleg-nenashev I added some but feel free to tweak
    1 reply
    Gavin Mogan
    @halkeye
    @FelixQueiruga_twitter https://graphql-jenkins.g4v.dev/graphql/client okay, fixed the javax issue
    my local dev copy is having issues with actions {} but that one seems to work, so its not perfect yet
    Félix Queiruga
    @FelixQueiruga_twitter
    looks good, I'll try to play a bit more with !
    Daniel Beck
    @daniel-beck
    FYI https://issues.jenkins.io/browse/JENKINS-64252 tables-to-div problem without any plugins
    26 replies
    Tim Jacomb
    @timja
    Lot of companies and frameworks dropping IE11 support recently, https://twitter.com/swyx/status/1260627626739130369?s=21 is it something we would be interested in doing?
    we could stop adding css variable fallbacks, polyfills, and target more modern js for smaller bundles
    Félix Queiruga
    @FelixQueiruga_twitter
    IE11 has been "dying" for years. I don't think we should drop it's support. It's not that problematic to support it if we deal with webpack modules etc.
    One thing to keep in mind is that in some cases, the kind of company / organization that uses jenkins is the kind of org that does not upgrade their browsers, or where sysadmins control upgrades with an iron fist
    I know that's the case at least in Spain, where even the government is using both Jenkins and IE11
    we could stop adding css variable fallbacks, polyfills, and target more modern js for smaller bundles
    we could start by minifying hudson-behavior & family, that could reduce more JS load than any other changes combined IMO
    Tim Jacomb
    @timja
    if they don't upgrade their browsers are they updating jenkins?
    Félix Queiruga
    @FelixQueiruga_twitter
    I'll tell of what I know:
    • Certain regional government is forced to use IE11 because legacy apps they use only work there. They can update other infra but if they upgrade browsers, they will simply not be able to run essential software
    And I'm sure that's the case in bigger companies as well
    IIRC, the use of IE11 was also bigger in East Asia, but I'm not sure about that.
    Tim Jacomb
    @timja
    Microsoft has added IE tab to edge I believe to solve that issue
    Félix Queiruga
    @FelixQueiruga_twitter
    :shrug: I don't know. I don't think supporting IE11 is that big of a problem anyway
    Especially if we manage to move all existing JS to webpack
    Tim Jacomb
    @timja
    sure
    Félix Queiruga
    @FelixQueiruga_twitter
    Tim Jacomb
    @timja

    I've added how to triage someone else's issue to the main tables to divs issue, https://issues.jenkins.io/browse/JENKINS-64072?focusedCommentId=401604&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-401604

    if anyone has time triaging some of them would be appreciated :)

    1 reply
    Tim Jacomb
    @timja
    and jfrog fixed artifactory plugin btw :)
    Félix Queiruga
    @FelixQueiruga_twitter
    nice!
    Tim Jacomb
    @timja
    I also found that quite a few of the open issues in tables to divs had fixes opened but jira hadn't been updated :joy:
    Félix Queiruga
    @FelixQueiruga_twitter
    haha
    I'm going to add a small triage section to the SIG meeting, to go over some tickets if we have time
    Tim Jacomb
    @timja
    sure
    Félix Queiruga
    @FelixQueiruga_twitter
    I have added 2 that I think are sort of critical . I took a look at the dashboard and most of them are stuff like normal plugin failures
    Can you think of any critical issue we should look into?
    Tim Jacomb
    @timja
    the plugins :)
    I haven't seen a user report an issue for core, they've all been plugins
    Félix Queiruga
    @FelixQueiruga_twitter
    The three that I put on the agenda relate to core
    I worry about the drag & drop one especially
    naiksanjay76
    @naiksanjay76
    HI All
    I need to change Email Receiver display name in Jenkins. I want to set display name as different Name like DEV OPS. I had done configuration in manage jenkins E-mail Notification. Please let me know the configuration to do this changes.
    Gavin Mogan
    @halkeye
    @naiksanjay76: not sure why your asking this special insterest group, I would recommend the general support in #jenkinsci/jenkins
    唐 明
    @hummerstudio
    I see the proxy setting in pluginManager/advanced page, while in CasC ‘proxy' is not in ‘updateCenter’. Is this setting global? Maybe we can move proxy setting section to Manage Jenkins page.
    3 replies
    naiksanjay76
    @naiksanjay76
    @halkeye :- Sorry for asking question on wrong group. Could you please share me correct link for General Support in #jenkinsci/jenkins
    Gavin Mogan
    @halkeye
    I wonder if it's worth planning for 3.x or even 4.x and having more drastic breaking changes like flat out removing prototype
    I'd love to see things as reusable web components
    Félix Queiruga
    @FelixQueiruga_twitter
    I think that'd be great. But realistically we would need to give a > 1 year deprecation notice for prototype
    Ullrich Hafner
    @uhafner

    A small addition to our icon discussion in the SIG meeting on Wednesday (it was a little bit hard for me to follow the discussion since I needed to take care of my children in parallel :smile:) I think both FontAwesome and Material Design provide a lot of good looking icons. I prefer the style of FontAwesome: they also seem to have more useful icons (for Jenkins), have an active community to get new icons designed, etc. But I think that by using Material Design we also would not do something completely wrong.

    However, before we now start to replace icons in PRs we should go one step back and think about that in more detail. Otherwise we would get the same design diversity as we have now with some Tango icons and a lot of icons from varying sources. Where do we need icons in the upcoming Jenkins versions? I know we need a build status, alerts (warnings, errors, etc.) actions like search, copy, edit, etc. But where else do we need icons? Do we still want that every plugin action provides UI elements that use icons? How can we achieve that so that the UI still looks consistent? Maybe it would be helpful to make a list of elements that currently use icons and show which of these icons can be replaced by existing icons of the icon libraries (FontAwesome or Material Design). If there is no existing icon, how can we get one? Do we have designers on board? Do have have supporting companies that would sponsor the design of a consistent icon set? Can we follow a way similar to FontAwesome (with Crowdsourcing?)… Sorry a lot of questions, for which I do not have an answer yet.

    Ullrich Hafner
    @uhafner

    I’m currently fixing some small bugs in my warnings plugin due to the table to div conversion. Is it intended, that the font of the label is 14px while the font of the description text is 16px? In most cases the labels are more important than the descriptions.

    And another question related to the new layout: now that the label is above the input field there is much more space available for the label text. What is the idea for form controls now: should we rework labels and descriptions so that the label gets a longer text and maybe the description can be removed at all? Or should labels still be as short as possible. It would be helpful if we would provide some guidelines on how to create good and consistent forms...

    1 reply