Allow contributors to launch integration tests against local registry#1014
Allow contributors to launch integration tests against local registry#1014tejal29 merged 1 commit intoGoogleContainerTools:masterfrom antechrestos:feature/add_documentation_for_local_integration_test
Conversation
|
@tejal29 can I have the kokoro result? |
|
Nice pull request. Significant improvement over how it was before. We're planning to get rid of Kokoro since Travis CI seems to be doing the job well enough and has public build logs. I don't know why Kokoro is failing. @tejal29 can you take a look at why Kokoro is failing? this is the short error log: |
|
@samos123 Luckily (for me) kokoro run successfully 😄 |
|
@tejal29 done. Other point, the integration test TestRun/test_Dockerfile_test_copy_symlink has random behaviour. I don't know why but it passed the first time, then I had to repush cause my code was not well formatted (one excessive space), then it failed twice and succeeded the third time. The two failure were due to |
This change allows user to launch integration tests with a local registry Fixes #1012
|
@tejal29 looks like you fixed the issue. I've rebased my work and it passed directly. I hope it was not due to luck 😏 . |
|
Thank you much! |
Fixes #1012
Description
This change allows contributors to launch integration tests with a local registry.
The idea is to check whether
IMAGE_REPOparameter andgcr.io, keep the previous thinggcr.iopublic images and push them to the target repo then launch the test. The rollback of savec files is made as a defer functionPlease also note that I isolated the code of test launching in a dedicated function as
os.Exitanddefercannot be mixed (asos.Exitexists without calling defered functions).Submitter Checklist
These are the criteria that every PR should meet, please check them off as you
review them:
See the contribution guide for more details.
Reviewer Notes