buildbot.mariadb.org (MDEV-8244)

[MDEV-12509] Don't upload packages to master Created: 2017-04-16  Updated: 2018-10-29  Resolved: 2018-10-29

Status: Closed
Project: MariaDB Server
Component/s: OTHER
Affects Version/s: None
Fix Version/s: N/A

Type: Technical task Priority: Major
Reporter: Sergei Golubchik Assignee: Sergei Golubchik
Resolution: Won't Fix Votes: 0
Labels: None


 Description   

Build slaves should not upload packages to the master.
Instead, they should be stored locally on slaves and the main download page should have links to them. Ideally, the download page will look as before, just links to binaries will be non-local.



 Comments   
Comment by Teodor Mircea Ionita (Inactive) [ 2018-10-22 ]

serg as discussed before, this doesn't really make sense for buildbot.mariadb.org, since many builders are:
1. using docker, no webserving or other public service running on the machines
2. build workers vary wildly in configuration between computing power, storage and network performance
3. actual machines are either owned or donated, behind firewalls or not and with unlimited resources or not
4. in the future we might scale builders, aka. run some extra machines temporarily in the cloud just for the duration of high activity period, say before a GA release

The only feasible way is still having a single download location. For now, buildbot.mariadb.org artefacts are available at:
ci.mariadb.org and from within the build logs:
https://buildbot.mariadb.org/#/builders/11/builds/637

Click on Step 11 -> Download. For now, the server can handle it, but yes, in the future this might not be desirable, however, this being hosted on DigitalOcean, I can easily split the asset serving to a different machine or just a Storage Bucket Space with static CDN serving that should scale for any load.

If you're satisfied with this resolution, you can close this issue.

Generated at Thu Feb 08 07:58:16 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.