Skip to content
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

Provide binary packages on Github #5647

Open
onitake opened this issue Oct 14, 2019 · 4 comments
Open

Provide binary packages on Github #5647

onitake opened this issue Oct 14, 2019 · 4 comments
Assignees
Labels

Comments

@onitake
Copy link

@onitake onitake commented Oct 14, 2019

Feature Request

Is your feature request related to a problem? Please describe:

Feature request

Describe the feature you'd like:

Currently, the only download location for binary releases seems to be http://download.pingcap.org , and there is no obvious place for a list of files or checksums.

Github already provides a convenient download page for releases, it would make a lot of sense to also post binaries there, along with the tarball of each release.

Describe alternatives you've considered:

Teachability, Documentation, Adoption, Migration Strategy:

Along with posting releases on Github, it might also make sense to integrate with a public CI/CD system that posts directly to Github. It's currently somewhat unclear how binaries are built and released.

@siddontang

This comment has been minimized.

Copy link
Contributor

@siddontang siddontang commented Oct 14, 2019

PTAL @zhouqiang-cl @dcalvin

maybe we can add the download here https://github.com/tikv/tikv/releases

@onitake

This comment has been minimized.

Copy link
Author

@onitake onitake commented Oct 17, 2019

That would be great!
It might also save on download time, because not all TiDB binaries are always need on every node.

@Hoverbear

This comment has been minimized.

Copy link
Member

@Hoverbear Hoverbear commented Oct 21, 2019

I've been talking to @zhouqiang-cl about this recently and we have a plan. I'm just waiting to hear back from him around some changes that might be required in the SRE repo.

@Hoverbear

This comment has been minimized.

Copy link
Member

@Hoverbear Hoverbear commented Nov 22, 2019

#5777 got us to a milestone here, we're just adjusting our CI infrastructure. :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
4 participants
You can’t perform that action at this time.