This article is about Codeship Pro.

Differing Results between Jet CLI and CodeShip Pro

You will need roughly 2 minutes to read this article.

Results with the Jet CLI tool may differ from a build on CodeShip Pro. Let’s explore why this might be the case.

Jet CLI Disjoints

  • Jet tool can be out of date (and out of alignment with CodeShip Pro environment).

    Run jet update to ensure latest version of CLI tool.

  • Jet may be reliant on outdated Docker image(s).

    Identify the current image with docker image ls, then remove via docker rmi IMAGE_ID. jet steps will now trigger an image rebuild.

  • jet steps runs with additional files present that would otherwise not be expected in the CodeShip Pro build.

    We recommend running jet steps on a freshly git cloned version of your project OR running a git reset and git clean operation on your project prior to jet steps.

  • Jet overlooks volume mappings to absolute paths on the host.

    This may work just fine on one’s local machine, but can be problematic with an ephemeral Docker Host (i.e., the CodeShip Pro build). Please ensure that volumes are mapped relative to the project folder on the Docker Host.

  • Unless explicitly passed along to jet steps as a flag, most CI environment variables will not be present in a jet steps build.

    See jet steps --help for flag options.

  • Outdated Docker Engine version

    Ensure that your local machine is utilizing an up-to-date version of Docker Engine. CodeShip Pro currently runs with 18.03

  • AES key may have been recently reset from UI, preventing decryption of environment variables with the outdated AES key on local machine.

    The AES key for your project can be located on the Project Settings > General page.

CodeShip Pro Disjoints

  • Resource constraints for the allotted CodeShip Pro instance size are forcing background processes to be killed on CodeShip Pro builds, while the same build runs without issue via jet steps.

    If you suspect your build is failing on account of resource constraints, then please reach out to our support team with the CodeShip Pro build url in question.

  • CodeShip Pro may be reliant on outdated Docker image(s).

    To clear the project’s Docker image cache, click the drop down arrow of any build status icon and select ‘Reset Cache’.

Need more help?

Contact our support team or post on Stack Overflow using the tag #codeship. Did you check the status page and changelog?

There are also several code examples and sample projects available for you to get started with.

Article not helpful?

Does this article need improvement? If so, please send feedback or submit a pull request!