Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Daniel Beck
    @daniel-beck
    This message was deleted

    This has been intentional to make it simpler to test ideas that may or may not work - if they don’t work they have limited impact and can be iterated on quickly (such as the all caps table design, or the plugin manager search bar).

    @janfaracik (triggered by Tim's new comment on your sidepanel PR):

    What does success look like for these ideas/experiments? By when do you expect to be able to determine whether it was successful or not?

    Does core need a built-in dedicated feedback feature to allow people to provide low barrier feedback on UI experiments (and to mark experiments as such)?

    Daniel Beck
    @daniel-beck
    (The latter is based on the assumption that user feedback is an important component to success y/n)
    Daniel Beck
    @daniel-beck
    What do I need to do to build Jenkins ~2.321? I always get "Unknown Syntax Error: Unsupported option name ("--mutex")." from yarn when building the :jenkins-war.
    halkeye
    @halkeye:g4v.dev
    [m]
    @daniel-beck: i don't know specifically, but for debugging purposes, what does yarn --version give you?
    Daniel Beck
    @daniel-beck
    $ yarn --version
    1.22.10
    halkeye
    @halkeye:g4v.dev
    [m]
    oh i guess the maven front end script deploys yarn somewhere else, like node sub directory or something?
    Daniel Beck
    @daniel-beck
    [INFO] --- frontend-maven-plugin:1.12.0:install-node-and-yarn (install node and yarn) @ jenkins-war ---
    [INFO] Node v14.16.0 is already installed.
    [INFO] Yarn 3.2.2 was installed, but we need version v1.22.10
    [INFO] Installing Yarn version v1.22.10
    I guess I'm patching the pom.xml to remove this argument
    halkeye
    @halkeye:g4v.dev
    [m]
    i'm guessing its not using yarn 1.22, cause it seems like --mutex is a yarn 1 thing
    Daniel Beck
    @daniel-beck
    Perhaps mvn clean doesn't clean enough and there's stuff still around from current versions of Jenkins?
    Daniel Beck
    @daniel-beck
    it worked when patching the pom.xml, good enough for a bit of bisecting
    UX SIG feedback welcome: jenkinsci/jenkins#6986 (unrelated to previous messages)
    Tim Jacomb
    @timja
    from watching the video it seems a bit jumpy but i'll try run it locally myself later on to get a better feel for it
    Daniel Beck
    @daniel-beck
    right, I'm not even sure background is what we want. Might be a border, border-left, or something else entirely. I just think there should be some indicator for what is newly added.
    (but animation that fades to "same as everything else" seems preferable to having a fixed last-child style, that's weird in logs without new content for a while.)
    Jan Faracik
    @janfaracik

    What does success look like for these ideas/experiments? By when do you expect to be able to determine whether it was successful or not?

    Hey,

    Defining success is tricky, e.g. I can't say for a fact that users are interacting with the larger search bar more than they were. I largely view something as successful based off of the feedback from UX SIG, PRs, fellow users and comments (e.g. YouTube).

    For the screens we want to look at going forward (e.g. the project/build pages) it'd be super helpful to define a set of criteria that we can assess any changes against + some useful stats about the existing implementation. This provides us some good ground as to why we're making the change and a set of criteria to say if the changes we've made were successful, which will be helpful if we face any backlash for changing a design that's been around for over a decade (even if it has flaws).

    Does core need a built-in dedicated feedback feature to allow people to provide low barrier feedback on UI experiments (and to mark experiments as such)?

    An unobtrusive way to gather feedback in core would be great. I'm not sure what the best way to approach something like that would be as it'd have to be somewhat visible but without getting in the way of the user, nobody wants the classic Windows esque feedback popups. A 'feedback' link in the footer might be helpful.

    Hrushikesh
    @Hrushi20

    Hello World, I wanted to create a table to display git maintenance logs in UI. I planned on using the DataTable Plugin in Jenkins. While using that plugin, I am getting an import error which states that html,css & js files are not found.

    The error is caused by this line <st:adjunct includes="io.jenkins.plugins.data-tables"/>. I am currently using jenkins version 2.332.4

    Tim Jacomb
    @timja
    easier if you push an example @Hrushi20
    link a branch and instructions on how to reproduce
    Hrushikesh
    @Hrushi20
    I realized there was an error in the pom.xml file. Thank you :)
    Daniel Beck
    @daniel-beck
    Forgot to mention, but FYI: The number of UX regressions still grows and outpaces the fixes: https://issues.jenkins.io/secure/Dashboard.jspa?selectPageId=22043
    Which TBH makes me hesitate even more (difficult to imagine, but true) to merge completely new core changes…
    Tim Jacomb
    @timja
    I've pushed a commit which addresses all of the pm UI feedback except for update center breadcrumb
    any suggestions on how to make that work would be loved @daniel-beck
    or if it's a UI oddity on a dis-used page that we can accept also :D
    Tim Jacomb
    @timja
    (need to update localizations still
    Daniel Beck
    @daniel-beck
    Thank Stapler: Jenkins#getUpdateCenter
    We could migrate the UI and leave this as a UI-less class
    That would break the "Rest API" link though :-/
    Daniel Beck
    @daniel-beck
    Ah correction, breadcrumbs use Stapler request ancestors, those are independent from Jenkins model objects with conventional URLs…
    So ModelObject only controls presence in the breadcrumbs, not what the URL is.
    Daniel Beck
    @daniel-beck
    I have an idea
    (insert evil/crazy laughter here)
    it works :)
    Daniel Beck
    @daniel-beck
    @timja What do you prefer, me to just update the PR, or want a PR against Jan's PR, or just a commit demonstrating it for you to apply?
    Daniel Beck
    @daniel-beck
    GTG so enjoy: daniel-beck/jenkins@84a59b0
    Only drawback I could find so far is that /pluginManager/api and /pluginManager/updates/api are different pages, yet have the same breadcrumbs.
    Tim Jacomb
    @timja
    thanks @daniel-beck adapted and pushed!
    should be all sorted now
    cc @janfaracik
    hervelemeur
    @hervelemeur:matrix.org
    [m]
    FTR, got some funny looking "+ Add" buttons on https://infra.ci.jenkins.io/configureClouds/ (v2.364, FF v103.0.2)
    Is this known or should I open an issue?
    Alexander Brandes
    @NotMyFault
    I didn't see that before yet :eyes:
    But as little pointer, the ec2 plugin uses the logic from the credentials plugin for buttons (afaik)
    Alexander Brandes
    @NotMyFault
    Yeah, something adds a yui-button class on top of it, hence we have a button on a button. Stripping it via DOM looks as intended and uses the new jenkins-button class: https://i.imgur.com/EYs10Jm.png
    3 replies
    Hrushikesh
    @hrushi2001:matrix.org
    [m]

    Hello world. I'm currently using the data-table plugin to display the the maintenance results of caches on Jenkins controller.

    The problem I'm currently facing is I'm loading all the data at a time (100's of data) and displaying it in the table. Is there a way to load the data when required and display it in the table?

    The link to my PR is jenkinsci/git-plugin#1277

    The lastest commits contains the code regarding the data-table.

    Ulli Hafner
    @uhafner:matrix.org
    [m]
    This is supported by DataTables but I did not yet provide a Java API for such a use case. In order to use that functionality you need to write the Java API on your own.
    1 reply