new-app: fix priority of Jenkinsfile, Dockerfile, source when strategy unspecified

[jim-minter]

https://trello.com/c/H6ZwrpCo/995-5-new-app-new-build-support-for-pipeline-buildconfigs-techdebt

@wanghaoran1988

Resolves the further discussion in #11897.

I agree it's not clear what's best and no way to maintain true compatibility.

jenkinsfile -> dockerfile -> source seems reasonable to me. As you say, making jenkinsfile king makes sense.

[bparees]

lgtm [merge]

[openshift-bot]

[Test]ing while waiting on the merge queue

[openshift-bot]

Evaluated for origin test up to 9c2cb79

[openshift-bot]

continuous-integration/openshift-jenkins/test FAILURE (https://ci.openshift.redhat.com/jenkins/job/test_pr_origin/11609/) (Base Commit: 1f1e6de)

[bparees]

[merge]

Ben Parees | OpenShift

On Nov 21, 2016 8:37 PM, "OpenShift Bot" notifications@github.com wrote:

continuous-integration/openshift-jenkins/merge FAILURE (
https://ci.openshift.redhat.com/jenkins/job/test_pr_origin/11621/) (Base
Commit: 75aa09c
75aa09c
)

—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
#11982 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEvl3ngjJRHFasrpbwJnThoJgrmBSE5qks5rAkdRgaJpZM4K4ZtN
.

[openshift-bot]

Evaluated for origin merge up to 9c2cb79

[openshift-bot]

continuous-integration/openshift-jenkins/merge SUCCESS (https://ci.openshift.redhat.com/jenkins/job/test_pr_origin/11622/) (Base Commit: 75aa09c) (Image: devenv-rhel7_5397)