108
Need view to see all Jobs/Workflows for a tag
B
Ben
You are able to see all workflows/jobs for a given branch by going to https://circleci.com/gh/{org}/{project}/tree/{branch} such as https://circleci.com/gh/socialtables/ent-killer/tree/master
It would be extremely useful to see a list of all tagged jobs/workflows for all tags. We use tags to trigger staging/production builds and have no way of visualizing a record of all workflows/jobs of this type.
Added filtering to be able to get workflows that have done a certain step would also be very useful. For us, viewing all workflows that have succeeded job deploy-production would allow us to fully use Circle to manage deploys.
CCI-I-621
Col
I simply cannot comprehend how this is still not supported by CircleCI. 😞
E
Edrick Leong
For those using GitHub, I created an extension called "GitHub to CircleCI" which allows you to open a CircleCI project from a GitHub release.
The extension will only display pipelines matching the release tag. It does this by automatically searching through pages until it finds a matching pipeline.
Robert Wiesner
If we get 100 votes it will be implemented right?
Nikhil Vandanapu
Robert Wiesner: I just created an account to give it the 100th upvote. Hopefully they'll do something about this.
S
Sebastian Lerner
open
This was mistakenly marked as complete, re-opening as this is not complete.
This post was marked as
complete
C
Christopher Corea
I see this was marked as complete, but what does that mean? Is this feature scheduled or has it already been released?
C
Christopher Corea
For anyone interested in following this, I've opened a question/"discuss topic" in the community forum: https://discuss.circleci.com/t/filter-pipelines-and-workflows-by-tag-on-a-projects-dashboard/48426
P
Payton Green
This would be hugely helpful for my company's workflow, and I have to imagine not too much different than existing branch filtering features?
Alex
This would also be extremely useful to us. I just spent 10 minutes finding out the status of a release from earlier this week, which should have taken seconds.
Joe Atzberger
Using git tags to produce release artifacts is a best practice, but Circle treats git tags as an afterthought, resulting in all manner of undesirable downstream effects. The filtering for even triggering a CI run based on tags is counter-intuitive, hard to combine with other features, requires clumsy composition, etc.
Then, when CI targeting is resolved, actually finding the results in the UI is intractable!
Robert Wiesner
Still relevant and missing
Oliver Tosky
+1 for the same deployment reasons stated by everyone else
Load More
→