Hey everyone, I've been trying out the new Hailuo UI for the last couple of weeks on our staging pipelines. I was really excited when I saw the announcement, but honestly, I'm finding it a bit frustrating to work with daily.
The main thing I'm noticing is that everything feels slower. Just navigating between pipeline views, or expanding a job to see the logs, there's a noticeable lag that wasn't there before. My connection is fine, so I don't think it's on my end. It also feels more cluttered—like there's more information crammed into the same space, but it's harder to find what I need quickly. For example, finding the "Retry Job" button or the artifact downloads seems to take an extra click now.
As someone still getting their head around CI/CD best practices, a clear and fast UI is super important for debugging. When a pipeline fails at 2 AM, I don't want to be fighting the interface. Has anyone else experienced this? I'm curious if it's just me or if others are seeing the same performance hit.
From a DevOps perspective, I'm also wondering if there are new API endpoints or if the existing ones have changed with this UI update. I haven't dug into that yet. If the web UI is slower, I might just rely more on the CLI, but that's not always ideal for the whole team.
Learning by breaking
I've been analyzing the performance regression as well, and it aligns with what you're seeing. The lag when expanding job logs is likely due to the new UI fetching additional metadata and rendering more detailed component trees before displaying the core content. It's a common trade-off when moving to a component-rich framework.
Regarding the API, I checked the changelog, and the underlying REST API endpoints are unchanged. The slowness is isolated to the frontend client. This is actually a critical point: if your monitoring or automation scripts use the API directly, they won't experience this performance hit. You could consider using the API for late-night debugging until the UI performance is optimized.
The clutter you mention, specifically the extra click for "Retry Job," is a design choice to reduce visual noise, but it fails for high-frequency actions. I've provided that feedback to their team. For now, bookmarking the direct API endpoint for job retries might be a faster workaround for those 2 AM scenarios.
Data is the new oil – but only if refined
That's exactly what I've noticed too, the lag when trying to check logs is really disruptive. It's frustrating when you're trying to solve a problem quickly and the interface gets in the way.
You mentioned the "Retry Job" button, and I completely agree. I spend half my day in project management tools where efficiency is everything, so that extra click feels like a real step back. It sounds like user747 might have a workaround with the API, but honestly, not everyone has time to jump over to API scripts for basic tasks.
Do you know if there's a setting somewhere to switch back to the old view, even temporarily? Or are we stuck with this until they release a fix?