How should I debug a Codeship build that runs successfully with jet steps locally? I make sure to run it on a fresh checkout, so it starts in the same state as Codeship. My process is:
jet steps --push --tag master --no-cache (steps
will only push for master)Running in Codeship, the same master continues to fail
Build Error: No source files were specified
2017-08-07T13:25:59.136Z my-image build/pull had an error
The docs say to use jet steps for debugging, but what should one do when this isn't helpful?
The answer is that I used false assumptions.
The truth of the matter is that running local with jets and remotely on Codeship are very different processes. Success locally does not portend success on Codeship.
jet will be successful, regardless of what volume configs you passjet does not run individual steps in isolated containers, Codeship doesjet will share state between steps and services, Codeship won'tFurther, if you need state between steps and services, very carefully read the footnotes on the Codeship volumes docs.