-
Notifications
You must be signed in to change notification settings - Fork 339
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
ci: update build script, integrate with circleci #250
Conversation
247cdff
to
50501fe
Compare
e9620a3
to
65d95ea
Compare
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.
Hi @gszr .
Great work! Thanks a lot.
I've left a few comments on source files.
Additionally, I'm also wondering:
- would it be possible to setup a test repo on bintray so that we could test these scripts before merging into master ?
- I don't see handling of Docker images. will it be a separate PR ?
65d95ea
to
6cf8513
Compare
Will do one more test release on top of the "wip" commit (changing the Bintray repository to kuma-tests) - it'll be pushed to https://bintray.com/kong/kuma-tests. Edit: test was completed, commit reverted. |
6cf8513
to
9320f48
Compare
Actually, we need the |
3eaa820
to
324f7d6
Compare
I've been testing on https://bintray.com/kong/kuma-tests.
Yes, it will be done in a separate PR. |
6c245fa
to
2dc34be
Compare
2dc34be
to
ace94a0
Compare
@gszr awesome shell script, by the way. Thanks a lot! |
Summary
Releases are automatically built and pushed to Bintray whenever a tag is pushed.