Hi
1) building the dlls
this sounds like a typical CI process
set up a ccnet project with a source control section and a task, this
task does the compile
2) copy them to a deestination server
a ccnet project with an exec task that copies the files
or a build script that does this : nant, msbuild
the docs are here
http://confluence.public.thoughtworks.org/display/CCNET/Welcome+to+CruiseControl.NET
if something is not clear, let us know
with kind regards
Ruben Willems
On Thu, Oct 22, 2009 at 9:18 AM, Vikas Narasimha <
[email protected]> wrote:
> If yes, is there any documentation on this website which details this.
> Kindly advice
>
> RegardsVikas Narasimha
>
> On 22 Oct 2009, at 07:40, Ruben Willems <[email protected]> wrote:
>
> Hi
>
>
> 1) yes
>
> 2) if you mean copy them to target servers : yes
> if you mean copy and register : that depends
> --> copying no problem
> registring requires that the process is ran at the remote
> computer
> pstools(free) of sysinternals can be helpfull here
> 3) do not know
> 4) do not really understand the question, you want to control what a
> buildscript does via the dashboard?
>
>
>
> with kind regards
> Ruben Willems
>
>
> On Wed, Oct 21, 2009 at 5:44 PM, captedgar <<[email protected]>
> [email protected]> wrote:
>
>>
>> Sorry, I'm new to CruiseControl.
>> Does CruiseControl allow you to do both of the following?
>>
>> 1) Build .dlls and
>> 2) Deploy them onto target servers.
>> 3) If 1 and 2 are not applicable, is there any release tool with which
>> cruisecontrol can integrate easily
>> 4) We have a list of Window Script which are used for releases. So is
>> it possible to automate the build process through cruisecontrol and
>> then call the windows scripts on the dashboard to perform and complete
>> the release process?
>>
>> can this achieved through some config settings?
>>
>> regards
>>
>
>
