Shopify build e2e #4300
Shopify build e2e #4300
Conversation
* Fix CI by letting travis build Shopify/ingress image * Remove static check, coverage and e2e jobs temporarily * Update .travis/common.sh * Change registry to Docker Hub * Add condition to trigger travis image build only on master * Trigger image push + build on push events only * Re-add travis CI tests * Fix CI e2e problem * Update nginx-ingress:test image * Trigger NGINX image build by changing on travis CI ENV * Update build.sh to be the same as upstream * Stop building all architectures except amd64 * Re-add docker_tag exists function to common.sh * Modify docker_tag_exists() method to work with Docker Hub * Re-add test coverage to CI * Publish image only on pushes to master * Undo Makefile ENV changes and add environment changes on travis ci environment settings * Re-add multiple architecture image builds * Update common.sh with build checks * Add new line to EOF: common.sh
* Update nginx image * Update minikube start script
release latest version
…fault nginx-configuration state between tests
Extract UpdateConfigmap into e2e framework
LuaJIT is not available for s390x and ppc64le, disable the lua part in nginx.tmpl on these platform.
Sync upstream
Sync upstream
match with upstream
group client metrics by host? dest_host tag instead of host tag add tags to client response time upstream name instead not reading json config anymore, relying on env vars Resort to default instead of crashing Proper variable scoping in defer.lua and other small fixes juggling methods around for better division of responsibilities
Emit response StatsD metrics about upstreams when dynamic configuration is enabled
Sync upstream
Enabling Shopify Build Pipeline: ingress
|
Keywords which can automatically close issues and at(@) mentions are not allowed in commit messages. The list of commits with invalid commit messages:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
k8s-ci-robot
added
the
do-not-merge/invalid-commit-message
k8s-ci-robot
added
the
size/XXL
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ElvinEfendi The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
k8s-ci-robot
added
the
approved
|
@ElvinEfendi: The following test failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
What this PR does / why we need it:
Which issue this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)format, will close that issue when PR gets merged): fixes #Special notes for your reviewer: