We are thrilled to announce the latest addition to our platform: Support for Debian Components! 🐧🔧
Debian Components are a cornerstone in the Debian ecosystem, allowing for the classification of packages into distinct channels, such as main (Debian Free Software Guidelines compliant), contrib (non-free dependencies),non-free (non-compliant), etc. Now, we're bringing this powerful feature to you!
With our new support for Debian Components, you can leverage the same system to create custom channels tailored to your development cycle or for other purposes. Introducing channels like alpha, beta, and unstable has never been easier, providing a seamless way to manage package releases and distributions within your team or to your users.
Key Benefits:
You can try this out today by either specifying a component other than the default of main in the UI. or if pushing Debian artifacts via the Cloudsmith CLI; you can do that by using --component name:
cloudsmith push deb OWNER/REPOSITORY/DISTRO/VERSION your-package.deb --component unstableNote that components are already supported for Debian upstreams. Any upstream components will be mapped into the main component by default. Please let us know if you're interested in this being mappable (e.g., map an upstream main into your repositories alpha).
Additionally, we've added deb_component support to search, so it's now possible to search for said components, which also means you can include them in entitlement restrictions, thus pinning your users to specific components (e.g., hiding alpha or some, or perhaps only showing paid for others).
For more details on getting started, check out our documentation or contact our support team.
Happy packaging! 🚀🛠️
We are pleased to announce that we have extended Cloudsmith's policy management to include the ability to configure Package Deny Policies. Package Deny Policies let you explicitly block matched packages from being downloaded through your organization. Package Deny Policies use Cloudsmith's core search and filter syntax to describe the rules, allow…
We are pleased to let you know that we are expanding the System for Cross-domain Identity Management (SCIM) capabilities in Cloudsmith to include provisioning new Cloudsmith users. By integrating Cloudsmith with your identity provider (IdP) via SCIM, you can automate provisioning and de-provisioning users in Cloudsmith, letting your IdP serve as yo…
We are pleased to announce we have extended our support for CRAN repositories to include R binary support. Cloudsmith now supports the ability to upload (and distribute) source packages and Windows and macOS binaries (both for arm64 & x86_64). To upload binaries, you must specify the version of R that the binary was built for, and if it's a macOS…
.NET developers - we are happy to let you know that Cloudsmith now provides symbol server support for NuGet. Now, you can create public or private repositories that contain NuGet symbols. Visual Studio uses these .pdb files to let you step through code as it runs in Debug mode on your machine. Any repository in Cloudsmith can be configured as a sy…
We are pleased to add Go and Helm to our list of package formats where we extract and report license information. License information is an important part of many customers' organizational compliance requirements. For the full list of supported package formats, please review our documentation on license compliance. License Policies In addition to…
Cloudsmith lets you control how your software is licensed by making it quick and easy to add a custom End User Licence Agreement for raw package downloads. And now, you can extend that control to any package format with EULA for entitlement tokens. With this new feature, you can specify that a EULA must be accepted before an entitlement token can…
By submitting this form, you agree to our privacy policy
