pipeline status misleads into longer deployment time and does not give proper info of the process #2100
Description
When a pipeline is triggered, it might take time to complete the deployment process given if another deployment is still in progress. This confuses the user with the application status. To update the timeline for pipeline status for clearer understanding.
Checklist:
- I've searched in the docs and FAQ for my answer
- I've included steps to reproduce the bug.
Describe the bug
When deploying with argo cd, 2 threads run for git commit revisions and kubectl apply each. If two deployments are triggered with very little time in between then the user understands that the older trigger of the two will be cancelled but argo does not starts applying new deployment on kubernetes until the older one is done.
Changes done
Created timeline for pipeline status. Updated app status if new deployment is not initiated and older deployment is running.
Screenshots
If applicable, add screenshots to help explain your problem.
Logs
Paste any relevant application logs here.
AB#2