Expose more attributes in pipeline execution history
under review
N
New Cricket
Currently, the pipeline execution history exposes a lot of set fields (e.g. env details, service for CD) that makes it easy for users to find which executions were tied to a specific env or service.
The ask is to expand this exposure so that custom attributes can be then searchable. Harness pipeline tags do not quite fit the use case as it is not possible to dynamically add a tag to an execution after the execution kicks off - the tag structure is too rigid to set this.
Use case 1:
In CI, I dynamically build a number of packages, which is determined programmatically, so it is not directly injectable as an input. One of my steps outputs the list of successfully/failed packages. I would like to "tag" my execution with this array of package names so that in the future, I can search the history and see some of the following metrics for which pipeline executions:
- built x,y,z package
- built a/x,y,z package last
- failed to build x,y,z package
etc in a similar manner to how I can search deployments to "prod" today.
Log In
Rohan Gupta
Merged in a post:
The filters applied to the Execution History for remote pipelines are causing confusion.
P
Pink Salamander
The filters applied to the Execution History for remote pipelines are causing confusion.
When switching from Pipeline Studio to Execution History, Harness by default uses the same branch in Execution History, which only displays the execution history for that specific branch. If the user is unaware of the branch name, they may not be able to see the latest execution.
N
Nofar Bluestein
under review