PowerShell / PowerShell/PSResourceGet
Host more common package repositories for automated testing with PSResourceGet
Open
Nobody has claimed this yet.
Area-Build&Release
feature_request
- Dominant language
- C#
- Stars
- 576
- Forks
- 114
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 7
Description
Summary of the new feature / enhancement
PSResourceGet tries to support multiple repositories, but only tests against some of them.
Add test instance of more repositories so one can make reliable additions and changes to PSResourceGet in regards to other repository systems. Like:
- Azure DevOps
- Supports NuGet v2 and NuGet v3: https://learn.microsoft.com/en-us/azure/devops/artifacts/nuget/nuget-exe?view=azure-devops#legacy-project-setup
- SonarType Nexus
- JFrog Artifactory
Else issues like #1491 will continue popping up.
Proposed technical implementation details (optional)
- Microsoft owned stuff like Azure DevOps should be easy enough.
- Ask 3rd parties to host public test instances?
- Spin up and take down self hosted repositories as part of GitHub actions / workflows?
- Will require some CI/CD engineering.
Contributor guide
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 by reviewing the test/ directory and the proposed GitHub Actions/workflows approach. Define repeatable test instances for Azure DevOps NuGet v2 and v3, Sonatype Nexus, and JFrog Artifactory, then verify that PSResourceGet tests exercise them reliably.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, csharp, github-actions, powershell
- Domain
- ci-cd, devops, testing-qa
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100