Infrastructure

- Start with existing 4.4 bibisect repository (http://people.canonical.com/~bjoern/bibisect/bibisect-44alpha2only.tar.xz)
- Remote server will build and then provide public access to 4.4 linux repo (Correction: I guess we have space on dev-downloads.libreoffice.org/bibisect/linux/ for them now)

Bjoern has suggested that we split up the bibisect repo as the first one (3.5 - 4.3) is 12GB. I think one repo for each Major.minor release series might be too small a chunk, and one repo for each Major release might be (roughly) about right. If the size of each build increases and we can't de-duplicate that overhead, then we may need to use more repositories to contain all of the bibisect information.

Alex: Couple of q's for you:
1) Is the bibisect server referred to as the "Colocated Buildbot" in our infra documentation?
2) Are my credentials properly added to the bibisect server?
I was running into some problems when I tried to log-in

Thanks!

Thanks! Does this require continuous/recurring work, or can this task be closed now and the machine "automagically" :) works?

Robinson? Can you give me feedback on the above question? :-)

Robinson?

Florian Effenberger wrote:

Robinson?

The bibisect repositories have usually been updated manually in chunks, so we could go from 4.4 betas -> RC, or go to the first release. I just talked with Joel this week, and he was supportive of having the bibisect builder feed automatically into the git repository; I do need to figure out some details about gc'ing the repo (and how much data individuals need to download daily), so I'm going to get my notes together and then ping Bjoern. [That could be a new task, or I can just contineu in this thread]

Ping?

Florian Effenberger wrote:

If you can make it a new task, that'd be great. Ideally a recurring one (just prefix the title with "RECURRING: " until I've installed a Redmine plugin for this, so it can be shifted to each new week, and someone can jump in when needed

Yep, created as #1028