Re: Re: Continuous Integration Servers for php-src
| From: | Israel Ekpo | Date: | Fri, 16 Oct 2009 16:52:39 +0000 |
| Subject: | Re: Re: Continuous Integration Servers for php-src | ||
| References: | 1 2 3 4 5 6 | Groups: | php.qa |
| Request: | Send a blank email to php-qa+get-65401@lists.php.net to get a copy of this message | ||
On Fri, Oct 16, 2009 at 3:28 AM, Pierre Joye <pierre.php@gmail.com> wrote:
> hi Israel,
>
> On Fri, Oct 16, 2009 at 4:47 AM, Israel Ekpo <israelekpo@gmail.com> wrote:
>
> > Hi David and Eric,
> >
> > The current state of the continuous integration project is that I am
> still
> > developing the continuous integration system and it is not yet ready for
> > initial testing/use.
>
> Would it be possible to have some specs in the wiki first so we can
> agree on the procedure or needs?
>
> Then we can help you to implement what has to be implemented or to
> adapt exisiting software (like cdash for the reporting/web frontend
> parts) or share the work.
>
>
> Cheers,
> --
> Pierre
>
> http://blog.thepimp.net |
> http://www.libgd.org
>
Hi Pierre,
I did put up the initial specifications on the wiki about 2 weeks ago.
http://wiki.php.net/internals/buildbot#proposed_implementation
I will be modifying the design so that the slaves can be run in either
staggered or sequential mode.
In staggered mode, the slave will run only 3-4 times a day and it will only
check out the latest revision, if it has changed from the last time.
In sequential mode, the slave will process all revisions to the php-src URL.
The staggered mode will be used on slow machines and the sequential mode
will be used on the machines with mode horsepower.
CDash looks like a good option for the reporting phase but I don't have any
experience with it.
So please take a look at the proposed specs and let me know what you think.
We can share the work too after the design is finalized.
Right now I was working on the notification phase.
--
"Good Enough" is not good enough.
To give anything less than your best is to sacrifice the gift.
Quality First. Measure Twice. Cut Once.