PACman BuildBox (ALL DEVICE MAINTAINERS NEED TO REPLY)

[bluefa1con]

hey guys i have a great news for you guys. The guys at basketbuild are offering us buildbox and hosting for pacman.Now i need some help from you guys to have as many devices to build automatically as we can. The buildbox will build stable aswell as nightlies when needed.

To have your device on buildbox here are the conditions

1. Your dependencies and manifest files should be complete under https://github.com/PAC-man/android_vendor_pac/tree/cm-10.1/manifest (only use the removes where needed) https://github.com/PAC-man/android_vendor_pac/tree/cm-10.1/dependencies
2. The settings you pushed for your devices MUST be able to build pacman and the output zip must be working as you wont be able to add or remove stuff from zip, it will be automatically uploaded to the file host when built.
3. You must specifically tell me to include your device in the buildbox as i wont risk adding devices unless told my the device maintainer.
4. You must have the spirit of sharing and open source and not using pacman to get fame, for example useless themes and tweak apps. Things like these maybe included in a separate zip on your thread but they must not be associated with pacman.
5. There must be atleast a significant amount of people using your builds, for example a device that has under 100 downloads per release will take time off buildbox but wont be able to deliver to as much people as a semi popular device. So i will prefer devices having atleast a decent amount of activity related to pacman. In short we dont have infinite spots so i will prefer more popular devices over less popular.

Another thing i need some people to manage buildbox with me.

1. The buildbox access is a sensitive thing and comes with great power so i will only be accepting people who i or szl trust and have contributed to the project.
2. You must be able to configure and have knowledge of linux terminal via SSH. Ability to write build script etc will also be appreciated.

i also need some ideas about layout of the download page. we will be getting a special pacman domain on the site basketbuild.com i was thinking about 2 folders: Official Release and Nightlies, and they can be further divided to devices or Device Folders and than Official Release and Nightlies inside which one do you think is better? the first one is how CM manages it

NOTE: Dont close this, i will close it once i feel its time to

[blindndumb]

Cool man ! that's awesome.. I will update the dependencies , adds and removes soon for desire s. Downloads are more than 5000 for RC's

Getting files ready to support Desire HD and Incredible S too

[cmartinbaughman]

I'm very interested in this one! I maintain 3 devices. One is very popular (about 600 downloads to 800) but the others one has around 500 or so downloads per release and the other only about 250 give or take. Would only the more popular of the three be eligible for inclusion? Let me know if you need help with any setup or whatever, I was a developer for an ISP for a few years and have been using Linux as my OS for over a decade.

[jaydub82]

I would love this. As of now though the devices I maintain ( Hercules and t0lte ) are a litle light on downloads. If they pick up I will let you know. On Mar 11, 2013 1:18 AM, "bluefa1con" notifications@github.com wrote:

hey guys i have a great news for you guys. The guys at basketbuild are offering us buildbox and hosting for pacman.Now i need some help from you guys to have as many devices to build automatically as we can. The buildbox will build stable aswell as nightlies when needed.

To have your device on buildbox here are the conditions

1. Your dependencies and manifest files should be complete under https://github.com/PAC-man/android_vendor_pac/tree/cm-10.1/manifest https://github.com/PAC-man/android_vendor_pac/tree/cm-10.1/dependencies

   1.

   The settings you pushed for your devices MUST be able to build pacman and the output zip must be working as you wont be able to add or remove stuff from zip, it will be automatically uploaded to the file host when built. 2.

   You must specifically tell me to include your device in the buildbox as i wont risk adding devices unless told my the device maintainer. 3.

   You must have the spirit of sharing and open source and not using pacman to get fame, for example useless themes and tweak apps. Things like these maybe included in a separate zip on your thread but they must not be associated with pacman. 4.

   There must be atleast a handful of people using your builds, for example a device that has under 100 downloads per release will take time off buildbox but wont be able to deliver to as much people as a semi popular device. So i will prefer devices having atleast a decent amount of activity related to pacman.

Another thing i need some people to manage buildbox with me.

1. The buildbox access is a sensitive thing and comes with great power so i will only be accepting people who i or szl trust and have contributed to the project.
2. You must be able to configure and have knowledge of linux terminal via SSH. Ability to write build script etc will also be appreciated.

i also need some ideas about layout of the download page. we will be getting a special pacman domain on the site basketbuild.com i was thinking about 2 folders: Official Release and Nightlies, and they can be further divided to devices or Device Folders and than Official Release and Nightlies inside which one do you think is better? the first one is how CM manages it

NOTE: Dont close this, i will close it once i feel its time to

— Reply to this email directly or view it on GitHubhttps://github.com/PAC-man/android_vendor_pac/issues/54 .

[markp-mckinney]

You already know I'm in :)

Hit me up on gtalk, I have something to show you/talk to you about. I put a script together for all devices which includes test and release uploads and I could add in nightlies as well.

[oerner]

great! the p920 gets about 250 downloads would be nice to have it in the buildbox cause my upload speeds are crap :D

[gs2usr]

skyrocket gets pretty decent downloads, everything's in place for it to build. it'd be greatly appreciated if it was included. I like the idea of the page like CMs with the exception of when you first arrive to the page, instead of showing all downloads, we should have the PAC logo and some quick info about PAC-man ROM, as well as flashing warnings and what not.

[bluefa1con]

adding .remove files can cluster the local manifest on buildbox i think its better that we only use dependencies files unless really needed to change a pacman/cm repo for a third party i am testing the buildbox right now page will be done tonight but we can edit it later

[metaiiica]

this is a good idea, but yesterday i have registered a new Domain for use with OTA-Updater so i can upload directly to the Domain... Have fast speed and the upload is fast too..in the Moment i would build a automatic uploader and automatic subscriber for the OTA. Must see if that work

[Druboo666]

Dont Forget About Haida (Xperia Neo V) as this one is also quite popular

[Papa-Smurf151]

I'd like to add d2spr to build box. Ill make sure all the vendor files r up to date when i get home from work On Mar 11, 2013 2:18 AM, "bluefa1con" notifications@github.com wrote:

hey guys i have a great news for you guys. The guys at basketbuild are offering us buildbox and hosting for pacman.Now i need some help from you guys to have as many devices to build automatically as we can. The buildbox will build stable aswell as nightlies when needed.

To have your device on buildbox here are the conditions

1. Your dependencies and manifest files should be complete under https://github.com/PAC-man/android_vendor_pac/tree/cm-10.1/manifest https://github.com/PAC-man/android_vendor_pac/tree/cm-10.1/dependencies

   1.

   The settings you pushed for your devices MUST be able to build pacman and the output zip must be working as you wont be able to add or remove stuff from zip, it will be automatically uploaded to the file host when built. 2.

   You must specifically tell me to include your device in the buildbox as i wont risk adding devices unless told my the device maintainer. 3.

   You must have the spirit of sharing and open source and not using pacman to get fame, for example useless themes and tweak apps. Things like these maybe included in a separate zip on your thread but they must not be associated with pacman. 4.

   There must be atleast a handful of people using your builds, for example a device that has under 100 downloads per release will take time off buildbox but wont be able to deliver to as much people as a semi popular device. So i will prefer devices having atleast a decent amount of activity related to pacman.

Another thing i need some people to manage buildbox with me.

1. The buildbox access is a sensitive thing and comes with great power so i will only be accepting people who i or szl trust and have contributed to the project.
2. You must be able to configure and have knowledge of linux terminal via SSH. Ability to write build script etc will also be appreciated.

i also need some ideas about layout of the download page. we will be getting a special pacman domain on the site basketbuild.com i was thinking about 2 folders: Official Release and Nightlies, and they can be further divided to devices or Device Folders and than Official Release and Nightlies inside which one do you think is better? the first one is how CM manages it

NOTE: Dont close this, i will close it once i feel its time to

— Reply to this email directly or view it on GitHubhttps://github.com/PAC-man/android_vendor_pac/issues/54 .

[gs2usr]

@bluefa1con, so does everyone need to update their pac_(product).mk files to include: GET_DEPENDENCIES := $(shell vendor/pac/tools/getdependencies.py $(PRODUCT_NAME)) so that all dependencies get added to the buildbox' local minifest?

[markp-mckinney]

@gs2usr, no, the build script we have does that already so the device files themselves don't need to be changed as long as there is a device.dependencies file

[gs2usr]

Thanks for the response.

[bluefa1con]

sniper saved me time in writing a new script he made a script that will compile and upload the build to either nighly or stable folders

[jaydub82]

Bluefa1con, Is there anything I need to do to get my devices ready for the build bot? Sorry trying to follow but I am at work so its kinda hard. On Mar 11, 2013 3:28 PM, "bluefa1con" notifications@github.com wrote:

sniper saved me time in writing a new script he made a script that will compile and upload the build to either nighly or stable folders

— Reply to this email directly or view it on GitHubhttps://github.com/PAC-man/android_vendor_pac/issues/54#issuecomment-14740571 .

[Nick0703]

Thanks! It would be nice to have a buildbox for my captivatemtd.

[bluefa1con]

@jaydub82 just make sure there is a dependencies file for your device

[singhdd93]

Nice thing but My devices dont need this at all. The max downloads is 100 of a nightly of Mango/Coconut and other two have even lesser

[jaydub82]

@bluefa1con thanks t0lte and Hercules are good to go. On Mar 12, 2013 1:40 AM, "bluefa1con" notifications@github.com wrote:

@jaydub82 https://github.com/jaydub82 just make sure there is a dependencies file for your device

— Reply to this email directly or view it on GitHubhttps://github.com/PAC-man/android_vendor_pac/issues/54#issuecomment-14760800 .

[bluefa1con]

http://pacman.basketbuild.com/saga build up please test and report back i will build the rest tonight

[blindndumb]

Tested SAGA , Working fine !! The clock issue still there , I will commit a fix tonight :)

[OldDroid]

add me ;-) will rebase my manifest aswell ;-) oh and my roms gots over 26000+ downloads

[szlkiev]

Wow thats a lot, 26000 per every release, per device? or globally for all of your several devices & summarize them from all release since beginning?

Xperia ray just get average 1500 downloads each release :-/

[OldDroid]

w8, for p500 i got around 3200 for the first release, on gio 6700 and on ace almost 10000 compared with the last statts :)

[bluefa1con]

some changes i need to tell you guys if your device cant use the default CM/PACman repos i cant include that in the buildbox it ruins the point of having automated builds when you have to change the local manifest every time for different devices this includes changing the camera app, changing the proprietary vendor folder to a custom one having custom framework/native etc repos so i need you guys to include ONLY THE DEVICE TREE IN THE DEPENDENCIES FILE yesterday when i launched buildbox for a nightly build it failed because the local manifest had different repos removed and added from different devices here is an example of what happened http://pastebin.com/ZHNUwsbZ

changing repos like this will ruin the buildbox so comply with the instructions and include only the device tree if u want automated builds

[blindndumb]

May be we can do this way.. It will check if roomservice.xml is present or not at start of build. If yes then it will delete it and continue with creating a new roomservice.xml for the device, fetching its repo and building !

The problem is devices are old and now they are no more compatible with hardware repos of CyanogenMod.

[inyourface09]

At about 6000 dl's for primoc and primou. Once i get the build stable ill add the adds and removes for them. I'm very happy about this Pacman is growing faster than I ever could have hoped.

[oerner]

crespo first builf got about 100 downloads in less then a day

[OldDroid]

agreed with blinddump, many xperia devices using aswell new hardware things, for my one (armv6 repos) there are around 17 trees to re-new so build doesnt land in trouble

[atrus5]

Would love to use this feature. I don't add anything to the rom after building it with the exact same files as what is merged with the pac vendor. I am at 250 downloads after 2 days. I am new to maintaining this so I don't know yet what a full release will look like as far as numbers go. They have taken down the blob files and device tree for the ville, some violation of terms. I am using my own repo for that. I hope this is acceptable. I don't know how to use the adds and removes files yet. If someone could help me understand how to use that I would appreciate it. Thank you. Would love to learn.

[klin1344]

Please add d2tmo, d2att, and d2vzw. They build fine using the default CM / PAC-Man repos, with no need for adds and removes files. They get around 500 to 600 downloads each, per each new build (every 3-5 days). Thanks for this, and I think that users would really appreciate nightlies for PAC-Man.

[klin1344]

I have fixed up the dependencies for the all the d2's, so you can add them to the buildbox for future nightlies / releases. Thanks.

[C457]

Wish the fascinate and epic 4g were more popular, but updated fascinate .adds and removes to fix force closing issue.

[Nick0703]

I updated the captivatemtd manifests, it should be compatible with the buildbox now.

[bluefa1con]

the devices that are confirmed to work and are on buildbox i9100 i9100G mako grouper maguro d710

[gs2usr]

Are there any confirmed not working?

[bluefa1con]

any device which changes the default repos the buildbox is getting an upgrade soon and i might add more devices

[klin1344]

Bluefa1con, can you try d2tmo, d2att, and d2vzw when you have time and the resources? They do not change the default repos; all that is tracked in the local_manifest are the additional device trees and the kernel for those devices. A d2tmo build I uploaded on 3/13 just hit over 1000 downloads, and the d2att and d2vzw have about 700 each. Thank you.

[jaydub82]

Can you also run t0lte hercules

They only pull device trees and kernel to local_manifests as well On Mar 21, 2013 5:48 PM, "klin1344" notifications@github.com wrote:

Bluefa1con, can you try d2tmo, d2att, and d2vzw when you have time and the resources? They do not change the default repos; all that is tracked in the local_manifest are the additional device trees and the kernel for those devices. A d2tmo build I uploaded on 3/13 just hit over 1000 downloads, and the d2att and d2vzw have about 700 each. Thank you.

— Reply to this email directly or view it on GitHubhttps://github.com/PAC-man/android_vendor_pac/issues/54#issuecomment-15271266 .

[OldDroid]

i think you should try a build with 1 of my armv6 devices to test it fully! they are replacinf in manifest around 20 repos ;-)

[szlkiev]

The repo in buldbox is static, because its used to build several devices at the same time, so the repo can not be switched to others than the main manifest, unless it been told to build 1 by 1 with repo syncing first every time before it build a different device, so if in 1 day the server build for 20 devices, mean it will repo sync 20 times.

So it depends on the build script for a batch build

[markp-mckinney]

@bluefa1con and everyone else

The last one is finishing uploading, but I just ran a successful build of the following on the bot: i9100, i9100G, mako, maguro, d710

And that was just with one command :)

bluefa1con, you wrote it down, but we don't currently have support for grouper?...

[vertigo2012]

I've just built grouper and was going to open a thread tomorrow, well today now lol... Squared it with bluefa1con, just been waiting for the right time to build... let me know if someone else wants to do it ;)

Glad the mako built ok with the PA kernel instead of CM

[markp-mckinney]

@vertigo2012 You're welcome to submit a commit for the device if you want :)

[Nick0703]

@Sniper- Could you make a test build for the captivatemtd, p3100, p3110, p5100 and p5110? I updated their manifests and dependencies.

[markp-mckinney]

Alright, so I just set up the bot to do nightlies of the following devices:

i9100, i9100G, mako, grouper, maguro, d710

@Nick0703 Do those add/remove from the default repos or just have local manifest edits?

[Nick0703]

@Sniper- Yeah those add/remove are from the default repos (captivatemtd) and for the p31xx and p51xx I had to use another repo sources as the CM's one don't work properly for the device. But either way both of them don't modify or change any of PAC's repos.

[klin1344]

Sniper, could you include d2tmo, d2att, and d2vzw (US Galaxy S3's) in the nightlies? They do not add or remove the default repos and just use the local manifests for device trees and the kernel.

Thanks.

[Papa-Smurf151]

and d2spr

On Mon, Apr 1, 2013 at 8:45 PM, klin1344 notifications@github.com wrote:

Sniper, could you include d2tmo, d2att, and d2vzw (US Galaxy S3's) in the nightlies? They do not add or remove the default repos and just use the local manifests for device trees and the kernel.

Thanks.

— Reply to this email directly or view it on GitHubhttps://github.com/PAC-man/android_vendor_pac/issues/54#issuecomment-15746521 .

[markp-mckinney]

I added all the d2's

@Nick0703 they're building now.