We are very pleased to announce that upstream proxying and caching for the Maven package format is now available!
Proxying allows requests for packages not found within your Cloudsmith repository to be directed to another location. Maven Central has been supported as a proxy location for a while now on Cloudsmith - but from today, you can now specify any number of additional repositories. So, if you have an on-premise repository installation or a repository hosted somewhere in the cloud - Cloudsmith has you covered, and can help distribute your packages worldwide via it's high performance global CDN.
Along with proxying, Cloudsmith now supports caching of Maven upstream packages to your Cloudsmith repository. Caching allows for packages found in an upstream repository to be fetched and synchronised to your Cloudsmith repository as a regular package. Cached upstream packages behave like any other within the system, allowing you to apply fine grained access controls and permissioning for your teams, users, and customers; in addition to all the other security and management features you love.
Both proxying and caching are designed to help place Cloudsmith as a single source of truth for all the packages and assets used within your software delivery and distribution pipelines. These features are available today on the Team plan and above, and we can't wait for you to try them out. We love hearing from our users, any and all feedback is very welcome.
We're already working hard to expand this to additional package formats, and can't wait to share more!
In order to streamline things for exciting changes coming up, we've restyled the package detail and package list pages. If you've got a keen eye, you'll also notice that the tags have been restyled too and that there's an extra sneaky edit tags button on the package detail page at the top-right. More details to follow next week!
If you, like many of your contemporaries here, are using Cloudsmith for mission-critical delivery of software, we'll bet you're always interested in better ways to protect your assets.
With today's update, we have added support for restricting the location at which your API key can be used to access your account, programmatically. If an IP doesn't…
The groups for packages will now be by name and package format. So the UI will no longer group together (e.g.) Maven and Docker packages as a single group.
This should make it a little easier to tell what packages you have, based on package format. More improvements for the management of this are planned too. Watch this space!