The built-in package store in Jaws Deploy is a secure, workspace-specific repository for storing deployment artifacts like .zip, .tar.gz, or NuGet packages. It's your go-to feed for managing versions without relying on external services, ensuring artifacts are private and accessible only during deploys. This simplifies workflows by keeping everything in one place—no need for separate artifact servers.
Designed for ease, the store supports manual uploads via UI, automated via API, and versioning with SemVer 2.0. For enterprises migrating from tools like Bamboo, it's a direct replacement for shared artifact repositories, with added benefits like automatic cleanup and integration with project steps. As of September 2025, the store now handles larger files (up to 500MB base) and includes metadata for container references.
This article explains the store's features, setup, usage, and maintenance.
Features of the Built-in Package Store
- Private and Secure: Artifacts are not public; access limited to your workspace and service accounts.
- Version Management: Upload multiple versions per package ID; releases reference specific ones for consistency.
- Supported Formats: .zip/.tar.gz for general files, .nupkg for NuGet; prepare with dot-separated name.version (e.g., MyApp.1.2.3.zip).
- Inspection and Download: View details, download versions, or delete unused ones.
- Storage: Per-workspace limits (expandable via plans); automatic versioning prevents overwrites.
In deployments, targets pull from the store on-demand, with transforms applied post-download. For migrations, bulk-upload Bamboo artifacts via API to seed the store.
This page shows the upload section, preparation instructions, and package list with IDs, latest versions, sizes, upload dates, and actions like "Show all versions."
Setting Up and Uploading to the Store
- Access the Store: From the left menu > Package Store.
- Prepare Packages: Zip your artifacts; name with ID.version.ext (e.g., filemail.2.1.37.zip). Use SemVer for consistency.
- Upload Manually: Click "Choose File" > Select your .zip/.tar.gz/.nupkg > Upload. Jaws validates and adds to the list.
- Upload via API: For automation (e.g., from CI):
- Use POST /api/packagestore/package
- Headers: Authorization (Basic with service account)
- Form Data: file=@path/to/package, packageId=my-app, version=1.2.3
- Versioning Rules: New uploads create versions; duplicates prompt overwrite or error.
For enterprise teams, set up service accounts for CI uploads; integrate with Bamboo post-build scripts during migration.
Using the Store in Deployments
- In Projects: In a "Deploy Package" step, select from the store's dropdown—Jaws lists available IDs/versions.
- During Release: Associate versions in release creation; deploys pull automatically.
- Redownload: Option in deploy settings to force fresh pulls, useful if packages update post-release.
- Transforms: Auto-apply to configs inside packages (e.g., appsettings.json with #{VAR} placeholders).
In container workflows, use the store for sidecar artifacts; note image tags separately in releases.
Maintenance and Best Practices
- Cleanup: Delete old versions via UI to free storage; Jaws warns on limits.
- Auditing: Upload history tracks who/when; integrate with enterprise logs.
- Optimization: Compress packages; use external feeds for massive artifacts.
- Migration from Bamboo: Script bulk uploads from Bamboo shared artifacts; test references in Jaws projects.
- Security: Mask sensitive data in packages; use scoped service accounts for uploads.
- Scaling: For high-volume, consider connecting external NuGet feeds to offload storage.
Troubleshooting Common Issues
- Upload Failures: Check file format/size; API errors like 2002 (auth) or 3001 (params).
- Not Found in Steps: Ensure package ID/version matches; refresh store list.
- Storage Limits: Monitor via dashboard; upgrade or clean up.
- Debugging: Use __debug in deploys to log package resolutions.
Conclusion
The built-in package store in Jaws Deploy offers a simple, integrated way to manage artifacts, reducing complexity in your CD pipelines—especially during enterprise migrations from tools like Bamboo.
For advanced use, see Connecting External Feeds or Using Package Feeds. Start uploading—visit your Package Store! New to Jaws? Check Getting Started.
