Codeship SSH Debug Access

Codeship NewsOperations

Reading Time: 2 minutes

At Codeship we care deeply about your productivity.

Your Continuous Integration (CI), local and production environment are not the same. They have different locale settings and sometimes even run another operating system.

With various environments, it happens that your code behaves differently on each platform. Some of your builds might fail on the Codeship but pass on your local environment as they depend on another timezone or have other environment specific dependencies.

In the past you had to write a support ticket and together we figured out what’s going on with that failing test. Even though we put a lot of effort and time into customer support it still wasn’t as responsive as we want it to be. It doesn’t matter how hard we try to answer your questions as fast as possible, it broke your workflow. In this article I will write about our new SSH Debug Access.

Introducing the Codeship SSH Debug Build

To fix all those issues we are happy to announce SSH Debug Access.

This means that you can SSH into a build and start debugging in seconds. We checkout your code. You start with a clean environment and can debug right away.

How it works

To be able to use the Codeship SSH Debug Access you need to provide your public SSH key. Just go to your account settings.

Access your Public SSH Key through the Codeship Account Settings

There you’ll find a “SSH Public Key” text field where you need to enter your public key.

Find your Public SSH Key in the "My Account" Menu

Below each build you can find the “Debug this Build” button which fires up a debug machine for you.

Below every build you can find the "Debug this build" button

You get the SSH command a few seconds after you requested the debug build. Just copy and paste it into your terminal and you are good to go.

Copy and Paste the SSH command into your terminal

After the login you’ll see a little guide.

SSH Debug Guide by Codeship

Making you more productive

Additionally to the SSH Debug Access we wrote a little shell script which helps you navigate around. It includes some helpful shortcuts like listing your setup and test commands so you don’t need to switch to the build view back and forth. It also gives an easy command to reset the dependency cache in case you really want to start fresh.

You can find a detailed explanation of the SSH Debug Access, where to find your SSH public key and our Codeship helper script in our Documentation.

Sign up for a free Codeship Account

Conclusion

It is really important for us to keep you focused on your actual work. With our super fast support, SSH Debug Access and our intelligent build help (which I will write about in a different blog post) we provide you with tools that help you accomplish your tasks as fast as possible and keep you productive.

You can learn more about our SSH Debug Access in our Codeship SSH Access documentation article.

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.

  • Gilles Doge

    Hi,

    I like this feature (just used 10min ago :P). This make really easy to see what is going wrong with a specific build.

    Like this time, I see that you updated PHPUnit to the latest version (4.x) and I was running local test with version 3.7. I fixed PHPUnit version with composer and directly tested this change with SSH Debug session to see what I’ve to change in my test configuration.

    • beanieboi

      Hey Giles

      thanks for checking it out. glad it helps! if you have any feedback please let me know.
      we don’t actually preinstall PHPUnit, can you please check your composer file if the version is really pinned down to 3.7.

      ben

      • Gilles Doge

        It is. All is fine. Thanks.

  • Francis Pilon

    To be sure: this debug vm doesn’t run the Setup Commands, correct?

  • Dean

    When I run the ssh command, it’s asking me for the password for the “rof” user. What is the password?

    • Luis

      same here. it goes straight to user/password as far as I can tell. :/

      • Dean

        Seems you need to restart the SSH service on the build for it to work. If you copy your public key to Codeship after you start the SSH service, then you’ll get that problem. Just restart the SSH service on Codeship after you copy the public key there.

        Hope that helps.

        • Jules Moretti

          And how do you reset SSH service on Codeship?

          • tomkerswill

            I’d like to know this too — how do you reset SSH on codeship, in order for it to pick up the key?

        • pyromjm

          bueller?

          • I didn’t find that I need to “reset ssh service” – just make sure you have the correct public key in your account settings, then *start a new build* before trying to debug. Worked awesome, this feature is a big timesaver!

  • Pingback: How I develop Meteorjs apps - part 3. Continuous Integration and Delivery of your Meteor “package for everything” project. | How We Do Apps()

  • I’m trying to configure my setup-commands. But, once I’ve wrote them, how can I execute them and exit the setup-commands? And how can I then set the setup-test as I’m still in setup-commands mode?

  • Zach Rose

    Looks like the UI has changed, and I don’t see the “Debug this Build” button anymore. Where should I see it?