Req #69042 [Csd]: Regular snapshot builds of php/php-src

Edit report at https://bugs.php.net/bug.php?id=69042&edit=1 ID: 69042 Updated by: pajoye@php.net Reported by: hiro+php at travis-ci dot org Summary: Regular snapshot builds of php/php-src Status: Closed Type: Feature/Change Request Package: *General Issues Operating System: N/A PHP Version: master-Git-2015-02-12 (snap) Assigned To: jacob Block user comment: N Private report: N New Comment: @hiro Do you have some time to chat about that? We have something very similar in place using some of the most popular apps and frameworks as test bases. It is used as part of our QA efforts, almost for all commits and for the RC phase of each release. It would be even more useful if we can get them run on travis as well along this php7 effort. I can imagine to increase the apps or cases and make them public, reducing the duplication of efforts, resources, etc. to test these usual suspects against latest php7-dev. Previous Comments: ------------------------------------------------------------------------ [2015-02-25 18:32:10] hiro+php at travis-ci dot org Hi, Jacob, We ended up hosting the nightly build archive on our S3 bucket. (And announced it to the world earlier today.) We'll see how much bandwidth we consume. https://twitter.com/travisci/status/570616566171242497 http://docs.travis-ci.com/user/languages/php/#PHP-nightly-builds ------------------------------------------------------------------------ [2015-02-18 20:50:35] jacob@php.net Hey, Thanks for your understanding here - I know it's not always ideal to push this sort of thing back to the end user services. > I think we can host the archives for our use, and see how it goes. Would love to know what you guys end up with! Let me know how you progress and if you need any assistance, I would be happy to set some time aside for it. ------------------------------------------------------------------------ [2015-02-18 02:14:42] hiro+php at travis-ci dot org Hi, Jacob, Thanks for checking. I appreciate the effort you expended on our behalf. I also understand that the dev team decided not to pursue it. I think we can host the archives for our use, and see how it goes. You can close this ticket now. Thanks again! ------------------------------------------------------------------------ [2015-02-17 23:12:45] jacob@php.net Hey, Apologies on the delay in getting back to you on this - I've had a tough time trying to get all of the right people online at the same time! Thanks for those usage stats, they came in handy. I haven't been able to get a definite answer on the uploading the php/php-src build artifact to another source for download and from the feedback I received, it wasn't something people were interested in using (for the development team anyway). Outside of the internals team, the nightly build probably isn't something we would be encouraging people to use as it's sometimes quite unstable and prone to breakage. I would still like to probe further into this one as I can see benefit however I'm not sure when, if ever, this would be implemented so I would rather not leave this ticket lingering. Are you ok for me to close this one off? Or do you have further questions? NB: The references to http://snaps.php.net have been removed from across the PHP site to eliminate any further confusion. ------------------------------------------------------------------------ [2015-02-14 22:12:23] hiro+php at travis-ci dot org Hi, Jacob, We compile all other versions with php-build at image provisioning time, so we are all set for those. The bandwidth requirement is a bit hard to estimate; it depends on how popular "php 7 nightly" is going to be. Currently, on .org (for public repositories) we run about 10000 PHP builds over the course of a calendar month. Of these, I believe about 25% include builds with 5.6, which seems a good upper bound for what we can expect to have for the "php 7 nightly". We run slightly fewer PHP builds on .com, but I suspect that demands for the bleeding edge versions are a lot less (almost negligible, even) there. The archive is about 18MB, That adds up to about 450 GB of bandwidth in a month. Let's say 500 GB to overestimate the cost. Do note that about 1/3 of the builds mentioned above seem to be running on the new container builds on EC2, so if we put stuff on S3, we'll save some bandwidth. ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at https://bugs.php.net/bug.php?id=69042 -- Edit this bug report at https://bugs.php.net/bug.php?id=69042&edit=1