Req #69042 [Asn]: Regular snapshot builds of php/php-src
| From: | hiro+php at travis-ci dot org | Date: | Sat, 14 Feb 2015 22:12:24 +0000 |
| Subject: | Req #69042 [Asn]: Regular snapshot builds of php/php-src | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-190688@lists.php.net to get a copy of this message | ||
Edit report at https://bugs.php.net/bug.php?id=69042&edit=1
ID: 69042
User updated by: hiro+php at travis-ci dot org
Reported by: hiro+php at travis-ci dot org
Summary: Regular snapshot builds of php/php-src
Status: Assigned
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:
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.
Previous Comments:
------------------------------------------------------------------------
[2015-02-14 05:58:45] jacob@php.net
> Thanks for looking into it. Our needs are limited; at the moment, we only need
> an archive for Ubuntu Precise (also on Trusty in the near future) on x86_64.
> (And I don't see this expanding much before PHP 7 is released.)
Could you use the 5.4[1] and 5.5[2] PPA's for Precise (and down the track
Trusty)? Or would you only be interested in the source? If you use apt-get, you
could look at using an apt cacher to only download it once but serve to multiple
builds and save bandwidth.
> Since php/php-src is building on Travis CI already, one thing we can try is to
> upload the resulting archive to a place where Travis (and perhaps some brave
> souls among your user base) can download subsequently.
Sure! Let me shoot out an email to the internals and see whether it's something
everyone can see some benefit in adding. In doing this, we may also get some
insight for your next point.
> Do you have a place suitable for such storage?
I am not sure on as most mirrors for PHP are sponsored so I would need to
investigate what is involved in getting this setup. Do you know what sort of
bandwidth this would consume?
[1]: https://launchpad.net/~ondrej/+archive/ubuntu/php5-oldstable
[2]: https://launchpad.net/~ondrej/+archive/ubuntu/php5
------------------------------------------------------------------------
[2015-02-14 03:40:10] hiro+php at travis-ci dot org
(I changed the PHP version inadvertently)
------------------------------------------------------------------------
[2015-02-14 03:36:51] hiro+php at travis-ci dot org
Hi, Jacob,
Thanks for looking into it. Our needs are limited; at the moment, we only need an archive for Ubuntu
Precise (also on Trusty in the near future) on x86_64. (And I don't see this expanding much
before PHP 7 is released.)
Since php/php-src is building on Travis CI already, one thing we can try is to upload the resulting
archive to a place where Travis (and perhaps some brave souls among your user base) can download
subsequently.
One can deploy via S3 (http://docs.travis-ci.com/user/deployment/s3/), Google Cloud Storage
(http://docs.travis-ci.com/user/deployment/gcs/), or a custom "after_success" section
(http://docs.travis-ci.com/user/deployment/custom/). One can also use artifacts
(http://docs.travis-ci.com/user/uploading-artifacts/) to upload to S3.
Do you have a place suitable for such storage? The upload setup is easy, and I'm willing to
work on a PR. The hard part is to find a place for it.
------------------------------------------------------------------------
[2015-02-14 03:16:46] jacob@php.net
> While it seems to work (as far as compilation goes; this doesn't include other
> modules or phpunit we offer in other PHP versions), but it adds significant
> amount of time (10+ minutes).
This is definitely less than ideal as this could quickly blow out to a long
build if you need to be doing this for multiple versions of PHP.
> It would be great if a precompiled binary package of reasonably recent
> development version existed.
There are precompiled versions out in the wild however they vary from
distribution to distribution and having a single source for this would be a huge
maintainance task.
After some discussions it would appear the reasoning behind removing
http://snaps.php.net was because there are better alternatives
available and it
isn't worth the maintenance involved in keeping it running.
I've also discovered that http://php.net/releases
contains historical releases
(don't think this solves any issues though - it's more of a heads up).
I'm not sure where to go from here with this as it doesn't look like
http://snaps.php.net will be coming back and we haven't got
any closer to a
solution.
What do you think?
------------------------------------------------------------------------
[2015-02-13 14:17:45] hiro+php at travis-ci dot org
Thanks for the suggestions so far.
I've fiddled with this information, and tried it on Travis CI: https://travis-ci.org/BanzaiMan/travis_production_test/jobs/50634414#L1191
While it seems to work (as far as compilation goes; this doesn't include other modules or
phpunit we offer in other PHP versions), but it adds significant amount of time (10+ minutes). It
would be great if a precompiled binary package of reasonably recent development version existed.
------------------------------------------------------------------------
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