On Thu, Jun 12, 2014 at 4:52 PM, Hannes Magnusson <[email protected]> wrote: > On Thu, Jun 12, 2014 at 4:21 PM, Stephen Zarkos > <[email protected]> wrote: >> Hi Hannes, >> >> >>> -----Original Message----- >>> From: Hannes Magnusson [mailto:[email protected]] >>> >>> On Tue, Jun 10, 2014 at 3:59 PM, Hannes Magnusson >>> <[email protected]> wrote: >>> > On Tue, Jun 10, 2014 at 3:29 PM, Anatol Belski <[email protected]> >>> wrote: >>> >> On Wed, June 11, 2014 00:06, Hannes Magnusson wrote: >>> >>> On Tue, Jun 10, 2014 at 2:56 PM, Anatol Belski >>> >>> <[email protected]> >>> >>> wrote: >>> >>> >>> >>>> Hi, >>> >>>> >>> >>>> >>> >>>> On Mon, June 9, 2014 19:09, Hannes Magnusson wrote: >>> >>>> >>> >>>>> On Tue, Jun 3, 2014 at 2:53 PM, Hannes Magnusson >>> >>>>> <[email protected]> wrote: >>> >>>>> >>> >>>>> >>> >>>>>> On Tue, Jun 3, 2014 at 12:06 PM, Anatol Belski <[email protected]> wrote: >>> >>>>>> >>> >>>>>> >>> >>>>>>> Hi, >>> >>>>>>> >>> >>>>>>> >>> >>>>>>> >>> >>>>>>> On Tue, June 3, 2014 19:14, Hannes Magnusson wrote: >>> >>>>>>> >>> >>>>>>> >>> >>>>>>> >>> >>>>>>>> I noticed you pushed bunch of changes to the repo just which >>> >>>>>>>> seem to actually have been live for a while.. Does the build >>> >>>>>>>> host update from some other repo I would need to merge up to? >>> >>>>>>>> >>> >>>>>>> that's the github OSTC repo forked from rmtools somewhen, >>> havent >>> >>>>>>> synced for a while. As that system is a prerunner for what we >>> >>>>>>> gonna have with the travis integration, it doesn't really matter. >>> >>>>>>> As besides >>> >>>>>>> the snapshot builds running tests is also the topic, which is >>> >>>>>>> much finer done with travis. Probably also a good thing to >>> >>>>>>> deliberate before starting to do something. >>> >>>>>> >>> >>>>>> >>> >>>>>> I think we just did that and have a solid plan I can work on. >>> >>>>>> >>> >>>>>> >>> >>>>>> >>> >>>>>> Since attempting to duplicate the machinery is clearly impossible >>> >>>>>> task without having access to the current setup I would need to >>> >>>>>> work blind folded with trial and error here and there - which is >>> >>>>>> why I asked can I somehow see any logs (and to confirm, it is >>> >>>>>> running the rmtools repo on git.php.net you pointed me too, right?). >>> >>>>>> Alternatively, if I can get >>> >>>>>> access to the infrastructure that would be best. >>> >>>>> >>> >>>>> >>> >>>>> Any updates? >>> >>>>> Feel like I am slacklining in a pitch dark cave above a lake full >>> >>>>> of piranha :) If this is maintained on a vm or something I can >>> >>>>> replicate it would be awesomest... >>> >>>>> >>> >>>> yes, that's a VM but a clone is out of a question as there are too >>> >>>> much things there we can't simply "revert" to anonymize it. Btw. i >>> >>>> really think travis-ci integration were interesting to keep in >>> >>>> mind, as that would probably turn the whole thing upside down. >>> >>>> >>> >>> >>> >>> >>> >>> Can I get access to the server then while I attempt to develop these >>> >>> patches? >>> >>> >>> >> actually that is out of my competention, but i guess it's the same as >>> >> with the vm clone. I'm going OOF for the next three weeks, and >>> >> probably offline for some time due to the Internet provider update, >>> >> so will probably be able to continue to talk about this topic after that >>> >> first. >>> >> >>> > >>> > >>> > Who else has access to it I would be able to talk to? >>> > >>> > It doesn't look like there is much of anything I can actually work on >>> > since the infrastructure itself is uncloneable and inaccessible? >>> > >>> >>> >>> ping? >> >> I'm coming in a bit late here. Do you just need a clone of a build host to >> see how things are set up? > > > 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.
ping? -Hannes -- PECL development discussion Mailing List (http://pecl.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
