ccnet-jira Mailing List for CruiseControl.NET

     [ http://jira.public.thoughtworks.org/browse/CCNET-326?page=comments#action_11170 ]
     
Owen Rogers commented on CCNET-326:
-----------------------------------

builders are now interchangeable with tasks.  the question is: do we want to go to the next step and get rid of the Builder element from Project?  this would be require a forced config migration for ccnet users.

> Allow arbitrary task list as workflow
> -------------------------------------
>
>          Key: CCNET-326
>          URL: http://jira.public.thoughtworks.org/browse/CCNET-326
>      Project: CruiseControl .NET
>         Type: New Feature
>     Reporter: Mike Roberts
>      Fix For: Medium Term

>
>
> Currently the workflow (after all the source control) is:
> - run (the 1 and only) builder 
> - run tasks
> - run publishers
> I want to change this so that the first 2 get merged, i.e. :
> - run tasks
> - run publishers
> This allows zero or multiple builders, arbitrarily interspersed with tasks.
> (later on we can consider publishers)
> ToDo:
> - Change Project to be able to handle this
> - figure out what to do with Result object (What?)
> - Anything else?

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.public.thoughtworks.org/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

     [ http://jira.public.thoughtworks.org/browse/CCNET-273?page=history ]
     
Owen Rogers closed CCNET-273:
-----------------------------

    Fix Version: Next
     Resolution: Fixed

this can now be accomplished using the MutliBuilder (http://confluence.public.thoughtworks.org/display/CCNET/Multi+Builder)
it is available in build 811

> Multiple build tags should run multiple build commands
> ------------------------------------------------------
>
>          Key: CCNET-273
>          URL: http://jira.public.thoughtworks.org/browse/CCNET-273
>      Project: CruiseControl .NET
>         Type: New Feature
>   Components: Builder
>     Versions: 0.7
>     Reporter: 
>      Fix For: Next

>
> Original Estimate: 2 hours
>         Remaining: 2 hours
>
> I have the following project setup, it loads fine, but it only builds the first solution.  I would expect it to build each of them in order.
>   <project name="Dataphor">
>     <webURL>http://yoda/CruiseControl/Controller.aspx?_action_ViewProjectReport=true&amp;server=local&amp;project=Dataphor</webURL>
>     <triggers>
>       <forceBuildInterval seconds="1800" />
>     </triggers>
>     <sourcecontrol type="vss" autoGetSource="true">
>        *snip*
>     </sourcecontrol>
>     <build type="devenv" solutionfile="c:\CruiseControl\Source\Dataphor\dataphor\Dataphor.sln" configuration="debug" />
>     <build type="devenv" solutionfile="c:\CruiseControl\Source\Dataphor\libraries\Libraries.sln" configuration="debug" />
>     <build type="devenv" solutionfile="c:\CruiseControl\Source\Dataphor\dataphor\Synergism.sln" configuration="debug" />
>     <publishers>
>        *snip*
>     </publishers>
>     <modificationDelaySeconds>1200</modificationDelaySeconds>
>   </project>

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.public.thoughtworks.org/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

     [ http://jira.public.thoughtworks.org/browse/CCNET-113?page=history ]
     
Owen Rogers resolved CCNET-113:
-------------------------------

    Fix Version:     (was: Medium Term)
                 Next
     Resolution: Fixed

implemented in build 811

> Create a MultiBuilder that will aggregate results from several builders
> -----------------------------------------------------------------------
>
>          Key: CCNET-113
>          URL: http://jira.public.thoughtworks.org/browse/CCNET-113
>      Project: CruiseControl .NET
>         Type: New Feature
>   Components: Builder
>     Versions: 0.6.1
>     Reporter: Owen Rogers
>     Priority: Minor
>      Fix For: Next

>
>


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.public.thoughtworks.org/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

Include ReplyTo property in EmailPublisher
------------------------------------------

         Key: CCNET-369
         URL: http://jira.public.thoughtworks.org/browse/CCNET-369
     Project: CruiseControl .NET
        Type: Improvement
  Components: Publisher  
    Versions: 0.8    
    Reporter: Owen Rogers
     Fix For: Soon


as per request: include support for replyto in the emailpublisher.
this url has information about how to do this: 
- http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cdosys/html/_cdosys_schema_configuration_senduserreplyemailaddress.asp
- http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfsystemwebmailmailmessageclassfieldstopic.asp

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.public.thoughtworks.org/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

     [ http://jira.public.thoughtworks.org/browse/CCNET-38?page=history ]
     
Owen Rogers closed CCNET-38:
----------------------------

    Fix Version:     (was: Medium Term)
                 Next
     Resolution: Fixed

this issue was fixed by moving the xsls to a common folder and linking them to each project.

> In HtmlDetailsMessageBuiler read css settings from file
> -------------------------------------------------------
>
>          Key: CCNET-38
>          URL: http://jira.public.thoughtworks.org/browse/CCNET-38
>      Project: CruiseControl .NET
>         Type: Improvement
>   Components: Publisher
>     Versions: 0.5, 0.4.2
>     Reporter: Owen Rogers
>     Assignee: V Sreekanth
>      Fix For: Next

>
>
> Css details are duplicated in the HtmlDetailsMessageBuilder class.  They should be loaded in from the cruisecontrol.css file instead.  The cruisecontrol.css file must be located somewhere that is accessible to the server (like in the xsl folder).

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.public.thoughtworks.org/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

     [ http://jira.public.thoughtworks.org/browse/CCNET-161?page=history ]
     
Owen Rogers resolved CCNET-161:
-------------------------------

    Fix Version: Next
     Resolution: Fixed

fixed in build 810

> WebURL in Project is duplicated with ProjectUrl in EmailPublisher
> -----------------------------------------------------------------
>
>          Key: CCNET-161
>          URL: http://jira.public.thoughtworks.org/browse/CCNET-161
>      Project: CruiseControl .NET
>         Type: Improvement
>   Components: Publisher
>     Versions: 0.7 RC-1
>     Reporter: Owen Rogers
>     Assignee: Owen Rogers
>      Fix For: Next

>
>
> eliminate the ProjectUrl from the EmailPublisher and use the WebURL from Project instead.  Note: this is potentially a breaking change if users have set these two urls to different values.
> does this cause problems for anyone?

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.public.thoughtworks.org/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

     [ http://jira.public.thoughtworks.org/browse/CCNET-80?page=history ]
     
Owen Rogers resolved CCNET-80:
------------------------------

    Fix Version:     (was: Medium Term)
     Resolution: Won't Fix

with all of the changes to the webdashboard, this is no longer an issue.

> Reports of False Fails
> ----------------------
>
>          Key: CCNET-80
>          URL: http://jira.public.thoughtworks.org/browse/CCNET-80
>      Project: CruiseControl .NET
>         Type: Bug
>   Components: Dashboard
>     Versions: 0.6
>  Environment: WinXP
>     Reporter: 
>     Assignee: Owen Rogers

>
>
> Changing the ccnet.config file to add projects will sometimes cause the Dashboard to report false build failures, setting all projects to fail. They remain that way until forced rebuild occurs, at which time completion is successful for the one project that was forced.
> When run in a debugger, the IList coming from the remoting object is reporting this way, so it is not the Dashboard application itself.
> dav...@ms...

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.public.thoughtworks.org/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

     [ http://jira.public.thoughtworks.org/browse/CCNET-159?page=history ]
     
Owen Rogers resolved CCNET-159:
-------------------------------

    Fix Version: Next
     Resolution: Fixed

fixed in build: 809

> exception when use url from email publisher
> -------------------------------------------
>
>          Key: CCNET-159
>          URL: http://jira.public.thoughtworks.org/browse/CCNET-159
>      Project: CruiseControl .NET
>         Type: Bug
>   Components: Publisher
>     Reporter: Martin Aliger
>     Assignee: Owen Rogers
>     Priority: Critical
>      Fix For: Next

>
> Original Estimate: 30 minutes
>         Remaining: 30 minutes
>
> The constructor to deserialize an object of type ThoughtWorks.CruiseControl.Remote.NoSuchProjectException was not found. 
> message is raised when I click on url at emails. NoSuchProjectException is raised becouse email publisher add ?log=xxx to specified url which is incorrect for new webapp-urls containing ? already.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.public.thoughtworks.org/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

     [ http://jira.public.thoughtworks.org/browse/CCNET-368?page=history ]
     
Owen Rogers resolved CCNET-368:
-------------------------------

    Resolution: Fixed

fixed in build 808

> Merge file output is wrapped in CDATA section if it starts with blank line
> --------------------------------------------------------------------------
>
>          Key: CCNET-368
>          URL: http://jira.public.thoughtworks.org/browse/CCNET-368
>      Project: CruiseControl .NET
>         Type: Bug
>   Components: Task
>     Versions: 0.8
>     Reporter: Owen Rogers
>      Fix For: Next

>
>
> If the merge file starts with a blank line followed by an xml declaration, ccnet will treat this as invalid xml (which it is) and will wrap it in a CDATA tag.  We need to update the code so that it will strip this blank line so that the xml will be valid. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.public.thoughtworks.org/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

Merge file output is wrapped in CDATA section if it starts with blank line
--------------------------------------------------------------------------

         Key: CCNET-368
         URL: http://jira.public.thoughtworks.org/browse/CCNET-368
     Project: CruiseControl .NET
        Type: Bug
  Components: Task  
    Versions: 0.8    
    Reporter: Owen Rogers
     Fix For: Next


If the merge file starts with a blank line followed by an xml declaration, ccnet will treat this as invalid xml (which it is) and will wrap it in a CDATA tag.  We need to update the code so that it will strip this blank line so that the xml will be valid. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.public.thoughtworks.org/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

     [ http://jira.public.thoughtworks.org/browse/CCNET-33?page=history ]
     
Owen Rogers resolved CCNET-33:
------------------------------

    Fix Version:     (was: Medium Term)
                 Next
     Resolution: Fixed

this is implemented in build 806.  there is a new appSettings element added to the ccservice.exe.config file for specifying the service name.

> Allow service name to be configured (Bill Simser)
> -------------------------------------------------
>
>          Key: CCNET-33
>          URL: http://jira.public.thoughtworks.org/browse/CCNET-33
>      Project: CruiseControl .NET
>         Type: New Feature
>   Components: Service
>     Versions: 0.5
>     Reporter: Mike Roberts
>     Assignee: Owen Rogers
>      Fix For: Next

>
>
> Currently the service name is hardcoded as 'CCService' in both the service class and the installer - is there anyway we could make this configurable? This would allow more than one instance of the service to be running on one machine.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.public.thoughtworks.org/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

'Latest' links on Dashboard should be evaluated when clicked, not when the link was renderred
---------------------------------------------------------------------------------------------

         Key: CCNET-367
         URL: http://jira.public.thoughtworks.org/browse/CCNET-367
     Project: CruiseControl .NET
        Type: Improvement
    Reporter: Mike Roberts


There are a few latest links on the Dashboard that are static once renderred. It would be much better if they actually went to the build that was latest at the time that the user clicked 'latest'.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.public.thoughtworks.org/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

     [ http://jira.public.thoughtworks.org/browse/CCNET-253?page=history ]

Owen Rogers reassigned CCNET-253:
---------------------------------

    Assign To: Owen Rogers

> NAnt warnings showing as errors in build report
> -----------------------------------------------
>
>          Key: CCNET-253
>          URL: http://jira.public.thoughtworks.org/browse/CCNET-253
>      Project: CruiseControl .NET
>         Type: Bug
>     Versions: 0.7
>     Reporter: Mike Roberts
>     Assignee: Owen Rogers

>
>
> From Nicklas Norling's email:
> --
> Just got around to test 0.7 and found that every task with 'failonerror=false' that actually fails
> during the build is logged under the error section of the build publisher email. I don't have a IIS
> setup here so I can't tell if the webpages look the same.
> All of the cases where Nant emitts an error has been scrutinized by me and where nothing
> else could be done I've had to use failonerror=false. I really don't see the point in showing them
> with each build. There is a distinct risk real errors might get drowned in those as well.
> I think that non-critical errors from nant should never been displayed like this. Not even as warnings.
> --
> We could do with getting a test case for this, even if we can't automate it.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.public.thoughtworks.org/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

     [ http://jira.public.thoughtworks.org/browse/CCNET-253?page=history ]
     
Owen Rogers reopened CCNET-253:
-------------------------------


actually i think that this is still an issue.  as i'm the main contributor to the XmlLogger and as this issue directly affects ccnet, i like to keep this open until we can resolve it.  it should be possible to indicate which failures can be ignored because of failonerror="false", but it will require some modifications to the XmlLogger.

> NAnt warnings showing as errors in build report
> -----------------------------------------------
>
>          Key: CCNET-253
>          URL: http://jira.public.thoughtworks.org/browse/CCNET-253
>      Project: CruiseControl .NET
>         Type: Bug
>     Versions: 0.7
>     Reporter: Mike Roberts

>
>
> From Nicklas Norling's email:
> --
> Just got around to test 0.7 and found that every task with 'failonerror=false' that actually fails
> during the build is logged under the error section of the build publisher email. I don't have a IIS
> setup here so I can't tell if the webpages look the same.
> All of the cases where Nant emitts an error has been scrutinized by me and where nothing
> else could be done I've had to use failonerror=false. I really don't see the point in showing them
> with each build. There is a distinct risk real errors might get drowned in those as well.
> I think that non-critical errors from nant should never been displayed like this. Not even as warnings.
> --
> We could do with getting a test case for this, even if we can't automate it.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.public.thoughtworks.org/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

     [ http://jira.public.thoughtworks.org/browse/CCNET-366?page=history ]

Mike Roberts updated CCNET-366:
-------------------------------

    Attachment: svn.patch

> Subversion specific labeller for using Subversion revision number
> -----------------------------------------------------------------
>
>          Key: CCNET-366
>          URL: http://jira.public.thoughtworks.org/browse/CCNET-366
>      Project: CruiseControl .NET
>         Type: New Feature
>     Reporter: Mike Roberts
>      Fix For: Soon
>  Attachments: svn.patch
>
>
> As supplied by Nick Head (ni...@ko...)
> At the moment there's an issue about Force Builds - we might get '0' or repeated version numbers - is this a problem or is it a case of 'buyer beware' ?

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.public.thoughtworks.org/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

Subversion specific labeller for using Subversion revision number
-----------------------------------------------------------------

         Key: CCNET-366
         URL: http://jira.public.thoughtworks.org/browse/CCNET-366
     Project: CruiseControl .NET
        Type: New Feature
    Reporter: Mike Roberts
     Fix For: Soon
 Attachments: svn.patch

As supplied by Nick Head (ni...@ko...)

At the moment there's an issue about Force Builds - we might get '0' or repeated version numbers - is this a problem or is it a case of 'buyer beware' ?

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.public.thoughtworks.org/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

     [ http://jira.public.thoughtworks.org/browse/CCNET-365?page=history ]

Mike Roberts updated CCNET-365:
-------------------------------

    Fix Version: Medium Term
        Version: 0.8

> Clarify use of CVSROOT for CVS plugin
> -------------------------------------
>
>          Key: CCNET-365
>          URL: http://jira.public.thoughtworks.org/browse/CCNET-365
>      Project: CruiseControl .NET
>         Type: Improvement
>     Versions: 0.8
>     Reporter: Mike Roberts
>      Fix For: Medium Term

>
>
> Mark Henry writes:
> --
> the cvsroot configuration isn't always used.  In particular,
> it was used when checking for modifications, but not when checking out
> the changes.  In order to work around this, I created a batch file that
> was called instead of directly calling cvs.exe.  The batch file simply
> added the correct cvsroot value to the cvs command line.
> --

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.public.thoughtworks.org/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

Clarify use of CVSROOT for CVS plugin
-------------------------------------

         Key: CCNET-365
         URL: http://jira.public.thoughtworks.org/browse/CCNET-365
     Project: CruiseControl .NET
        Type: Improvement
    Versions: 0.8    
    Reporter: Mike Roberts
     Fix For: Medium Term


Mark Henry writes:
--
the cvsroot configuration isn't always used.  In particular,
it was used when checking for modifications, but not when checking out
the changes.  In order to work around this, I created a batch file that
was called instead of directly calling cvs.exe.  The batch file simply
added the correct cvsroot value to the cvs command line.
--

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.public.thoughtworks.org/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

     [ http://jira.public.thoughtworks.org/browse/CCNET-30?page=history ]
     
Mike Roberts resolved CCNET-30:
-------------------------------

    Fix Version:     (was: Medium Term)
     Resolution: Won't Fix

We haven't heard a similar to problem to this so am marking it as WontFix . If anyone does have a similar problem please add a new issue and link this one.

> Problem with -tag for Cvs provider
> ----------------------------------
>
>          Key: CCNET-30
>          URL: http://jira.public.thoughtworks.org/browse/CCNET-30
>      Project: CruiseControl .NET
>         Type: Bug
>   Components: Source Control
>     Versions: 0.5
>     Reporter: Owen Rogers
>     Assignee: Owen Rogers

>
>
> ** copied from sourceforge tracker
> I have had the same problem with CVS.
> I don't know why, but if you use CVS/pserver try out to 
> remove the -tag - if you have.
> The -tag must point to the 'outchecked' 
> project root where should be scanned for modifications.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.public.thoughtworks.org/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

     [ http://jira.public.thoughtworks.org/browse/CCNET-123?page=history ]

Mike Roberts updated CCNET-123:
-------------------------------

    Fix Version:     (was: Medium Term)
                 Eventually
    Environment: 

> Allow CVS plugin to be more configurable
> ----------------------------------------
>
>          Key: CCNET-123
>          URL: http://jira.public.thoughtworks.org/browse/CCNET-123
>      Project: CruiseControl .NET
>         Type: New Feature
>   Components: Builder
>     Versions: 0.7 RC-1
>     Reporter: Mike Roberts
>     Priority: Minor
>      Fix For: Eventually

>
>
> The CVS plugin uses the 'cvs log' command. In certain situations, it may be more useful to use the 'cvs history' command. It would be useful to allow a user to choose what kind of command they want to use.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.public.thoughtworks.org/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

     [ http://jira.public.thoughtworks.org/browse/CCNET-243?page=comments#action_11142 ]
     
Mike Roberts commented on CCNET-243:
------------------------------------

On Jan 19 Mark Henry wrote:
--
First, with our version of CVS (1.12.10), the date format has changed -
CVS now uses dashes ("-") instead of slashes ("/") as a date separator.
And the timezone is now taken into account as well, rather then having
all times reported as GMT.  That required a modification to the source
in order to get CC to work with the new CVS.
--

... so I don't know what the current status is.

> Latest cvs server breaks date parser for "log" command
> ------------------------------------------------------
>
>          Key: CCNET-243
>          URL: http://jira.public.thoughtworks.org/browse/CCNET-243
>      Project: CruiseControl .NET
>         Type: Bug
>   Components: Source Control
>     Versions: 0.7
>  Environment: cvs 1.12.9
>     Reporter: Shawn Hempel
>     Assignee: Owen Rogers
>     Priority: Blocker
>      Fix For: Soon

>
>
> cvs release 1.12.9 [http://ccvs.cvshome.org/] has been out since June 9, 2004. Unfortunately we just installed it over top of our existing cvs server 1.11.16 and it broke our entire build process.
> The ccnet sources need to be updated to handle the log command's new date format used by this version. Currently they assume RCS date format, which is no longer the case and the result is a run-time exception in [CvsHistoryParser.ParseModifiedTime].
> The following lines are no longer sufficient:
> \project\core\sourcecontrol: Lines 234-238
>   string dateTimeString = dateStamp + " " + timeStamp + " +0";
>   return DateTime.ParseExact(
>     dateTimeString,
>     LOGDATE_FORMAT,
>     DateTimeFormatInfo.GetInstance(CultureInfo.InvariantCulture));
> Where LOGDATE_FORMAT is pre-defined as:
>   LOGDATE_FORMAT = "yyyy/MM/dd HH:mm:ss z";
> The date format can not be guaranteed since it by server verion. Thus I think the problem could be solved by changing from DateTime.ParseExact to DateTime.Parse. I don't fully understand the desire to enforce an exact date format anyway since any parsable date should be sufficient.
> If the decision is made to enforce a strict date format, at least catch the FormatException and just log it so CCNet can continue to run. And it will have to be kept up-to-date with changes in cvs versions.
> Relevant Error Output:
> 11/8/2004 11:13:57 PM: [MyProject:Debug]: Attempting to start process [C:\Program Files\GNU\WinCvs 1.3\CVSNT\cvs.exe] in working directory [C:\{...}\{...}] with arguments [-d myCvsRoot -q log -N "-d>2004-11-08 07:13:57 GMT"]
> 11/8/2004 11:14:03 PM: [MyProject:Error]: INTERNAL ERROR: String was not recognized as a valid DateTime.
> ----------
> System.FormatException: String was not recognized as a valid DateTime.
>    at System.DateTimeParse.ParseFormatError(Boolean isThrowException, String resourceID)
>    at System.DateTimeParse.ParseByFormat(__DTString str, __DTString format, ParsingInfo parseInfo, DateTimeFormatInfo dtfi, Boolean isThrowExp, DateTimeResult result)
>    at System.DateTimeParse.DoStrictParse(String s, String formatParam, DateTimeStyles styles, DateTimeFormatInfo dtfi, Boolean isThrowExp, DateTime& returnValue)
>    at System.DateTimeParse.ParseExact(String s, String format, DateTimeFormatInfo dtfi, DateTimeStyles style)
>    at System.DateTime.ParseExact(String s, String format, IFormatProvider provider)
>    at ThoughtWorks.CruiseControl.Core.Sourcecontrol.CvsHistoryParser.ParseModifiedTime(String dateStamp, String timeStamp) in d:\sourceforge\ccnet\project\core\sourcecontrol\CvsHistoryParser.cs:line 235
>    at ThoughtWorks.CruiseControl.Core.Sourcecontrol.CvsHistoryParser.ParseDateLine(String dateLine) in d:\sourceforge\ccnet\project\core\sourcecontrol\CvsHistoryParser.cs:line 227
>    at ThoughtWorks.CruiseControl.Core.Sourcecontrol.CvsHistoryParser.ParseModification(TextReader reader) in d:\sourceforge\ccnet\project\core\sourcecontrol\CvsHistoryParser.cs:line 149
>    at ThoughtWorks.CruiseControl.Core.Sourcecontrol.CvsHistoryParser.ParseFileEntry(TextReader cvsLog) in d:\sourceforge\ccnet\project\core\sourcecontrol\CvsHistoryParser.cs:line 108
>    at ThoughtWorks.CruiseControl.Core.Sourcecontrol.CvsHistoryParser.Parse(TextReader cvsLog, DateTime from, DateTime to) in d:\sourceforge\ccnet\project\core\sourcecontrol\CvsHistoryParser.cs:line 86
>    at ThoughtWorks.CruiseControl.Core.Sourcecontrol.ProcessSourceControl.ParseModifications(TextReader reader, DateTime from, DateTime to) in d:\sourceforge\ccnet\project\core\sourcecontrol\ProcessSourceControl.cs:line 70
>    at ThoughtWorks.CruiseControl.Core.Sourcecontrol.ProcessSourceControl.ParseModifications(ProcessResult result, DateTime from, DateTime to) in d:\sourceforge\ccnet\project\core\sourcecontrol\ProcessSourceControl.cs:line 65
>    at ThoughtWorks.CruiseControl.Core.Sourcecontrol.ProcessSourceControl.GetModifications(ProcessInfo info, DateTime from, DateTime to) in d:\sourceforge\ccnet\project\core\sourcecontrol\ProcessSourceControl.cs:line 39
>    at ThoughtWorks.CruiseControl.Core.Sourcecontrol.Cvs.GetModifications(DateTime from, DateTime to) in d:\sourceforge\ccnet\project\core\sourcecontrol\Cvs.cs:line 68
>    at ThoughtWorks.CruiseControl.Core.Project.GetSourceModifications(IIntegrationResult result) in d:\sourceforge\ccnet\project\core\Project.cs:line 185
>    at ThoughtWorks.CruiseControl.Core.Project.AttemptToRunIntegration(IIntegrationResult result) in d:\sourceforge\ccnet\project\core\Project.cs:line 163
> ----------

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.public.thoughtworks.org/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

     [ http://jira.public.thoughtworks.org/browse/CCNET-363?page=comments#action_11139 ]
     
Steve Moyer commented on CCNET-363:
-----------------------------------

I realize I'll have to force the build, the tool I wrote scripts databases to vss and then attempts to rebuild them using the scripts so theres no real good way to tell when any part of the db has changed.  Thanks for making the quick response!

> Project SourceControl should not be required
> --------------------------------------------
>
>          Key: CCNET-363
>          URL: http://jira.public.thoughtworks.org/browse/CCNET-363
>      Project: CruiseControl .NET
>         Type: Improvement
>   Components: Source Control
>     Versions: 0.8
>     Reporter: 
>      Fix For: Next

>
> Original Estimate: 2 days
>         Remaining: 2 days
>
> SourceControl element of project should not be required as this limits the scope of what can be run as a project.  I would like to run a tool that does the source control interaction on its own and it doesn't make sense to be forced to set up a dummy SourceControl object just to get it running.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.public.thoughtworks.org/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

     [ http://jira.public.thoughtworks.org/browse/CCNET-253?page=history ]
     
Mike Roberts resolved CCNET-253:
--------------------------------

    Fix Version:     (was: Soon)
     Resolution: Won't Fix

I think this is a NAnt issue (there was some discussion on the mailing list). Owen, please unfix this if there is still wrk for us to do.

> NAnt warnings showing as errors in build report
> -----------------------------------------------
>
>          Key: CCNET-253
>          URL: http://jira.public.thoughtworks.org/browse/CCNET-253
>      Project: CruiseControl .NET
>         Type: Bug
>     Versions: 0.7
>     Reporter: Mike Roberts

>
>
> From Nicklas Norling's email:
> --
> Just got around to test 0.7 and found that every task with 'failonerror=false' that actually fails
> during the build is logged under the error section of the build publisher email. I don't have a IIS
> setup here so I can't tell if the webpages look the same.
> All of the cases where Nant emitts an error has been scrutinized by me and where nothing
> else could be done I've had to use failonerror=false. I really don't see the point in showing them
> with each build. There is a distinct risk real errors might get drowned in those as well.
> I think that non-critical errors from nant should never been displayed like this. Not even as warnings.
> --
> We could do with getting a test case for this, even if we can't automate it.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.public.thoughtworks.org/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

     [ http://jira.public.thoughtworks.org/browse/CCNET-124?page=history ]
     
Mike Roberts resolved CCNET-124:
--------------------------------

    Resolution: Won't Fix

> email publishers don't work consistently. 
> ------------------------------------------
>
>          Key: CCNET-124
>          URL: http://jira.public.thoughtworks.org/browse/CCNET-124
>      Project: CruiseControl .NET
>         Type: Bug
>   Components: Service
>     Versions: 0.6.1
>  Environment: windows 2003 server, latest nightly
>     Reporter: 

>
>
> email publisher seems broken.  Works when build fails, but not otherwise.  Here is the exception in the ccnet.log I get when it doesn't send out emails.
> 7/21/2004 11:52:37 AM: [Integration:Warning]: Exception: Exception thrown by publisher
> ----------
> ThoughtWorks.CruiseControl.Core.CruiseControlException: Exception thrown by publisher ---> ThoughtWorks.CruiseControl.Core.CruiseControlException: EmailPublisher exception: System.Web.HttpException: Could not access 'CDO.Message' object. ---> System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.Runtime.InteropServices.COMException (0x80040213): The transport failed to connect to the server.
>    --- End of inner exception stack trace ---
>    at System.RuntimeType.InvokeDispMethod(String name, BindingFlags invokeAttr, Object target, Object[] args, Boolean[] byrefModifiers, Int32 culture, String[] namedParameters)
>    at System.RuntimeType.InvokeMember(String name, BindingFlags invokeAttr, Binder binder, Object target, Object[] args, ParameterModifier[] modifiers, CultureInfo culture, String[] namedParameters)
>    at System.Web.Mail.LateBoundAccessHelper.CallMethod(Object obj, String methodName, Object[] args)
>    --- End of inner exception stack trace ---
>    at System.Web.Mail.LateBoundAccessHelper.CallMethod(Object obj, String methodName, Object[] args)
>    at System.Web.Mail.CdoSysHelper.Send(MailMessage message)
>    at System.Web.Mail.SmtpMail.Send(MailMessage message)
>    at ThoughtWorks.CruiseControl.Core.Publishers.EmailGateway.Send(String from, String to, String subject, String messageText) in d:\sourceforge\ccnet\project\core\publishers\EmailGateway.cs:line 22
>    at ThoughtWorks.CruiseControl.Core.Publishers.EmailPublisher.SendMessage(String from, String to, String subject, String message) in d:\sourceforge\ccnet\project\core\publishers\EmailPublisher.cs:line 140 ---> System.Web.HttpException: Could not access 'CDO.Message' object. ---> System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.Runtime.InteropServices.COMException (0x80040213): The transport failed to connect to the server.
>    --- End of inner exception stack trace ---
>    at System.RuntimeType.InvokeDispMethod(String name, BindingFlags invokeAttr, Object target, Object[] args, Boolean[] byrefModifiers, Int32 culture, String[] namedParameters)
>    at System.RuntimeType.InvokeMember(String name, BindingFlags invokeAttr, Binder binder, Object target, Object[] args, ParameterModifier[] modifiers, CultureInfo culture, String[] namedParameters)
>    at System.Web.Mail.LateBoundAccessHelper.CallMethod(Object obj, String methodName, Object[] args)
>    --- End of inner exception stack trace ---
>    at System.Web.Mail.LateBoundAccessHelper.CallMethod(Object obj, String methodName, Object[] args)
>    at System.Web.Mail.CdoSysHelper.Send(MailMessage message)
>    at System.Web.Mail.SmtpMail.Send(MailMessage message)
>    at ThoughtWorks.CruiseControl.Core.Publishers.EmailGateway.Send(String from, String to, String subject, String messageText) in d:\sourceforge\ccnet\project\core\publishers\EmailGateway.cs:line 22
>    at ThoughtWorks.CruiseControl.Core.Publishers.EmailPublisher.SendMessage(String from, String to, String subject, String message) in d:\sourceforge\ccnet\project\core\publishers\EmailPublisher.cs:line 140
>    --- End of inner exception stack trace ---
>    at ThoughtWorks.CruiseControl.Core.Publishers.EmailPublisher.SendMessage(String from, String to, String subject, String message) in d:\sourceforge\ccnet\project\core\publishers\EmailPublisher.cs:line 144
>    at ThoughtWorks.CruiseControl.Core.Publishers.EmailPublisher.PublishIntegrationResults(IProject project, IntegrationResult result) in d:\sourceforge\ccnet\project\core\publishers\EmailPublisher.cs:line 127
>    at ThoughtWorks.CruiseControl.Core.Publishers.PublisherBase.Project_IntegrationCompleted(Object source, IntegrationCompletedEventArgs e) in d:\sourceforge\ccnet\project\core\publishers\PublisherBase.cs:line 38
>    --- End of inner exception stack trace ---
> ----------

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.public.thoughtworks.org/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

     [ http://jira.public.thoughtworks.org/browse/CCNET-28?page=history ]
     
Mike Roberts resolved CCNET-28:
-------------------------------

    Fix Version:     (was: Medium Term)
     Resolution: Fixed

Pretty certain this got fixed a while back. HtmlDetailsMessageBuilder now uses a HtmlLinkMessageBuilder with 'includeAnchorTag' set to true.

> Path to build log in email as an active link (Martin Hanson)
> ------------------------------------------------------------
>
>          Key: CCNET-28
>          URL: http://jira.public.thoughtworks.org/browse/CCNET-28
>      Project: CruiseControl .NET
>         Type: Improvement
>   Components: Publisher
>     Versions: 0.5 (CCNetLive), 0.5
>     Reporter: Owen Rogers
>     Assignee: Owen Rogers

>
>
> The HTML email message that is sent to developers 
> does not display the path to the build log as a link. It 
> would be good if it did.
> I have implemented a workaround to support this. The 
> change is to CreateHtmlMessage in EmailPublisher in 
> tw.ccnet.core.publishers. The new implementation is as 
> follows:
> private string CreateHtmlMessage(IntegrationResult 
> result)
> {
> StringBuilder message = new StringBuilder(10000);
> message.Append("<html><head></head><body>");
> message.AppendFormat("CC.NET Build Results for 
> {0}: <a href=\"{1}\">{1}</a>",
> result.ProjectName, LogFile.CreateUrl(ProjectUrl, 
> result));
> AppendHtmlMessageDetails(result, message);
> message.Append("</body></html>");
> return message.ToString();

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.public.thoughtworks.org/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira