Skip CI and Notifications on Codeship

Codeship News

Reading Time: 2 minutes

Today we announce two new features to help you implement Codeship in your workflow. We will show how to use Hipchat for notifications and skipping Continuous Integration on specific builds.

Hipchat notifications

UPDATE: You can do all this now by simpling navigating to the notifications settings in your project You can set up Hipchat Notifications by simply calling

codeship notifications hipchat

in your appliction folder. The command simply sets the following config parameters (which you can also set with codeship config add)

hipchat_key=xb9d35fhcle53n7586c09e9c1pedes hipchat_room=CI

When setting these config parameters a Test message will be posted to Hipchat to make sure everything worked.

Hipchat setup

Hipchat setup

From now on every time a build is started and finished on Codeship a message will be posted to Hipchat.
Hipchat notification

Hipchat notification

We will expand from Hipchat to other Chat providers like Flowdock or Campfire.

Skipping Continuous Integration

To skip a push simply add --skip-ci to the commit message of the last commit before you push.

Sign up for a free Codeship Account


With Hipchat Notifications and skip you can now use Codeship more than ever before in your day to day workflow and configure it to fit the way you and your team works and deploys. If there are any other features you would like to see in Codeship tell us via Twitter or by email.

Subscribe via Email

Over 60,000 people from companies like Netflix, Apple, Spotify and O'Reilly are reading our articles.
Subscribe to receive a weekly newsletter with articles around Continuous Integration, Docker, and software development best practices.

We promise that we won't spam you. You can unsubscribe any time.

Join the Discussion

Leave us some comments on what you think about this topic or if you like to add something.

  • Harri Kauhanen

    Very cool! But how do run this:

    <span class=”pln”>codeship config add KEY……

    Looks like there used to be ‘codeship’ command. And the formatting of these commands are somehow screwed in your blog (showing some HTML tags).

    How to control your branches which to build with the current Codeship version?

    • Hy Harri,

      we had a gem, but removed that at the end of last year. You can skip specific commits by adding –skip-ci to the commit before pushing.

      We have taken out the feature to only run specific branches as we think you should test all features at all times and we want to help with this.


      • Harri Kauhanen

        Fair enough :) Is the special branch name ending still supported? Sometimes I would feel fine to work on some spike and not care about tests that much.

        PS: Remember to fix the formatting of those code/terminal examples, as it makes reading the articles on the blog a bit hard…

      • Sto

        Hello Florian,
        We work with a branch-per-feature policy, but and it would be enough to have CI running on our “staging” and “production” branches.
        Right now, as we push all branches to GitHub, most of our code pushes result in 2 to 3 builds:

        – first I push my feature branch “feature-foo” to GitHub
        – then I merge my branch to “staging” branch, and push again
        – ultimately, my branch will be merged to “production” branch, and pushed once more

        We would like to avoid running CI on “feature-foo” branch, as we know that those code changes will also be pushed to “staging”, which then will be tested.
        Adding `–skip-ci` at the end of my last commit message is not a solution in this case, as it would prevent CI to run on all branches.

        Do you have any solution to this problem, or are we condemned to run twice as many builds as necessary?

        Thank you for your answers,


        • Hi David, currently we don’t support any other way to skip builds than –skip-ci in the commit message.

          We do believe it is really important though to run builds for every branch in your repository.

          We are currently working on some updates and changes that will remedy this issue with running too many builds there.

          • maybe you should support ignoring some directories within a project via .codeshipignore file. Because Static assets or documentation doesn’t require running tests.