Hi, The more complex example is creating one task that uses the same source code (java, C++, PERL etc.) and building it for several different platforms on different servers (WinNT, WIN64, Unix, HP or somewhat) simultaneously.
Regards Fyodor Koryazhkin. On Thu, Feb 19, 2009 at 10:11 AM, Fyodor Koryazhkin <[email protected]>wrote: > Hi, > The simpliest scenario may look like following: > 1. I created a project for compiling and building some VS solution that has > code written in C#. > 2. The default configuration passed to the msbuild process is "Release", > but sometimes I want to build a "Debug" configuration. > 3. Ability to pass this from outside will privent from me creating two > tasks in ccnet.config file (or in some other place) and will allow me to > create some system that will ask building user to choose what configuration > he wants to build at the time. > > Regards > > Fyodor Koryazhkin > > On Thu, Feb 19, 2009 at 9:59 AM, Ruben Willems > <[email protected]>wrote: > >> Hi >> >> for the moment these things are not possible without changing the source, >> but why do you want to pass properties to CCNet? >> >> >> can you give a more detailed example of what you are trying to do >> >> >> with kind regards >> Ruben Willems >> >> >> >> >> >> On Thu, Feb 19, 2009 at 8:55 AM, fyodorkor <[email protected]> wrote: >> >>> >>> Hi, >>> I have two questions relatively closed to each other: >>> 1. Can I determine a custom integration property through a command >>> line if launching ccnet.exe as process like msbuild does? For instance >>> I can pass project name to build but can I also pass a working >>> directory? >>> 2. Can I change/add custom integration property in custom task to be >>> able to use it later in other custom tasks? >>> >>> Thank you. >>> Fyodor Koryazhkin >> >> >> >
