Kernl: Important BitBucket Changes

It came to my attention that the way BitBucket handles deployment keys has changed. Until recently the same deployment key could be shared across multiple repositories. That rule has been changed and now each repository requires a unique deployment key. So what does this mean for you? You’ll need to take a few steps to make sure that your “push to build” functionality continues to work as you expect it to.

  1. I’ve deployed changes that allow you to add unique deployment keys to all of your repositories. For those of you with a lot of repositories this is going to be pretty tedious, but in the end it will give you greater access control to your repositories. Documentation for adding deployment keys can be found at , but you likely won’t need it. Just go to “Continuous Deployment” and then click “Manage Deployment Keys” (if you don’t see that button, hard refresh).
  2. Starting tomorrow (February 21, 2017) at 7pm EST, access with the old Kernl deployment key will be cut off. From this point forward only the new deployment keys will be able to access your repository.
  3. After February 21, 2017 @ 7pm EST you can delete the old Kernl deployment key from your repositories. If you do it before then your builds will fail.

Sorry for the short notice and inconvienience of this change, but it’s necessary to make sure that all customers are able to deploy continuously with Kernl. If you have any questions or concerns about this change, please reach out. And once again, sorry for this inconvience!

What’s New With Kernl – February 2017

It’s been a little while since my update, so let’s dive right in to what’s new.

  • Kernl now has an enhanced billing area. The mechanism for paying an expired invoice was pretty confusing and it wasn’t possible to see your past invoice amounts. With these changes you can now see the last 10 invoices from Kernl and if you ever need to pay an out-of-date invoice that process is much simpler.
  • Purchase codes can now be limited to a domain. This is handy if you don’t want your customers buying a single license and using it on many sites.
  • Work has started on feature flags! Feature flags are a software development best practice of gating functionality. Functionality can be deployed “off”, then turned on via the feature flag, separate from deployment. With feature flags, you can manage the entire lifecycle of a feature. This is _super_ useful for the WordPress community because it allows you to turn functionality on/off without creating and deploying a new version. You can roll out flags based on a boolean on/off, percentage of users, or just to specific users. If you’d like to be part of the beta, let us know.
  • Kernl’s 3 Node.js app servers were upgraded. They now have 1GB of RAM per server instead of 512MB.

If you have any questions, thoughts, or concerns, feel free to reach out on Twitter or comment here.  Cheers!