Added checks in build path for docker-compose import #9816
Conversation
surajssd
changed the title
surajssd
force-pushed
the
absolute-path-docker-compose
branch
from
bfbd542 to
8b0e2ec
Compare
So when build path is resolved, or when it is being converted from relative path to absolute path, a check has been added which checks if the path is already absolute, if it is, no further operations performed and value of Build path is kept unaltered. Fixes openshift#9815
surajssd
force-pushed
the
absolute-path-docker-compose
branch
from
8b0e2ec to
994857a
Compare
|
ping @smarterclayton |
|
LGTM [merge] thanks |
|
[merge] On Tue, Jul 19, 2016 at 1:45 PM, OpenShift Bot [email protected]
|
|
[merge] On Tue, Jul 19, 2016 at 3:00 PM, OpenShift Bot [email protected]
|
|
continuous-integration/openshift-jenkins/merge SUCCESS (https://ci.openshift.redhat.com/jenkins/job/test_pr_origin/6578/) (Image: devenv-rhel7_4631) |
|
Something seems to be wrong with the test infra? |
|
AWS was down. [merge] On Wed, Jul 20, 2016 at 6:04 AM, Suraj Deshmukh [email protected]
|
|
Evaluated for origin merge up to 994857a |
So when build path is resolved, or when it is being converted from relative path to absolute path, a check has been added which checks if the path is already absolute, if it is, no further operations performed and value of Build path is kept unaltered.
Fixes #9815