A month-long celebration to open source projects: coming soon!
Cloudsmith loves open-source software! The team is actively involved in the community and love giving back whenever we can. As a team, we are preparing early to get involved with Hacktoberfest. If you would like to find out more about how we plan to do this and even contribute to an open-source project, check out our blog post.
Read More
Webhook Operators/Filters
It's now possible to create more robust webhooks templates, and to filter for specific packages!
Whether you're automating in the name of ChatOps to get notifications for events on packages, or you're building complex CI/CD deployment machinery, or you're integrating payments via IFTTT or Zapier; our webhooks have got you covered to make this easier.
Two new enhancements added:
- A "standard library" of functions/operators is now available that you call to build more complicated and dynamic messages. For example, you might loop over the tags on a package, and do something different if one of the tags is labelled "hotfix".
- You can now add a package search query to the webhook, and this uses the same search syntax supported elsewhere. If present, packages that emit events need to match the search query provided. In this way, you could filter webhooks for only certain types of packages, in addition to specific events.
Putting both of them together, you can create some powerfully dynamic notification pipelines:
Debian DSC Support
We're pleased to announce that Debian (and related) DSC/source packages are now fully supported!
From the Debian Wiki, a source package is one that provides you with all of the necessary files to compile or otherwise, build the desired piece of software. In other words, you can get the sources used to create a binary package, and compile them yourself; perhaps to customise the package, or build it for a different operating environment.
When uploading a DSC package, the following files are involved:
- Required: The DSC package file is a metadata file that describes the other sources/changes files.
- Required: The sources file contains the actual source files used to build the software.
- Optional: The changes file usually contains the patch applied, or to be applied, to the sources file if different from the original.
Assuming you've got these, uploading via the latest Cloudsmith CLI (0.23.0+) release is simple:
cloudsmith push deb your-org/your-repo/ubuntu/bionic my-package_1.0.0.dsc --sources-file my-package_1.0.0.debian.tar.xz
Then, once it's synched (ready for download), you can grab and build the package yourself with:
apt-get --build source my-package=1.0.0
Add your Conan Packages
We’re delighted to announce that Cloudsmith now supports Conan!
Conan is an open-source package manager for C/C++, including everything from its client to server implementation and even documentation. You can read all about Conan and how to get started over on our blog. If you would prefer a demo be sure to check out our 5 minutes Conan over on Youtube, where you can see a developer set up their local development environment, upload, and download Conan packages to Cloudsmith. We offer further examples within repositories and via our documentation to simplify setup to help you get started using for our open-source, public, or private Conan repository. Finally, let us know your feedback via Intercom. We love to get developer feedback!
Read More
Universal Package Tagging
We're pleased to announce the general availability for universal tagging of packages!
Why should you care? Tags, which are little snippets of keywords that you can attach to packages, are an excellent way of organising your packages for different reasons. You can now manage and search for tags via the API, the CLI and the UI, which makes management a breeze.
You can tag packages during upload, or you can tag them later on. A common use-case is to tag a package based on its category or function, such as it is a "third-party" "vendored" "library", but you could also tag it based on how/where you use the package (e.g. it is "deployed" in the "auth-app" layer).
You can also add them to entitlement tokens, to limit what your customers have access to download. For example, you can tag your packages in such a way that standard edition customers only have access to the "standard" packages, but pro edition customers have access to both "standard" and "pro" packages.
Now go forth, and tag those packages!
Read More
Custom Domains
Did you know that we have support for custom domains, for any package format?
Whether you're a vendor, selling and distributing software to your customers, or you're a security-conscious DevOps team, looking to control the source endpoint for artifacts; either way, with custom domains you can present your brand when distributing from Cloudsmith.
For API-based package formats, such as NuGet, Docker, Cargo, npm, Conan and Terraform, you can have a specific custom domain, such as docker.notcloudsmith.com. For other package formats, and downloads in general, you can have a custom domain such as dl.notcloudsmith.com.
Custom domains have been extremely popular with our users, and for a good reason. You maintain control over the endpoints and get to put your name on them, while leaving the concerns of powering them, to Cloudsmith. Simple.
How? If you're on our Velocity plan, this is available for use today. Just ask.
Read More