1. 27 Mar, 2019 9 commits
  2. 26 Mar, 2019 10 commits
  3. 20 Mar, 2019 2 commits
  4. 19 Mar, 2019 7 commits
  5. 08 Jun, 2017 3 commits
  6. 07 Jun, 2017 4 commits
  7. 03 Jun, 2017 3 commits
    • Andy Wilkinson's avatar
    • Andy Wilkinson's avatar
      Tolerate Successfully built being found in response other than last · 31ff7f18
      Andy Wilkinson authored
      Different versions of Docker produce different responses when building
      and tagging an image. On CI, a response with a stream like
      "Successfully built 185991ffe24a" followed by a response with a
      stream like "Successfully tagged spring-boot-it/centos:6.9-a23bced6"
      is received. By default, for the building of an image to be considered
      successful, the Docker Java client requires the stream for the last
      response item to contain "Successfully built". This means that, on the
      CI server, it incorrectly believes that the building of the tagged
      image has failed.
      
      This commit uses a custom BuildImageResultCallback that doesn't
      require the last response to be the one that has a stream containing
      "Successfully built". Instead, it looks back through the error-free
      responses (newest to oldest) looking for one with a stream containing
      "Successfully built".
      31ff7f18
    • Andy Wilkinson's avatar
  8. 02 Jun, 2017 2 commits