Consider serving the nightlies out/ folder over HTTP

There are multiple artifacts we need to fetch in order to do development builds of tor and mullvad browser. Not only on Android, but also on Desktop we have fetch steps in the build.

Desktop gets clever and fetches a released binary and then gets the artifacts from there, while Android requires a user to have built tbb and then fetches from their local out/ folder.

Other than the artifacts we already fetch, there are toolchains we need to use for development that could be fetched from tbb such as clang, node, rust etc.

I propose we make the nightlies out/ folder public, so that we can easily fetch artifacts from tbb --without having to build it.

This is related to also building in the browsers CI, as it would make sense to use as much of the toolchains from tbb as possible in there for consistency sake.

Once this is published, we will also be able to hook ./mach bootstrap to fetch from this folder for a very nice developer experience.

marked this issue as related to #41368

marked this issue as related to tor-browser#43564

I propose we make the nightlies out/ folder public, so that we can easily fetch artifacts from tbb --without having to build it.

I think it's a good idea, and very easy to do.

On tb-build-06 I've now added a symlink in ~tb-build/public_html, so the out directory is now accessible at this URL: https://tb-build-06.torproject.org/~tb-builder/tor-browser-build/out/

On tb-build-06 I've now added a symlink in ~tb-build/public_html, so the out directory is now accessible at this URL: https://tb-build-06.torproject.org/~tb-builder/tor-browser-build/out/

It seems that's not enough, as many of the directories inside out are created with permission 0700. I've opened rbm#40083 (closed).

@boklm Amazing! Thanks you!

Q: How often do we prune old builds from these directories?

Q: How often do we prune old builds from these directories?

We're pruning files in this directory every night just before starting the new build.

If a file is not used in the new build, it gets removed, but it is kept if still used.

Ok, good to know. That is fine for now. I wonder if in the future we will want o hold on for artifacts for longer to keep supporting older builds, but let's not worry about it for now since it's not an issue.

It seems that's not enough, as many of the directories inside out are created with permission 0700. I've opened rbm#40083 (closed).

When it's merged, rbm!69 (merged) should fix the permission issue.

When it's merged, rbm!69 (merged) should fix the permission issue.

This should fix permission on the directories of the components when they get rebuilt, and I've manually fixed permissions on the other directories.

marked this issue as related to rbm#40083 (closed)

mentioned in merge request rbm!69 (merged)