ccnet-devel Mailing List for CruiseControl.NET

On 12/20/05, Graham Tackley <gr...@ta...> wrote:

>    2. It's set up to read log4net settings from the normal app.config
>       file.  This is easy and consistant with the old way, but does mean
>       log4net can't watch the file for changes.  How important is it to
>       support dynamic updates to the log settings?

Not important at all. I am quite happy for the log4net settings to be
in the same config. ccnet.exe.config is only fiddled about at set up
time. I haven't touch mine in months!

--
Perry Ismangil

Hi,

We use Log4Net heavily in our projects and have found it very stable, flexi=
ble and overall extremely useful.

We use a wrapper ( called LOG ) class with static methods for each of the W=
arn/Debug/Info etc functions - very similar to you implementation in CCNETs=
 Log class.

However, we go one step further and use the StackTrace class to determing t=
he calling object which is then used in the LogManager.GetLogger( ) call to=
 get a scoped logger object.

This means that not only can you outpu the calling Thread Name/ID but also =
the object from which the made the logging statement came.

If you think this would be useful I can provide our source code or ( time p=
ermitting ) I could provide a patch/unit tests.

Regards,

Nick Vaughan
-----------------------------------------------
http://www.codestuff.net
-----------------------------------------------

----- Start Original Message -----
From: Graham Tackley <gr...@ta...>
To: ccn...@li...
Subject: [Ccnet-devel] CCNET-199: log4net support

> I've just committed an initial implementation of CCNET-199 - log4net=20
> support - into HEAD (1.1).  The approach taken for this initial step was=
=20
> to minimise the changes to the rest of ccnet: the only significant=20
> change was to the "Log" class (and of course to the .config files).  The=
=20
> aim was to keep the output looking mostly the same as current.
>=20
> In order to do this, and use the latest version of log4net, I had to=20
> rebuild the NVelocity DLL which had a dependency on an 2 year old=20
> version of log4net.
>=20
> The only noticiable change is that log output which is not from a=20
> project-builder thread is now prefixed with the thread id (it used to be=
=20
> "CruiseControl server").  Log output from the project builder threads is=
=20
> prefixed with the name of the project, as previously.=20
>=20
> The default configuration is set to create a new log file after 1MB, and=
=20
> keep the last 10 log files. This all seems to work ok with the dashboard=
=20
> log viewer.  Logging also works fine under mono on linux (with the same=
=20
> binaries).
>=20
> Some potential improvements:
>=20
>    1. Switch to having a separate log instance for each project
>       builder.  That would enable changing log levels on a per project
>       basis, but is a non trivial change.  (And, to be honest, the
>       current thread-affinity approach seems to work just fine.)
>    2. It's set up to read log4net settings from the normal app.config
>       file.  This is easy and consistant with the old way, but does mean
>       log4net can't watch the file for changes.  How important is it to
>       support dynamic updates to the log settings?
>=20
> If we're happy with this, we need to go through and delete all the old=20
> System.Diagnostics support stuff, fix up the couple of tests I had to=20
> ignore because they had initimate knowledge of how the Log class was=20
> working, and update the docs of course.
>=20
> Feedback welcome.
>=20
> Cheers
> g
>=20
>=20
>=20
>=20
>=20
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through log fi=
les
> for problems?  Stop!  Download the new AJAX search engine that makes
> searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
> http://ads.osdn.com/?ad_id=3D7637&alloc_id=3D16865&op=3Dclick
> _______________________________________________
> Ccnet-devel mailing list
> Ccn...@li...
> https://lists.sourceforge.net/lists/listinfo/ccnet-devel
>=20
>=20

----- End Original Message -----

I've just committed an initial implementation of CCNET-199 - log4net 
support - into HEAD (1.1).  The approach taken for this initial step was 
to minimise the changes to the rest of ccnet: the only significant 
change was to the "Log" class (and of course to the .config files).  The 
aim was to keep the output looking mostly the same as current.

In order to do this, and use the latest version of log4net, I had to 
rebuild the NVelocity DLL which had a dependency on an 2 year old 
version of log4net.

The only noticiable change is that log output which is not from a 
project-builder thread is now prefixed with the thread id (it used to be 
"CruiseControl server").  Log output from the project builder threads is 
prefixed with the name of the project, as previously. 

The default configuration is set to create a new log file after 1MB, and 
keep the last 10 log files. This all seems to work ok with the dashboard 
log viewer.  Logging also works fine under mono on linux (with the same 
binaries).

Some potential improvements:

   1. Switch to having a separate log instance for each project
      builder.  That would enable changing log levels on a per project
      basis, but is a non trivial change.  (And, to be honest, the
      current thread-affinity approach seems to work just fine.)
   2. It's set up to read log4net settings from the normal app.config
      file.  This is easy and consistant with the old way, but does mean
      log4net can't watch the file for changes.  How important is it to
      support dynamic updates to the log settings?

If we're happy with this, we need to go through and delete all the old 
System.Diagnostics support stuff, fix up the couple of tests I had to 
ignore because they had initimate knowledge of how the Log class was 
working, and update the docs of course.

Feedback welcome.

Cheers
g

Owen,

Owen Rogers wrote:

>this past weekend mike and i spent some time talking about the
>priorities (at least as far as we see them for the 1.1 release). 
>we've identified 4 core enhancements that we are planning to make up
>the 1.1 release.  they are (in no particular order):
>
>1) cctray: completing the work on cctray to read its status from the
>dashboard rather than polling the build server directly.  this
>simplifies aggregating build results across multiple servers and
>should reduce the amount of cctray configuration required.  this work
>will also include polishing the x10 integration from cctray.
>  
>
+1.  CCNET-228 covers the reading status from dashboard stuff (and 
contains a list of what's left to do). CCNET-601 covers the X10 stuff. 

>2) artifact management: right now ccnet manages artifacts by merging
>everything into one large xml file.  we are very aware of the
>shortcomings of this approach.  the plan is to replace/supplement this
>with a better system for artifact management, where ccnet will be able
>to manage and report on the various artifacts produced during the
>build process by using build-specific artifact directories to provide
>a common location for storing the artifacts.  the goal is to use
>sensible names and defaults to minimise the amount of configuration
>required for ccnet to identify the type of each artifact (ie. place
>nunit result files in an 'nunit' folder, etc).
>  
>
+1, though I'll leave working out the detail on this to yourself, mike 
and all of the others on the list :)

>3) build visibility: once a build starts, it is currently not possible
>to gauge the progress of the build until it completes.  the plan is
>improve the visibility of what is happening during the build via the
>dashboard and cctray.  this work will also include providing profiling
>information on the running time for ccnet tasks.
>
>  
>
+1.  I notice owen that you started some work on this as a result of 
CCNET-625 (and CCNET-158 I think is probably the same thing).  I'm not 
totally convinced that updating ProjectActivity is the way to go -- 
fundamentally there are the just 3 states of sleeping, building, and 
checking modifications (more accurately,  "working out whether a build 
should occur").  I'd like to retain those  computer-meaningful three 
values, but then additionally allow the server to provide 
human-meaningful free text that describes where it is in that step.

(And did that change break compatibility of the remoting interface?  I 
think we still don't have a good story in that area.)

>4) logging: currently, ccnet does not provide much flexibility on how
>it logs information and the ccnet.log file has a propensity to grow
>rapidly.  the plan for this release is to keep things simple by adding
>support for some additional loggers/appenders by linking in an
>external log framework (possibly log4net).
>
>  
>
+5.  (Especially since this is the current biggest blocker for running 
under mono.)  I couldn't find a jira case for this, so I've taken the 
liberty of updating CCNET-199 to cover.  (It used to read "create a 
log4net bridge" which I think ends up with the worst of all worlds.)

I've been doing some work on this today -- i'll update the list with a 
separate email (4 topics with 25 replies already is probably enough for 
this thread ;) )

Rgds
g

Hi

I prefer the xml configuration :
1) other settings are also found in there, makes it easy
2) you can get into trouble with reading/writing in the registry and
security


with kind regards

On 12/19/05, Graham Tackley <gr...@ta...> wrote:
>
> Grant,
>
> Thanks again -- this looks really good and something that has been
> called for for quite a while.  I've created jira case CCNET-633 and
> committed your changes against it.  This will be part of the ccnet 1.1
> release.
>
> I changed the names of the registry values slightly so they were english
> rather than code - e.g. colProjectWidth became ProjectColumnWidth.
>
> This is the first time that any part of ccnet has used the registry for
> configuration, and I did consider changing PersistableWindowState so
> that it used a xml file instead, which is the project standard.  I
> convinced myself that the registry was OK for this kind of stuff as it
> is just "UI fluff" rather than core configuration.  Does anyone on the
> list object?
>
> Thanks,
> Graham
>
>
> Graham Tackley wrote:
>
> > Grant,
> >
> > That sounds great -- those are features that cctray has been severly
> > missing.  I should get a chance to process your changes and include
> > them in early next week.
> >
> > Thanks,
> > Graham
> >
> >
> > Gra...@ba... wrote:
> >
> >> I accept the ThoughtWorks contributor agreement. The zip file needs
> >> renaming.
> >>
> >> As per my posting to ccnet-user please find attached some changed/new
> >> files
> >> for the CCTrayLib project. Apologies for them not being in "patch"
> >> format
> >> but couldn't get TortoiseCVS to manage that part too well...
> >>
> >> Changes to support the following:
> >> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> >> - CCTray main window re-opening where the window last closed from.
> >> - CCTray main window remembering the sizing of the column widths.
> >> - Retains focus on selected line in listview when clicking "Force
> Build"
> >> button.
> >> - CCTray main window has full row selection making much easier to read=
.
> >>
> >> Notes:
> >> =3D=3D=3D=3D=3D=3D=3D
> >> - PersistableWindowState could be re-used on other forms within
> >> CCTrayLib. I
> >> have just applied it to the MainForm.cs at this point since it's most
> >> frequently used.
> >> - Registry key location is hard-coded in the form
> >> "HookPersistentWindowState" method. If re-using across multiple forms
> >> would
> >> want to add another level of depth to the registry location and
> >> refactor out
> >> the constant.
> >>
> >> Grant.
> >>
> >>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through log
> files
> for problems?  Stop!  Download the new AJAX search engine that makes
> searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
> http://ads.osdn.com/?ad_id=3D7637&alloc_id=3D16865&op=3Dclick
> _______________________________________________
> Ccnet-devel mailing list
> Ccn...@li...
> https://lists.sourceforge.net/lists/listinfo/ccnet-devel
>

I'm still not very happy with the SerialPort libraries that are in use in my
version of the code; and I want to test out the Firecracker interface before
any commits are done.

I will change the Tab name.  Good idea.

Sunrise/Sunset.  To exclude based on sunrise and sunset means that you don't
want any X10 action to happen during the off hours.  

"If the sun is not up, no one is at work so don't do any X10 Automation"

I should probably add a sub-tab to give people the ability to do something
on the rise/set or the off/on events of the day.  For example, at sunset
Turn All Lights Off.  I need lat/long because it will calculate the rise/set
times based on their exact location.

-Rob
 

-----Original Message-----
From: ccn...@li...
[mailto:ccn...@li...] On Behalf Of Graham Tackley
Sent: Monday, December 19, 2005 7:55 AM
To: ccn...@li...
Subject: Re: [Ccnet-devel] CCTray with X10 Demo

Rob,

I haven't got any X10 devices to try out alas.

But I did download & play with your stuff to check out the newly tabbed
configuration dialog.  Looks great I think, and works well!  I'm keen to get
that committed into 1.1 asap...

One (minor) comment: I'd suggest renaming the X10 tab from Automation to
"X10 Automation".  Just plain "Automation" makes me think that the tab is
going to give me a scripting language of some kind...

BTW out of interest how does/will the lat/long sunrise/sunset stuff work?

Cheers
g


Rob Chartier wrote:

>ccnet devs,
>
>
>Anyone want to test out my new build of the CCTray with X10 support, 
>including the UI for settings?  I want to gather feedback before I 
>actually submit it to Owen and Mike for CVS.  It is built with the 
>current "CruiseControl.NET-1.0.source".
>
>Download: http://www.mscorlib.com/CCTrayWithX10.rar
>
>Here is a screenshot of the Automation Tab in the Settings UI:
>
>http://static.flickr.com/35/73602360_d9305384b4_o.jpg
>
>
>I have not yet fully tested the CM17A (firecracker) interface; but I 
>know the code works just haven't been able to test it in this 
>environment.  I have a new one on order and it should be here anytime now.
>
>
>Features:
>- Turn on or off X10 support all together
>
>- Choose the COM Port
>- Choose the X10 Device CM11A or CM17A
>
>- Testing inline
>
>- Ability to chain together a collection of X10 actions to:
>	Successful, Fixed, Broken and Still Failing events
>
>- Turn on or off the Time based Exclusions
>	- Exclude on Weekends
>	- Exclude by specific time of day
>	- Exclude based on Sunrise/Sunset for your given longitude/latitude
>		(default long/lat are for Vancouver BC, Canada)
>
>
>Let me know your thoughts.
>
>Thanks,
>
>-Rob
>
>
>
>
>-------------------------------------------------------
>This SF.net email is sponsored by: Splunk Inc. Do you grep through log 
>files for problems?  Stop!  Download the new AJAX search engine that 
>makes searching your log files as easy as surfing the  web.  DOWNLOAD
SPLUNK!
>http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
>_______________________________________________
>Ccnet-devel mailing list
>Ccn...@li...
>https://lists.sourceforge.net/lists/listinfo/ccnet-devel
>  
>



-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Ccnet-devel mailing list
Ccn...@li...
https://lists.sourceforge.net/lists/listinfo/ccnet-devel

Rob,

I haven't got any X10 devices to try out alas.

But I did download & play with your stuff to check out the newly tabbed 
configuration dialog.  Looks great I think, and works well!  I'm keen to 
get that committed into 1.1 asap...

One (minor) comment: I'd suggest renaming the X10 tab from Automation to 
"X10 Automation".  Just plain "Automation" makes me think that the tab 
is going to give me a scripting language of some kind...

BTW out of interest how does/will the lat/long sunrise/sunset stuff work?

Cheers
g


Rob Chartier wrote:

>ccnet devs,
>
>
>Anyone want to test out my new build of the CCTray with X10 support,
>including the UI for settings?  I want to gather feedback before I actually
>submit it to Owen and Mike for CVS.  It is built with the current
>"CruiseControl.NET-1.0.source".
>
>Download: http://www.mscorlib.com/CCTrayWithX10.rar
>
>Here is a screenshot of the Automation Tab in the Settings UI:
>
>http://static.flickr.com/35/73602360_d9305384b4_o.jpg
>
>
>I have not yet fully tested the CM17A (firecracker) interface; but I know
>the code works just haven't been able to test it in this environment.  I
>have a new one on order and it should be here anytime now.  
>
>
>Features:
>- Turn on or off X10 support all together
>
>- Choose the COM Port
>- Choose the X10 Device CM11A or CM17A
>
>- Testing inline
>
>- Ability to chain together a collection of X10 actions to:
>	Successful, Fixed, Broken and Still Failing events
>
>- Turn on or off the Time based Exclusions
>	- Exclude on Weekends
>	- Exclude by specific time of day
>	- Exclude based on Sunrise/Sunset for your given longitude/latitude
>		(default long/lat are for Vancouver BC, Canada)
>
>
>Let me know your thoughts.
>
>Thanks,
>
>-Rob
>
>
>
>
>-------------------------------------------------------
>This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
>for problems?  Stop!  Download the new AJAX search engine that makes
>searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
>http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
>_______________________________________________
>Ccnet-devel mailing list
>Ccn...@li...
>https://lists.sourceforge.net/lists/listinfo/ccnet-devel
>  
>

Grant,

Thanks again -- this looks really good and something that has been 
called for for quite a while.  I've created jira case CCNET-633 and 
committed your changes against it.  This will be part of the ccnet 1.1 
release.

I changed the names of the registry values slightly so they were english 
rather than code - e.g. colProjectWidth became ProjectColumnWidth.

This is the first time that any part of ccnet has used the registry for 
configuration, and I did consider changing PersistableWindowState so 
that it used a xml file instead, which is the project standard.  I 
convinced myself that the registry was OK for this kind of stuff as it 
is just "UI fluff" rather than core configuration.  Does anyone on the 
list object?

Thanks,
Graham


Graham Tackley wrote:

> Grant,
>
> That sounds great -- those are features that cctray has been severly 
> missing.  I should get a chance to process your changes and include 
> them in early next week.
>
> Thanks,
> Graham
>
>
> Gra...@ba... wrote:
>
>> I accept the ThoughtWorks contributor agreement. The zip file needs
>> renaming.
>>
>> As per my posting to ccnet-user please find attached some changed/new 
>> files
>> for the CCTrayLib project. Apologies for them not being in "patch" 
>> format
>> but couldn't get TortoiseCVS to manage that part too well...
>>
>> Changes to support the following:
>> =================================
>> - CCTray main window re-opening where the window last closed from.
>> - CCTray main window remembering the sizing of the column widths.
>> - Retains focus on selected line in listview when clicking "Force Build"
>> button.
>> - CCTray main window has full row selection making much easier to read.
>>
>> Notes:
>> =======
>> - PersistableWindowState could be re-used on other forms within 
>> CCTrayLib. I
>> have just applied it to the MainForm.cs at this point since it's most
>> frequently used.
>> - Registry key location is hard-coded in the form
>> "HookPersistentWindowState" method. If re-using across multiple forms 
>> would
>> want to add another level of depth to the registry location and 
>> refactor out
>> the constant.
>>
>> Grant.
>>  
>>

So here is the code:

private string TagSource(int revision)
{
      string text1 =3D this.TrunkUrl;
      if (revision =3D=3D 0)
      {
            char[] chArray1 =3D new char[] { Path.DirectorySeparatorChar } =
;
            text1 =3D this.WorkingDirectory.TrimEnd(chArray1);
      }
      return this.SurroundInQuotesIfContainsSpace(text1);
}


The act of barfing occurs when trying to access this.WorkingDirectory.
 I notice in the docs:

 Node =09 Description =09 Type =09 Default =09 Required
workingDirectory =09The directory containing the locally checked out
workspace. =09string =09N/A =09true

So this seems to be a bug to me:

[ReflectorProperty("workingDirectory", Required=3Dfalse)]
public string WorkingDirectory;

P.S. Wouldn't it be easyier to determine and use the Revision number
that should be tagged?


On 12/18/05, Jay Flowers <jay...@gm...> wrote:
> I seem to have a misconfiguration on the tagging.  Any help would be
> great.  Thanks
>
> <sourcecontrol type=3D"filtered">
>       <sourceControlProvider  type=3D"svn" tagOnSuccess=3D"true">
>         <trunkUrl>https://svn.berlios.de/svnroot/repos/cif/Current</trunk=
Url>
>         <username>username</username>
>         <password>password</password>
>         <webUrlBuilder type=3D"websvn">
>           <url>http://svn.berlios.de/wsvn/cif</url>
>         </webUrlBuilder>
>         <tagBaseUrl>https://svn.berlios.de/svnroot/repos/cif/Tags</tagBas=
eUrl>
>       </sourceControlProvider>
>       <exclusionFilters>
>         <pathFilter>
>           <pattern>**/Current/Product/**/AssemblyInfo.*</pattern>
>         </pathFilter>
>         <pathFilter>
>           <pattern>**/Current/Product/ProjectInfo.*</pattern>
>         </pathFilter>
>         <pathFilter>
>           <pattern>**/Current/Product/**/ProjectInfo.*</pattern>
>         </pathFilter>
>         <pathFilter>
>           <pattern>**/Current/Build/*.*</pattern>
>         </pathFilter>
>         <pathFilter>
>           <pattern>**/Current/Build/**/*.*</pattern>
>         </pathFilter>
>       </exclusionFilters>
>     </sourcecontrol>
>
> [CI Factory:Info]: Build complete: Success
> [CI Factory:Error]: Exception: Exception occurred while labelling
> source control provider.
> ----------
> ThoughtWorks.CruiseControl.Core.CruiseControlException: Exception
> occurred while labelling source co
> ntrol provider. ---> System.NullReferenceException: Object reference
> not set to an instance of an ob
> ject.
>    at ThoughtWorks.CruiseControl.Core.Sourcecontrol.Svn.TagSource(Int32
> revision)
>    at ThoughtWorks.CruiseControl.Core.Sourcecontrol.Svn.NewLabelProcessIn=
fo(IIntegrationResult
> resul
> t)
>    at ThoughtWorks.CruiseControl.Core.Sourcecontrol.Svn.LabelSourceContro=
l(IIntegrationResult
> result
> )
>    at ThoughtWorks.CruiseControl.Core.Sourcecontrol.FilteredSourceControl=
.LabelSourceControl(IIntegr
> ationResult result)
>    at ThoughtWorks.CruiseControl.Core.IntegrationRunner.LabelSourceContro=
l(IIntegrationResult
> result
> )
>    --- End of inner exception stack trace ---
> ----------
>
> [CI Factory:Info]: Integration complete: 12/18/2005 3:20:49 PM
>
>
> --
> Jay Flowers
> ----------------------------------------------------------------------
> http://jayflowers.com
> ---------------------------------------------------------------------
>


--
Jay Flowers
----------------------------------------------------------------------
http://jayflowers.com
---------------------------------------------------------------------

I'll give it a shot this week.

Stephen Tunney, MCAD.NET
-----Original Message-----
From: ccn...@li...
[mailto:ccn...@li...] On Behalf Of Rob
Chartier
Sent: December 14, 2005 4:26 AM
To: ccn...@li...
Subject: [Ccnet-devel] CCTray with X10 Demo


ccnet devs,


Anyone want to test out my new build of the CCTray with X10 support,
including the UI for settings?  I want to gather feedback before I
actually
submit it to Owen and Mike for CVS.  It is built with the current
"CruiseControl.NET-1.0.source".

Download: http://www.mscorlib.com/CCTrayWithX10.rar

Here is a screenshot of the Automation Tab in the Settings UI:

http://static.flickr.com/35/73602360_d9305384b4_o.jpg


I have not yet fully tested the CM17A (firecracker) interface; but I
know
the code works just haven't been able to test it in this environment.  I
have a new one on order and it should be here anytime now. =20


Features:
- Turn on or off X10 support all together

- Choose the COM Port
- Choose the X10 Device CM11A or CM17A

- Testing inline

- Ability to chain together a collection of X10 actions to:
	Successful, Fixed, Broken and Still Failing events

- Turn on or off the Time based Exclusions
	- Exclude on Weekends
	- Exclude by specific time of day
	- Exclude based on Sunrise/Sunset for your given
longitude/latitude
		(default long/lat are for Vancouver BC, Canada)


Let me know your thoughts.

Thanks,

-Rob




-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log
files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=3D7637&alloc_id=3D16865&op=3Dclick
_______________________________________________
Ccnet-devel mailing list
Ccn...@li...
https://lists.sourceforge.net/lists/listinfo/ccnet-devel


This Message Scanned for Viruses by McAfee WebShield .

I seem to have a misconfiguration on the tagging.  Any help would be
great.  Thanks

<sourcecontrol type=3D"filtered">
      <sourceControlProvider  type=3D"svn" tagOnSuccess=3D"true">
        <trunkUrl>https://svn.berlios.de/svnroot/repos/cif/Current</trunkUr=
l>
        <username>username</username>
        <password>password</password>
        <webUrlBuilder type=3D"websvn">
          <url>http://svn.berlios.de/wsvn/cif</url>
        </webUrlBuilder>
        <tagBaseUrl>https://svn.berlios.de/svnroot/repos/cif/Tags</tagBaseU=
rl>
      </sourceControlProvider>
      <exclusionFilters>
        <pathFilter>
          <pattern>**/Current/Product/**/AssemblyInfo.*</pattern>
        </pathFilter>
        <pathFilter>
          <pattern>**/Current/Product/ProjectInfo.*</pattern>
        </pathFilter>
        <pathFilter>
          <pattern>**/Current/Product/**/ProjectInfo.*</pattern>
        </pathFilter>
        <pathFilter>
          <pattern>**/Current/Build/*.*</pattern>
        </pathFilter>
        <pathFilter>
          <pattern>**/Current/Build/**/*.*</pattern>
        </pathFilter>
      </exclusionFilters>
    </sourcecontrol>

[CI Factory:Info]: Build complete: Success
[CI Factory:Error]: Exception: Exception occurred while labelling
source control provider.
----------
ThoughtWorks.CruiseControl.Core.CruiseControlException: Exception
occurred while labelling source co
ntrol provider. ---> System.NullReferenceException: Object reference
not set to an instance of an ob
ject.
   at ThoughtWorks.CruiseControl.Core.Sourcecontrol.Svn.TagSource(Int32
revision)
   at ThoughtWorks.CruiseControl.Core.Sourcecontrol.Svn.NewLabelProcessInfo=
(IIntegrationResult
resul
t)
   at ThoughtWorks.CruiseControl.Core.Sourcecontrol.Svn.LabelSourceControl(=
IIntegrationResult
result
)
   at ThoughtWorks.CruiseControl.Core.Sourcecontrol.FilteredSourceControl.L=
abelSourceControl(IIntegr
ationResult result)
   at ThoughtWorks.CruiseControl.Core.IntegrationRunner.LabelSourceControl(=
IIntegrationResult
result
)
   --- End of inner exception stack trace ---
----------

[CI Factory:Info]: Integration complete: 12/18/2005 3:20:49 PM


--
Jay Flowers
----------------------------------------------------------------------
http://jayflowers.com
---------------------------------------------------------------------

cvs diff -u -wb -- core\Triggers\FilterTrigger.cs core\IIntegratable.cs core\IIntegrationResult.cs core\IIntegrationResultManager.cs core\IntegrationResult.cs core\IntegrationResultManager.cs core\IntegrationRunner.cs core\Triggers\IntervalTrigger.cs Remote\ITrigger.cs core\Triggers\MultipleTrigger.cs core\Project.cs core\ProjectIntegrator.cs core\Triggers\ProjectTrigger.cs core\Triggers\ScheduleTrigger.cs core\Workflow.cs (in directory C:\temp\CCNet\ccnet\project\)
Index: core/Triggers/FilterTrigger.cs
===================================================================
RCS file: /cvsroot/ccnet/ccnet/project/core/Triggers/FilterTrigger.cs,v
retrieving revision 1.3
diff -u -w -b -r1.3 FilterTrigger.cs
--- core/Triggers/FilterTrigger.cs	25 Jun 2005 15:04:28 -0000	1.3
+++ core/Triggers/FilterTrigger.cs	18 Dec 2005 06:38:24 -0000
@@ -12,6 +12,7 @@
 		private TimeSpan startTime;
 		private TimeSpan endTime;
 		private DayOfWeek[] weekDays = (DayOfWeek[]) DayOfWeek.GetValues(typeof (DayOfWeek));
+        private string myName;
 
 		public FilterTrigger() : this(new DateTimeProvider())
 		{
@@ -112,5 +113,7 @@
 				}
 			}
 		}
+
+        public string Name()
        {        
            return myName;        
        }

 	}
 }
\ No newline at end of file
Index: core/Triggers/IntervalTrigger.cs
===================================================================
RCS file: /cvsroot/ccnet/ccnet/project/core/Triggers/IntervalTrigger.cs,v
retrieving revision 1.5.2.1
diff -u -w -b -r1.5.2.1 IntervalTrigger.cs
--- core/Triggers/IntervalTrigger.cs	30 Sep 2005 17:46:06 -0000	1.5.2.1
+++ core/Triggers/IntervalTrigger.cs	18 Dec 2005 07:20:23 -0000
@@ -10,6 +10,7 @@
 	{

 		public const double DefaultIntervalSeconds = 60;

 		private readonly DateTimeProvider dateTimeProvider;

+        private string myName;
        private const string DefaultID = "IntervalTrigger";
 

 		private DateTime lastIntegrationCompleteTime;

 		private DateTime nextBuildTime;

@@ -43,11 +44,12 @@
 

 		public virtual BuildCondition ShouldRunIntegration()

 		{

+            myName = ID;
+            
 			TimeSpan timeSinceLastBuild = dateTimeProvider.Now - lastIntegrationCompleteTime;

 			if (timeSinceLastBuild.TotalSeconds < IntervalSeconds)

 				return BuildCondition.NoBuild;

 

 			return BuildCondition;

-		}

-	}

+		}

        [ReflectorProperty("ID", Required=false)]     
        public string ID = DefaultID;

 
        public string Name()
        {        
            return myName;        
        }

        }

 }
\ No newline at end of file
Index: core/Triggers/MultipleTrigger.cs
===================================================================
RCS file: /cvsroot/ccnet/ccnet/project/core/Triggers/MultipleTrigger.cs,v
retrieving revision 1.4
diff -u -w -b -r1.4 MultipleTrigger.cs
--- core/Triggers/MultipleTrigger.cs	4 Feb 2005 11:48:24 -0000	1.4
+++ core/Triggers/MultipleTrigger.cs	17 Dec 2005 20:02:10 -0000
@@ -6,7 +6,7 @@
 {

 	public class MultipleTrigger : ITrigger

 	{

-		private ITrigger[] triggers;

+		private ITrigger[] triggers;
        static string myName;
 

 		public MultipleTrigger(ITrigger[] triggers)

 		{

@@ -36,7 +36,7 @@
 				// Assumes ordering of elements of enum

 				BuildCondition condition = trigger.ShouldRunIntegration();

 				if (condition > overallCondition)

-				{

+				{
                    myName = trigger.Name();
 					overallCondition = condition;

 				}

 			}

@@ -64,6 +64,6 @@
 				return earliestDate;

 			}

 		}

-

+        public string Name()
        {        
            return myName;

        }


 	}

 }

Index: core/Triggers/ProjectTrigger.cs
===================================================================
RCS file: /cvsroot/ccnet/ccnet/project/core/Triggers/ProjectTrigger.cs,v
retrieving revision 1.2.2.2
diff -u -w -b -r1.2.2.2 ProjectTrigger.cs
--- core/Triggers/ProjectTrigger.cs	17 Oct 2005 14:38:34 -0000	1.2.2.2
+++ core/Triggers/ProjectTrigger.cs	17 Dec 2005 18:26:57 -0000
@@ -10,6 +10,7 @@
 	{
 		public const string DefaultServerUri = RemoteCruiseServer.DefaultUri;
 		private const int DefaultIntervalSeconds = 5;
+        private string myName;
 
 		private readonly IRemotingService remoteService;
 		private ProjectStatus lastStatus;
@@ -88,7 +89,11 @@
 			IntervalTrigger trigger = new IntervalTrigger();
 			trigger.IntervalSeconds = DefaultIntervalSeconds;
 			trigger.BuildCondition = BuildCondition.ForceBuild;
+            
 			return trigger;
 		}
+
+
+        public string Name()
        {        
            return myName;        
        }

 	}
 }
\ No newline at end of file
Index: core/Triggers/ScheduleTrigger.cs
===================================================================
RCS file: /cvsroot/ccnet/ccnet/project/core/Triggers/ScheduleTrigger.cs,v
retrieving revision 1.4
diff -u -w -b -r1.4 ScheduleTrigger.cs
--- core/Triggers/ScheduleTrigger.cs	4 Feb 2005 11:48:24 -0000	1.4
+++ core/Triggers/ScheduleTrigger.cs	17 Dec 2005 17:59:45 -0000
@@ -13,7 +13,7 @@
 		private DateTimeProvider dtProvider;

 		private TimeSpan integrationTime;

 		private DateTime nextIntegration;

-

+        private string myName;

 		public ScheduleTrigger() : this(new DateTimeProvider())

 		{

 		}

@@ -94,6 +94,7 @@
 				return BuildCondition;

 			}

 			return BuildCondition.NoBuild;

-		}

+		}

        public string Name()
        {        
            return myName;        
        }
+
 	}

 }
\ No newline at end of file
Index: core/IIntegratable.cs
===================================================================
RCS file: /cvsroot/ccnet/ccnet/project/core/IIntegratable.cs,v
retrieving revision 1.2
diff -u -w -b -r1.2 IIntegratable.cs
--- core/IIntegratable.cs	15 Jun 2005 02:20:10 -0000	1.2
+++ core/IIntegratable.cs	17 Dec 2005 19:19:32 -0000
@@ -10,5 +10,5 @@
 		/// <param name="buildCondition"></param>

 		/// <returns>The result of the integration, or null if no integration took place.</returns>

 		IIntegrationResult RunIntegration(BuildCondition buildCondition);

-	}

+        IIntegrationResult RunIntegration(BuildCondition buildCondition, string triggerID);

    }

 }
\ No newline at end of file
Index: core/IIntegrationResult.cs
===================================================================
RCS file: /cvsroot/ccnet/ccnet/project/core/IIntegrationResult.cs,v
retrieving revision 1.11
diff -u -w -b -r1.11 IIntegrationResult.cs
--- core/IIntegrationResult.cs	10 Sep 2005 23:05:18 -0000	1.11
+++ core/IIntegrationResult.cs	17 Dec 2005 18:40:33 -0000
@@ -38,5 +38,7 @@
 		string BaseFromArtifactsDirectory(string pathToBase);
 		string BaseFromWorkingDirectory(string pathToBase);
 		IDictionary IntegrationProperties { get; }
+
+        string TriggerID {get; set;}
 	}
 }
\ No newline at end of file
Index: core/IIntegrationResultManager.cs
===================================================================
RCS file: /cvsroot/ccnet/ccnet/project/core/IIntegrationResultManager.cs,v
retrieving revision 1.1
diff -u -w -b -r1.1 IIntegrationResultManager.cs
--- core/IIntegrationResultManager.cs	16 Mar 2005 02:28:52 -0000	1.1
+++ core/IIntegrationResultManager.cs	17 Dec 2005 19:16:31 -0000
@@ -7,6 +7,9 @@
 		IIntegrationResult LastIntegrationResult { get; }
 
 		IIntegrationResult StartNewIntegration(BuildCondition buildCondition);
+
+        IIntegrationResult StartNewIntegration(BuildCondition buildCondition, string theTriggerID);
+
 		void FinishIntegration();
 	}
 }
\ No newline at end of file
Index: core/IntegrationResult.cs
===================================================================
RCS file: /cvsroot/ccnet/ccnet/project/core/IntegrationResult.cs,v
retrieving revision 1.38
diff -u -w -b -r1.38 IntegrationResult.cs
--- core/IntegrationResult.cs	10 Sep 2005 23:05:18 -0000	1.38
+++ core/IntegrationResult.cs	17 Dec 2005 18:41:39 -0000
@@ -46,6 +46,13 @@
 			set { properties["CCNetProject"] = value; }
 		}
 
+        public string TriggerID
+        {
+            get { return Convert(properties["CCNetTriggerID"]); }
+            set { properties["CCNetTriggerID"] = value; }
+        }
+
+
 		public string ProjectUrl
 		{
 			get { return Convert(properties["CCNetProjectUrl"]); }
Index: core/IntegrationResultManager.cs
===================================================================
RCS file: /cvsroot/ccnet/ccnet/project/core/IntegrationResultManager.cs,v
retrieving revision 1.4
diff -u -w -b -r1.4 IntegrationResultManager.cs
--- core/IntegrationResultManager.cs	15 Jun 2005 02:20:10 -0000	1.4
+++ core/IntegrationResultManager.cs	18 Dec 2005 06:44:02 -0000
@@ -43,9 +43,25 @@
 			currentResult.ArtifactDirectory = project.ArtifactDirectory;
 			currentResult.ProjectUrl = project.WebURL;
 			currentResult.LastSuccessfulIntegrationLabel = LastIntegrationResult.LastSuccessfulIntegrationLabel;
+            currentResult.TriggerID = "Unknown"; //TODO rw get trigger id by caller
 			return currentResult;
 		}
 
+
+        public IIntegrationResult StartNewIntegration(BuildCondition buildCondition, string theTriggerID)
+        {
+            currentResult = new IntegrationResult(project.Name, project.WorkingDirectory);
+            currentResult.LastIntegrationStatus = LastIntegrationResult.Status;
+            currentResult.BuildCondition = DetermineBuildCondition(buildCondition);
+            currentResult.Label = project.Labeller.Generate(LastIntegrationResult);
+            currentResult.ArtifactDirectory = project.ArtifactDirectory;
+            currentResult.ProjectUrl = project.WebURL;
+            currentResult.LastSuccessfulIntegrationLabel = LastIntegrationResult.LastSuccessfulIntegrationLabel;
+            currentResult.TriggerID = theTriggerID; //TODO rw get trigger id by caller
+            return currentResult;
+        }
+
+
 		private BuildCondition DetermineBuildCondition(BuildCondition buildCondition)
 		{
 			if (LastIntegrationResult.IsInitial())
Index: core/IntegrationRunner.cs
===================================================================
RCS file: /cvsroot/ccnet/ccnet/project/core/IntegrationRunner.cs,v
retrieving revision 1.13
diff -u -w -b -r1.13 IntegrationRunner.cs
--- core/IntegrationRunner.cs	28 Sep 2005 18:43:20 -0000	1.13
+++ core/IntegrationRunner.cs	18 Dec 2005 06:46:43 -0000
@@ -49,6 +49,42 @@
 			return result;
 		}
 
+
+        public IIntegrationResult RunIntegration(BuildCondition buildCondition, string triggerID)
+        {
+            ThoughtWorks.CruiseControl.Core.Util.Log.Debug(string.Format("Triggered by {0}, condition {1}",  triggerID , buildCondition.ToString() ) );
+ 
+            IIntegrationResult result = resultManager.StartNewIntegration(buildCondition, triggerID);
+            IIntegrationResult lastResult = resultManager.LastIntegrationResult;
+ 
+            CreateDirectoryIfItDoesntExist(result.WorkingDirectory);
+            CreateDirectoryIfItDoesntExist(result.ArtifactDirectory);
+            result.MarkStartTime();
+            try
+            {
+                result.Modifications = GetModifications(lastResult, result);
+                if (result.ShouldRunBuild())
+                {
+                    target.Activity = ProjectActivity.Building;
+                    target.SourceControl.GetSource(result);
+                    RunBuild(result);
+                }
+            }
+            catch (Exception ex)
+            {
+                Log.Error(ex);
+                result.ExceptionResult = ex;
+            }
+            result.MarkEndTime();
+
+            PostBuild(result);
+
+            return result;
+        }
+
+        
+        
+        
 		private Modification[] GetModifications(IIntegrationResult from, IIntegrationResult to)
 		{
 			target.Activity = ProjectActivity.CheckingModifications;
Index: core/Project.cs
===================================================================
RCS file: /cvsroot/ccnet/ccnet/project/core/Project.cs,v
retrieving revision 1.61
diff -u -w -b -r1.61 Project.cs
--- core/Project.cs	28 Sep 2005 18:43:20 -0000	1.61
+++ core/Project.cs	18 Dec 2005 06:50:42 -0000
@@ -159,6 +159,17 @@
 			return integratable.RunIntegration(buildCondition);
 		}
 
+
+        public IIntegrationResult RunIntegration(BuildCondition buildCondition, string triggerID)
+        {
+            if (buildCondition == BuildCondition.ForceBuild)
+                Log.Debug("Build forced by " + triggerID);
+
+            return integratable.RunIntegration(buildCondition, triggerID);
+        }
+
+        
+        
 		public void Run(IIntegrationResult result)
 		{
 			IList tasksToRun = new ArrayList(tasks);
Index: core/ProjectIntegrator.cs
===================================================================
RCS file: /cvsroot/ccnet/ccnet/project/core/ProjectIntegrator.cs,v
retrieving revision 1.20
diff -u -w -b -r1.20 ProjectIntegrator.cs
--- core/ProjectIntegrator.cs	4 Feb 2005 11:48:23 -0000	1.20
+++ core/ProjectIntegrator.cs	17 Dec 2005 19:25:02 -0000
@@ -123,7 +123,7 @@
 			{
 				try
 				{
-					_integratable.RunIntegration(buildCondition);
+					_integratable.RunIntegration(buildCondition, _trigger.Name());
 				}
 				catch (Exception ex)
 				{
Index: core/Workflow.cs
===================================================================
RCS file: /cvsroot/ccnet/ccnet/project/core/Workflow.cs,v
retrieving revision 1.12
diff -u -w -b -r1.12 Workflow.cs
--- core/Workflow.cs	10 May 2005 10:50:25 -0000	1.12
+++ core/Workflow.cs	17 Dec 2005 19:24:08 -0000
@@ -54,6 +54,25 @@
 			return _currentIntegrationResult;
 		}
 
+        public IIntegrationResult RunIntegration(BuildCondition buildCondition, string triggerID)
+        {
+            _currentIntegrationResult = new WorkflowResult();
+
+            foreach (ITask task in Tasks)
+            {
+                try 
+                { 
+                    RunTask(task); 
+                }
+                catch (CruiseControlException ex) 
+                {
+                    _currentIntegrationResult.ExceptionResult = ex;
+                }
+            }
+            return _currentIntegrationResult;
+        }
+
+        
 		private void RunTask(ITask task)
 		{
 			task.Run(_currentIntegrationResult);
Index: Remote/ITrigger.cs
===================================================================
RCS file: /cvsroot/ccnet/ccnet/project/Remote/ITrigger.cs,v
retrieving revision 1.3
diff -u -w -b -r1.3 ITrigger.cs
--- Remote/ITrigger.cs	10 Jul 2005 02:48:04 -0000	1.3
+++ Remote/ITrigger.cs	18 Dec 2005 06:36:14 -0000
@@ -30,5 +30,10 @@
 		/// Returns the time of the next build.

 		/// </summary>

 		DateTime NextBuild { get; }

+
+        /// <summary>
+        /// Identifies the trigger which triggered the next build.
+        /// </summary>
+        string Name();
 	}

 }
\ No newline at end of file

***** CVS exited normally with code 1 *****

Hi Rob,

That settings screen was in dire need of tidying up, and the thoughts I 
had was to do exactly what you have done.  Great!

I'll hopefully have time early next week to download your stuff and give 
feedback.

Cheers
g


Rob Chartier wrote:

>I have been working on the new settings area for the CCTray app to include
>tabs and the X10 automation stuff.
>
>Here is a slide show of the screenshots so far.
>
>http://www.flickr.com/photos/chartier-family/sets/1544748/show/
>
>Other than the actual tabs themselves, the "Automation" tab is the only
>thing new.  
>
>The "All Off" checkbox would indicate that all other devices would be sent
>the TurnOff command first before the selected item would be sent to TurnOn.
>This seems awkward. I was also thinking about having the ability to set any
>number of X10 actions for each event.  
>
>For example...
> 
>	on Successful Turn On A1, Turn Off A2; 
>	on Fail Turn On A2, Turn Off A1.
>
>or
>	on Fixed Dim A1 up 50%, Turn Off A2; 
>	on successful Dim A1 up 10%
>	on Broken Dim A2 up 50%, Turn off A1;
>	on Still Failing Dim A2 up 10%
>
>
>I was contemplating adding an "Automatic" checkbox in the Audio settings to
>use Microsoft's Text to Speech engine to actually say the status of the
>build instead of choosing some random sound effect.  Of course the
>application wont require the Redist install of the Speech stuff but I can
>determine if it is installed or not, and if so then I will make the option
>available to the user.
>
>Let me know other config and/or layout options that you feel would be of
>benefit.
>
>
>Thanks
>
>-Rob Chartier
>
>
>
>
>-------------------------------------------------------
>This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
>for problems?  Stop!  Download the new AJAX search engine that makes
>searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
>http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
>_______________________________________________
>Ccnet-devel mailing list
>Ccn...@li...
>https://lists.sourceforge.net/lists/listinfo/ccnet-devel
>  
>

Grant,

That sounds great -- those are features that cctray has been severly 
missing.  I should get a chance to process your changes and include them 
in early next week.

Thanks,
Graham


Gra...@ba... wrote:

>I accept the ThoughtWorks contributor agreement. The zip file needs
>renaming.
> 
>As per my posting to ccnet-user please find attached some changed/new files
>for the CCTrayLib project. Apologies for them not being in "patch" format
>but couldn't get TortoiseCVS to manage that part too well...
>
>Changes to support the following:
>=================================
>- CCTray main window re-opening where the window last closed from.
>- CCTray main window remembering the sizing of the column widths.
>- Retains focus on selected line in listview when clicking "Force Build"
>button.
>- CCTray main window has full row selection making much easier to read.
>
>Notes:
>=======
>- PersistableWindowState could be re-used on other forms within CCTrayLib. I
>have just applied it to the MainForm.cs at this point since it's most
>frequently used.
>- Registry key location is hard-coded in the form
>"HookPersistentWindowState" method. If re-using across multiple forms would
>want to add another level of depth to the registry location and refactor out
>the constant.
>
>Grant.
>  
>

Mike Roberts wrote:

>-1 from me.
>
>Quiet Period should only be used if you are using a non-atomic
>sourcecontrol, and if you are there's no reason to try and build half
>way through a commit.
>
>Or maybe its Friday afternoon and I've missed the point. :)
>
>Mike
>
>  
>
And a -1 from me too -- agree with mike (it's not just a Friday 
afternoon thing...)

g

Hi,

I have made a very simple change in the BuildPublisher. What I needed
was to tell it to publish things directly inside the publishDir,
without creating subdirectories for each build. For that I added a new
boolean attribute called createDirectoryForEachBuild and tweaked the
Run() method. The default attribute's value is *true* for backward
compatibility. If you find it useful, feel free to commit it to the
repository. The changed file is attached.

Cheers,

C=E9lio Cidral Jr

ccnet devs,


Anyone want to test out my new build of the CCTray with X10 support,
including the UI for settings?  I want to gather feedback before I actually
submit it to Owen and Mike for CVS.  It is built with the current
"CruiseControl.NET-1.0.source".

Download: http://www.mscorlib.com/CCTrayWithX10.rar

Here is a screenshot of the Automation Tab in the Settings UI:

http://static.flickr.com/35/73602360_d9305384b4_o.jpg


I have not yet fully tested the CM17A (firecracker) interface; but I know
the code works just haven't been able to test it in this environment.  I
have a new one on order and it should be here anytime now.  


Features:
- Turn on or off X10 support all together

- Choose the COM Port
- Choose the X10 Device CM11A or CM17A

- Testing inline

- Ability to chain together a collection of X10 actions to:
	Successful, Fixed, Broken and Still Failing events

- Turn on or off the Time based Exclusions
	- Exclude on Weekends
	- Exclude by specific time of day
	- Exclude based on Sunrise/Sunset for your given longitude/latitude
		(default long/lat are for Vancouver BC, Canada)


Let me know your thoughts.

Thanks,

-Rob

I've also seen this problem: a transient source control access problem
results in a broken build staying that way.=20

A patch would definitely be nice!

=20
Leo


________________________________

	From: ccn...@li...
[mailto:ccn...@li...] On Behalf Of John
Morales
	Sent: Mittwoch, 14. Dezember 2005 15:50
	To: ccn...@li...
	Subject: [Ccnet-devel] "Exception" status problem while checking
for modifications.
=09
=09
	Hi guys, using cruise control i would get sporadic "exception"
statuses in my dashboard. Looking deeper into the error it seemed the
problem would occur due to the vault client timing out, for what ever
reason. Vault would timeout just sporadically, I patched cruisecontrol
to handle these problems from incompetent source control clients be just
retrying three times in the 'checkmodifications' method before bailing.=20
	Not sure if this is a problem for other people, but i just
wanted to know if the project would like the patch?
=09
=09

Hi guys, using cruise control i would get sporadic "exception" statuses in
my dashboard. Looking deeper into the error it seemed the problem would
occur due to the vault client timing out, for what ever reason. Vault would
timeout just sporadically, I patched cruisecontrol to handle these problems
from incompetent source control clients be just retrying three times in the
'checkmodifications' method before bailing.
Not sure if this is a problem for other people, but i just wanted to know i=
f
the project would like the patch?

Hi Owen,

> > In my local 1.0 tree, none of the source control providers 
> > do this. I 
> > suspected there was a reason for VSS's workingDirectory not being 
> > based from the project working dir, but now I'm not so sure...
> >
> > Has this been fixed recently? I'm not sure how up-to-date 
> > my local CVS 
> > copy is, I've had trouble accessing the SF CVS lately.
> 
> this was fixed at some point prior to the 1.0 release.  you 
> should be able to use relative paths with vss (and many other 
> providers). 

After a cvs -update this is indeed included. It must've been a while since I
managed to get the latest...

It worked fine for me during the demo -- I managed to sell CC.NET to at
least one new user yesterday ;-)

Thanks,
- Kim

Right now its just all mockup other than the existing X10 code.

=20

-----Original Message-----
From: ccn...@li...
[mailto:ccn...@li...] On Behalf Of Owen =
Rogers
Sent: Monday, December 12, 2005 7:46 AM
To: ccn...@li...
Subject: Re: [Ccnet-devel] CCTray Settings - Screenshots

hi rob,

On 09/12/05, Rob Chartier <rob...@gm...> wrote:
> I have been working on the new settings area for the CCTray app to=20
> include tabs and the X10 automation stuff.
>
> Here is a slide show of the screenshots so far.

looks good -- though i have to admit that i'm not to sure what should go =
on
the x10 tab.  just so that i'm clear: are these just ui mockups?
 or is there actual code behind them?
cheers,
owen.

--
Owen Rogers | http://dotnetjunkies.com/weblog/exortech | =
CruiseControl.NET -
http://ccnet.thoughtworks.com


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log =
files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37&alloc_id=16865&op=3Dick
_______________________________________________
Ccnet-devel mailing list
Ccn...@li...
https://lists.sourceforge.net/lists/listinfo/ccnet-devel

hi kim,

On 12/12/05, Kim Gr=E4sman <ki...@mv...> wrote:
> In my local 1.0 tree, none of the source control providers do this. I
> suspected there was a reason for VSS's workingDirectory not being based
> from the project working dir, but now I'm not so sure...
>
> Has this been fixed recently? I'm not sure how up-to-date my local CVS
> copy is, I've had trouble accessing the SF CVS lately.

this was fixed at some point prior to the 1.0 release.  you should be
able to use relative paths with vss (and many other providers).
cheers,
owen.
--
Owen Rogers | http://dotnetjunkies.com/weblog/exortech |
CruiseControl.NET - http://ccnet.thoughtworks.com

Hi Owen,

I've been meaning to ask you about this, and now that you mention it...

 > 1) we should add support to rebase the working directory so that you
 > can specify relative paths for the provider.  translating what this
 > means for a sec: a user can specify a working directory at the
 > project-level in their ccnet.config file.  this is generally the only
 > absolute path that ccnet needs -- everything else can be defined
 > relative to it.  to take advantage of this, we need to use a function
 > on the integration result called BaseFromWorkingDirectory.

In my local 1.0 tree, none of the source control providers do this. I 
suspected there was a reason for VSS's workingDirectory not being based 
from the project working dir, but now I'm not so sure...

Has this been fixed recently? I'm not sure how up-to-date my local CVS 
copy is, I've had trouble accessing the SF CVS lately.

Thanks,
- Kim

hi francis,

On 28/11/05, Owen Rogers <exo...@gm...> wrote:
> On 28/11/05, Francis Tremblay <fra...@gm...> wrote:
> > This patch.txt is filled with :
> > - Alienbrain.cs and AlienbrainHistoryParser.cs to support Alienbrain
> > (tested on version 7)
> > - Alienbraintest.cs and AlienbrainHistoryParser.cs unit tests
> > - Fixes to support filters
> >
> > Also, here's the updated documentation

i've just finished integrating your changes into cvs and they should
be included as part of build 1.1.0.2129.  the documentation is up
here:
confluence.public.thoughtworks.org/display/CCNET/Alienbrain+Source+Control+=
Block
thanks again for your contribution.

a few small comments on the source:
1) we should add support to rebase the working directory so that you
can specify relative paths for the provider.  translating what this
means for a sec: a user can specify a working directory at the
project-level in their ccnet.config file.  this is generally the only
absolute path that ccnet needs -- everything else can be defined
relative to it.  to take advantage of this, we need to use a function
on the integration result called BaseFromWorkingDirectory.
2) i would encourage including explicit command-line argument strings
in the unit tests.  the reasons are two-fold: i) the unit tests server
as documentation for the code, and it's much easier to read explicit
strings than building them using string.format; ii) it is important
that the tests do not reuse functionality in the code under test --
otherwise, what are we really testing?

anyway, thanks again for your hard work on this.  i expect that you'll
start getting some questions as soon as people start using the new
provider.
cheers,
owen.
--
Owen Rogers | http://dotnetjunkies.com/weblog/exortech |
CruiseControl.NET - http://ccnet.thoughtworks.com

hi rob,

On 09/12/05, Rob Chartier <rob...@gm...> wrote:
> I have been working on the new settings area for the CCTray app to includ=
e
> tabs and the X10 automation stuff.
>
> Here is a slide show of the screenshots so far.

looks good -- though i have to admit that i'm not to sure what should
go on the x10 tab.  just so that i'm clear: are these just ui mockups?
 or is there actual code behind them?
cheers,
owen.

--
Owen Rogers | http://dotnetjunkies.com/weblog/exortech |
CruiseControl.NET - http://ccnet.thoughtworks.com