Hi all

CCNet 1.5.0 RC1 has been released!  It has taken us longer than we hoped
for, but here it is.
The RC1 fixes many bugs reported on the CTP, but also has some extra
goodies.
This build is already used by many people in production environments, but a
backup is never a bad idea [?]

You can have a look at the new dashboard  at :
http://build.nauck-it.de/ViewFarmReport.aspx

The release notes can be found at :
<http://confluence.public.thoughtworks.org/display/CCNET/CCNet+1.5+CTP+Release+Notes>
http://confluence.public.thoughtworks.org/display/CCNET/CCNet+1.5+RC1+Release+Notes

And you can download it from sourceforge at :
https://sourceforge.net/projects/ccnet/


Let us know what you think of this release, and please report any issues
This will only make CCNet even better [?]



For those not knowing what is new since 1.4.4 : (the major points only)
Security

It is now possible to secure parts of CruiseControl.NET. Security is all
based on the server-side, and is set in ccnet.config.

Currently it is possible to lock down the following items:

   - Viewing projects
   - Forcing/aborting builds
   - Starting/stopping projects
   - Viewing security settings
   - Modifying security settings
   - Viewing configuration
   - Changing configuration

A few new source control systems

RoboCopy, VSTS,
Ftp<http://confluence.public.thoughtworks.org/display/CCNET/FTP+Source+control>,
Git<http://confluence.public.thoughtworks.org/display/CCNET/Git+Source+Control+Block>and
Mercurial<http://confluence.public.thoughtworks.org/display/CCNET/Mercurial+Source+Control+Block>.
The last 2 are DVCS, so an entire new kind of source control!
New Tasks/Publishers

A number of new tasks have been added:

   - Parallel 
Task<http://confluence.public.thoughtworks.org/display/CCNET/Parallel+Task>and
Sequential
   
Task<http://confluence.public.thoughtworks.org/display/CCNET/Sequential+Task>-
allow running tasks in parallel or in sequence, or any combination of
the
   two. While this can speed things up, be careful of using too much
   parallelism as each parallel task uses its own thread and there is only a
   limited thread pool.
   - NCover tasks - perform NCover analysis and reporting within
CC.NETitself (no need to run it in a build script).
   - PowerShell
Task<http://confluence.public.thoughtworks.org/display/CCNET/PowerShell+Task>-
run a PowerShell script.
   - Conditional
Publisher<http://confluence.public.thoughtworks.org/display/CCNET/Conditional+Publisher>-
this provides a standard way of only running publishers for certain
build
   states.
   - CruiseServer Control
Task<http://confluence.public.thoughtworks.org/display/CCNET/CruiseServer+Control+Task>-
send control commands to a local or remote instance of
CruiseControl.NET.
   - Ftp task -
Publisher<http://confluence.public.thoughtworks.org/display/CCNET/Ftp+task+-+Publisher>-
   upload / download files from a server

Dynamic Parameters

This allows to ask the user for input on forcing a build, so reducing the
amount of CCNet projects.
eg.: ask which branch to build
Time Line chart

This shows the a build overview as a chart.
Translation of the webDashboard

Current translation involve French and German.


with kind regards
Ruben Willems

on behalve of the CCNet team

<<343.gif>>

<<347.gif>>

Reply via email to