Skip to content
This repository has been archived by the owner on Sep 4, 2024. It is now read-only.

Extra deployment object when processing ZIP and WAR deployments #3268

Closed
JasonFreeberg opened this issue Feb 4, 2021 · 4 comments
Closed

Comments

@JasonFreeberg
Copy link
Contributor

JasonFreeberg commented Feb 4, 2021

When deploying with GitHub Actions (uses /zipdeploy and /wardeploy) 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.

Duplicate entries in Kudu

image

... which creates duplicates in the deployment center

image

@ehamai
Copy link

ehamai commented Feb 9, 2021

Just a little more context. Since the extra deployment object isn't tied to a real commit id, this affects the portal experience because it means that we're not able to group all the logs from GitHub Actions to Zip Deploy based on commit id.

@suwatch do you know who we should talk to about this by chance?

@suwatch
Copy link
Member

suwatch commented Feb 14, 2021

There were 2 calls making to KUDU from Github action – both instructed Kudu to create deployment entry (one being ZipDeploy and another to create deployment entry). I would follow up to the team owning github action task on DevOps.

@JasonFreeberg
Copy link
Contributor Author

JasonFreeberg commented Feb 15, 2021 via email

@suwatch
Copy link
Member

suwatch commented Feb 15, 2021

Wonderful. Will close this for now.

@suwatch suwatch closed this as completed Feb 15, 2021
@JasonFreeberg JasonFreeberg changed the title Kudu controller adds extra deployment when processing ZIP and WAR Extra deployment object when processing ZIP and WAR deployments Feb 17, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants