WIP Improve new-build output cycle detection

[rhcarvalho]

This is a follow up to #7936.

The idea is to test all combinations of build strategy/from, triggers
and output reference, and improve the implementation to behave correctly
in all cases.

@bparees FYI.

[rhcarvalho]

Cover:

• The input and output images are not the same (from Regression: new-build / new-app input output cycle detection #7718)

          "sourceStrategy": {
            "from": {
              "kind": "DockerImage",
              "name": "centos/ruby-22-centos7:latest"
            }
          }

        "output": {
          "to": {
            "kind": "ImageStreamTag",
            "name": "internal-image:latest"
          }
        },

• Print a warning if we can detect a build loop in oc new-app

[bparees]

1 commit, zero files changed. impressive :)

[rhcarvalho]

Yes! Can you find any bug? ;-)
On Mar 14, 2016 8:30 PM, "Ben Parees" notifications@github.com wrote:

1 commit, zero files changed. impressive :)

—
Reply to this email directly or view it on GitHub
#7984 (comment).

[bparees]

Yes! Can you find any bug? ;-)

touche :)

[danmcp]

@rhcarvalho @bparees Bump

[openshift-bot]

Origin Action Required: Pull request cannot be automatically merged, please rebase your branch from latest HEAD and push again

[rhcarvalho]

Superseded by #10067.