Avoid using bsdtar for extraction during build

[joelsmith]

No description provided.

[bparees]

[test]

[bparees]

[testextended][extended:core(builds)]

[bparees]

this seems to have pretty clearly broken binary build functionality :(

[bparees]

failure is:

F0812 15:05:16.451243       1 helpers.go:108] error: build error: unable to extract binary build input, must be a zip, tar, or gzipped tar, or specified as a file: exit status 2

[joelsmith]

@bparees I think I have fixed the issue. The shell wanted $0 instead of $1 for -c params. From bash(1):
If the -c option is present, then commands are read from the first non-option argument command_string. If there are arguments after the command_string, they are assigned to the positional parameters, starting with $0
I made a little test program that only extracts and that change seemed to fix it, so I expect this time things will go better.

[joelsmith]

[test]

[openshift-bot]

Evaluated for origin testextended up to 4beb260

[openshift-bot]

continuous-integration/openshift-jenkins/testextended SUCCESS (https://ci.openshift.redhat.com/jenkins/job/test_pr_origin_extended/427/) (Extended Tests: core(builds))

[openshift-bot]

Evaluated for origin test up to 4beb260

[bparees]

@smarterclayton tested this syntax locally using a zip archive, tar archive, tar.gz archive, and tar.bz2 archive, all worked.

thanks @joelsmith!

[merge]

[openshift-bot]

continuous-integration/openshift-jenkins/merge SUCCESS (https://ci.openshift.redhat.com/jenkins/job/test_pr_origin/7892/) (Image: devenv-rhel7_4817)

[openshift-bot]

Evaluated for origin merge up to 4beb260

[openshift-bot]

continuous-integration/openshift-jenkins/test SUCCESS (https://ci.openshift.redhat.com/jenkins/job/test_pr_origin/7875/)