You are able to activate build debugging at the bottom of the build detail view for projects running on Codeship Basic. The SSH debugging session only works for branches still available in your repository.
If you are using Codeship Pro, you can debug locally by using the command-line tool. You can refer to the Installation Documentation to get your builds running locally for debugging.
When you start a SSH Debug session we will clone the repository and set up all environment variables that you defined and that we set by default. We won’t run any setup or test commands. This gives you a clean machine so you can fully test and debug your application on Codeship. No generated files or changes done in any previous builds will be available. The SSH session is completely separate from any builds before.
Inside the SSH session, you have access to the Codeship command. It provides some convenient methods to debug your project.
There are a few directories in your home directory (
The most important one is the
clone directory. The
clone directory is your project root and contains your source code.
Get insight into Environment variables.
You can use
grep to filter the Environment
printenv | grep CI
By default we set the NodeJS version to
You can manage the NodeJS version via NVM.
To install a new version of NodeJS use
nvm install 0.11
or use a different version of NodeJS
nvm use 0.10.25
The debug build will shutdown itself after
You can shutdown the debug build manually by using
If you want to start really fresh, you can clear the Dependency Cache by using
SSH is a protocol which uses asymmetric key algorithms for authentication. If you want to dig deeper into Public-Key cryptography you can start by reading the Wikipedia article.
You can retrieve your public SSH Key by using the following command in your Terminal.
To generate your own SSH Key, open up your Terminal and use this command.
ssh-keygen -b 8192