Hi Jeffrey, I am happy that you like the feature (which I think was already there in 2.3.1)!

Another nice usage is the ability to rename the plugin. Useful if you have different project types, e.g. if you are in the middle of a migration, or if you have 2 different project groups but consolidate the CI on one server.

E.g.

<plugin name="antproject">
... project with ant builder(s) ...
</plugin>
<plugin name="mavenproject">
... project with maven builder(s) ...
</plugin>

<antproject name="ant1" />
<antproject name="ant2" />
<mavenproject name="maven1" />
<mavenproject name="maven2" />
...

You could do the same for cvs/svn, etc...

The URL to the official documentation:
http://cruisecontrol.sourceforge.net/main/plugins.html#preconfiguration

(PS: not sure if this comment will show up correctly, the preview doesn't...)

Hi Jerome!

(for those who don't know Jerome is the person who wrote the patch to allow preconfiguration of project elements.)

looking at the release notes 2.3.1 had preconfigure log elements and preconfiguration of log elements was added in 2.4.

I agree, I really like the ability to create meaningful names using the preconfiguration. Can make the config file much more readable.

Oh yeah, and to make your comment display correctly I had to replace your angle brackets (< & >) with entities. (the pre tag isn't the same as the old verbose tag.)

You're right for the 2.4, it was checked in 2-3 weeks after 2.3.1 was released.

With regard to preview, I had tried several formats, including with entities, but the preview still destroyed formatting. Anyway, each blog system has its own set of oddities...

Hello,

I am working on an open-source-project based on an eclipse-rcp.

I have already read the tutorial (http://www.eclipse.org/articles/Article-PDE-Automation/automation.html), but I still got some problems.

I could manage to install CruiseControl on our server and integrating in our web container...
...but, my main target is to have automated plug-in builds including building and packaging rcp-applications outside eclipse by using CruiseControl.

However I am far away from the main target:…isn’t there a tutorial/guide which covers this topic referring to eclipse 3.1?

What is necessary to let the build fail if a JUnit Plugin Test is not successful?

Definition of JUnitPluginTests: These are test cases contained in a plugin that test another plugin. Plugin tests have to be run inside an Eclipse workbench (if they need UI) or an Eclipse workspace (when the require no UI functionality).
(see http://www.testdriven.com/modules/mylinks/singlelink.php?cid=4&lid=186)

Bye, Amro.

I don't know of another guide other than the one you mention, though it I didn't follow it much when I put one of our plug-in builds under CC. Across our various modules we either have or have had eclipse plug-ins being built with all manner of approaches: using the eclipse generated build files, using templated versions of their build files, using handcrafted build files, building using eclipse and building w/out using eclipse... on way or another we've managed to make all these work.

But they key in all cases is to get the build working as you like it outside of eclipse before trying to automated it.

Wrt failing when a JUnit Plugin test fails I'm not really sure what that takes. Perhaps it requires post processing of the result files?

If you haven't done so you might try asking your questions on the CC-User mailing list to see how other people have approached these problems:

http://cruisecontrol.sourceforge.net/contact.html

Hi Jeffrey,

I didn't realise it was possible to use plugin pre-configuration to create project templates in the way you show here. This is very cool! :)

Patrick

Yes, this is a really nice feature!

And perhaps this is an obvious comment... But to create similiar plugins like "BldProject" and "TestProject" that are templates for "project", one must use the classname attribute and must know that it's value should be net.sourceforge.cruisecontrol.ProjectConfig.

(could sombody please replace my \n with the linefeed tag or use kinda "pre"?)
I needed a second parameter for my project templates besides the name, so I used a template like this:\n

<plugin name="MyProject"
    classname="net.sourceforge.cruisecontrol.ProjectConfig">
    ....
    <schedule>
        <ant ... target="${parameter.1}_xyz"/>
    </schedule>
    <publishers>
        <artifactspublisher>
        <email>
            <always address="${parameter.2}"/>
        </email>
        </artifactspublisher>
    </publishers>
</plugin>

<MyProject name="p1">
    <property name="parameter.1" value="p1.bla"/>
    <property name="parameter.2" value="me@here.com"/>
</MyProject>

<MyProject name="p2">
    <property name="parameter.1" value="different"/>
    <property name="parameter.2" value="you@there.com"/>
</MyProject>

worlfram, I've fixed up your comment using non-breaking space entities. (the software already converts return to line breaks in comments apparently.)

Thanks for correcting my post. I was fooled by the preview function which removed all line breaks and any markup.

hi..

I want to know about cruise control.what is that use?.please send me complete introduction about that.

Terms of Use