What's new on Cloudsmith

Cloudsmith is your friendly neighbourhood Package Management SaaS; for secure delivery of the world's software. For DevOps-y people.

New
September 10, 2021

Let's Hash It Out: Debian Acquire-By-Hash

Our more observant Debian users may have noticed that we rolled out support for acquire-by-hash over the past week - you may have also noticed fewer pipeline disruptions as a result!

What does this mean for me?

If you're someone spinning many plates, you may have encountered some hiccups with your pipeline when updating your repository whilst simultaneously deploying from it - causing `hash sum mismatch` errors. This is the result of an active repository, with indexes fetched while the repository is in a state of change.

Well, no more - farewell to the troubles of yesterday! Debian acquire-by-hash functionality is here to steady the ship and avoid pipeline interruptions caused by those pesky race conditions. This removes the need for any pipeline workarounds - e.g. built-in delays.

How does one acquire this functionality?

So long as you are using APT v1.2.0 or newer, APT will take care of the rest. If you're not, we recommend upgrading - but don't worry, your client will still work; it just won't be able to fetch indexes using acquire-by-hash.

We have more exciting news on the way...

Keep an eye on our changelog; we have some exciting updates landing very soon - we think you'll be just as excited as us when they land!

emoji negative reaction for 'Let's Hash It Out: Debian Acquire-By-Hash' emoji neutral reaction for 'Let's Hash It Out: Debian Acquire-By-Hash' emoji positive reaction for 'Let's Hash It Out: Debian Acquire-By-Hash'
Thanks for your feedback; we appreciate it!
New
June 14, 2021

Lean On Me: Custom Support Details

Good news! You can now set a custom support email and URL for your organizations. For error messages when installs or setups go wrong or where we need to communicate an issue to your users, we'll now display your own support email and URL. You can configure it in your org profile settings:

For example, if your users use the automated bash installs for Linux-based scripts, and an error is encountered during setup, we will display your support email and URL instead of the defaults. So they'll now know how to contact you to resolve the situation quickly and efficiently.

We'll continue to roll out support (no pun intended) for this in other places where a contextual error message could be displayed. Don't worry; if the error message is because of an issue on our side, we'll still let the user let it know it was our fault, and we'll happily handle those issues for you. That's why we're here, after all!

emoji negative reaction for 'Lean On Me: Custom Support Details' emoji neutral reaction for 'Lean On Me: Custom Support Details' emoji positive reaction for 'Lean On Me: Custom Support Details'
Thanks for your feedback; we appreciate it!
Improvement
April 23, 2021

Version Badges: Now with Even Shorter Lifespans

Good news! When you're embedding version badges elsewhere, you'll probably have noticed that services like GitHub like to cache them for an excruciatingly long time*, often well beyond the lifetime of the package version itself. That changes today, along with a stylish (yes, stylish, not just style) update:

Couple of things to note:

  • The cache TTL (Time-To-Live) time has been reduced from 86400 seconds (1 day) to 300 seconds (5 mins).
  • You can now generate badges for Docker images that have a version (non-hashref) assigned to them.
  • The latest version badges will now show a "(latest)" prefix; you can turn this off via "show_latest=false".
  • You can now customise the appearance of the badge (see below for more details).
  • We'll now generate a (much) nicer "version not found" badge if a package or version isn't found.

Tweaking the badge appearance:

  • Figure out how you want to tweak it by looking at the official shields attributes.
  • Find the query string in the snippet (near the question mark), and add <attribute>=<value> to it.
  • Don't forget to put an ampersand between your new value and the next part of the string.

For example, why not go for a wild and crazy alternative colour badge?

Finally: A huge thank you to shields.io for providing an amazing badge rendering service! \o/

Note*: This isn't actually GitHub's fault, our previous use of shields.io meant the Cache-Control header was always returning a max-age of 86400. So we migrated to shields.io newer JSON-based endpoint to fix it.

emoji negative reaction for 'Version Badges: Now with Even Shorter Lifespans' emoji neutral reaction for 'Version Badges: Now with Even Shorter Lifespans' emoji positive reaction for 'Version Badges: Now with Even Shorter Lifespans'
Thanks for your feedback; we appreciate it!
We are ⚡by Beamer