Re: Re: Request feedback on the Jenkins setup/RFC
| From: | Johannes Schlüter | Date: | Tue, 08 Nov 2011 00:29:27 +0000 |
| Subject: | Re: Re: Request feedback on the Jenkins setup/RFC | ||
| References: | 1 2 3 4 5 | Groups: | php.internals php.qa |
| Request: | Send a blank email to internals+get-56135@lists.php.net to get a copy of this message | ||
On Tue, 2011-11-08 at 01:18 +0100, Ferenc Kovacs wrote:
> > Might also be nice to build (PECL) extensions as sub-tasks, so if
> they
> > fail they don't cause the whole build to fail, but just a single red
> > light between many green (or blue) ones.
> >
> >
> Yeah, thats a good idea, even for some of the core exts, as there are
> some
> exts which can't be built/loaded at the same time.
If you do that for core extensions, is it possible to strucutre it in a
way that the overall PHP compile process turns red if a core extension
fails, but not if a PECL extension fails, in the later case the overall
build might fails. In an ASCII tree something like this:
+-build
+-PHP core
|+-ext/dom
|+-ext/simplexml
+-PECL
+-pecl/htpp
+-pecl/foobar
So if pecl/http fails PECL turns read, as does "build" ... not sure
whether that's possible as "PECL" will depend on "PHP core". I'm not
sure where userland tests belong in that hierarchy, I think next to
"PECL".
johannes