Merge pull request cds-hooks#503 from buildpacks/fix/ci-pack-output

CI: Fix pipelines regarding changes to lifecycle output

Author: jkutner

Makefile

@@ -82,13 +82,12 @@ install-pack-cli: upgrade-pack
 	else \
 		echo "pack already installed at $(PACK_BIN)"; \
 	fi
-	@echo "pack version: $(shell pack --version)"
+	@echo "pack version: " `pack --version`
 
 .PHONY: check-pack-cli-version
-check-pack-cli-version: export INSTALLED_VERSION:=$(shell pack --version | cut -d '+' -f 1)
 check-pack-cli-version:
-	@echo "> Installed pack version: $(INSTALLED_VERSION)"
-	@if [ "$(INSTALLED_VERSION)" != "$(PACK_VERSION)" ]; then \
+	@echo "> Installed pack version: " `pack --version | cut -d '+' -f 1`
+	@if [ `pack --version | cut -d '+' -f 1` != "$(PACK_VERSION)" ]; then \
 		echo "!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!"; \
 		echo "WARNING: Expected pack version: $(PACK_VERSION)"; \
 		echo "You may need to upgrade your version of pack!  "; \

content/docs/buildpack-author-guide/create-buildpack/build-app.md

@@ -126,7 +126,6 @@ pack build test-ruby-app --path ./ruby-sample-app --buildpack ./ruby-buildpack
 
 You will see the following output:
 
-<!-- test:assert=contains;ignore-lines=... -->
 ```
 ===> DETECTING
 ...

content/docs/buildpack-author-guide/create-buildpack/detection.md

@@ -37,7 +37,6 @@ pack build test-ruby-app --path ./ruby-sample-app --buildpack ./ruby-buildpack
 
 You should see the following output:
 
-<!-- test:assert=contains -->
 ```
 Previous image with name "test-ruby-app" not found
 ===> DETECTING
@@ -46,7 +45,7 @@ examples/ruby 0.0.1
 ===> BUILDING
 ---> Ruby Buildpack
 ERROR: failed to build: exit status 1
-ERROR: failed to build: executing lifecycle
+ERROR: failed to build: executing lifecycle: failed with status code: 51
 ```
 
 Notice that `detect` now passes because there is a valid `Gemfile` in the Ruby app at `ruby-sample-app`, but now `build` fails because it is currently written to error out.

katacoda/scenarios/buildpack-author-guide/build-app.md

@@ -122,7 +122,6 @@ pack build test-ruby-app --path ./ruby-sample-app --buildpack ./ruby-buildpack
 
 You will see the following output:
 
-<!-- test:assert=contains;ignore-lines=... -->
 ```
 ===> DETECTING
 ...

katacoda/scenarios/buildpack-author-guide/detection.md

@@ -33,7 +33,6 @@ pack build test-ruby-app --path ./ruby-sample-app --buildpack ./ruby-buildpack
 
 You should see the following output:
 
-<!-- test:assert=contains -->
 ```
 Previous image with name "test-ruby-app" not found
 ===> DETECTING
@@ -42,7 +41,7 @@ examples/ruby 0.0.1
 ===> BUILDING
 ---> Ruby Buildpack
 ERROR: failed to build: exit status 1
-ERROR: failed to build: executing lifecycle
+ERROR: failed to build: executing lifecycle: failed with status code: 51
 ```
 
 Notice that `detect` now passes because there is a valid `Gemfile` in the Ruby app at `ruby-sample-app`, but now `build` fails because it is currently written to error out.