microsoft / microsoft/vscode-azureresourcegroups
[CoR] End-to-end deployment workflow takes excessive time to complete
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 78
- Forks
- 55
- Avg merge
- 16h 49m
- Merged PRs (30d)
- 139
Description
OS: Win11 x64
Build Version: 0.12.8-alpha.0
VS Code Version: Version: 1.137.0
Repro Steps:
- Create and deploy a CoR project
- Complete the deployment workflow
- Observe the total time reported in Deployment Results
Expect:
The deployment workflow should complete within a reasonable amount of time.
Actual:
The deployment completed successfully, but the Deployment Results page reported an elapsed time of 16h47m which includes overnight idle time and waiting/confirmation stages, so it does not represent continuous execution time. However, it was still very lengthy.
More Info:
Recovery Attempts: 5 in Deploy stage
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the deployment workflow and the Deployment Results page, focusing on how elapsed time includes overnight idle time, waiting/confirmation stages, and recovery attempts. Compare the displayed duration with continuous execution time and define the corrected reporting behavior; no files or tests are named in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, typescript
- Domain
- cloud, devops, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100