Re: example of using advertised nant plugin from cruisecontrol

Most NAnt people probably use CC.NET, but CruiseControl does work with NAnt.
I don't know NAnt myself but perhaps we could help you debug your problem if
you tell us what's happening?

The example in the documentation should be a valid starting point.

Jtf


On Tue, Nov 16, 2010 at 8:02 AM, Adam Bruss <[email protected]> wrote:

>  Could someone please post a working example of using the nant plugin in
> cruisecontrol?
>
>
>
> According to the doc it’s doable.
>
> *<nant>***
>
> <cruisecontrol><http://localhost:8080/documentation/main/configxml.html#cruisecontrol>
>
>   <project><http://localhost:8080/documentation/main/configxml.html#project>
>
>     <schedule><http://localhost:8080/documentation/main/configxml.html#schedule>
>
>       <nant>
>
> Specifies a NAnt <http://nant.sourceforge.net/> build to be run at a given
> time or build number. For instance, we can run a clean build every 5 builds,
> or run more comprehensive (and time intensive) system tests every 10 builds.
> We can also schedule an official build to run every night at midnight, if we
> so desire.
>
> When a build runs, NAnt is invoked in a separate Java process. NAnt and the
> .NET Framework or Mono need to be installed for this builder to function.
> See NAnt's documentation for details on configuration and compatibility with
> .NET implementations.
>
> The standard CruiseControl properties passed to builders<http://localhost:8080/documentation/main/configxml.html#buildproperties>are available from within the NAnt build.
>
> See below for examples<http://localhost:8080/documentation/main/configxml.html#nant-examples>of the
> <nant> element.
>
> *Attributes*
>
> See also the common attributes<http://localhost:8080/documentation/main/configxml.html#builderattributes>for builders.
>
> *Attribute***
>
> *Required***
>
> *Description***
>
> buildfile
>
> No (defaults to default.build)
>
> Path to NAnt build file.
>
> target
>
> No
>
> NAnt target(s) to run. Default is "", or the default target for the build
> file.
>
> tempfile
>
> No
>
> Name of temp file. Defaults to log.xml
>
> targetFramework
>
> No, but recommended
>
> Specifies the framework to target. Typical values are "net-1.1" and
> "mono-1.0".
>
> nantWorkingDir
>
> No
>
> Will invoke NAnt in the specified directory.
>
> timeout
>
> No
>
> NAnt build will be halted if it continues longer than the specified
> timeout. Value in seconds.
>
> uselogger
>
> No
>
> 'true' if CruiseControl should call NAnt using -logger; 'false' to call
> NAnt without '-logger', thus using the loggerclass as a Listener.
> uselogger="true" will make NAnt log its messages using the class specified
> by loggerclassname as a NAnt Logger, which can make for smaller log files
> since it doesn't log DEBUG messages (see useDebug and useQuiet attributes
> below, and the NAnt documentation<http://nant.sourceforge.net/release/0.85-rc1/help/fundamentals/listeners.html>).
> Listener will echo NAnt messages to console which is useful when debugging
> your NAnt build. Defaults to 'false' for historical reasons, but setting it
> to 'true' is recommended for production situations.
>
> loggerclassname
>
> No (defaults to NAnt.Core.XmlLogger)
>
> If you want to use another logger than NAnt's XmlLogger, you can specify
> the classname of the logger here. The logger needs to output compatible XML,
> and the class needs to be available on the classpath at buildtime.
>
> usedebug
>
> No
>
> If true will invoke NAnt with -debug, which can be useful for debugging
> your NAnt build. Defaults to 'false', cannot be set to 'true' if usequiet is
> also set to 'true'. Is only effective when used in combination with
> uselogger="true"!
>
> usequiet
>
> No
>
> If true will invoke NAnt with -quiet, which can be useful for creating
> smaller log files since messages with a priority of INFO will not be logged.
> Defaults to 'false', cannot be set to 'true' if usedebug is also set to
> 'true'. Is only effective when used in combination with uselogger="true"!
>
> *Child Elements*
>
> *Element***
>
> *Cardinality***
>
> *Description***
>
> <property>
>
> 0 .. *
>
> Used to define properties for the NAnt build. The element has two required
> attributes: "name" and "value". These will be passed on the NAnt
> command-line as "-D:name=value"
> *Example:* <property name="foo" value="bar"/>
>
> *Examples***
>
>    1. Invoke NAnt, specifying the working directory as
>    D:\workspace\MyProject and the NAnt build file as
>    MyProject-nightly.build using the default target.
>
>  2.  <schedule>
>
> 3.      <nant nantworkingdir="D:\workspace\MyProject"
>
> 4.           buildfile="MyProject-nightly.build"
>
> 5.           uselogger="true"
>
> 6.           usedebug="false"/>
>
> <schedule>
>
>    1. Invoke NAnt, specifying the working directory as /home/cc/workspace,
>    the build file as default.build, the nant target as smoketest, and the
>    targetframework as .NET version 1.1.
>
>  8.  <schedule>
>
> 9.      <nant targetframework="net-1.1"
>
> 10.         nantworkingdir="/home/cc/workspace"
>
> 11.         target="smoketest"
>
> 12.         uselogger="true"/>
>
> <schedule>
>
>
>
>
>
> Thanks,
>
> Adam
>
>
>
> Adam Bruss
>
> Development Engineer
>
> AWR Corporation/Simulation Technology & Applied Research
>
> 11520 N. Port Washington Rd., Suite 201
>
> Mequon, WI  53092  USA
>
> P: 1.262.240.0291 x104
>
> F: 1.262.240.0294
>
> E: [email protected]
>
> W: http://www.awrcorp.com
>
>
>
>
> ------------------------------------------------------------------------------
> Beautiful is writing same markup. Internet Explorer 9 supports
> standards for HTML5, CSS3, SVG 1.1,  ECMAScript5, and DOM L2 & L3.
> Spend less time writing and  rewriting code and more time creating great
> experiences on the web. Be a part of the beta today
> http://p.sf.net/sfu/msIE9-sfdev2dev
> _______________________________________________
> Cruisecontrol-user mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/cruisecontrol-user
>
>


-- 
CITCON
Continuous Integration and Testing Conference
http://www.citconf.com/

------------------------------------------------------------------------------
Increase Visibility of Your 3D Game App & Earn a Chance To Win $500!
Tap into the largest installed PC base & get more eyes on your game by
optimizing for Intel(R) Graphics Technology. Get started today with the
Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs.
http://p.sf.net/sfu/intelisp-dev2dev

_______________________________________________
Cruisecontrol-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/cruisecontrol-user