Excellent news guys... I have this installed in production and will report any 
problems.

Thanks so much for the teams efforts on this release... I really appreciate 
everyone's time and effort... you guys are great!

/Justin

  ----- Original Message ----- 
  From: Ruben Willems 
  To: [email protected] ; ccnet-devel 
  Sent: Saturday, January 30, 2010 3:11 PM
  Subject: [ccnet-user] CCNet 1.5 RC1 has been released !


  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+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:

    a.. Viewing projects
    b.. Forcing/aborting builds
    c.. Starting/stopping projects
    d.. Viewing security settings
    e.. Modifying security settings
    f.. Viewing configuration
    g.. Changing configuration 
  A few new source control systems
  RoboCopy, VSTS, Ftp, Git and Mercurial. The last 2 are DVCS, so an entire new 
kind of source control!

  New Tasks/Publishers
  A number of new tasks have been added:

    a.. Parallel Task and 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.
    b.. NCover tasks - perform NCover analysis and reporting within CC.NET 
itself (no need to run it in a build script).
    c.. PowerShell Task - run a PowerShell script. 
    d.. Conditional Publisher - this provides a standard way of only running 
publishers for certain build states. 
    e.. CruiseServer Control Task - send control commands to a local or remote 
instance of CruiseControl.NET. 
    f.. 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