-
Notifications
You must be signed in to change notification settings - Fork 8.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add scripts to release from travis-ci #1582
Conversation
Coverage remained the same at 33.49% when pulling 47ab12a31c171acd30ce1492b02782431383b3aa on aledbf:publish-scripts into d965ee8 on kubernetes:master. |
47ab12a
to
578ab75
Compare
No problem with that. Just tell me what registry I need to use. |
@bowei besides that, it makes the change to publish the images? |
578ab75
to
42dc410
Compare
Coverage decreased (-0.04%) to 33.452% when pulling 42dc4108e29389b13cf6c86aee25310961d3745a on aledbf:publish-scripts into d965ee8 on kubernetes:master. |
42dc410
to
7f85e5c
Compare
Coverage remained the same at 33.389% when pulling 7f85e5cc46295a6c2099ecaa87639f2fd08d80a1 on aledbf:publish-scripts into f8c2fb9 on kubernetes:master. |
7f85e5c
to
db04359
Compare
db04359
to
32d996f
Compare
32d996f
to
febd7cf
Compare
What this PR does / why we need it:
We need this PR to automate the release of images located in this repository using a third party service (travis-ci in this case)
To release an image we just require a personal travis-ci token with access to
kubernetes/ingress-nginx
and the name of the component to be released:Edit: the change of registries can be reverted. This is just to show the release procedure