Using Package Feeds in Jaws Deploy: Artifact Management Guide

Package feeds in Jaws Deploy are sources from which deployment artifacts—such as .zip files, .tar.gz archives, or NuGet packages—are retrieved during a release or deployment. They act as repositories for your build outputs, ensuring that the right versions are pulled securely and consistently across environments. Whether you're using the built-in package store for simplicity or connecting external feeds for integration with existing CI tools, feeds streamline artifact management without exposing them publicly.

This approach is particularly helpful in enterprise setups, where you might migrate from scattered artifact storage in tools like Bamboo to a centralized, versioned system in Jaws. Feeds support SemVer 2.0 for versioning, enabling precise control and rollbacks. As of September 2025, feeds now include enhanced support for container image references in package notes, aiding hybrid workflows.

This article covers how to use package feeds, their role in deployments, and tips for optimization.

The Role of Package Feeds

Feeds provide a reliable way to store and reference artifacts:

Artifact Types: Supports compressed files (.zip, .tar.gz) for general apps, NuGet (.nupkg) for .NET libraries, and indirect references for containers (e.g., Docker tags in notes).
Versioning: Each package has a unique ID and version; releases snapshot specific versions for immutability.
Security: Feeds are private to your workspace; access controlled via service accounts for API uploads.
Integration: Pull from feeds in steps like "Deploy Package," where Jaws handles extraction, transforms (JSON/XML), and installation.

In deployments, targets (machines/cloud apps) download from feeds on-demand, with options to redownload for freshness. This decouples builds from deploys, ideal for CI/CD where Bamboo/GitHub Actions pushes to a feed, and Jaws pulls during release.

For migrations, map Bamboo artifacts to Jaws feeds: Upload via API post-build, then reference in projects for seamless transition.

Setting Up and Using Feeds

Jaws offers built-in and external feeds—configure via the Package Store menu.

Built-in Feeds

Jaws' internal store per workspace; upload manually or via API (see Built-in Package Store).
Usage: In a project step, select "Deploy Package" and choose from the store's list.

External Feeds

Connect to NuGet servers or custom repositories (see Connecting External Feeds).
Usage: Reference by URL in steps; Jaws authenticates and pulls during deploy.

To use in a deployment:

Upload Artifact: From CI or manually to a feed.
Create Release: Associate package versions (e.g., my-app@1.2.3).
Execute Deploy: Jaws fetches and applies on targets.

This lists packages with IDs, versions, sizes, upload dates, and download links. Search and filter to find artifacts quickly.

Jaws Deploy Package Store interface showing a list of uploaded artifacts with their IDs, versions, file sizes, and upload dates.

Best Practices

Version Consistently: Use CI build numbers in SemVer (e.g., 1.0.${BUILD_NUMBER}) for traceability.
Automate Uploads: Script API calls in CI (e.g., curl POST to /api/packagestore/package) for zero-touch.
Security: Use service accounts for uploads; avoid public feeds for sensitive artifacts.
Optimization: For large packages, compress well; use redownload sparingly to save bandwidth.
Enterprise Migration: From Bamboo, export artifacts and batch-upload to Jaws feeds; test pulls in dev environments.
Container Workflows: Note image tags in releases; use "Run Script" steps to pull/deploy from registries.

Troubleshooting Common Issues

Package Not Found: Verify upload/version in store; check API responses for errors (e.g., 3001 invalid param).
Download Failures: Ensure targets have network access; test with manual deploys.
Version Conflicts: Use unique SemVer; delete duplicates via UI.
Large Files: Workspace storage limits apply; upgrade plans for more.
Debugging: Enable __debug to log feed resolutions during deploys.

Conclusion

Using package feeds in Jaws Deploy centralizes artifact management, making deployments reliable and integrated with your CI/CD. Whether built-in for quick starts or external for legacy compatibility, feeds simplify enterprise migrations from tools like Bamboo.

For details, see Built-in Package Store or Connecting External Feeds. Upload your first package—head to the Package Store now! New to Jaws? Try Getting Started.