-
Notifications
You must be signed in to change notification settings - Fork 159
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
Optimize image pushes and integration tests #5
Conversation
4d915b5
to
aa836d4
Compare
db17e35
to
ce5b98c
Compare
integ/main_test.go
Outdated
// var image = flag.String("image", "lyft/flinkk8soperator:latest", "image for the operator") | ||
var image = os.Getenv("OPERATOR_IMAGE") | ||
// var image = flag.String("image", "flinkk8soperator:latest", "image for the operator") | ||
var image = os.Getenv("IMAGE") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think OPERATOR_IMAGE is clearer, as there are several different images involved.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes. The documentation was IMage. Will change to Operator_image everywhere
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, I forgot to update the doc when I changed it a while back.
This PR will make images to be pushed only after merging to master. Integration tests will build images, and use the locally built images to run tests.
We can in future make images to be pushed to dockerhub on successful PR if needed.