Include workflows triggered by tag pushes in the insights API & Dashboard | Voters

Include workflows triggered by tag pushes in the insights API & Dashboard

in progress

Angelisa Candler

At this time, the Insights API excludes workflows triggered by tag pushes. Adding this feature will allow customers to view workflows, including those triggered by tags via GET /insights/{project-slug}/workflows rather than having to query all pipelines.

CCI-I-1413

March 9, 2020

Dawit Gebregziabher

marked this post as

in progress

Andy [[Unknown]]

Hi, This seems like a fairly glaring omission and not a feature that require voting.

Given the trend towards single trunk based monolithic repository based source management, this seems like a liability for Circle with respect to alternative vendors. Looking at workflow history tracking is problematic enough as it is.

Justin Comins

This would be very useful for my org. We just setup tags with stage and prod, and now we can't easily access the test cases without going to

all branches

and scrolling across many pages.

searching by tag would solve my problem too

Dawit Gebregziabher

Merged in a post:

Show tags in Insights

Daniel Tomas

Currently, it is not possible to show insights for tags. It would be greate if we could show all tag insights since those are the ones we use most often

December 21, 2020

April 21, 2022

Dawit Gebregziabher

Merged in a post:

Query Build & Insights API by tag

Sasha Gerrand

Ability to query Insights by tags as well as branches. We run workflows for deployments which are triggered by a git tag. We're currently unable to view performance data for these tags via the Insights UI or API.

Related to this, we can currently only view the build runs for git tags by not scoping results to a branch and searching for the tags in the list of builds. We'd like to be able to scope the builds by git tags as well as branches.

October 5, 2021

April 21, 2022

Dawit Gebregziabher

Merged in a post:

Search branches - search also by tag

Boaz Shalom

April 7, 2022

April 21, 2022

Ethan Jones

+1. Orgs that use trunk based development are especially likely to trigger workflows on tags.

Ethan Jones

+1 This would be very useful for us.

Parker Self

+1. Our deployment workflows run based off of tags, which makes them the one's we are most interested in having insights for

Jesse Price

Our most critical builds are tagged builds, so the insights feature is not as helpful as it could be for us.

→