On Fri, Jun 13, 2014 at 9:41 PM, Pierre Joye <[email protected]> wrote: > On Sat, Jun 14, 2014 at 6:38 AM, Pierre Joye <[email protected]> wrote: >> On Sat, Jun 14, 2014 at 6:31 AM, Hannes Magnusson >> <[email protected]> wrote: >>> On Fri, Jun 13, 2014 at 9:14 PM, Pierre Joye <[email protected]> wrote: >>>> On Sat, Jun 14, 2014 at 4:36 AM, Hannes Magnusson >>>> <[email protected]> wrote: >>>> >>>>>> Something like that yes. I need something I can test my changes on so >>>>>> I don't push completely broken code. >>>>>> A vm clone of the build host would fantastic as I could test the >>>>>> entire process completely. >>>> >>>> We can't provide images of a full host. However all dependencies, both >>>> sources and binaries, are available http://windows.php.net/downloads/, >>>> be in pecl's (non core dependencies) or php-sdk deps (everything used >>>> for the core). It is pretty straight forward to use. Mongodb has >>>> windows and msdn licenses, so you should have access to all the >>>> software as well. If you do not, please let me know so I can provide >>>> you what you need. >>> >>> >>> Good news that MongoDB has Windows and MSDN licenses.. Can you >>> elaborate how that is related to the pecl.php.net windows build >>> infrastructure? >> >> I was not sure what you referred to here. But now it is. You refer to >> the build infrastructure only.
Yes, this thread is about the Windows binaries for PECL extensions - and how I can implement snapshot capabilities into that infrastructure. >> Please let me summarize again what has been said previously: >> >> - semi automatic build using rmtools >> - rmtools is pretty easy to understand, it wraps what one has to do >> manually in php >> - most of its code is about generating human friendly reports (build >> log or analyzers) >> - mid term (within a couple of months), travis will be used. I >> repeat: Travis-ci will be used for this task. If you scroll up to the first couple of message of this thread you see Anatol saying although it is on his todo list he doesn't have the time for it. That was in reply to me saying I would like to implement this. > And I forgot to mention the on going work on Pickle, which aims to > replace the pecl installer, to install/compile PHP extensions, on all > supported platforms, from source or binaries. So far we did not get Thats excellent. As you know, I've been throwing around ideas for replacement tool too. Along with replacing just the installer, the "channel" stuff should probably go away to. I've also more recently wanting to provide a tool where you only get PHP when installing PHP. Then you can upgrade things independently - why should I need to upgrade mysqlnd and all mysql* extension when I just need that curl fix? Or fix for CVE...? :/ see: http://bjori.blogspot.com/2014/05/i-have-dream.html Toying around the idea of having binaries available for the most popular platforms - for php too - using something like https://build.opensuse.org/ has been kicked around too. What it boils down to is - an installer isn't actually difficult to create. It is dependency management that is complicated - and that has to be fixed in php-src really. In anycase - this is not what this thread is about.. All I am trying to do here is to be able to develop snapshot functionality into the PECL Windows binary infrastructure - preferably not blind in a cave - so getting access to deployment logs, php error logs etc etc etc, or access to the server, or someone describing what exactly the infrastructure is running so I can replicate it ... That is what I am asking for. I would appreciate help getting that up. Doing this blindly in a cave will inevitably result in breaking something, which I am trying very very hard to avoid happening. > any feedback from core or extension developers but Johannes on IRC. > This is the future, let focus on that. The sooner we have this tool > done, the easier it will be to have win snapshots builds in place for > anyone willing to do it. Indeed we will use it in travis as well and > provides the snaps on pecl.php.net as well. Wait.. Are you saying the tool is going to be capable of doing Windows builds? >>> I am attempting to make sure mine, or anyone elses for that matter, >>> commits to this 'rmtools' repository don't break stuff. >>> For that I need one or more of the following two things: >>> - Access to the logs/servers >> >> Build logs or something else? >> >> Build logs are sent to the extension developers on error and are part >> of the builds archives. You can fetch them on windows.php.net. Those are user logs. Not logs from the system upgrading itself from git, runetime logs, cronjob logs, php error log, and whatever else the chain of execution really is. >>> - Duplicate the server setup >> >> Should not be too hard. Do you have a windows VM with VC + SDK >> installed at hand? I imagine the build infrastructure is however sensitive to versions - so which Windows version do I need, VC, ..? -Hannes -- PECL development discussion Mailing List (http://pecl.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
