ccnet-devel Mailing List for CruiseControl.NET

Hi all,

I am using ccnet since version 0.1 and now I wanted to update to the latest
version.

A few issues:

- Because my solution has a couple of projects in c++ I had to use the the
latest nant,
  because the one provided by ccnet doesn't include the cl task.

  Q: Would be possible to add the other nant dlls to the ccnet project?

- Using the latest nant, ccnet was producing an error because was not able
to find
  Sourceforge.Core.XmlLogger. Finally I found how to solve adding an option
to the ccnet config file

	<buildArgs>-logger:NAnt.Core.XmlLogger</buildArgs>

  Q: Why the name of the default logger is different?

- But the log file that I have is like:

<task name="call">
          <target name="build-windows">
            <task name="csc">
              <message><![CDATA[Compiling 40 files to
D:\builds\continuousIntegration\dante\Dante\build\com.slb.ofs.wcp.ap.dante.w
indows.dll.]]></message>

<message><![CDATA[D:\builds\continuousIntegration\dante\Dante\Windows\contro
ls\Plot2DControl.cs(510,5): warning CS0168: The variable 'e' is declared but
never used]]></message>

<message><![CDATA[D:\builds\continuousIntegration\dante\Dante\Windows\contro
ls\SlideController.cs(195,44): warning CS0649: Field
'com.slb.ofs.wcp.ap.dante.windows.controls.SlideController.components' is
never assigned to, and will always have its default value null]]></message>

<message><![CDATA[D:\builds\continuousIntegration\dante\Dante\Windows\contro
ls\UnitTextBox.cs(34,33): warning CS0067: The event
'com.slb.ofs.wcp.ap.dante.windows.controls.UnitTextBox.OnReturnKeyPressed'
is never used]]></message>
            </task>

	when there are no errors, and like :

          </target>
        </task>
        <task name="call">
          <target name="build-thelma">
            <task name="csc">
              <message><![CDATA[Compiling 51 files to
D:\builds\continuousIntegration\dante\Dante\build\com.slb.ofs.wcp.ap.dante.t
helma.exe.]]></message>

<message><![CDATA[D:\builds\continuousIntegration\dante\Dante\Thelma\MainWin
dow.cs(9,7): error CS0246: The type or namespace name 'ThelmaModel' could
not be found (are you missing a using directive or an assembly
reference?)]]></message>

<message><![CDATA[D:\builds\continuousIntegration\dante\Dante\Thelma\StudyMa
in.cs(122,11): error CS0104: 'GotoSlideCommand' is an ambiguous
reference]]></message>

<message><![CDATA[D:\builds\continuousIntegration\dante\Dante\build\com.slb.
ofs.wcp.ap.dante.windows.dll: (Location of symbol related to previous
error)]]></message>

<message><![CDATA[D:\builds\continuousIntegration\dante\Dante\Thelma\MainWin
dow.cs(44,11): error CS0246: The type or namespace name 'PlotViewer' could
not be found (are you missing a using directive or an assembly
reference?)]]></message>
            </task>
          </target>
        </task>

	when there is an error. But with this log file the xsl file doesn't detect
the errors produced and doesn't print the result of the compilation.
	Q: Any suggestions?

Thanx.

Jesus Arevalo

I've copied Mike Two's Sys Tray monitoring app into the main solution. 
Actually its a slightly cut down version since for where I am we want to 
roll it out to all dev machines (and the ability for any developer to 
shut down the CC server from their own machine is probably a bad thing 
in this scenario)

There's a 'dist.cctray' target that puts the tray app into a zip file 
that you can extract and run 'as is' after editting the config file for 
the location of your server.

I'm thinking perhaps remoting should be turned on by default for the 
main app - can anyone think of a reason we shouldn't do this? (It can 
always be turned off using a '-remoting:off' startup flag)

I also had a problem with the VS project file for 'core' - it didn't 
build unless I set 'copy local' to true for the nunit reference. I've 
checked this in too.

Mike

+1 on integrationPeriod.  
 
Don
 



  _____  

From: DN...@th... [mailto:DN...@th...] 
Sent: Thursday, May 29, 2003 4:09 AM
To: mi...@th...
Cc: ccn...@li...; ccn...@li...



>> I've never been a big fan of using the word timeout for that. It 
>> strongly conflicts with the concept of buildTimeout for example. 
>
> Perhaps 'frequency' would be better?

How about buildPeriodSeconds, or minimumBuildPeriodSeconds.  Perhaps *integrationPeriod*, as it's the period between integration passes.

>> I've never been a big fan of using the word timeout for that. It 
>> strongly conflicts with the concept of buildTimeout for example. 
>
> Perhaps 'frequency' would be better?

How about buildPeriodSeconds, or minimumBuildPeriodSeconds.  Perhaps 
*integrationPeriod*, as it's the period between integration passes.

> How about 'requiredQuietTime' ? I also think this should be a 
> sourcecontrol property, since it is not required for Source Control 
> Systems with atomic checkin (e.g. Perforce)

I think moving the modification delay attribute to source control would be 
bad. If we move the attribute we also have to move the code that does 
something with it. Otherwise you just end up with the same problem. 
Currently there is a method on project called ShouldRunIntegration. Part 
of the answer to that question lies in the modification delay code. If we 
move modification delay to source control we now have to move all of that 
logic to source control. It would be easy enough to move the question 
"Should I Build" to source control and have a base class for non atomic 
systems check modification delay. BUT part of the functionality is that if 
the modification delay is 5 minutes and a check in happened two minutes 
ago the project will sleep for three minutes. It is critical (in my mind 
at least) that we only sleep long enough to cross the modification delay 
threshold. I don't want a project with a 30 minute delay between builds 
sleeping another 30 minutes because someone checked in 4 minutes ago. I 
want it to wait 1 minute. Since the modification delay feature changes the 
sleep time (and thus now the schedule) it can't be an "only for this type 
of source control" feature. It is fine to omit the element for your 
project and let the default of zero be used. In this case the modification 
delay is never checked.

I do think the code needs some refactoring but I really don't think you 
can put it on source control. It really is part of project.

In the "not in the near future but still something to consider" catagory 
we might be allowing two source control checks per project. I ran into 
this at a client. They had a set of common framework components shared 
between multiple projects and the stuff for this project only. They wanted 
to build if either changed. They way their source control system was set 
up life would have been much easier if we could have treated them as two 
independent checks. I would not want different modification delay checks 
on the two systems. It doesn't make sense to me.


Mike Two; Putting the tWo in Thoughrks




Mike Roberts <mi...@th...>
Sent by: ccn...@li...
05/28/2003 06:00 PM

 
        To:     ccn...@li...
        cc: 
        Subject:        Re: [Ccnet-devel] Time related configuration


mc...@th... wrote:

> only sleeptime has been deprecated. It is replaced by the schedule 
> timeout attribute 


OK - I'll look into where that still exists in the code

> I've never been a big fan of using the word timeout for that. It 
> strongly conflicts with the concept of buildTimeout for example. 


Perhaps 'frequency' would be better?

> buildTimeout in the <build> element is literrally a timeout. If the 
> nant build takes longer than that it is killed (and the xml ends up 
> being crap and won't display so be careful) 


Yep - I like the name of that too and think should probably stay as is.

> the timeout attribute on schedule is the time to sleep between builds 
> or modification checks. I originally changed the timeout element on 
> project to sleepTime but I never liked that word either. At least it 
> was different from timeout


(discussed above, I think)

> modificationDelay (another bad name I came up with) is the minimum 
> allowed time between the last check in and the start of the build. So 
> if I set it at 1 minute and see a check in 30 seconds before the build 
> started I assume someone is still checking in and sleep for 30 seconds 
> (just long enough to meet the modification delay requirement).


How about 'requiredQuietTime' ? I also think this should be a 
sourcecontrol property, since it is not required for Source Control 
Systems with atomic checkin (e.g. Perforce)

Mike




-------------------------------------------------------
This SF.net email is sponsored by: eBay
Get office equipment for less on eBay!
http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5
_______________________________________________
Ccnet-devel mailing list
Ccn...@li...
https://lists.sourceforge.net/lists/listinfo/ccnet-devel

mc...@th... wrote:

> only sleeptime has been deprecated. It is replaced by the schedule 
> timeout attribute 


OK - I'll look into where that still exists in the code

> I've never been a big fan of using the word timeout for that. It 
> strongly conflicts with the concept of buildTimeout for example. 


Perhaps 'frequency' would be better?

> buildTimeout in the <build> element is literrally a timeout. If the 
> nant build takes longer than that it is killed (and the xml ends up 
> being crap and won't display so be careful) 


Yep - I like the name of that too and think should probably stay as is.

> the timeout attribute on schedule is the time to sleep between builds 
> or modification checks. I originally changed the timeout element on 
> project to sleepTime but I never liked that word either. At least it 
> was different from timeout


(discussed above, I think)

> modificationDelay (another bad name I came up with) is the minimum 
> allowed time between the last check in and the start of the build. So 
> if I set it at 1 minute and see a check in 30 seconds before the build 
> started I assume someone is still checking in and sleep for 30 seconds 
> (just long enough to meet the modification delay requirement).


How about 'requiredQuietTime' ? I also think this should be a 
sourcecontrol property, since it is not required for Source Control 
Systems with atomic checkin (e.g. Perforce)

Mike

only sleeptime has been deprecated. It is replaced by the schedule timeout 
attribute

I've never been a big fan of using the word timeout for that. It strongly 
conflicts with the concept of buildTimeout for example.

buildTimeout in the <build> element is literrally a timeout. If the nant 
build takes longer than that it is killed (and the xml ends up being crap 
and won't display so be careful)

the timeout attribute on schedule is the time to sleep between builds or 
modification checks. I originally changed the timeout element on project 
to sleepTime but I never liked that word either. At least it was different 
from timeout.

modificationDelay (another bad name I came up with) is the minimum allowed 
time between the last check in and the start of the build. So if I set it 
at 1 minute and see a check in 30 seconds before the build started I 
assume someone is still checking in and sleep for 30 seconds (just long 
enough to meet the modification delay requirement).

Mike Two; Putting the tWo in Thoughrks




Mike Roberts <mi...@th...>
Sent by: ccn...@li...
05/28/2003 05:33 PM

 
        To:     ccn...@li...
        cc: 
        Subject:        [Ccnet-devel] Time related configuration


I'm guessing Owen's going to answer this one. :)

In a config file I'm looking at I currently have 4 time-related items of 
configuration (This is all against latest CVS):

<cruisecontrol>
  <project ...>
    <build type="nant">
       ...
      <buildTimeout>300000</buildTimeout>
    </build>
    ...
    <modificationDelay>5000</modificationDelay>
    <schedule type="schedule" timeout="300000"/>
    <sleepTime>300000</sleepTime>
  </project>
</cruisecontrol>

So which of these are mandatory? Which are optional? Which are 
deprecated? (if any)

If sleepTime and modificationDelay are deprecated my suggestion is we 
take them out of the code and documentation - we are still in beta so 
should not be too concerned about maintaining backwards compatiblity 
over ease of use.

Cheers,
Mike



-------------------------------------------------------
This SF.net email is sponsored by: eBay
Get office equipment for less on eBay!
http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5
_______________________________________________
Ccnet-devel mailing list
Ccn...@li...
https://lists.sourceforge.net/lists/listinfo/ccnet-devel

I'm guessing Owen's going to answer this one. :)

In a config file I'm looking at I currently have 4 time-related items of 
configuration (This is all against latest CVS):

<cruisecontrol>
  <project ...>
    <build type="nant">
       ...
      <buildTimeout>300000</buildTimeout>
    </build>
    ...
    <modificationDelay>5000</modificationDelay>
    <schedule type="schedule" timeout="300000"/>
    <sleepTime>300000</sleepTime>
  </project>
</cruisecontrol>

So which of these are mandatory? Which are optional? Which are 
deprecated? (if any)

If sleepTime and modificationDelay are deprecated my suggestion is we 
take them out of the code and documentation - we are still in beta so 
should not be too concerned about maintaining backwards compatiblity 
over ease of use.

Cheers,
Mike

Mike Roberts wrote:

> I checked in few things on the webapp side of things. The 'deploy' 
> target now creates a subfolder with a deployed version of the webapp, 
> and uses NantContrib's IIS automation task to setup a virtual 
> directory on your machine called 'ccnetdev' (the IIS stuff was already 
> there, but NantContrib's dll wasn't checked in). So if you do a 'build 
> deploy', you can point IE at http://localhost/ccnetdev/ to see the web 
> app.


Just a quick note - I tried the <mkiisdir> task with IIS 6 / Windows 
Server 2003 today and it fails, so I think this will only work with 
Windows 2000 / XP.

Mike

Hi folks, 2 things...

Currently, http://www.continuousintegration.org/ is hosted on a box 
owned by Joe Walnes ( a friend of the project ). We're moving this to a 
ThoughtWorks hosted machine - http://ccnet.thoughtworks.com/ now hosts 
the latest version of the website (which itself is checked into source 
control in the 'website' module), and Owen will be updating the DNS 
entry for continuousintegration.org to point here too (so both URLs will 
point to the same site). The website documentation itself could do with 
some updating, but that's another thing entirely. :)

I'm going to be setting up CruiseControl.NET instances (on one of 
ThoughtWorks' internal .NET machines) to automatically update the 
website when changes are made to the website module, and also to push up 
distributions whenever a good build happens (we don't currently have a 
publically accessable .NET server, so we can't have a publically 
viewable CCNet webapp at this time)

... and the next thing ...

I checked in few things on the webapp side of things. The 'deploy' 
target now creates a subfolder with a deployed version of the webapp, 
and uses NantContrib's IIS automation task to setup a virtual directory 
on your machine called 'ccnetdev' (the IIS stuff was already there, but 
NantContrib's dll wasn't checked in). So if you do a 'build deploy', you 
can point IE at http://localhost/ccnetdev/ to see the web app.

To get this working out-of-the-box, I needed to update the webapp to 
allow relative paths for the log directory (which is useful in its own 
right, I think).

I also added a tiny hack to allow the contents of an arbitrary file to 
be included on the latest page - check out the web.config if you're 
interested.

Mike - 'enjoying' the Boston rain ;)

Hi all,

There was a problem with the 0.3 MSI's (thanks Don!). I've created new 
0.3.1 installers based on CVS as of today, and they're up in the file 
release area. I deleted the 0.3 release since it was bad.

Cheers,

Mike

actually, it may not just be you.  i haven't taken a look at the release
yet myself, but this is the first time releasing with new vs2003 installer
projects.
i don't have vs2003 installed, so i can't test it.  hopefully mike will
take a look at the msi's later today.  mike?
o.


---
R. Owen Rogers
ThoughtWorks Ltd
Peek House
20, Eastcheap
London EC3M 1EB
tel:        +44 (0) 207 090 7400
mobile:  +44 (0) 787 673 8898



|---------+---------------------------->
|         |           "Browning, Don"  |
|         |           <Don.Browning@tur|
|         |           ner.com>         |
|         |                            |
|         |           05/23/2003 03:16 |
|         |           PM               |
|---------+---------------------------->
  >------------------------------------------------------------------------------------------------------------------------------|
  |                                                                                                                              |
  |       To:       "'OR...@th...'" <OR...@th...>                                                      |
  |       cc:       "'ccn...@li...'" <ccn...@li...>                                    |
  |       Subject:  RE: [Ccnet-devel] Unable to run 0.3 install packages                                                         |
  >------------------------------------------------------------------------------------------------------------------------------|




 Hmmm... That's strange.  I trying to use them on a win2k3 box with vs.net
1.1 installed.  Now that I know its just me, I'll pound on it for a little
while and see if I can figure out whats going on...


I'll  let everyone know when I fix it...


Don





>
> -----Original Message-----
> From: OR...@th... [mailto:OR...@th...]
> Sent: Friday, May 23, 2003 10:12 AM
> To: Don...@tu...
> Cc: 'ccn...@li...';
> ccn...@li...
>
> the msi's were build with vs2003 and compiled for .net 1.1.
> do you have
> 1.1 installed?
> we are currently working on a version that is compatible with 1.0.
> cheers,
> owen.
>
>
> ---
> R. Owen Rogers
> ThoughtWorks Ltd
> Peek House
> 20, Eastcheap
> London EC3M 1EB
> tel:        +44 (0) 207 090 7400
> mobile:  +44 (0) 787 673 8898
>
>
>
> |---------+--------------------------------------->
> |         |           "Browning, Don"             |
> |         |           <Don...@tu...>   |
> |         |           Sent by:                    |
> |         |           ccn...@li...|
> |         |           ceforge.net                 |
> |         |                                       |
> |         |                                       |
> |         |           05/23/2003 03:05 PM         |
> |---------+--------------------------------------->
>
> >-------------------------------------------------------------
> -------------------------------------------------------------------|
>   |
>                                                                      |
>   |       To:       "'ccn...@li...'"
> <ccn...@li...>
>            |
>   |       cc:
>                                                                      |
>   |       Subject:  [Ccnet-devel] Unable to run 0.3 install
> packages
>          |
>
> >-------------------------------------------------------------
> -------------------------------------------------------------------|
>
>
>
>
> Whenever I attempt to run the 0.3 install packages I get the following
> error:
>
> "The installation package could not be opened.  Contact the
> vendor to ensure it is a valid windows installer package"
>
> Are these .msi's working for everyone else?
>
> Don
>
>

 Hmmm... That's strange.  I trying to use them on a win2k3 box with vs.net 1.1 installed.  Now that I know its just me, I'll pound on it for a little while and see if I can figure out whats going on...

I'll  let everyone know when I fix it...

Don


> 
> -----Original Message-----
> From: OR...@th... [mailto:OR...@th...] 
> Sent: Friday, May 23, 2003 10:12 AM
> To: Don...@tu...
> Cc: 'ccn...@li...'; 
> ccn...@li...
>
> the msi's were build with vs2003 and compiled for .net 1.1.  
> do you have
> 1.1 installed?
> we are currently working on a version that is compatible with 1.0.
> cheers,
> owen.
> 
> 
> ---
> R. Owen Rogers
> ThoughtWorks Ltd
> Peek House
> 20, Eastcheap
> London EC3M 1EB
> tel:        +44 (0) 207 090 7400
> mobile:  +44 (0) 787 673 8898
> 
> 
> 
> |---------+--------------------------------------->
> |         |           "Browning, Don"             |
> |         |           <Don...@tu...>   |
> |         |           Sent by:                    |
> |         |           ccn...@li...|
> |         |           ceforge.net                 |
> |         |                                       |
> |         |                                       |
> |         |           05/23/2003 03:05 PM         |
> |---------+--------------------------------------->
>   
> >-------------------------------------------------------------
> -------------------------------------------------------------------|
>   |                                                           
>                                                                      |
>   |       To:       "'ccn...@li...'" 
> <ccn...@li...>                           
>            |
>   |       cc:                                                 
>                                                                      |
>   |       Subject:  [Ccnet-devel] Unable to run 0.3 install 
> packages                                                      
>          |
>   
> >-------------------------------------------------------------
> -------------------------------------------------------------------|
> 
> 
> 
> 
> Whenever I attempt to run the 0.3 install packages I get the following
> error:
> 
> "The installation package could not be opened.  Contact the 
> vendor to ensure it is a valid windows installer package"
> 
> Are these .msi's working for everyone else?
> 
> Don
> 
> 

the msi's were build with vs2003 and compiled for .net 1.1.  do you have
1.1 installed?
we are currently working on a version that is compatible with 1.0.
cheers,
owen.


---
R. Owen Rogers
ThoughtWorks Ltd
Peek House
20, Eastcheap
London EC3M 1EB
tel:        +44 (0) 207 090 7400
mobile:  +44 (0) 787 673 8898



|---------+--------------------------------------->
|         |           "Browning, Don"             |
|         |           <Don...@tu...>   |
|         |           Sent by:                    |
|         |           ccn...@li...|
|         |           ceforge.net                 |
|         |                                       |
|         |                                       |
|         |           05/23/2003 03:05 PM         |
|---------+--------------------------------------->
  >--------------------------------------------------------------------------------------------------------------------------------|
  |                                                                                                                                |
  |       To:       "'ccn...@li...'" <ccn...@li...>                                      |
  |       cc:                                                                                                                      |
  |       Subject:  [Ccnet-devel] Unable to run 0.3 install packages                                                               |
  >--------------------------------------------------------------------------------------------------------------------------------|




Whenever I attempt to run the 0.3 install packages I get the following
error:

"The installation package could not be opened.  Contact the vendor to
ensure it is a valid windows installer package"

Are these .msi's working for everyone else?

Don

Whenever I attempt to run the 0.3 install packages I get the following error:
 
"The installation package could not be opened.  Contact the vendor to ensure it is a valid windows installer package"
 
Are these .msi's working for everyone else?
 
Don
 

the source for ccnet web site is now checked into the CVS repository on
SourceForge.  it is in a new root module called: website.
cheers,
owen.


---
R. Owen Rogers
ThoughtWorks Ltd
Peek House
20, Eastcheap
London EC3M 1EB
tel:        +44 (0) 207 090 7400
mobile:  +44 (0) 787 673 8898

Hey Owen,

> the ControlPanel project looks great!
> a few questions:
> 1) this seems to overlap with CCTray.  will these
> two tools be merged?

I would think so, in addition to whatever ControlPanel
does/controls, it should also have that nice
green/red/gray icon on the taskbar to show current
build status.  However, it may be that we want CCTray
to be on all developers machines and ControlPanel to
only be on the build machine.  Opinions?

> 2) will it be possible to launch the ControlPanel in
> a way that doesn't
> require loading to the system tray?  it would be
> great to have a
> command-line or at least WinForm app interface for
> this.

I don't see why.  The control panel is a winform app. 
We can change the behavior of close to actually close
it as opposed to just minimizing it, while minimizing
it would leave it in the system tray if people think
that's a good idea.

> 3) i'm currently working on a tool to run builds on
> demand.  it is just
> going to provide a simple command-line interface. 
> it would be great to
> merge this into the control panel.  what do you
> reckon is the best way
> forward: for me to continue to build it as a
> separate project and then
> merge it in afterwards, or merge it in now and hope
> that we don't step on
> each other's toes too much.

I'd say yes, except that it might be easier to do this
after the fact.  But feel free to start it.

Jeremy

__________________________________
Do you Yahoo!?
The New Yahoo! Search - Faster. Easier. Bingo.
http://search.yahoo.com

don,
thanks for putting together this list.  it's good to have.  i'd just
produced something similar after doing a number of clean installs of ccnet.
in regards to your issues:
1. relative paths should work fine with the cvs <executable> element.
could you send an example (or, better, a test) of what you were trying, so
we can see what was going on.
2. the readme.html needs to be updated again -- thanks for that.  the
installation process should be easier with 0.3 release.
4. includeDetails attribute is now optional and the default value is
'false'.  you can find detials about the available xml tags for the ccnet
configuration file by checking the ccnet.config.html file in the docs
folder (though this might not be included in the distribution).  also,
there is some information on the web site
(http://continuousintegration.net/?page=tasks.html) about this too.

cheers,
owen.

---
R. Owen Rogers
ThoughtWorks Ltd
Peek House
20, Eastcheap
London EC3M 1EB
tel:        +44 (0) 207 090 7400
mobile:  +44 (0) 787 673 8898



|---------+---------------------------->
|         |           "Browning, Don"  |
|         |           <Don.Browning@tur|
|         |           ner.com>         |
|         |                            |
|         |           05/16/2003 08:58 |
|         |           PM               |
|---------+---------------------------->
  >------------------------------------------------------------------------------------------------------------------------------|
  |                                                                                                                              |
  |       To:       "'OR...@th...'" <OR...@th...>, "Browning, Don" <Don...@tu...>           |
  |       cc:       "'ccn...@li...'" <ccn...@li...>                                    |
  |       Subject:  RE: [Ccnet-devel] Problems with the web interface                                                            |
  >------------------------------------------------------------------------------------------------------------------------------|




Thanks... That fixed the problem.  Glad to hear another drop is on the way.
Since you guys are in the process of putting together a new release, I'll
mention some of the hurdles I jumped through to get the 0.2.1 build to
install.


1. I had to modify the <executable> element value to point at the absolute
path to ccnet's cvs exe.  The relative path blew chunks.


2. I had to manually modify the <history historyDir=""> value.  The readme
doesn't mention it.
3. The aforementioned .xsl bug, which you fixed for me.
4. Some information of the <email> element was left off.  The readme
doesn't tell you to set the from, mailhost, or includeDetails attributes
(though it should be self-explainatory).


Other than that, all went well.  Currently, the build process seems to be
working fine, and while the ccnet web interface now works, it shows the
build results but if you click on an individual build all the details are
empty.  Also, I'm not getting any emails, not sure why b/c nothing seems to
be blowing an error.


Just wanted to drop this info your way.  Great work guys, I look forward to
the next drop!


Don





>
> -----Original Message-----
> From: OR...@th... [mailto:OR...@th...]
> Sent: Friday, May 16, 2003 3:30 PM
> To: Don...@tu...
> Cc: 'ccn...@li...'
>
>
>
>
>
> hi don,
> there is a bug in the xsl for the distributables.xsl file.
>
>
> (See attached file: distributables.xsl)
> we are in the process of putting together a new release which
> should be ready middle of next week.
> cheers,
> owen.
>
> ---
> R. Owen Rogers
> ThoughtWorks Ltd
> Peek House
> 20, Eastcheap
> London EC3M 1EB
> tel:        +44 (0) 207 090 7400
> mobile:  +44 (0) 787 673 8898
>
>
>
> |---------+--------------------------------------->
> |         |           "Browning, Don"             |
> |         |           <Don...@tu...>   |
> |         |           Sent by:                    |
> |         |           ccn...@li...|
> |         |           ceforge.net                 |
> |         |                                       |
> |         |                                       |
> |         |           05/16/2003 08:18 PM         |
> |---------+--------------------------------------->
>
> >-------------------------------------------------------------
> -----------------------------------------------------------------|
>   |
>                                                                    |
>   |       To:       "'ccn...@li...'"
> <ccn...@li...>
>          |
>   |       cc:
>                                                                    |
>   |       Subject:  [Ccnet-devel] Problems with the web
> interface
>            |
>
> >-------------------------------------------------------------
> -----------------------------------------------------------------|
>
>
>
>
> Hey guys!
>
> Well, I installed the cc.net server piece and managed to get
> it up and running with minimal effort (good job!), but I have
> a question on the web interface.
>
> I installed the web interface to the following location:
> C:\Projects\trip\build\ccnet
>
> Which maps to the following vroot:
> http://indiana/trip/ccnet
>
> When I attempt to access the url, I get the following
> exception
> 'task[attribute::name='War']message[attribute::priority='info'
> ]' has an invalid token
>
> Has anyone else seen this?  I'm currently running this on a
> Win2K3 box with the following runtime info:
> Microsoft .NET Framework Version:1.1.4322.342; ASP.NET
> Version:1.1.4322.342
>
> Any help would be appriciated...
>
> Don
>

hey jeremy,
the ControlPanel project looks great!
a few questions:
1) this seems to overlap with CCTray.  will these two tools be merged?
2) will it be possible to launch the ControlPanel in a way that doesn't
require loading to the system tray?  it would be great to have a
command-line or at least WinForm app interface for this.
3) i'm currently working on a tool to run builds on demand.  it is just
going to provide a simple command-line interface.  it would be great to
merge this into the control panel.  what do you reckon is the best way
forward: for me to continue to build it as a separate project and then
merge it in afterwards, or merge it in now and hope that we don't step on
each other's toes too much.
cheers,
owen.


---
R. Owen Rogers
ThoughtWorks Ltd
Peek House
20, Eastcheap
London EC3M 1EB
tel:        +44 (0) 207 090 7400
mobile:  +44 (0) 787 673 8898



|---------+--------------------------------------->
|         |           Jeremy Stell-Smith          |
|         |           <ste...@ya...>        |
|         |           Sent by:                    |
|         |           ccn...@li...|
|         |           ceforge.net                 |
|         |                                       |
|         |                                       |
|         |           05/19/2003 03:20 AM         |
|---------+--------------------------------------->
  >------------------------------------------------------------------------------------------------------------------------------|
  |                                                                                                                              |
  |       To:       ccnet <ccn...@li...>                                                                    |
  |       cc:                                                                                                                    |
  |       Subject:  [Ccnet-devel] Control Panel Project                                                                          |
  >------------------------------------------------------------------------------------------------------------------------------|




I just checked in a new project dir called
controlpanel into ccnet.  It's a gui that lives in the
system tray that let's you
start/stop/monitor/configure cc.net.

First page is the start/stop/monitor status, and
eventually install?  It's connected, but is showing
some bugs in the remoting interface w/ status and
stopping of cc.

Second page is for configuring cruise, eventually I'd
like to see some kind of a gui or something, but as a
first step, I'm going to try to just have the xml that
the service is looking at along w/ a load/save for it.

Additional features we could add are a console output
listener and multi project support.

The idea of all of this is to make cc.net very easy
and ms developer friendly.  The metaphor I'm thinking
of is configuring and controlling SQL Server.

Comments?  Thoughts?

Jeremy

__________________________________
Do you Yahoo!?
The New Yahoo! Search - Faster. Easier. Bingo.
http://search.yahoo.com


-------------------------------------------------------
This SF.net email is sponsored by: If flattening out C++ or Java
code to make your application fit in a relational database is painful,
don't do it! Check out ObjectStore. Now part of Progress Software.
http://www.objectstore.net/sourceforge
_______________________________________________
Ccnet-devel mailing list
Ccn...@li...
https://lists.sourceforge.net/lists/listinfo/ccnet-devel

doug,
if you are interested, we have added an alternate way of getting nunit2
test results reported by ccnet.  the approach uses the XmlLogPublisher to
merge the output of different xml files into a single xml file that is
transformed and displayed by the web app.  this approach means that you
don't need to hack your nant build file to get nunit2 to output xml when
you are running the ccnet build and plain text when running a developer
build.
you can pick this up by downloading the latest source or picking up the 0.3
release.
attached below is xml info from mike's previous email.

<snip>
There is also a new feature on the xmlLogger to allow you to list a set of
files to merge into the xml log file. Right now that is the only way to get
nunit 2.1 support to work.

<xmlLogger>
<logDir>C:\foo\log</logDir>
<mergeFiles>
        <file>C:\foo\build\*-results.xml</file>
</mergeFiles>
</xmlLogger>
</snip>


cheers,
owen.

---
R. Owen Rogers
ThoughtWorks Ltd
Peek House
20, Eastcheap
London EC3M 1EB
tel:        +44 (0) 207 090 7400
mobile:  +44 (0) 787 673 8898



|---------+---------------------------->
|         |           "Douglas de la   |
|         |           Torre"           |
|         |           <res...@gt...|
|         |           >                |
|         |                            |
|         |           05/17/2003 06:28 |
|         |           AM               |
|         |           Please respond to|
|         |           "Douglas de la   |
|         |           Torre"           |
|---------+---------------------------->
  >------------------------------------------------------------------------------------------------------------------------------|
  |                                                                                                                              |
  |       To:       <OR...@th...>                                                                                   |
  |       cc:       <ccn...@li...>                                                                          |
  |       Subject:  Re: Fw: Cruise Control not finding unit test results                                                         |
  >------------------------------------------------------------------------------------------------------------------------------|




Thank you, Owen!  Worked perfectly.

The secret was to include the usefile="false".

<nunit2>
  <formatter type="Xml" usefile="false"/>
        :
</nunit2>

I love the CruiseControl product, and now that I have it finding my tests,
can't wait to have in building continuously!

Thanks.

-Doug
 ----- Original Message -----
 From: OR...@th...
 To: Douglas de la Torre
 Cc: ccn...@li...
 Sent: Friday, May 16, 2003 1:21 AM
 Subject: Re: Fw: Cruise Control not finding unit test results





 hi doug,
 sorry about the delay in my reply.  it is not always possible for me to
 give immediate feedback.  you are welcome to email the mailing list
 instead: ccn...@li....
 with regards to nunit2 test results, it requires some fiddling with
 configuration files and build files to get the nunit2 task to output xml.
 have you had the chance to look at the nant.html file located in the doc
 folder?  i've attached the file for reference.

 (See attached file: nant.html)

 we are looking for a way to make this process easier.  suggestions are
 welcome.
 regards,
 owen.


 ---
 R. Owen Rogers
 ThoughtWorks Ltd
 Peek House
 20, Eastcheap
 London EC3M 1EB
 tel:        +44 (0) 207 090 7400
 mobile:  +44 (0) 787 673 8898



 |---------+---------------------------->
 |         |           "Douglas de la   |
 |         |           Torre"           |
 |         |           <res...@gt...|
 |         |           >                |
 |         |                            |
 |         |           05/16/2003 07:59 |
 |         |           AM               |
 |         |           Please respond to|
 |         |           "Douglas de la   |
 |         |           Torre"           |
 |---------+---------------------------->

 >------------------------------------------------------------------------------------------------------------------------------|

   |
 |
   |       To:       <man...@th...>,
 <dan...@th...>
 |
   |       cc:       <OR...@th...>
 |
   |       Subject:  Fw: Cruise Control not finding unit test results
 |

 >------------------------------------------------------------------------------------------------------------------------------|





 Owen - if you received my email, apologies for resending to these others,
 but I haven't heard back.  Just trying other resources in hope there is
 someone who can help.

 I sent an email yesterday Owen Rogers, who appears to be a significant
 contributor to the CruiseControl.NET sourceforge project.  I haven't heard
 from him, so I thought I'd check with either of you.

 A detailed description of the problem is below.  In short, I have CC
 running, but am not getting any nunit2 test results.  Attached is some
 very
 simple sample code, plus the XML output.  Not sure if this is a problem
 with NUnit or with CC, so was hoping someone could weigh in with
 suggestions.

 Thanks!

 -Doug

 ----- Original Message -----
 From: Douglas de la Torre
 To: OR...@th...
 Sent: Wednesday, May 14, 2003 11:13 PM
 Subject: Cruise Control not finding unit test results

 Hi Owen,

 As a new user to Cruise Control, I'm intrigued by what I see.  It looks
 like this will be a 'must-have' tool for C# development.

 My problem is this:  when a build kicks off, code compiles and unit tests
 are run.  However, it always reports that "no tests were found".  Yet if I
 look in the directory where the code builds, it shows
 mytest.dll-results.xml.  It appears as if the nunit2 task is not reporting
 test results to the console, because they never seem to make their way
 into
 the log file that the ccnet web application reads results out of.

 I've included a very simple project I whipped up to test the system out.
 If you drop it in your ccnet root directory and setup the build files the
 way they appear in the zipfile, you will be able to build the same code.

 What am I missing?  I am running WinXP with the .Net framework 1.0 and 1.1
 installed.  I'm using the nant.exe that came with ccnet, although I have
 hand-built the 0.8.3 version of nant.exe and tried that too, with the same
 result.

 I appreciate any suggestions.  I'm secretly hoping that I am missing
 something totally obvious and simple.  I've been through the site (the
 wiki, sourceforge, and the cruise control page on thoughtworks), and have
 seen no mention of my problem, so I decided to try you directly in hopes
 you might be able to help.

 -Doug

 Doug de la Torre
 cru...@ze...
  (See attached file: ccnet.zip)

I just checked in a new project dir called
controlpanel into ccnet.  It's a gui that lives in the
system tray that let's you
start/stop/monitor/configure cc.net.  

First page is the start/stop/monitor status, and
eventually install?  It's connected, but is showing
some bugs in the remoting interface w/ status and
stopping of cc.

Second page is for configuring cruise, eventually I'd
like to see some kind of a gui or something, but as a
first step, I'm going to try to just have the xml that
the service is looking at along w/ a load/save for it.

Additional features we could add are a console output
listener and multi project support.

The idea of all of this is to make cc.net very easy
and ms developer friendly.  The metaphor I'm thinking
of is configuring and controlling SQL Server.

Comments?  Thoughts?

Jeremy

__________________________________
Do you Yahoo!?
The New Yahoo! Search - Faster. Easier. Bingo.
http://search.yahoo.com

Hate to be a bother, but you might want to do it again.

I fixed the issue we were having yesterday and the configurable xslfiles 
feature now works

Instead of having the xsl sections for the web page hard coded you list 
them in the web.config. New sections can be added just by modifying the 
xslFiles section in the web.config.

There is also a new feature on the xmlLogger to allow you to list a set of 
files to merge into the xml log file. Right now that is the only way to 
get nunit 2.1 support to work.

<xmlLogger>
<logDir>C:\foo\log</logDir>
<mergeFiles>
        <file>C:\foo\build\*-results.xml</file>
</mergeFiles>
</xmlLogger>

Mike Two; Putting the tWo in Thoughrks




Mike Roberts <mi...@th...>
Sent by: ccn...@li...
05/16/2003 04:43 PM

 
        To:     ccn...@li...
        cc: 
        Subject:        [Ccnet-devel] CCNet 0.3 Release


Hi all,

I've put MSI's up in the files section of the Sourceforge project - I 
haven't tested them fully but feel free to try them out.

http://sourceforge.net/project/showfiles.php?group_id=71179

Mike



-------------------------------------------------------
This SF.net email is sponsored by: If flattening out C++ or Java
code to make your application fit in a relational database is painful, 
don't do it! Check out ObjectStore. Now part of Progress Software.
http://www.objectstore.net/sourceforge
_______________________________________________
Ccnet-devel mailing list
Ccn...@li...
https://lists.sourceforge.net/lists/listinfo/ccnet-devel

Thank you, Owen!  Worked perfectly.

The secret was to include the usefile=3D"false".

<nunit2>
  <formatter type=3D"Xml" usefile=3D"false"/>
        :
</nunit2>

I love the CruiseControl product, and now that I have it finding my =
tests, can't wait to have in building continuously!

Thanks.

-Doug
  ----- Original Message -----=20
  From: OR...@th...=20
  To: Douglas de la Torre=20
  Cc: ccn...@li...=20
  Sent: Friday, May 16, 2003 1:21 AM
  Subject: Re: Fw: Cruise Control not finding unit test results






  hi doug,
  sorry about the delay in my reply.  it is not always possible for me =
to
  give immediate feedback.  you are welcome to email the mailing list
  instead: ccn...@li....
  with regards to nunit2 test results, it requires some fiddling with
  configuration files and build files to get the nunit2 task to output =
xml.
  have you had the chance to look at the nant.html file located in the =
doc
  folder?  i've attached the file for reference.

  (See attached file: nant.html)

  we are looking for a way to make this process easier.  suggestions are
  welcome.
  regards,
  owen.


  ---
  R. Owen Rogers
  ThoughtWorks Ltd
  Peek House
  20, Eastcheap
  London EC3M 1EB
  tel:        +44 (0) 207 090 7400
  mobile:  +44 (0) 787 673 8898



  |---------+---------------------------->
  |         |           "Douglas de la   |
  |         |           Torre"           |
  |         |           <res...@gt...|
  |         |           >                |
  |         |                            |
  |         |           05/16/2003 07:59 |
  |         |           AM               |
  |         |           Please respond to|
  |         |           "Douglas de la   |
  |         |           Torre"           |
  |---------+---------------------------->
    =
>------------------------------------------------------------------------=
------------------------------------------------------|
    |                                                                    =
                                                          |
    |       To:       <man...@th...>, =
<dan...@th...>                                            =
      |
    |       cc:       <OR...@th...>                         =
                                                          |
    |       Subject:  Fw: Cruise Control not finding unit test results   =
                                                          |
    =
>------------------------------------------------------------------------=
------------------------------------------------------|




  Owen - if you received my email, apologies for resending to these =
others,
  but I haven't heard back.  Just trying other resources in hope there =
is
  someone who can help.

  I sent an email yesterday Owen Rogers, who appears to be a significant
  contributor to the CruiseControl.NET sourceforge project.  I haven't =
heard
  from him, so I thought I'd check with either of you.

  A detailed description of the problem is below.  In short, I have CC
  running, but am not getting any nunit2 test results.  Attached is some =
very
  simple sample code, plus the XML output.  Not sure if this is a =
problem
  with NUnit or with CC, so was hoping someone could weigh in with
  suggestions.

  Thanks!

  -Doug

  ----- Original Message -----
  From: Douglas de la Torre
  To: OR...@th...
  Sent: Wednesday, May 14, 2003 11:13 PM
  Subject: Cruise Control not finding unit test results

  Hi Owen,

  As a new user to Cruise Control, I'm intrigued by what I see.  It =
looks
  like this will be a 'must-have' tool for C# development.

  My problem is this:  when a build kicks off, code compiles and unit =
tests
  are run.  However, it always reports that "no tests were found".  Yet =
if I
  look in the directory where the code builds, it shows
  mytest.dll-results.xml.  It appears as if the nunit2 task is not =
reporting
  test results to the console, because they never seem to make their way =
into
  the log file that the ccnet web application reads results out of.

  I've included a very simple project I whipped up to test the system =
out.
  If you drop it in your ccnet root directory and setup the build files =
the
  way they appear in the zipfile, you will be able to build the same =
code.

  What am I missing?  I am running WinXP with the .Net framework 1.0 and =
1.1
  installed.  I'm using the nant.exe that came with ccnet, although I =
have
  hand-built the 0.8.3 version of nant.exe and tried that too, with the =
same
  result.

  I appreciate any suggestions.  I'm secretly hoping that I am missing
  something totally obvious and simple.  I've been through the site (the
  wiki, sourceforge, and the cruise control page on thoughtworks), and =
have
  seen no mention of my problem, so I decided to try you directly in =
hopes
  you might be able to help.

  -Doug

  Doug de la Torre
  cru...@ze...
   (See attached file: ccnet.zip)

Hi all,

I've put MSI's up in the files section of the Sourceforge project - I 
haven't tested them fully but feel free to try them out.

http://sourceforge.net/project/showfiles.php?group_id=71179

Mike

Thanks... That fixed the problem.  Glad to hear another drop is on the way.  Since you guys are in the process of putting together a new release, I'll mention some of the hurdles I jumped through to get the 0.2.1 build to install.

1. I had to modify the <executable> element value to point at the absolute path to ccnet's cvs exe.  The relative path blew chunks.
2. I had to manually modify the <history historyDir=""> value.  The readme doesn't mention it.
3. The aforementioned .xsl bug, which you fixed for me.
4. Some information of the <email> element was left off.  The readme doesn't tell you to set the from, mailhost, or includeDetails attributes (though it should be self-explainatory).

Other than that, all went well.  Currently, the build process seems to be working fine, and while the ccnet web interface now works, it shows the build results but if you click on an individual build all the details are empty.  Also, I'm not getting any emails, not sure why b/c nothing seems to be blowing an error.

Just wanted to drop this info your way.  Great work guys, I look forward to the next drop!

Don


> 
> -----Original Message-----
> From: OR...@th... [mailto:OR...@th...] 
> Sent: Friday, May 16, 2003 3:30 PM
> To: Don...@tu...
> Cc: 'ccn...@li...'
> 
> 
> 
> 
> 
> hi don,
> there is a bug in the xsl for the distributables.xsl file.
> 
> 
> (See attached file: distributables.xsl)
> we are in the process of putting together a new release which 
> should be ready middle of next week.
> cheers,
> owen.
> 
> ---
> R. Owen Rogers
> ThoughtWorks Ltd
> Peek House
> 20, Eastcheap
> London EC3M 1EB
> tel:        +44 (0) 207 090 7400
> mobile:  +44 (0) 787 673 8898
> 
> 
> 
> |---------+--------------------------------------->
> |         |           "Browning, Don"             |
> |         |           <Don...@tu...>   |
> |         |           Sent by:                    |
> |         |           ccn...@li...|
> |         |           ceforge.net                 |
> |         |                                       |
> |         |                                       |
> |         |           05/16/2003 08:18 PM         |
> |---------+--------------------------------------->
>   
> >-------------------------------------------------------------
> -----------------------------------------------------------------|
>   |                                                           
>                                                                    |
>   |       To:       "'ccn...@li...'" 
> <ccn...@li...>                           
>          |
>   |       cc:                                                 
>                                                                    |
>   |       Subject:  [Ccnet-devel] Problems with the web 
> interface                                                     
>            |
>   
> >-------------------------------------------------------------
> -----------------------------------------------------------------|
> 
> 
> 
> 
> Hey guys!
> 
> Well, I installed the cc.net server piece and managed to get 
> it up and running with minimal effort (good job!), but I have 
> a question on the web interface.
> 
> I installed the web interface to the following location:
> C:\Projects\trip\build\ccnet
> 
> Which maps to the following vroot:
> http://indiana/trip/ccnet
> 
> When I attempt to access the url, I get the following 
> exception 
> 'task[attribute::name='War']message[attribute::priority='info'
> ]' has an invalid token
> 
> Has anyone else seen this?  I'm currently running this on a 
> Win2K3 box with the following runtime info:
> Microsoft .NET Framework Version:1.1.4322.342; ASP.NET 
> Version:1.1.4322.342
> 
> Any help would be appriciated...
> 
> Don
>