VSTS Maven包发布咨询：如何将内部Feed中的包复制至公开Feed？

Absolutely you can copy packages from your internal feed to a public one in Azure DevOps (formerly VSTS) — here’s how you can pull this off smoothly, tailored to your existing workflow:

Automated Pipeline Approach (Recommended for Your CI Flow) #

Since you already have a CI pipeline triggered on master branch updates, you can extend it to handle the copy once your final internal testing is complete:

• Add a Package Copy task directly in your pipeline: This task lets you transfer packages between Azure Artifacts feeds without downloading/uploading them manually. Just configure the source (internal feed) and target (public feed), and make sure your pipeline service connection has read access to the internal feed and publish access to the public feed.
• For non-Azure Artifacts public feeds (like npm public registry), use the appropriate package publisher task (e.g., NuGetCommand for NuGet, npm task for npm packages): First pull the package from your internal feed, then publish it to the public destination. You can gate this step to only run if all final tests pass.

Manual Copy for Ad-Hoc Scenarios #

If you need to publish a package occasionally without pipeline changes:

• Navigate to your internal feed in Azure Artifacts, find the package version you want to share.
• Open the package details page, click the Copy to button in the top-right corner.
• Select your public feed from the dropdown, confirm the action, and the package will be replicated.

Key Things to Keep in Mind #

• Permissions Setup: Ensure your public feed is configured to allow anonymous access (or the appropriate level of public visibility) so third-party developers can retrieve the package. Restrict copy/publish permissions to only trusted users or service accounts to prevent accidental releases.
• Version Consistency: Maintain matching versions between your internal and public feeds to avoid confusion. Use pipeline conditions to only copy packages that have passed all final validation steps.
• Trigger Logic: Tie the copy step to your existing CI success trigger — this way, every valid master branch update that makes it through internal testing automatically gets pushed to the public feed, keeping your release process seamless.

内容的提问来源于stack exchange，提问作者Steve