Answers: <p>Look at the Travis CI Logs.  Often a failed build step will return "Error", "Failure", "-1", buried in a wall of text.  If you want a better way to collect and  these logs you can check out the following:</p>
  
  <ul>
  <li><a href="https://github.com/travis-ci/travis-logs" rel="nofollow noreferrer">Official Github page with details on how log collection works</a></li>
  <li><a href="https://blog.travis-ci.com/2014-04-11-fun-with-logs/" rel="nofollow noreferrer">An official blog on how to structure your production logs.</a></li>
  </ul>
  
Answers: CC BY-SA 4.0
Answers: 2019-10-10T15:05:46.247Z
Answers: So manually search / grep for "Exited with 1" / "Error"?
Answers: Chris Stryczynski
Answers: CC BY-SA 4.0
Answers: 2019-10-10T15:01:18.313Z
Answers: 2019-10-10T15:01:18.313Z
Answers: Wesley Rolnick
Body: <p>So I have a CICD travis build that failed... How do I know which line / step is the culprit?</p>
  
Comments: CC BY-SA 4.0
Comments: 2019-10-12T02:22:45.463Z
Comments: Have you looked at the output of the build that failed?
Comments: chicks
Comments: CC BY-SA 4.0
Comments: 2019-10-12T05:15:21.463Z
Comments: Please improve your question to include relevant output of your failed build.
Comments: Pierre.Vriens
Tags: <travis-ci>
Title: How can I determine which command / step failed within a travis build
UserDisplayName: Chris Stryczynski
ThreadText: # How can I determine which command / step failed within a travis build
  
  (Asked by: username_0 on 2019-10-10)
  
  So I have a CICD travis build that failed... How do I know which line / step is the culprit?
  
  **Tags:** travis-ci
  
  > **Comments:**
  > **username_1**: Have you looked at the output of the build that failed?  
  > **username_2**: Please improve your question to include relevant output of your failed build.  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_3 on 2019-10-10. Score: 1
  
  Look at the Travis CI Logs. Often a failed build step will return "Error", "Failure", "-1", buried in a wall of text. If you want a better way to collect and these logs you can check out the following:
  
  * [Official Github page with details on how log collection works](https://github.com/travis-ci/travis-logs)
  * [An official blog on how to structure your production logs.](https://blog.travis-ci.com/2014-04-11-fun-with-logs/)
  
  > **Comments:**
  > **username_0**: So manually search / grep for "Exited with 1" / "Error"?  
  
  ---
  
  