> If I go to, say, > http://build.chromium.org/p/chromium/builders/Mac/builds/22569 and click the > "download" link in the "archive build" step I'm taken to a valid URL whose > parent directory contains valid binaries. The same holds for other builders > there.
Yes, you are right. I was just reading the log of the archive step and seems it is archiving to google storage. Sorry for that. > In any case, if you mean the binaries could be hosted in a location > accessible only to Intel employees, I disagree: there should be no separation > between Intel and non-Intel contributors (especially if we decide to keep the > binaries somewhere and some people report bugs or test those while others > cannot). > Right, this is in line with what I originally described. Most of the time, > the changes in a single commit should be small enough for the other people > you're working with to be able to build it themselves too, no? > If the current upload speed problems cannot be solved, using the build bot as > a fast compiler does not sound like a compelling enough reason to keep > archiving those binaries IMO. There is always alternatives, and we just need to determine whether it worth the tradeoff. The archiving will bring us convenience, but if it's too painful to achieve it right now. I am ok with not having it currently. If people find they really need it, we can add it then. Let's hearing others if they have more desire on the archiving. Thanks, Shiliu. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Raphael Kubo da Costa Sent: Thursday, October 24, 2013 5:07 PM To: [email protected] Subject: Re: [Crosswalk-dev] RFC: Not archive build on the public build bots "Wang, Shiliu" <[email protected]> writes: >> Depending on the platform, the binaries generated by each of those >> builders can be several hundreds of megabytes in size (for example, >> crosswalk-debuginfo-2.31.22.0-0.i586.rpm has 441M, xwalk-linux.zip >> plus its two tests are around 250M). Transfering such amount of data >> from the build slaves to the master in 01.org can be insanely slow >> (the test Linux builder I mentioned above took more than 1 hour to >> transfer 250M). > > Shiliu: The archive host doesn't have to be 01.org. That is true, but it's sort of the only place we have for that (and also the official one with the rest of crosswalk-project.org). > I think that we keep the archive host internal is also acceptable. ( > The download link on chromium's waterfall page is also invalid ) If I go to, say, http://build.chromium.org/p/chromium/builders/Mac/builds/22569 and click the "download" link in the "archive build" step I'm taken to a valid URL whose parent directory contains valid binaries. The same holds for other builders there. In any case, if you mean the binaries could be hosted in a location accessible only to Intel employees, I disagree: there should be no separation between Intel and non-Intel contributors (especially if we decide to keep the binaries somewhere and some people report bugs or test those while others cannot). >> Personally, I don't find it very useful to archive such data, even if >> for a limited amount of time: so far, I've seen people use the Linux >> binaries to avoid having to build Crosswalk themselves, or the Tizen >> RPMs for the same reason. Does anyone else know of another reason >> other than that for keeping those binaries around? Would it ruin >> anyone's life if we stopped doing that once we start using >> build.crosswalk-project.org? > > Shiliu: For me, when I want to get some binaries without compiling it > myself, I will get to buildbot archive instead of canary build. The > main reason is that the canary build will never contain the change I > just check in, and I may work with others on some feature, and I want > them to verify the change I just made. Right, this is in line with what I originally described. Most of the time, the changes in a single commit should be small enough for the other people you're working with to be able to build it themselves too, no? If the current upload speed problems cannot be solved, using the build bot as a fast compiler does not sound like a compelling enough reason to keep archiving those binaries IMO. _______________________________________________ Crosswalk-dev mailing list [email protected] https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-dev _______________________________________________ Crosswalk-dev mailing list [email protected] https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-dev
