[CI] bicep lint job in CI fails randomly and does not spark joy
- Dominant language
- Go
- Stars
- 569
- Forks
- 364
- Avg merge
- 2d 19h
- Merged PRs (30d)
- 136
Description
https://github.com/Azure/azure-dev/actions/runs/30320139612/job/90154113914?pr=9282
In PRs where I'm not touching any bicep, I'll see bicep lint fail. It's possible it's failed in other pipeline runs/commits, but it seems to be some transient network issues.
This is a "do a quick peek and see if there's a quick fix/retry loop" type issue. I don't think we need to get deep into how bicep pulls deps.
Contributor guide
Research direction
Start with the linked GitHub Actions run and the CI workflow that invokes the Bicep lint job. Check whether the failure is transient and whether a retry is appropriate; done means unrelated pull requests no longer fail randomly because of this lint step.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 65/100