If the step’s corresponding log is not appearing at all for the build, it is possible that you have run up against the 16mb step log limit. Reducing the log output of dependent containers is a good starting point for keeping under the log limit threshold.
If the logs must be viewed for this particular build, one additional
workaround is to run the CloudBees CodeShip Pro build from your local machine via
jet steps (see our
Jet tool doc page for more information).