Docker test container for travis login#3732
Conversation
Codecov Report
@@ Coverage Diff @@
## master #3732 +/- ##
=======================================
Coverage 44.19% 44.19%
=======================================
Files 139 139
Lines 13388 13388
=======================================
Hits 5917 5917
Misses 6888 6888
Partials 583 583 Continue to review full report at Codecov.
|
| @@ -0,0 +1,23 @@ | |||
| # Dockerfile to bootstrap build and test in openshift-ci | |||
|
|
|||
| FROM registry.svc.ci.openshift.org/openshift/release:golang-1.13 | |||
There was a problem hiding this comment.
Instead of fetching image stream again, I would say let's implement it as https://github.com/openshift/odo/blob/master/openshift-ci/build-root/source-image/Dockerfile#L1
There was a problem hiding this comment.
We can not create a separate test container with out pulling the image. BTW the travis test container has certain steps to follow and i do not pollute the regular test container with the travis steps.
Ofcourse as per the requirement i may need https://github.com/openshift/odo/blob/master/openshift-ci/build-root/source-image/Dockerfile#L1 in my corresponding release job pr for copying the oc binary.
There was a problem hiding this comment.
BTW the travis test container has certain steps to follow and i do not pollute the regular test container with the travis steps.
make sense 👍
But I would say once you get the overall workflow to do this, please ensure if we can have only one dockerfile for build. Other than that I am good with the changes.
/lgtm
There was a problem hiding this comment.
Corresponding ci pr created - openshift/release#10942
There was a problem hiding this comment.
But I would say once you get the overall workflow to do this, please ensure if we can have only one dockerfile for build.
@prietyc123 AFAIU It is not even possible because if i am installing packages in the source image for example https://github.com/openshift/odo/blob/master/openshift-ci/build-root/source-image/Dockerfile#L1 then it won't be propagated to the main build container. As per my requirement i do not need binary copy paste through the docker file, i need to install the packages for travis login in the main test container.
16d0fb1 to
ad043fb
Compare
/lgtm |
mohammedzee1000
left a comment
There was a problem hiding this comment.
looking good
/approve
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: mohammedzee1000 The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
3 similar comments
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
Please do not restart travis job. I am just experimenting the travis status is captured by prow bot or not |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
8 similar comments
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
1 similar comment
|
/retest Please review the full test history for this PR and help us cut down flakes. |
What type of PR is this?
/kind Feature
What does does this PR do / why we need it:
we are in process of getting the odo-bot GitHub token injected into prow. So creating a test container from where all these short of operation like travis cli install, travis login... etc will be launched
Which issue(s) this PR fixes:
Fixes : part of #2540
PR acceptance criteria:
Should not break master
How to test changes / Special notes to the reviewer: