Updating blue green pipeline with applier v2.0.3

[etsauer]

What does this PR do?

see title

How should this be tested?

Run the following command:

echo "SOURCE_REPOSITORY_URL=https://github.com/etsauer/container-pipelines.git
SOURCE_REPOSITORY_REF=blue-green-applier-update" >> blue-green-spring/.openshift/builds/params

Then follow the Automated Deployment steps in blue-green-spring/README.md

Is there a relevant Issue open for this?

#39

Who would you like to review this?

cc: @redhat-cop/containers-approvers

[oybed]

is it intentional to point to a person's repo here, rather than the redhat-cop repo?

[oybed]

Would be nice to see an updated "Display Name" for these projects to allow for a "natural grouping" in the OpenShift web console. (like the "basic spring" deployment) - especially the "non-descriptive" name Build - Jenkins is here

[oybed]

The build failed with the following error message in Jenkins:

 :
[spring-boot-web-build-spring-boot-web-pipeline] Running shell script
+ rm -rf oc-build
+ mkdir -p oc-build/deployments
++ echo 'jar;war;ear'
++ tr ';' '\n'
+ for t in '$(echo "jar;war;ear" | tr ";" "\n")'
+ cp -rfv ./target/shift-rest-0.1.0.jar oc-build/deployments/
'./target/shift-rest-0.1.0.jar' -> 'oc-build/deployments/shift-rest-0.1.0.jar'
+ for t in '$(echo "jar;war;ear" | tr ";" "\n")'
+ cp -rfv './target/*.war' oc-build/deployments/
+ echo 'No war files'
No war files
+ for t in '$(echo "jar;war;ear" | tr ";" "\n")'
+ cp -rfv './target/*.ear' oc-build/deployments/
+ echo 'No ear files'
No ear files
+ oc --request-timeout=0 --token=[hidden] --server=https://openshift.default.svc.cluster.local --certificate-authority=/run/secrets/kubernetes.io/serviceaccount/ca.crt --namespace=spring-boot-web-build start-build /spring-boot-web --from-dir=oc-build --wait=true --follow=true
error: a resource must be present, got: {  }
+ exit 1
[Pipeline] }
[Pipeline] // stage
[Pipeline] }
[Pipeline] // node
[Pipeline] End of Pipeline
ERROR: script returned exit code 1
Finished: FAILURE

[etsauer]

@oybed addressed your comments, and updated the testing instructions. hopefully that works for you now.

[oybed]

Tested and found to be fully working now. Merging.