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

Mirror source tarballs for contributing setup - oilshell.org and/or git scalar #1925

Open
andychu opened this issue Apr 8, 2024 · 4 comments

Comments

@andychu
Copy link
Contributor

andychu commented Apr 8, 2024

          Also python 2 package retriving from python's official source is apparantly extremely slow in China, about 5KB/s. I modified it to some mirror site in China and managed to run this script and get errors. I'll try to see if waiting for 30min from python's official source will actually solve the issue.

image

eta 28min, crazy.

Originally posted by @glyh in #1923 (comment)

@andychu
Copy link
Contributor Author

andychu commented Apr 8, 2024

This will reduce any flakiness due to all the hosts we use

There are probably 5 different hosts -- it should be one

@andychu
Copy link
Contributor Author

andychu commented Apr 8, 2024

This also relates to xz backdoor fallout -- we want to build tarballs on 2 completely separate systems, and then compare them

Also do something about the intermediate docker containers ...

we don't have a 1 step build -- we have "caching" in Docker, which is not ideal

@glyh
Copy link
Collaborator

glyh commented Apr 8, 2024

I think caching is fine?

@andychu
Copy link
Contributor Author

andychu commented Apr 8, 2024

Using Docker is necessary to make our CI fast, and for it to run on both sourcehut and Github Actions

However it's a dependency from a security perspective -- if someone hacks Docker, then they can backdoor BOTH the sourcehut AND the Github Actions tarballs

That's bad

So I would like to get rid of it in the future. Probably won't happen for awhile though


i.e. Docker is a single point of failure. I would like to have 2 completely separate cloud builds, all running from the same git source repos, that produce the same exact release tarball

So that if one provider is hacked, we will know. They would have to hack multiple clouds at the same time to trick us

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants