Also on a separate note, what would be the necessary procedure for getting nightlies going of this? I can happily set it up on my VPS (it's OpenVZ so it has its equal share of 2 hexacore xeons foor a make -j16 maybe 32
) then upload them to some sort of file host each night (or if there is an android hosting service that works over FTP I can automate that). Setting Jenkins up shouldn't be too much of an issue. Opinions on this? I assume I'd set it up by checking all the code out via repo and doing an initial build then future updates would just sync the repo again then re-make and zip/upload right? I'm getting into CyanogenMod compiling at the moment (source is taking ages to download on my puny home connection but my server has 100mbit down so that should help!).
My questions really are:
1) @waydownsouth would you want this?
2) @all: would it be useful?
3) @waydownsouth how does your source tree work in terms of pulling the code, syncing, compiling then syncing at a later date without having to pull the entire multi-gigabyte tree again?
4) If we went ahead with nightlies, where would you all want the files stored? I can't use my server for hosting the final builds due to a bandwidth cap each month but I've calculated that I have more then enough to put the files elsewhere
5) How does ¬3:45am BST for the cron sound? hehe
Sent from my A500 using Tapatalk 2