Feedback on Cloud UI / DX

[flint ridge]

it would be great to have a DAGGER_LOCAL_TITLE env var to set it in the cloud UI

also adding if git is dirty or not, as a column

or maybe these are values we can set with connect?

being able to set labels (key/value) on a build too

[muted tartan]

I added such filters to Jenkins Blue Ocean - when it was being built - so I agree @flint ridge this is super important!

Is the UI open source? can we add that feature? 🙂

[flint ridge]

I don't think it is open source

[muted tartan]

I didn't check the cloud UI yet, still deep into SDK mode so far. Will check it soon.

Want to showcase it to a large audience later this week

[spring token]

Thanks for the feedback! The UI isn't open source. I agree that the click-to-filter UX isn't great. We're planning to add an inline search and filter box. Please share if you have screenshots of UIs you love that do this well. We had a filter box before, but it wasn't very easy to use. We chose to go back to a more straightforward approach and revise the design.

cc @zealous sandal

We also have a new view for showing your runs rolled up by pull requests and GitHub Actions workflows (with statuses). We're taking feedback now on that UX and will follow up with support for merge requests (GitLab) and other CI workflows.

[flint ridge]

picking column visibility & order too

[spring token]

@flint ridge, I've added your awesome ideas to our UX backlog. 😄

[spring token]

For this one, what's an example of what would you put in the env var?

[flint ridge]

Probably a single token that fits DNS rules, we use this scheme consistently through our stack for branch names, artifacts, deploy related. We have special ones for local dev work

Right now, it picks up the last commit for my local environment and uses that, which is not what I would call accurate

It create noise for that commit / title

I'm really looking for a way to differentiate local vs ci in the first / notable column, but also generally throughout the columns / metadata / filtering

[flint ridge]

it could also be a flag like -m for git, to provide an intra-commit message about what I changed since last build, but the ENV var means I can set it to the machine/user and know who/where it was created, and what state the code is in {branch/commit}-dirty

One cool thing would be to attach the current git diff when running locally/dirty repo

[spring token]

We plan this, and I totally agree. With modules (aka Zenith), we get a lot more information about the relationship of a "run" event with the set of steps, if they were local, etc.