The CI/CD and DevOps Blog

Shippable IRC Notifications

Warning-Icon.png

DEPRECATED BLOG:

We have significantly updated the Shippable platform with several new features. Hence most of the content in this blog is deprecated. For the latest information, refer to our documentation and/or open a support issue, if you have questions.


 

shippableIRC

We've talked about integrating with messaging services before, such as slack, but there are many more messaging services you can integrate Shippable with. Starting today, your minions can print out build status messages to IRC!

IRC support is implemented as a subtag of notifications. The IRC subtag itself has a number of subtags, but the two most useful one is the "channels" subtag. The channels tag is used to specify which IRC channels you would like your build to message.

The channels tag is quite easy to use, but let's show a quick example anyway! If you want your build to message the "shippable" channel on freenode, you would add the following snippet to your shippable.yml file:

notifications:
  irc:
    channels:
      - "chat.freenode.net#shippable"

Dedicated Hosts... with custom Docker images!

This blog is deprecated

DEPRECATED BLOG:

We have significantly updated the Shippable platform with several new features.

Do you want to run your builds on your own machines? Refer to our Bring Your Own Node (BYON) feature.

Want to use custom Docker images for your CI? No problem, details here.

For the latest information on CI/CD for Docker Containers, refer to our documentation, and/or open a support issue, if you have questions.


Try Shippable


Multi-tenant SaaS platforms are awesome, primarily due to lower costs and minimal setup and maintenance overhead. However, these advantages come at a price - you sacrifice customization and control. This is true of Shippable’s multi-tenant platform as well. One, we disable SSH access to our build minions because of security concerns. Second, while we let you use custom docker containers, we still need to make sure they are ‘okay’ to use in our system.

While these are perfectly acceptable limitations for a lot of folks, we want to be the kind of platform that leaves no developer behind. We understand that ideally, all developers want full control over the machines that are building and testing their code. Some even go so far as to reject multi-tenant hosted solutions, preferring to bear the overhead of setting up and maintaining their own Jenkins setup.

What if you had all the benefits of a hosted service and still had full control? We’ve built just that with Dedicated Hosts!

Dedicated Hosts give you 
- the ability to 'attach' one or more machines to your Shippable org or individual profile, creating a fully functional, dedicated test lab in a few minutes!
- the best of both worlds - hosted orchestration with a dedicated build system.
complete control over your build machines.
- ability to use custom docker images. No restrictions. 
- ability to keep your code within your firewall. We support both cloud and on-premise hosts

Without further ado, let’s jump in and see how it all works!

Demystifying Shippable's deployment keys

Warning-Icon.png

DEPRECATED BLOG:

We have significantly updated the Shippable platform with several new features. Hence most of the content in this blog is deprecated. For the latest information, refer to our documentation and/or open a support issue, if you have questions.

Faster builds by caching containers