You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by Stefan Seelmann <se...@apache.org> on 2010/09/17 15:57:14 UTC

Continuous Integration Builds

Hi guys,

I setup some CI Jobs on Hudson [1] and created a Wiki page [2]. In
short the following builds from trunks are performed once a day:
- All projects (daemon, shared, apacheds, studio, etc.) are built on
Linux and on Windows
- Maven artifacts are deployed to to snapshot repository
- Studio snapshot binaries are packaged and can be downloaded
(ApacheDS will follow)
- Studio and ApacheDS manuals are built, PDFs can be downloaded, HTML
can be browsed
- Maven sites and Javadocs are generated (once a week only) and can be
browsed (soon, still in setup)

I’d like to observe how stable the builds are during the next days.
Then, if there are no objections, I’d like to post the links also to
the user mailing list and put a link to the nightly builds to the
website.

One open point is about the notifications of successful or failed
builds. Should we send a mail about failed builds to the dev mailing
list? An alternative is to subscribe to the RSS feed of the Directory
view. Thoughts?

Another open point is what we should do with the Continuum CI builds
[3]. I'd suggest we keep it as "real" CI build, those builds are
triggered by changes in SVN and provide quick feedback.

Kind Regards,
Stefan

[1] https://hudson.apache.org/hudson/view/Directory/
[2] https://cwiki.apache.org/confluence/display/DIRxDEV/Continuous+Integration+Builds
[3] http://vmbuild.apache.org/continuum/projectGroupSummary.action?projectGroupId=6

Re: Continuous Integration Builds

Posted by Emmanuel Lecharny <el...@gmail.com>.
  On 9/17/10 3:57 PM, Stefan Seelmann wrote:
> Hi guys,
>
> I setup some CI Jobs on Hudson [1] and created a Wiki page [2]. In
> short the following builds from trunks are performed once a day:
> - All projects (daemon, shared, apacheds, studio, etc.) are built on
> Linux and on Windows
> - Maven artifacts are deployed to to snapshot repository
> - Studio snapshot binaries are packaged and can be downloaded
> (ApacheDS will follow)
> - Studio and ApacheDS manuals are built, PDFs can be downloaded, HTML
> can be browsed
> - Maven sites and Javadocs are generated (once a week only) and can be
> browsed (soon, still in setup)

Great !!!
> I’d like to observe how stable the builds are during the next days.
> Then, if there are no objections, I’d like to post the links also to
> the user mailing list and put a link to the nightly builds to the
> website.
Sure, that would be a great addition.
> One open point is about the notifications of successful or failed
> builds. Should we send a mail about failed builds to the dev mailing
> list? An alternative is to subscribe to the RSS feed of the Directory
> view. Thoughts?
A mail would be ok. I don't use RSS feed (call me old fashion ...).
> Another open point is what we should do with the Continuum CI builds
> [3]. I'd suggest we keep it as "real" CI build, those builds are
> triggered by changes in SVN and provide quick feedback.
Yes, that's fine.

Thanks a lot Stefan !

-- 
Regards,
Cordialement,
Emmanuel Lécharny
www.iktek.com

Re: Continuous Integration Builds

Posted by Felix Knecht <fe...@apache.org>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Greate job!

That's what was missing - SNAPSHOT distributions of all (distributions
and documentation).

Big thanks Stefan

Regards
Felix

On 09/17/10 15:57, Stefan Seelmann wrote:
> Hi guys,
> 
> I setup some CI Jobs on Hudson [1] and created a Wiki page [2]. In
> short the following builds from trunks are performed once a day:
> - All projects (daemon, shared, apacheds, studio, etc.) are built on
> Linux and on Windows
> - Maven artifacts are deployed to to snapshot repository
> - Studio snapshot binaries are packaged and can be downloaded
> (ApacheDS will follow)
> - Studio and ApacheDS manuals are built, PDFs can be downloaded, HTML
> can be browsed
> - Maven sites and Javadocs are generated (once a week only) and can be
> browsed (soon, still in setup)
> 
> I’d like to observe how stable the builds are during the next days.
> Then, if there are no objections, I’d like to post the links also to
> the user mailing list and put a link to the nightly builds to the
> website.
> 
> One open point is about the notifications of successful or failed
> builds. Should we send a mail about failed builds to the dev mailing
> list? An alternative is to subscribe to the RSS feed of the Directory
> view. Thoughts?
> 
> Another open point is what we should do with the Continuum CI builds
> [3]. I'd suggest we keep it as "real" CI build, those builds are
> triggered by changes in SVN and provide quick feedback.
> 
> Kind Regards,
> Stefan
> 
> [1] https://hudson.apache.org/hudson/view/Directory/
> [2] https://cwiki.apache.org/confluence/display/DIRxDEV/Continuous+Integration+Builds
> [3] http://vmbuild.apache.org/continuum/projectGroupSummary.action?projectGroupId=6
> 

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.16 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkyWV34ACgkQ2lZVCB08qHGlTQCeI2BRhPosS2/UcDjAd/4mxr3r
ydcAnRCiK40Fzs/6QRsnnRiMARFEneKV
=s3fw
-----END PGP SIGNATURE-----

Re: Continuous Integration Builds

Posted by Stefan Seelmann <se...@apache.org>.
On Fri, Sep 24, 2010 at 9:55 AM, Felix Knecht <fe...@apache.org> wrote:
> Javadocs for shared [1] are missing, for studio [2] and apacheds [3]
> they are available. Is this a configuration problem or is it just not
> built yet (once a week)?
> The javadoc report for shared is also not available in the reports
> section of the "Maven Site" [4].

Javadoc is there now. I also configured the shared-site build to run daily.

> [1]
> https://hudson.apache.org/hudson/view/Directory/job/dir-shared-site/javadoc/
> [4]
> https://hudson.apache.org/hudson/view/Directory/job/dir-shared-site/site/

Re: Continuous Integration Builds

Posted by Stefan Seelmann <se...@apache.org>.
> Javadocs for shared [1] are missing, for studio [2] and apacheds [3]
> they are available. Is this a configuration problem or is it just not
> built yet (once a week)?
> The javadoc report for shared is also not available in the reports
> section of the "Maven Site" [4].

Seems my latest modifications caused that, I'll have a look at. Thanks
for reporting this.

Kind Regards,
Stefan

Re: Continuous Integration Builds

Posted by Felix Knecht <fe...@apache.org>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Stefan

> - Maven sites and Javadocs are generated (once a week only) and can be
> browsed (soon, still in setup)

Javadocs for shared [1] are missing, for studio [2] and apacheds [3]
they are available. Is this a configuration problem or is it just not
built yet (once a week)?
The javadoc report for shared is also not available in the reports
section of the "Maven Site" [4].

Regards
Felix

[1]
https://hudson.apache.org/hudson/view/Directory/job/dir-shared-site/javadoc/
[2]
https://hudson.apache.org/hudson/view/Directory/job/dir-studio-site/javadoc/
[3]
https://hudson.apache.org/hudson/view/Directory/job/dir-apacheds-site/javadoc/
[4]
https://hudson.apache.org/hudson/view/Directory/job/dir-shared-site/site/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.16 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkycWWsACgkQ2lZVCB08qHFjKACgsKC+FJtFQxjE11WLqPrfFMEN
j0AAnj4PxEiIhBpgu5K/m9f+jKyvkJMc
=DB7G
-----END PGP SIGNATURE-----

Re: Continuous Integration Builds

Posted by Kiran Ayyagari <ka...@apache.org>.
On Fri, Sep 17, 2010 at 7:27 PM, Stefan Seelmann <se...@apache.org> wrote:
> Hi guys,
>
> I setup some CI Jobs on Hudson [1] and created a Wiki page [2]. In
> short the following builds from trunks are performed once a day:
> - All projects (daemon, shared, apacheds, studio, etc.) are built on
> Linux and on Windows
> - Maven artifacts are deployed to to snapshot repository
> - Studio snapshot binaries are packaged and can be downloaded
> (ApacheDS will follow)
> - Studio and ApacheDS manuals are built, PDFs can be downloaded, HTML
> can be browsed
> - Maven sites and Javadocs are generated (once a week only) and can be
> browsed (soon, still in setup)
>
> I’d like to observe how stable the builds are during the next days.
> Then, if there are no objections, I’d like to post the links also to
> the user mailing list and put a link to the nightly builds to the
> website.
>
> One open point is about the notifications of successful or failed
> builds. Should we send a mail about failed builds to the dev mailing
> list? An alternative is to subscribe to the RSS feed of the Directory
> view. Thoughts?
IMO sending mail to dev ML will get our attention quickly. We can ignore
successful build notifications they are just noise.
>
> Another open point is what we should do with the Continuum CI builds
> [3]. I'd suggest we keep it as "real" CI build, those builds are
> triggered by changes in SVN and provide quick feedback.
let us keep this, it is the first watch dog
>
> Kind Regards,
> Stefan
>
> [1] https://hudson.apache.org/hudson/view/Directory/
> [2] https://cwiki.apache.org/confluence/display/DIRxDEV/Continuous+Integration+Builds
> [3] http://vmbuild.apache.org/continuum/projectGroupSummary.action?projectGroupId=6
>



thanks Seelmann, this is a huge effort

Kiran Ayyagari

Re: Continuous Integration Builds

Posted by Stefan Seelmann <se...@apache.org>.
On Fri, Sep 17, 2010 at 11:58 PM, Pierre-Arnaud Marcelot
<pa...@gmail.com> wrote:
>> One open point is about the notifications of successful or failed
>> builds. Should we send a mail about failed builds to the dev mailing
>> list? An alternative is to subscribe to the RSS feed of the Directory
>> view. Thoughts?
>
> I'd vote for commits@... ML. Maybe we could also reuse the
> notifications@... ML.
>
>> Another open point is what we should do with the Continuum CI builds
>> [3]. I'd suggest we keep it as "real" CI build, those builds are
>> triggered by changes in SVN and provide quick feedback.
>
> Makes sense.
> In that case I really think notifications@... is the best option for
> the Hudson notification mails.

Done, Hudson notifications to go notifications@

Kind Regards,
Stefan

Re: Continuous Integration Builds

Posted by Pierre-Arnaud Marcelot <pa...@gmail.com>.
Hi Stefan,

More inline...

On 17 sept. 2010, at 15:57, Stefan Seelmann <se...@apache.org> wrote:

> Hi guys,
>
> I setup some CI Jobs on Hudson [1] and created a Wiki page [2]. In
> short the following builds from trunks are performed once a day:
> - All projects (daemon, shared, apacheds, studio, etc.) are built on
> Linux and on Windows
> - Maven artifacts are deployed to to snapshot repository
> - Studio snapshot binaries are packaged and can be downloaded
> (ApacheDS will follow)
> - Studio and ApacheDS manuals are built, PDFs can be downloaded, HTML
> can be browsed
> - Maven sites and Javadocs are generated (once a week only) and can be
> browsed (soon, still in setup)

Wow. That's the best CI setup we've ever had.
Very well done.
Kudos, Stefan !!!

> I’d like to observe how stable the builds are during the next days.
> Then, if there are no objections, I’d like to post the links also to
> the user mailing list and put a link to the nightly builds to the
> website.

+1.

> One open point is about the notifications of successful or failed
> builds. Should we send a mail about failed builds to the dev mailing
> list? An alternative is to subscribe to the RSS feed of the Directory
> view. Thoughts?

I'd vote for commits@... ML. Maybe we could also reuse the
notifications@... ML.

> Another open point is what we should do with the Continuum CI builds
> [3]. I'd suggest we keep it as "real" CI build, those builds are
> triggered by changes in SVN and provide quick feedback.

Makes sense.
In that case I really think notifications@... is the best option for
the Hudson notification mails.
It's separate from the commits list and only interested people get them.

Thanks for setting all this.

Regards,
Pierre-Arnaud

>
> Kind Regards,
> Stefan
>
> [1] https://hudson.apache.org/hudson/view/Directory/
> [2] https://cwiki.apache.org/confluence/display/DIRxDEV/Continuous+Integration+Builds
> [3] http://vmbuild.apache.org/continuum/projectGroupSummary.action?projectGroupId=6