Improvement on Pipeline Execution page
long-term
R
Ruchira Bajaj
Feedback about the “Pipeline Executions” page and the “Deploy Execution History” page.
The Pipeline Executions page shows “Open” for builds triggered by a PR regardless of the current status of the PR. It seems to say the state of the PR at the time the build was triggered, which will probably always be “Open.”
The Deploy Execution History doesn’t show the artifact tag that is being deployed. This would be very helpful to allow users to see exactly what will be deployed and link that to a build and even a commit>.
Also, it would be very helpful to see the commit SHA and message associated with the artifact being deployed
Log In
M
Miniature Antlion
We have around 200 services for the one of the appCI and have added multiple input sets in one pipeline. I want to know which service we ran the pipeline for by seeing the service name value in the execution history and its difficult to identify which service ran and see the logs, so is there any workaround to get the service name value in CI pipeline. Thanks
Rohan Gupta
Merged in a post:
Pipeline execution history time range
C
Coral reef Lungfish
We are specifically looking to have the Time Range directly visible in the Execution View, rather than accessing it through the Filter tab.
Canny AI
Merged in a post:
Show tag on deployment that starts with approval
S
Sleepy Parrot
The tag to be deployed is not visible in the deployment list when the first step is an approval step. Please make it visible somewhere so that we can easier see what we are deploying
Canny AI
Merged in a post:
Artifact versions deployed should be more prominent (i.e. in slack notifications, pipeline executions, etc.)
X
Xenia silver Cuckoo
One detail that I see is missing from several places that list deployments is the artifact version that was deployed. I configured slack notifications and they all look the same, telling me a pipeline was executed, then it finished. They all look the same, with only the timing differentiating. The same goes for any view that lists pipeline executions. The primary item (the link on the left) is always the pipeline name, instead of being the artifact version or something of the sort, which would be much more helpful in identifying which one I want to click on.
Rohan Gupta
Merged in a post:
Support Artifact details as part of the NextGen Approval message
U
Utrecht blue Narwhal
Under the FF CDS_APPROVAL_AND_STAGE_NOTIFICATIONS_WITH_CD_METADATA, we currently include details of service, environment, and infrastructure definition for CD stages in approval notifications.
However there are limitations as documented here https://developer.harness.io/docs/platform/approvals/adding-harness-approval-stages/#limitations-of-cd-execution-metadata-feature-in-notifications
Artifact details are not supported currently.
Environment and infrastructure filters' details are not supported currently
"Artifact details are not supported currently" as it used to work on FirstGen.
Rohan Gupta
Merged in a post:
Ability to configure column in pipeline execution view
E
Environmental Cuckoo
Currently there are predefined columns in pipeline execution view page.
We need ability to select which columns users wants to view and the sequence.
Rohan Gupta
long-term
Thank you for your feature request we have taken this up in our backlog
Prasad Satam
under review