Ability to search for workflows
Daniel Straus
Right now in the UI you can easily search for all the workflows run for a project. However, there is no way to search for the jobs for a specific workflow. If I want to find a specific run of a job for a specific workflow there is no way to currently do this via the UI. The easiest way to achieve this in my opinion is to add another dropdown after the project one (seen below) for workflows. This way you can select the project/workflow you want.
L
Liam Sharp
We have soak test workflow that runs over night with one name, and our per commit workflow with another. First thing in the day we're having to press "See more" lots at the bottom to load in the previous days per commit workflow runs. Seems like a really obvious feature to be missing!
U
Ustun Ozgur
I was quite surprised that this is not already implemented, seems like such a common feature in other CI offerings.
R
Raghav Sai
Agreed. Would be great if we could see runs by workflow like you can in Jenkins Blue Ocean. Right now you can only see workflows per commit/schedule, which can get noisy. Filtering by workflow would allow one to see and compare runs of a workflow.
Jean-Baptiste Lasselle
I aboslutely agree with the feature request, and will one additional justification for this :
When we, in CICD, run jobs, we always actually runs thoses jobs, one after the other, as something "bigger" : what I will calll a Business Process, as defined by BPM / BPMN.
For exemple, If we run a release process in my company we are bound to run several jobs : because a "all that is necessayr to run a release, cannot be versioned in one single git repository".
Why not one single git repo ? Well I would say, for example, and most important point, that we split our source code into several git repositories. And we do not want mono repo pattern :
=> Yes many projects choose the mono repo pattern, to simplify their CICD and versionig policy management
=> But the bigger the source code is :
===> the longer, the Pipeline execution is (not uncommon to see pipelines running for 8 hours, or a lot more)
===> long pipeline executions means extremely long and difficult to analyze, logs (so how do we trouble shoot CICD? imagine the developer browsing tens of thousands of lnes to find one, small error message)
===> One pipeline execution , is one single point of failure : we are tofay in the world of resilient distribuited software, where is CICD in this world ? Monorepo induces single point of failures in CICD Systems. Such a shame, in world of CICD definitely into Kubernetes.
So ok, I wil not go further here developing my opinion about the matter : What I want to state here, is that there are strong reasons why, today, one single CICD Business Process Execution runs several jobs, across several git repos.
And this is why i propose the author of this feature request, to exetend it as such :
That in the Circle CI Web UI, in the dashboard view, with "All pipelines" selected, one can sort all pipelines executions (on all git repos), by Circle CI Workflow name, same with Circle CI Job name.
Finally, I want to point that if so many other people are suppporting this feature to be able to search workflows across different git repos, well it might probably be because "they want to see one thing that they do across several git repos". And I will risk assuming that this one thing they want to have a view on, whgich is happening on several git repos, is a Business Process, as meant by BPM/BPMN, iwhere the professional filed is CICD, instead of Health care like in HL7.