[kepler-dev] Continuous Integration System
cxh at eecs.berkeley.edu
Wed Jun 7 10:24:35 PDT 2006
Look like the continuous integration system is hung?
Shows last successful build: 05/31/06
Shows "now building since 06/01"
I added links to a version of Matthew's instructions and to
Hi Ilkay -
Yes - I forgot to mention the RSS feed - thanks!
> I'm still not receiving the nightly-build emails
> even if I'm in that email list.
last night was the first time a nightly build email was sent out - you
should have received it if you are subscribed to the
"kepler-nightly at ecoinformatics.org" mailing list. Dan received it, so
I'm not sure why you didn't. Did it maybe get marked as spam, since it
Of course, if you want to receive one of the continuous integration
emails, you could always go ahead and break the build... ;-)
Matthew Brooke, Ph.D.
Marine Sciences Research Building, Room #3407
University of California
Santa Barbara, CA 93106-6150
ph: (805) 893-7108 fx: 805-893-8062
brooke at nceas.ucsb.edu
Ilkay Altintas wrote:
> This is great. Thanks Matthew!
> Looks like it send RSS feeds. There's an RSS icon on the right-hand corne
> This is probably a simple question, but how do I receive them?
> I'm still not receiving the nighly-build emails even if I'm in that
> email list.
> On May 25, 2006, at 2:29 PM, Matthew Brooke wrote:
>> Hi all -
>> As a parting gift, I have set up a continuous integration system on a
>> dedicated build server for your delectation and delight...
>> The system is based on CruiseControl -
>> http://cruisecontrol.sourceforge.net - and is set up to do 2 tasks:
>> 1) Continuous Integration:
>> Checks the ptolemy and kepler CVS repositories every 10 minutes for
>> check-ins. If changes are detected, it does a clean build of ptolemy and
>> kepler, and runs the JUnit tests and the workflow tests (ant targets:
>> "full-clean ptolemy buildkarlib jar test test_workflows").
>> (** Side note - I created a new ant target in build.xml -
>> "test_workflows" - which uses JUnit to automatically test all the
>> workflows that are listed in "kepler/lib/test-workflows.lst" - this
>> target might also be useful to actor/test-workflow creators)
>> If the build becomes broken, the system will attempt to send out
>> notification emails to kepler-dev and to the people who have checked in
>> changes since the last successful build. It will continue to send out
>> emails until the build is fixed. When the build has been fixed, those
>> same recipients will receive notification emails - after which there
>> should be no more emails until the build is broken again.
>> 2) Nightly Build
>> Builds at 11:59pm every day, and sends out an email to the
>> kepler-nightly mailing list (whether the nightly build was successful or
>> not). The nightly build is a little different, in that is adds the
>> "generateDoc" and "buildkeplerzip" ant targets (so it is possible that
>> the nightly could be broken while the continuous integration build is
>> not). If the nightly build is broken for any reason, notification is
>> also sent to kepler-dev.
>> Web Log and Emails:
>> The notification emails are sent out in HTML format, and contain the
>> full output of the build. They also contain a link to the status
>> web-page on the build server:
>> Note that the "Build" buttons on this page will currently work only for
>> people at MSI (IP addresses like 128.11.242.x), but everyone should be
>> able to click on the "kepler-nightly-build" and
>> "kepler-continuous-integration" links and see the latest build log and
>> links to all the other archived logs
>> Matthew Brooke, Ph.D.
>> Marine Sciences Research Building, Room #3407
>> University of California
>> Santa Barbara, CA 93106-6150
>> ph: (805) 893-7108 fx: 805-893-8062
>> brooke at nceas.ucsb.edu
>> Kepler-dev mailing list
>> Kepler-dev at ecoinformatics.org
> Ilkay ALTINTAS
> Assistant Director, National Laboratory for Advanced Data Research (NLADR
> Manager, Scientific Workflow Automation Technologies (SWAT) Lab
> San Diego Supercomputer Center(SDSC), UCSD
> 9500 Gilman Drive, MC: 0505 La Jolla, CA 92093-0505
> phone: (858) 822-5453 fax: (858) 822-3693
> web: http://users.sdsc.edu/~altintas
Kepler-dev mailing list
Kepler-dev at ecoinformatics.org
More information about the Kepler-dev