Mailing-List: contact dev-help@directory.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Directory Developers List" <dev@directory.apache.org>
Received-SPF: pass (athena.apache.org: domain of jesse.mcconnell@gmail.com
 designates 72.14.204.229 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references;
        b=M6XVhh1+FxNdtZbgJmItcugbS/FUGkA+LsoCh87BwbHi3sxr0UXCLptgEJALKTTd12o6UOn1NYHBr/1j0FIXkbGPg187YvrctU18y99n1c5N+CrirM21jScJKDYfH/xK93Rt8fD1yCsG0lGgpv1gnQAr1Kqq3YAFjfhlpXvX69g=
Message-ID: <a43524d00803180927k21fee06at13bdc8422a4633c6@mail.gmail.com>
Date: Tue, 18 Mar 2008 11:27:46 -0500
From: "Jesse McConnell" <jesse.mcconnell@gmail.com>
To: "Apache Directory Developers List" <dev@directory.apache.org>
Subject: Re: Some questions about CI
In-Reply-To: <a32f6b020803180925t3eed44d3g15da7041dd680d2e@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_1932_26190859.1205857666421"
References: <47DF9608.8060900@otego.com>
	 <d45b08f00803180534g2802089ai55af47b33fc095db@mail.gmail.com>
	 <a32f6b020803180925t3eed44d3g15da7041dd680d2e@mail.gmail.com>

------=_Part_1932_26190859.1205857666421
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

I think maven uses 'notifications@' fwiw, its a bit broader in scope that
way

cheers!
jesse

On Tue, Mar 18, 2008 at 11:25 AM, Alex Karasulu <akarasulu@apache.org>
wrote:

> Hi,
>
> On Tue, Mar 18, 2008 at 8:34 AM, Emmanuel Lecharny <elecharny@gmail.com>
> wrote:
>
> > Hi Felix,
> >
> > >  - - How often shall a build be done (compile/test, sitegeneration)
> >
> > We have many possible options. We tried something like kicking CI
> > after each commit, but it leads to issues (usually, we don't commit
> > code in one big shot,
>
>
> Yes this does happen but it's bad practice on our part.  I prefer a build
> on each commit so it's easier to catch the offending commit and isolate it
> to a user who can be informed immediately while they still have a mental
> stack in memory.
>
> I personally would like to know immediately when I goofed something while
> that something is still in my head.
>
>
> > so it launch the integration test more than
> > once...). I would favor a daily build (every night, something like 6am
> > UTC to be sure that nobody in europe or USA are impacted.
> >
> >  and
> > >  which params shall be used for which project?
> > -Dintegration test seams to be mandatory. We may need some more, like
> > install.
> >
> > It could be also a good think to generate nighty builds, implying
> > generating some packages. To be checked.
>
>
> I think we should do both nightly and on commit builds.  The nightly
> builds can package up the product and provide it for human testers.  The
> products can then be pushed to machines which can run other tests on it.
> Like installing the products, perf tests, conformance (vsldap) tests, and
> other kinds of integration tests.  Then we can compile daily reports.
>
>
> > >
> > >  - - Where shall nag mails from continuum goto?
> >
> > a limited list of persons. Like the interested committers. I would
> > suggest the following list :
> > - alex
> > - stefan S
> > - stefan Z
> > - pierre-arnaud
> > - me
> > - david
> >
>
> I'd push the results to an CI specific mailing list.  This way anyone can
> register to get these notifications or unregister when they like.  It would
> be easy to ask for a new ci@d.a.o mailing list from infra just for this.
>
> Alex
>
>


-- 
jesse mcconnell
jesse.mcconnell@gmail.com

------=_Part_1932_26190859.1205857666421
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

I think maven uses &#39;notifications@&#39; fwiw, its a bit broader in scope that way<br><br>cheers!<br>jesse<br><br><div class="gmail_quote">On Tue, Mar 18, 2008 at 11:25 AM, Alex Karasulu &lt;<a href="mailto:akarasulu@apache.org">akarasulu@apache.org</a>&gt; wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hi,<div class="Ih2E3d"><br><br>On Tue, Mar 18, 2008 at 8:34 AM, Emmanuel Lecharny &lt;<a href="mailto:elecharny@gmail.com" target="_blank">elecharny@gmail.com</a>&gt; wrote:<br>
</div><div class="gmail_quote"><div class="Ih2E3d"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi Felix,<br>
<div><br>
&gt; &nbsp;- - How often shall a build be done (compile/test, sitegeneration)<br>
<br>
</div>We have many possible options. We tried something like kicking CI<br>
after each commit, but it leads to issues (usually, we don&#39;t commit<br>
code in one big shot, </blockquote></div><div><br>Yes this does happen but it&#39;s bad practice on our part.&nbsp; I prefer a build on each commit so it&#39;s easier to catch the offending commit and isolate it to a user who can be informed immediately while they still have a mental stack in memory.&nbsp; <br>

<br>I personally would like to know immediately when I goofed something while that something is still in my head.<br>&nbsp;</div><div class="Ih2E3d"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">

so it launch the integration test more than<br>
once...). I would favor a daily build (every night, something like 6am<br>
UTC to be sure that nobody in europe or USA are impacted.<br>
<div><br>
&nbsp;and<br>
&gt; &nbsp;which params shall be used for which project?<br>
</div>-Dintegration test seams to be mandatory. We may need some more, like install.<br>
<br>
It could be also a good think to generate nighty builds, implying<br>
generating some packages. To be checked.</blockquote></div><div><br>I think we should do both nightly and on commit builds.&nbsp; The nightly builds can package up the product and provide it for human testers.&nbsp; The products can then be pushed to machines which can run other tests on it.&nbsp; Like installing the products, perf tests, conformance (vsldap) tests, and other kinds of integration tests.&nbsp;  Then we can compile daily reports.&nbsp; <br>

<br></div><div class="Ih2E3d"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
<div>&gt;<br>
&gt; &nbsp;- - Where shall nag mails from continuum goto?<br>
<br>
</div>a limited list of persons. Like the interested committers. I would<br>
suggest the following list :<br>
- alex<br>
- stefan S<br>
- stefan Z<br>
- pierre-arnaud<br>
- me<br>
- david<br>
</blockquote></div><div><br>I&#39;d push the results to an CI specific mailing list.&nbsp; This way anyone can register to get these notifications or unregister when they like.&nbsp; It would be easy to ask for a new <a href="mailto:ci@d.a.o" target="_blank">ci@d.a.o</a> mailing list from infra just for this.<br>

<br>Alex<br>&nbsp;  <br></div></div>
</blockquote></div><br><br clear="all"><br>-- <br>jesse mcconnell<br><a href="mailto:jesse.mcconnell@gmail.com">jesse.mcconnell@gmail.com</a>

------=_Part_1932_26190859.1205857666421--