Duplicate deployment entries in the Portal

https://github.com/projectkudu/kudu/issues/3268

When deploying with this action an extra deployment object is created in the /deployments list. This clutters the deployments list, and the deployment logs are stored in this extra object, not in the deployment object from GitHub Actions, so it’s hard for users to find the right logs. The expected behavior is to have one deployment object with a commit ID that matches the one in GitHub, and that all the logs are in that object.

Duplicate entries in Kudu

… which creates duplicates in the deployment center

• It looks like the message is added to every push deployment handler: https://github.com/projectkudu/kudu/blob/13824205c60a4bdb53896b9553ef1f370a93b911/Kudu.Services/Deployment/PushDeploymentController.cs#L34
• This method adds the deployment to the deployments API: https://github.com/projectkudu/kudu/blob/13824205c60a4bdb53896b9553ef1f370a93b911/Kudu.Core/Deployment/ArtifactDeploymentInfo.cs#L8

[spellegrino021]

First entry of log will be as is, instead of Created via a push deployment message will be json object with sha of commit ID and second entry will removed

Hi @AmrutaKawade would it be possible for this message to be the corresponding commit message in GitHub? It might make a little more sense to people to have that information rather than the JSON object. Thanks!

[AmrutaKawade]

We use kudu zip deploy api for deploying app, which creates first entry in deployments with message Created via a push deployment

after this deployment we again update status of deployment here with additional details https://github.com/Azure/webapps-deploy/blob/b062dd053e72d63cf28324ec55ce8f77ec086947/src/main.ts#L54

which is creating another entry in deployment.

I have fixed this issue by adding additional details while calling zipdeploy itself https://github.com/microsoft/pipelines-appservice-lib/pull/34

and then removing updatestatus call https://github.com/Azure/webapps-deploy/pull/111