You will need roughly 2 minutes to read this article.
Running a build on your local machine with the Jet CLI tool may have differing results from a build on CodeShip Pro. Let’s explore why this might be the case.
jet updateto ensure latest version of CLI tool.
Identify the current image with
docker image ls, then remove via
docker rmi IMAGE_ID(you can also
docker rmithe image name directly if you have an
imageattribute set in the services file). Running
jet stepswill now trigger an image rebuild.
jet stepscould run with additional files present that would otherwise not be expected in the CodeShip Pro build.
We recommend running
jet stepson a freshly git cloned version of your project OR running a
git cleanoperation on your project prior to
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.
jet stepsas a flag, most CI environment variables will not be present in a
jet steps --helpfor flag options.
Ensure that your local machine is utilizing an up-to-date version of Docker Engine. CodeShip Pro currently runs with 18.03
The AES key for your project can be located on the
Project Settings > Generalpage.
To clear the project’s Docker image cache, click the drop down arrow of any build status icon and select ‘Reset Cache’.
jet steps. The error stack trace can be a bit more cryptic than with resource constraints imposed on the application level.
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.
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.