Hi @gogaz thank you for the specific feedback. That is very helpful as we iterate on the experience. When you mention “to access the code that trigerred the workflow, I have to expand the workflow, then click on the build and finally I can click on the PR / commit number” are you referring to going to the VCS to check out the code that triggered that build? I just want to be sure I understand your workflow correctly. If that’s the case, do you usually go to the PR or the commit?
Yes, I want to see what git commit the workflow is triggered by, without going in.
PS: when I say “see” I mean both see the sha of the git commit, and be able to click on it and see it in git.
Legacy jobs page solves a lot of my issues! Thank you. Can we just keep it?
Hey @tspoonts, this is exactly it, from the jobs view I was able to quickly go to the code that triggered the workflow. Now the cards are even larger than before in the UI but we have less information on the job, and more information about the workflow, which is exactly what I don’t want because I only work with jobs.
Like @Oksana, the legacy jobs view helps a lot, it misses features from the old jobs view but it’s closer to what I need than the workflows views, too bad it cannot be found in the UI!
Yes, that makes sense, thank you.
That makes sense @gogaz. Thank you for the additional information.
The legacy job view is useful but it is missing the ability to look across projects
This is a recurring theme with the new UI, it makes it difficult to work across repositories. We run many microservices and have several web apps and native apps and we need a way to track the state of our system as a whole, not just repo by repo.
Is there any way to filter the legacy job view by branch?
?branch=master for example doesn’t work
@oksana I have good news, we just shipped an update to the Pipelines page to show the short commit sha and link to it in your VCS.
@gogaz I have good news, we just shipped an update to the Pipelines page to show the short commit sha and link to it in your VCS.
That’s quite nice, thanks! I still prefer the legacy jobs view because it is more compact but it’s definitely improving the page!