Leverage DevOps Artifacts for dependencies
- Dominant language
- C#
- Stars
- 135
- Forks
- 260
- Avg merge
- 3d 1h
- Merged PRs (30d)
- 143
Description
We should look at leveraging DevOps Artifacts for dependencies rather than retrieving them from the central repositories (Maven, NPM, NuGet, PyPi). Using DevOps Artifacts could help improve reliability when downloading packages as it will be managed by the same project as what is running CI. Possibly resulting in performance improvements as well, which could allow for the SDK repos to remove any DevOps caching their doing, further simplifying the CI process and aligning it closer to what a developer would do locally.
Contributor guide
Research direction
No files or tests are named. Start by mapping how SDK repositories retrieve Maven, NPM, NuGet, and PyPi dependencies in CI and where DevOps caching is configured. Done should be a decided and documented implementation scope for using DevOps Artifacts, including whether existing caching can be removed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- build-system, ci-cd, devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 22/100