Status: Assigned Owner: eric.blake CC: maruelatchromium, [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected] Labels: Type-Feature Pri-2 OS-All Area-Infrastructure Size-Large Mstone-4
New issue 23315 by [email protected]: archive_build should be driven from the source http://code.google.com/p/chromium/issues/detail?id=23315 The archive_build step for official builds is a build slave script. Some of it is driven from file lists checked into the tree, but some of it is not. When the build output changes, we often have to change the archive_build.py script to keep the official build working. However, this means that the build slave will likely fail if we then feed it an official build from an older branch. I'd like the entire archive step to be driven from files/programs checked into the source tree. That way any branch should continue to build properly (if something changes, we can patch any branch to do the right thing). I don't care how we do this. Assigning to Eric, but anyone with good ideas and who has any understanding of the current spaghetti scripts is welcome to help, pitch in great ideas, etc. The archive step consists of mapping build outputs to some save location and also uploading symbols... do we need to split that up? -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs -~----------~----~----~----~------~----~------~--~---
