External feeds in Jaws Deploy allow you to connect to third-party repositories like NuGet servers, Artifactory, or custom artifact stores, expanding your package sources beyond the built-in store. This is useful for integrating with existing enterprise ecosystems, pulling from CI-generated feeds, or leveraging public registries without duplicating storage.
Jaws supports NuGet-compatible feeds out-of-the-box, with authentication for private ones. For enterprises migrating from tools like Bamboo, connecting external feeds bridges legacy artifact systems, enabling gradual transitions without immediate uploads to Jaws' store. As of September 2025, external feeds now support enhanced credential scoping and proxy handling for corporate networks.
This article covers setup, usage, security, and migration tips.
Benefits of External Feeds
- Integration Flexibility: Pull from Azure Artifacts, MyGet, or self-hosted NuGet—ideal for .NET-heavy enterprises.
- No Duplication: Reference existing packages without re-uploading; saves storage in Jaws.
- Hybrid Workflows: Use alongside built-in store; fallback if internal feeds fail.
- Enterprise Compliance: Connect to audited feeds; maintain data sovereignty.
In migrations, link Bamboo-exported NuGet feeds to Jaws, testing pulls before decommissioning.
Setting Up External Feeds
- Access Feeds: From Package Store > External Feeds (or via project steps for ad-hoc).
- Add a Feed: Click "Add external feed":
- Type: NuGet (primary; others via custom URL).
- URL: Feed endpoint (e.g., https://pkgs.dev.azure.com/org/_packaging/feed/nuget/v3/index.json).
- Credentials: Username/API key; store securely (integrate with Azure Key Vault).
- Name/Description: For easy reference.
- Test Connection: Jaws verifies access and lists sample packages.
- Proxy (Optional): For enterprises, configure via Jaws Stack settings (see Proxy Setup).
Feeds are workspace-shared; scope usage via service accounts for security.
Using External Feeds in Deployments
- In Projects: In "Deploy Package" steps, select the external feed and search for IDs/versions.
- During Release: Reference packages in creation; Jaws pulls during deploy with auth.
- Fallback: Set primary/secondary feeds; auto-switch if one fails.
- Transforms: Apply to pulled packages as usual.
For container workflows, use external feeds for manifests; pull images in "Run Script" steps.
Example API for release with external package:
json
{ "projectId": "abc123", "version": "1.2.3", "packageVersions": {"my-app": "1.2.3@external-feed-name"}}
In Bamboo migrations, script pushes to external feeds, then trigger Jaws releases referencing them.
Best Practices
- Authentication: Use API keys over usernames; rotate regularly.
- Performance: Cache frequently used packages in built-in store; monitor pull times.
- Security: Scope feeds to environments; avoid public ones for prod.
- Migration Strategy: From Bamboo, connect existing Artifactory feeds; validate in Staging before full switch.
- Version Control: Enforce SemVer in CI; use feed queries to list available versions.
- Enterprise Scale: For proxies/firewalls, test connectivity; integrate with SSO for auth.
Troubleshooting Common Issues
- Connection Failures: Check URL/creds; test with curl from agents.
- Auth Errors: Verify scopes; API returns 2002 for invalid.
- Package Not Resolved: Ensure feed indexed; refresh in Jaws.
- Proxy Issues: Configure in self-hosted; debug with logs.
- Debugging: Use __debug to trace feed pulls during deploys.
Conclusion
Connecting external feeds in Jaws Deploy extends your artifact options, facilitating integrations and enterprise migrations from tools like Bamboo while keeping deploys flexible.
Pair with Built-in Package Store or Using Package Feeds. Connect your first feed—go to Package Store! New to Jaws? See Getting Started.
