ccnet-devel Mailing List for CruiseControl.NET

Hi Steve,

At the moment, ISourceControl implementations have the working
directory / artifact directory available to them through the
IntegrationResult parameter, however they don't have access to these
values when GetModifications is called.

I have added an issue to add this :

http://jira.public.thoughtworks.org/browse/CCNET-322

The NAnt builder doesn't currently have the working directory or
artifact directory passed through as arguments. This would be a useful
addition, so I've also Jira'ed this:

http://jira.public.thoughtworks.org/browse/CCNET-323

Cheers,

Mike

On Mon, 31 Jan 2005 09:53:05 -0800 (PST), Steve Jansen
<st...@ya...> wrote:
> Hi Mike & Owen,
> 
> I have a question regarding the CCNET SDK.  Is there a way for my
> sourcecontrol plugin to read the project's configured values for the
> working directory and/or artifact directory?
> 
> Here's an example.
> <cruisecontrol>
>      <project>
>           <workingDirectory>c:\foo</workingDirectory>
>           <artifactDirectory>c:\bar</artifactDirectory>
>      </project>
> </cruisecontrol>
> 
> Also, are these values passed as command line arguments to the NAnt
> builder?
> 
> I want to take full advantage of both configuration settings, so any
> information is appreciated.
> 
> Thanks,
> Steve
> 


-- 
mike roberts | http://mikeroberts.thoughtworks.net/ |
http://www.thoughtworks.com/

Hi Mike & Owen,

I have a question regarding the CCNET SDK.  Is there a way for my
sourcecontrol plugin to read the project's configured values for the
working directory and/or artifact directory?

Here's an example.
<cruisecontrol>
     <project>
          <workingDirectory>c:\foo</workingDirectory>
          <artifactDirectory>c:\bar</artifactDirectory>
     </project>
</cruisecontrol>

Also, are these values passed as command line arguments to the NAnt
builder?

I want to take full advantage of both configuration settings, so any
information is appreciated.

Thanks,
Steve

Imagine my surprise...I was just catching up on email while downloading
the latest version of CCNet so that I can setup automated build for
NVelocity (and Maverick.Net).  Kinda ironic. :)  Nice to see people
using it.

Cort

-----Original Message-----
From: ccn...@li...
[mailto:ccn...@li...] On Behalf Of Mike
Roberts
Sent: Wednesday, January 26, 2005 10:28 PM
To: ccn...@li...
Subject: [Ccnet-devel] BREAKING CHANGES to Dashboard

Hi all,

If you use development (CCNetLive) builds, and use the reporting
features of the Dashboard, please read this mail. This effects builds
from 701 onwards.

The Dashboard no longer uses Sitemesh, and all pages now come from
Default.aspx. This requires you to make the following changes:
- Your Dashboard web.config file should no longer contain references
to Sitemesh at all
- You should update your Dashboard web.config to use the new
ServerReport and FarmReport plugins.
- ... in fact the BEST thing to do is to throw away your old Dashboard
folder and use the distributed one, re-adding your <server> settings
into the web.config file.

- You also need to update your ccnet.config files, specifically the
<webURL> tags. These should no longer contain a reference to
'controller.aspx'. The Dashboard now just uses the default page, so
you can do '/?'

See
http://confluence.public.thoughtworks.org/display/CCNET/Web+Dashboard+Re
porting+Features
for complete instructions.

CCNetLive has been updated with the latest build (701).

Since this is a breaking change, the next release of CruiseControl.NET
will be 0.9

For those in interested in more about this...

The Dashboard has had its own 'Front Controller' for a while. In this
release we are using the Controller for everything, including the
Project Grid. This has been made easier by the introduction of
NVelocity templates to the Dashboard.

Since all Dashboard 'actions' are now available through 1 'page' we no
longer need Sitemesh since Sitemesh is used to template applications
with multiple pages.

The 'default.aspx' page still has quite a lot of html in it, but this
too will be moved into velocity templates, and we will use more action
decorators to produce the look and feel of the application.

Either in this release or the next we will also be implementing
run-time Project URL's for both the Dashboard and CCTray, so then the
<webURL> configuration element will be disappearing totally from
ccnet.config.

Please reply if you have any questions or problems with these changes.

Mike

--=20
mike roberts | http://mikeroberts.thoughtworks.net/ |
http://www.thoughtworks.com/


-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Ccnet-devel mailing list
Ccn...@li...
https://lists.sourceforge.net/lists/listinfo/ccnet-devel

	Hi Mike,

	Thanks for the info. I will pass on this info to my manager, and
we'll evaluate from there. 

	Thanks,

	Chris...

	Chris Barrow
	Web Developer, eProduct Systems
	ADP Canada
	905-795-5400 ext 7568

	Think IT... Live IT... Do IT... ADP IT




				Mike Roberts
<mik...@gm...>@SMTP@Exchange 
				01/26/2005 05:15 PM

				Please respond to
	
ccn...@li...@SMTP@Exchange
					

To
		ccn...@li...@SMTP@Exchange
cc

Subject
		Re: [Ccnet-devel] Source Control System: Serena Dimensions
and Integration with CC. NET




	


	Hi Chris,

	I haven't heard anyone mention it. If you want some help developing
	your own plugin, ask here, but you'll first need to figure out how
to
	get lists of modifications from Dimensions in an automated fashion.

	Mike

	On Wed, 26 Jan 2005 09:19:26 -0500, Chr...@ad...
	<Chr...@ad...> wrote:
	> 
	> Does anyone know if there plans for CC.NET to support the Version
Control
	> System product Serena Dimenions? If someone could let me know, I
would
	> greatly appreciate it.


	-------------------------------------------------------
	This SF.Net email is sponsored by: IntelliVIEW -- Interactive
Reporting
	Tool for open source databases. Create drag-&-drop reports. Save
time
	by over 75%! Publish reports on the web. Export to DOC, XLS, RTF,
etc.
	Download a FREE copy at http://www.intelliview.com/go/osdn_nl
	_______________________________________________
	Ccnet-devel mailing list
	Ccn...@li...
	https://lists.sourceforge.net/lists/listinfo/ccnet-devel

another option -- and this option will work immediately -- is to use
the <publishExceptions> attribute on the <project> element.  see the
project configuration doc for details:
http://confluence.public.thoughtworks.org/display/CCNET/Project+Configuration+Block
cheers,
owen.


On Tue, 25 Jan 2005 09:28:41 -0600, Bolles, James E
<Jam...@el...> wrote:
>  
>  
> 
> Can we add a command-line operation at the Tasks level for running
> miscellaneous executables?  The problem with the command-line publisher is
> my emails go out stating the build was good but my Doxygen code blows up on
> the C++.  It gives me the false impression that everything with the build
> was successful. If we make a command-line task, we can have it fail as part
> of the build process so the publishers can report if an exceptions occurred.
> 
>   
> 
> What do you think about this feature? 
> 
>   
> 
> James E. Bolles
>  
>  
> 
>   
> 
>   
> 
>   ****************************************************************** This
> email and any files transmitted with it from the ElPaso Corporation are
> confidential and intended solely for the use of the individual or entity to
> whom they are addressed. If you have received this email in error please
> notify the sender.
> ****************************************************************** 


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

hi james,
i think that this is a great idea.  one of the long standing changes
that i've been meaning to make (it's very simple too), is to make the
publishers implement the ITask interface.  this would enable you to
transparently treat publishers as tasks.
cheers,
owen.


On Tue, 25 Jan 2005 09:28:41 -0600, Bolles, James E
<Jam...@el...> wrote:
>  
>  
> 
> Can we add a command-line operation at the Tasks level for running
> miscellaneous executables?  The problem with the command-line publisher is
> my emails go out stating the build was good but my Doxygen code blows up on
> the C++.  It gives me the false impression that everything with the build
> was successful. If we make a command-line task, we can have it fail as part
> of the build process so the publishers can report if an exceptions occurred.
> 
>   
> 
> What do you think about this feature? 
> 
>   
> 
> James E. Bolles
>  
>  
> 
>   
> 
>   
> 
>   ****************************************************************** This
> email and any files transmitted with it from the ElPaso Corporation are
> confidential and intended solely for the use of the individual or entity to
> whom they are addressed. If you have received this email in error please
> notify the sender.
> ****************************************************************** 


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

hi chris,
at this point, i don't know of anyone involved in implementing a
source control provider for Serena Dimensions.  we also don't have any
specific plans of implementing one ourselves.  however, we would be
happy to provide whatever support is necessary to help the development
of this.
cheers,
owen.


On Wed, 26 Jan 2005 09:19:26 -0500, Chr...@ad...
<Chr...@ad...> wrote:
> 
> Does anyone know if there plans for CC.NET to support the Version Control
> System product Serena Dimenions? If someone could let me know, I would
> greatly appreciate it.
> Thanks,
> Chris...
> Chris Barrow
> Web Developer, eProduct Systems
> ADP Canada
> 905-795-5400 ext 7568
> Think IT... Live IT... Do IT... ADP IT
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
> Tool for open source databases. Create drag-&-drop reports. Save time
> by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
> Download a FREE copy at http://www.intelliview.com/go/osdn_nl
> _______________________________________________
> Ccnet-devel mailing list
> Ccn...@li...
> https://lists.sourceforge.net/lists/listinfo/ccnet-devel
> 


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

Hi all,

If you use development (CCNetLive) builds, and use the reporting
features of the Dashboard, please read this mail. This effects builds
from 701 onwards.

The Dashboard no longer uses Sitemesh, and all pages now come from
Default.aspx. This requires you to make the following changes:
- Your Dashboard web.config file should no longer contain references
to Sitemesh at all
- You should update your Dashboard web.config to use the new
ServerReport and FarmReport plugins.
- ... in fact the BEST thing to do is to throw away your old Dashboard
folder and use the distributed one, re-adding your <server> settings
into the web.config file.

- You also need to update your ccnet.config files, specifically the
<webURL> tags. These should no longer contain a reference to
'controller.aspx'. The Dashboard now just uses the default page, so
you can do '/?'

See http://confluence.public.thoughtworks.org/display/CCNET/Web+Dashboard+Reporting+Features
for complete instructions.

CCNetLive has been updated with the latest build (701).

Since this is a breaking change, the next release of CruiseControl.NET
will be 0.9

For those in interested in more about this...

The Dashboard has had its own 'Front Controller' for a while. In this
release we are using the Controller for everything, including the
Project Grid. This has been made easier by the introduction of
NVelocity templates to the Dashboard.

Since all Dashboard 'actions' are now available through 1 'page' we no
longer need Sitemesh since Sitemesh is used to template applications
with multiple pages.

The 'default.aspx' page still has quite a lot of html in it, but this
too will be moved into velocity templates, and we will use more action
decorators to produce the look and feel of the application.

Either in this release or the next we will also be implementing
run-time Project URL's for both the Dashboard and CCTray, so then the
<webURL> configuration element will be disappearing totally from
ccnet.config.

Please reply if you have any questions or problems with these changes.

Mike

-- 
mike roberts | http://mikeroberts.thoughtworks.net/ |
http://www.thoughtworks.com/

Hi Chris,

I haven't heard anyone mention it. If you want some help developing
your own plugin, ask here, but you'll first need to figure out how to
get lists of modifications from Dimensions in an automated fashion.

Mike

On Wed, 26 Jan 2005 09:19:26 -0500, Chr...@ad...
<Chr...@ad...> wrote:
> 
> Does anyone know if there plans for CC.NET to support the Version Control
> System product Serena Dimenions? If someone could let me know, I would
> greatly appreciate it.

Does anyone know if there plans for CC.NET to support the Version Control
System product Serena Dimenions? If someone could let me know, I would
greatly appreciate it. 
Thanks, 
Chris... 
Chris Barrow
Web Developer, eProduct Systems
ADP Canada
905-795-5400 ext 7568
Think IT... Live IT... Do IT... ADP IT 

Hi,

You can define the 'pattern' of build numbers in the ccnet config file
using a 'labeller', but this cannot be configured from the UI as of
yet (and is not trivial to enable)

We also plan on adding functionality to manipulate the build number
itself from the UI but again this is not easy to do right now.

CruiseControl.NET is designed primarily for automated build systems
that have no manual interraction. This is why functionality such as
that which you suggest isn't available right now.

In future, please can you use the 'ccnet-user' lists for general
requests such as this?

Cheers,

Mike

On Tue, 25 Jan 2005 10:08:31 -0800 (PST), rama subba rao
<ve...@ya...> wrote:
> Hello All,
> 
> I am a newbie to CrusieControl.NET.Ihave started using
> this great tool last week.I have a requirement where I
> need to customize the webdashboard.To be specific, I
> should be able to do the following:
> 
> The person who does the automatic builds enters a
> value in a web control and that value should be sent
> as a parameter to the NAant Build.NAnt Build uses this
> parameter to label the builds.I am currently using
> Cruise Control.NET Version 0.85.
> 
> I would greatly appreciate, if some help is provided
> or point me in the right direction.
> 
> Thanks
> Ram
> 
> __________________________________
> Do you Yahoo!?
> Yahoo! Mail - Find what you need with new enhanced search.
> http://info.mail.yahoo.com/mail_250
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
> Tool for open source databases. Create drag-&-drop reports. Save time
> by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
> Download a FREE copy at http://www.intelliview.com/go/osdn_nl
> _______________________________________________
> Ccnet-devel mailing list
> Ccn...@li...
> https://lists.sourceforge.net/lists/listinfo/ccnet-devel
> 


-- 
mike roberts | http://mikeroberts.thoughtworks.net/ |
http://www.thoughtworks.com/

Hello All,

I am a newbie to CrusieControl.NET.Ihave started using
this great tool last week.I have a requirement where I
need to customize the webdashboard.To be specific, I
should be able to do the following:

The person who does the automatic builds enters a
value in a web control and that value should be sent
as a parameter to the NAant Build.NAnt Build uses this
parameter to label the builds.I am currently using
Cruise Control.NET Version 0.85.

I would greatly appreciate, if some help is provided
or point me in the right direction.

Thanks
Ram



		
__________________________________ 
Do you Yahoo!? 
Yahoo! Mail - Find what you need with new enhanced search.
http://info.mail.yahoo.com/mail_250

Can we add a command-line operation at the Tasks level for running
miscellaneous executables?  The problem with the command-line publisher
is my emails go out stating the build was good but my Doxygen code blows
up on the C++.  It gives me the false impression that everything with
the build was successful. If we make a command-line task, we can have it
fail as part of the build process so the publishers can report if an
exceptions occurred.

=20

What do you think about this feature?

=20

James E. Bolles



=20

=20

=20

******************************************************************
This email and any files transmitted with it from the ElPaso
Corporation are confidential and intended solely for the
use of the individual or entity to whom they are addressed.
If you have received this email in error please notify the
sender.
******************************************************************

Hi all,

The Java integration tests are leaving browser windows open - please
can someone fix this? (This is happening with Firefox 1.0 set as the
default system browser, on Windows)

Cheers,

Mike

-- 
mike roberts | http://mikeroberts.thoughtworks.net/ |
http://www.thoughtworks.com/

1) Fixed error related to rendering of test details page including some 
cosmetics. This was due to multiple test-result nodes in the new ccnet log 
file. This case is now handled and the test result name is also displayed.

2) The page is also doing a post-back even for *client-side* code - am 
currently investigating why that's happenning.

Vivek

----- Original Message ----- 
From: "Mike Roberts" <mik...@gm...>
To: <Ste...@mp...>; <ccn...@li...>
Sent: Sunday, January 23, 2005 4:33 PM
Subject: [Ccnet-devel] Re: [Ccnet-user] ToggleDiv javascript called twice


> (re posted to ccnet-dev)
>
> Are there any javascript experts on the list? JS is not one of my
> strong skills so any help would be appreciated! :)
>
> Thanks,
>
> Mike
>
> On Fri, 21 Jan 2005 07:50:06 -0600, Steve Mitcham
> <Ste...@mp...> wrote:
>> When I click on the drill down arrows in the unit test details page.
>> The toggleDiv function is getting called twice, resulting in the arrow
>> remaining in the original state at the page load.  Can anyone tell me
>> why this is, and how to deal with it?  I know next to nothing about
>> javascript.
>
> -- 
> mike roberts | http://mikeroberts.thoughtworks.net/ |
> http://www.thoughtworks.com/
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
> Tool for open source databases. Create drag-&-drop reports. Save time
> by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
> Download a FREE copy at http://www.intelliview.com/go/osdn_nl
> _______________________________________________
> Ccnet-devel mailing list
> Ccn...@li...
> https://lists.sourceforge.net/lists/listinfo/ccnet-devel 

 Ok,  I found the issue.  In the td section where the arrows are created
is the line:

<xsl:attribute name=3D"onclick">
	javascript:toggleDiv('img<xsl:value-of select=3D"$section.id"/>',
'divDetails<xsl:value-of select=3D"$section.id"/>');
</xsl:attribute>


It needs to have a 'return false' added to end of the handler to keep
from submitting the form.
So it now looks like:

<xsl:attribute name=3D"onclick">
javascript:toggleDiv('img<xsl:value-of select=3D"$section.id"/>',
'divDetails<xsl:value-of select=3D"$section.id"/>'); return false;
</xsl:attribute>
-----Original Message-----
From: Mike Roberts [mailto:mik...@gm...]=20
Sent: Sunday, January 23, 2005 4:34 PM
To: Steve Mitcham; ccn...@li...
Subject: Re: [Ccnet-user] ToggleDiv javascript called twice

(re posted to ccnet-dev)

Are there any javascript experts on the list? JS is not one of my strong
skills so any help would be appreciated! :)

Thanks,

Mike

On Fri, 21 Jan 2005 07:50:06 -0600, Steve Mitcham
<Ste...@mp...> wrote:
> When I click on the drill down arrows in the unit test details page.
> The toggleDiv function is getting called twice, resulting in the arrow

> remaining in the original state at the page load.  Can anyone tell me=20
> why this is, and how to deal with it?  I know next to nothing about=20
> javascript.

--
mike roberts | http://mikeroberts.thoughtworks.net/ |
http://www.thoughtworks.com/

Code changes have been sent.

James E. Bolles

=20

-----Original Message-----
From: ccn...@li...
[mailto:ccn...@li...] On Behalf Of Mike
Roberts
Sent: Monday, January 24, 2005 3:04 PM
To: ccn...@li...
Subject: Re: [Ccnet-devel] FW: [Ccnet-user] Updates to PVCS files in 0.7

Hi James, I understand now, thanks.

The project now has a concept called 'working directory' which by
default is set to something specific to any project. SourceControl's
already get given this when 'GetSource' is called, and we could change
the ISourceControl GetModifications() method similarly.

Owen - do you think this is a good idea? Also Owen - are you handling
this update or would you like me too?

James - if you can send the zip of what you have to both Owen and my
addresses that would be great.

Cheers,

Mike

On Mon, 24 Jan 2005 08:12:20 -0600, Bolles, James E
<Jam...@el...> wrote:
> Thanks for your response, Mike.  My need was to have the name of the
> project so I could create unique directories for the PVCS scripts that
> need to be run.  I felt the project name was what made each project
> unique so I passed the IProject reference into the
ProcessSourceControl
> class.  I am not trying to reinitialize the Project, I am just trying
to
> make sure the reference to IProject is passed in so I can get the Name
> property.  Do I have to have the Name, no, I guess not.  We could put
a
> required field that asked for the directory to place the scripts.  I
> have event considered making unique temp files that would get cleaned
up
> automatically but it makes it difficult to track in production when
> there is a problem.  Using the Project Name gave an easy way to store
> PCLI scripts and execute them from that path.
>=20
> In the ProjectIntegrator.cs file, I am passing a reference of the
> IProject interface into the ProcessSourceControl base so logs could be
> stored in a directory by Project name.  There is a virtual method that
> exists in ProcessSourceControl called Initialize where the IProject is
> the input but there is not logic implemented anywhere I can see.  I
just
> added the logic to set a local variable with the IProject reference.


-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Ccnet-devel mailing list
Ccn...@li...
https://lists.sourceforge.net/lists/listinfo/ccnet-devel
******************************************************************
This email and any files transmitted with it from the ElPaso
Corporation are confidential and intended solely for the
use of the individual or entity to whom they are addressed.
If you have received this email in error please notify the
sender.
******************************************************************

Hi James, I understand now, thanks.

The project now has a concept called 'working directory' which by
default is set to something specific to any project. SourceControl's
already get given this when 'GetSource' is called, and we could change
the ISourceControl GetModifications() method similarly.

Owen - do you think this is a good idea? Also Owen - are you handling
this update or would you like me too?

James - if you can send the zip of what you have to both Owen and my
addresses that would be great.

Cheers,

Mike

On Mon, 24 Jan 2005 08:12:20 -0600, Bolles, James E
<Jam...@el...> wrote:
> Thanks for your response, Mike.  My need was to have the name of the
> project so I could create unique directories for the PVCS scripts that
> need to be run.  I felt the project name was what made each project
> unique so I passed the IProject reference into the ProcessSourceControl
> class.  I am not trying to reinitialize the Project, I am just trying to
> make sure the reference to IProject is passed in so I can get the Name
> property.  Do I have to have the Name, no, I guess not.  We could put a
> required field that asked for the directory to place the scripts.  I
> have event considered making unique temp files that would get cleaned up
> automatically but it makes it difficult to track in production when
> there is a problem.  Using the Project Name gave an easy way to store
> PCLI scripts and execute them from that path.
> 
> In the ProjectIntegrator.cs file, I am passing a reference of the
> IProject interface into the ProcessSourceControl base so logs could be
> stored in a directory by Project name.  There is a virtual method that
> exists in ProcessSourceControl called Initialize where the IProject is
> the input but there is not logic implemented anywhere I can see.  I just
> added the logic to set a local variable with the IProject reference.

hi james,
all of this sounds good.  if you could send me your changes, i'll pair
up with irfan and process them this week.
cheers,
owen.

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

Thanks for your response, Mike.  My need was to have the name of the
project so I could create unique directories for the PVCS scripts that
need to be run.  I felt the project name was what made each project
unique so I passed the IProject reference into the ProcessSourceControl
class.  I am not trying to reinitialize the Project, I am just trying to
make sure the reference to IProject is passed in so I can get the Name
property.  Do I have to have the Name, no, I guess not.  We could put a
required field that asked for the directory to place the scripts.  I
have event considered making unique temp files that would get cleaned up
automatically but it makes it difficult to track in production when
there is a problem.  Using the Project Name gave an easy way to store
PCLI scripts and execute them from that path.

In the ProjectIntegrator.cs file, I am passing a reference of the
IProject interface into the ProcessSourceControl base so logs could be
stored in a directory by Project name.  There is a virtual method that
exists in ProcessSourceControl called Initialize where the IProject is
the input but there is not logic implemented anywhere I can see.  I just
added the logic to set a local variable with the IProject reference.

I am open to other suggestions and ideas. Do you want the code?  I have
merged it with 0.8 as well.

James E. Bolles

-----Original Message-----
From: ccn...@li...
[mailto:ccn...@li...] On Behalf Of Mike
Roberts
Sent: Sunday, January 23, 2005 6:07 PM
To: ccn...@li...
Subject: Re: [Ccnet-devel] FW: [Ccnet-user] Updates to PVCS files in 0.7

On Thu, 20 Jan 2005 16:38:14 -0600, Bolles, James E
<Jam...@el...> wrote:
> Thanks for your email, Mike.  Here is a list of files that I changed
and
> for what reason.  I can forward the files to someone if that would be
> easier so you can see them as well.
>=20
> Located in project\core
> Project.cs
> - added IsInitialized property to check if the Initialize method has
> been called
> - In the Initialize() method, added logic to call
> SourceControl.Initialize and pass a reference to the Project so the
base
> ProcessSourceControl.cs to be available to other sourcecontrol classes
>=20
> ProjectIntegrator.cs
> - Added logic to check if the Project has been Initialized, if not, it
> calls the Initialize method. This was to simulate the same call used
by
> CruiseServer.cs in the method AddProject.  Initialize is called here
but
> not anywhere else.

Hi James,

Thanks for this again. I just want to follow up on the Initialize
stuff - what are you using this for? Initialize is currently used once
in the lifetime of a project, even across server restarts. It was
introduced to allow better remote administration by automating
environmental setups. For instance, with Perforce source control it
creates a 'Perforce Client Spec', with CVS it would do a 'cvs
checkout' (wheras normally CVS performs an 'update'). These things=20
only ever need to be done once while the project is setup on that
build server.

We don't track the state of 'isInitialized' since we assume that a
project was either:
- created through the GUI and Initialize was called, or
- created manually by editting the config file, and any environment
requirements are setup manually.

Does this make sense? What were you trying to achieve? Maybe there's
an alternative I can suggest.

Mike


-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Ccnet-devel mailing list
Ccn...@li...
https://lists.sourceforge.net/lists/listinfo/ccnet-devel
******************************************************************
This email and any files transmitted with it from the ElPaso
Corporation are confidential and intended solely for the
use of the individual or entity to whom they are addressed.
If you have received this email in error please notify the
sender.
******************************************************************

This is caused I believe because the Thread.Sleep call in the test
classes are set like so: Thread.Sleep(0) but in the ProjectIntegrator
class, the Thread.Sleep is set to 100.  I set the test classes to 110
and do not get this exception anymore.  I had to make this change
through all of the Thread.Sleep calls where they were set to 0 when the
corresponding class was set to 100.  The error did not happen for me
every time but this did fix the problem for me.  =20

Can we incorporate this into the latest code as well?

James E. Bolles

=20

-----Original Message-----
From: ccn...@li...
[mailto:ccn...@li...] On Behalf Of
stj...@ya...
Sent: Sunday, January 23, 2005 7:58 PM
To: ccn...@li...
Subject: [Ccnet-devel] Problems with unit tests for 0.8.681

Hi Everyone,

I'm experiencing build problems with the unit tests for both the 0.7
and 0.8 RTM releases (0.7.571 and 0.8.681, respectively).

Two errors plague my builds.  The full build logs are attached.  The
relevant errors are below.  (The second failure was produced by
excluding the first failing test from the build.)

I've been trying conduct code coverage on the unit tests for the CCNET
Synergy plugin.  Unfortunately, I cannot successfully use the b.bat
automated build script, due to these failed tests.

I'm building on XP Pro SP1, with .NET SP 1 (1.1.4322.2032).  My
environmental PATH variable is devoid of any of the executables in the
tools directory (NAnt, NUnit, FxCop, NCover), so I am using the build
tools shipped with the distribution.

TIA,
Steve

--- START FAILURE #1 ---
[exec] ...........
[exec] ##### Unhandled Exception while running
ThoughtWorks.CruiseControl.Core.Util.Test.ProcessExecutorTest.ForceProce
ssTimeoutBecauseTargetIsNonTerminating
[exec] System.Threading.ThreadAbortException: Thread was being aborted.
[exec]
.=2E......................................................................
.=2E.................................F...
[exec] ##### Unhandled Exception while running
ThoughtWorks.CruiseControl.Core.Test.ProjectIntegratorTest.TerminateCall
edTwice
[exec] System.Threading.ThreadAbortException: Thread was being aborted.
[exec]
.=2E......................................................................
.=2E...........N....N.....................................................
.=2E......................................................................
.=2E......................................................................
.=2E........................N............................................
[exec] Tests run: 474, Failures: 1, Not run: 3, Time: 12.078125 seconds
[exec]=20
[exec] Failures:
[exec] 1)
ThoughtWorks.CruiseControl.Core.Test.ProjectIntegratorTest.VerifySchedul
erStateAfterException
:=20
[exec]    at
ThoughtWorks.CruiseControl.Core.Test.ProjectIntegratorTest.VerifySchedul
erStateAfterException()
in
d:\cmsynergy\sjansen\ccm_wa\wwdev\ThirdParty_Tools~ThirdParty_Tools_Dev_
sjansen\ThirdParty_Tools\src\CruiseControl.NET\project\core\test\Project
IntegratorTest.cs:line
148
---  END FAILURE #1  ---

--- START FAILURE #2 ---
[exec]
.=2E......................................................................
.=2E...............................................[CruiseControl
Server:Error]: INTERNAL ERROR:=20
[exec]=20
MockIIntegratable.RunIntegration(ThoughtWorks.CruiseControl.Remote.Build
Condition)
called too many times
[exec]=20
[exec]  expected:<0>
[exec]   but was:<1>
[exec] ----------
[exec] NMock.VerifyException:=20
[exec]=20
MockIIntegratable.RunIntegration(ThoughtWorks.CruiseControl.Remote.Build
Condition)
called too many times
[exec]=20
[exec]  expected:<0>
[exec]   but was:<1>
[exec]    at NMock.MockNoCall.Call(String methodName, Object[]
actualArgs)
[exec]    at NMock.Method.Call(Object[] parameters)
[exec]    at NMock.Mock.Invoke(String methodName, Object[] args)
[exec]    at ProxyIIntegratable_8.RunIntegration(BuildCondition )
[exec]    at
ThoughtWorks.CruiseControl.Core.ProjectIntegrator.Integrate() in
d:\cmsynergy\sjansen\ccm_wa\wwdev\ThirdParty_Tools~ThirdParty_Tools_Dev_
sjansen\ThirdParty_Tools\src\CruiseControl.NET\project\core\ProjectInteg
rator.cs:line
121
[exec] ----------
[exec]=20
[exec]=20
[exec] ##### Unhandled Exception while running
ThoughtWorks.CruiseControl.Core.Test.ProjectIntegratorTest.ForceBuild
[exec] System.Runtime.Serialization.SerializationException: The type
NMock.VerifyException in Assembly nmock, Version=3D1.0.1721.15437,
Culture=3Dneutral, PublicKeyToken=3Dnull is not marked as serializable.
[exec]
.=2E......................................................................
.=2E..........N....N......................................................
.=2E......................................................................
.=2E......................................................................
.=2E.......................N............................................
[exec] Tests run: 473, Failures: 0, Not run: 3, Time: 9 seconds

---  END FAILURE #2  ---
******************************************************************
This email and any files transmitted with it from the ElPaso
Corporation are confidential and intended solely for the
use of the individual or entity to whom they are addressed.
If you have received this email in error please notify the
sender.
******************************************************************

Hi Steve,

I'm really quite confused about that. I take it you are using the
source zip files? As you can tell, we don't have any failing tests
ourselves (look at the CCNetLive output for those 2 builds).

The only thing I can suggest is:
- Check your GAC (C:\windows\assembly) and see if you have any NUnit
dll's in there.
- Try on another machine.
- If you're using the source zip file, try the CVS version, or vice
versa (but it doesn't sound like file corruption).
- If you have Visual Studio, try running the failing tests in a
debugger ('testdriven.net' is a handy tool for that)

Apart from that, I don't know what to suggest. I myself run Windows XP
SP2 + .NET 1.1 (with Visual Studio installed), and CCNetLive is
Windows 2000 Server + .NET 1.1 (No Visual Studio)


On Sun, 23 Jan 2005 17:58:05 -0800 (PST), stj...@ya...
<stj...@ya...> wrote:
> Hi Everyone,
> 
> I'm experiencing build problems with the unit tests for both the 0.7
> and 0.8 RTM releases (0.7.571 and 0.8.681, respectively).
> 
> Two errors plague my builds.  The full build logs are attached.  The
> relevant errors are below.  (The second failure was produced by
> excluding the first failing test from the build.)
> 
> I've been trying conduct code coverage on the unit tests for the CCNET
> Synergy plugin.  Unfortunately, I cannot successfully use the b.bat
> automated build script, due to these failed tests.
> 
> I'm building on XP Pro SP1, with .NET SP 1 (1.1.4322.2032).  My
> environmental PATH variable is devoid of any of the executables in the
> tools directory (NAnt, NUnit, FxCop, NCover), so I am using the build
> tools shipped with the distribution.
> 
> TIA,
> Steve

-- 
mike roberts | http://mikeroberts.thoughtworks.net/ |
http://www.thoughtworks.com/

Hi Everyone,

I'm experiencing build problems with the unit tests for both the 0.7
and 0.8 RTM releases (0.7.571 and 0.8.681, respectively).

Two errors plague my builds.  The full build logs are attached.  The
relevant errors are below.  (The second failure was produced by
excluding the first failing test from the build.)

I've been trying conduct code coverage on the unit tests for the CCNET
Synergy plugin.  Unfortunately, I cannot successfully use the b.bat
automated build script, due to these failed tests.

I'm building on XP Pro SP1, with .NET SP 1 (1.1.4322.2032).  My
environmental PATH variable is devoid of any of the executables in the
tools directory (NAnt, NUnit, FxCop, NCover), so I am using the build
tools shipped with the distribution.

TIA,
Steve

--- START FAILURE #1 ---
[exec] ...........
[exec] ##### Unhandled Exception while running
ThoughtWorks.CruiseControl.Core.Util.Test.ProcessExecutorTest.ForceProcessTimeoutBecauseTargetIsNonTerminating
[exec] System.Threading.ThreadAbortException: Thread was being aborted.
[exec]
...........................................................................................................F...
[exec] ##### Unhandled Exception while running
ThoughtWorks.CruiseControl.Core.Test.ProjectIntegratorTest.TerminateCalledTwice
[exec] System.Threading.ThreadAbortException: Thread was being aborted.
[exec]
.....................................................................................N....N...............................................................................................................................................................................................................................N............................................
[exec] Tests run: 474, Failures: 1, Not run: 3, Time: 12.078125 seconds
[exec] 
[exec] Failures:
[exec] 1)
ThoughtWorks.CruiseControl.Core.Test.ProjectIntegratorTest.VerifySchedulerStateAfterException
: 
[exec]    at
ThoughtWorks.CruiseControl.Core.Test.ProjectIntegratorTest.VerifySchedulerStateAfterException()
in
d:\cmsynergy\sjansen\ccm_wa\wwdev\ThirdParty_Tools~ThirdParty_Tools_Dev_sjansen\ThirdParty_Tools\src\CruiseControl.NET\project\core\test\ProjectIntegratorTest.cs:line
148
---  END FAILURE #1  ---

--- START FAILURE #2 ---
[exec]
.........................................................................................................................[CruiseControl
Server:Error]: INTERNAL ERROR: 
[exec] 
MockIIntegratable.RunIntegration(ThoughtWorks.CruiseControl.Remote.BuildCondition)
called too many times
[exec] 
[exec]  expected:<0>
[exec]   but was:<1>
[exec] ----------
[exec] NMock.VerifyException: 
[exec] 
MockIIntegratable.RunIntegration(ThoughtWorks.CruiseControl.Remote.BuildCondition)
called too many times
[exec] 
[exec]  expected:<0>
[exec]   but was:<1>
[exec]    at NMock.MockNoCall.Call(String methodName, Object[]
actualArgs)
[exec]    at NMock.Method.Call(Object[] parameters)
[exec]    at NMock.Mock.Invoke(String methodName, Object[] args)
[exec]    at ProxyIIntegratable_8.RunIntegration(BuildCondition )
[exec]    at
ThoughtWorks.CruiseControl.Core.ProjectIntegrator.Integrate() in
d:\cmsynergy\sjansen\ccm_wa\wwdev\ThirdParty_Tools~ThirdParty_Tools_Dev_sjansen\ThirdParty_Tools\src\CruiseControl.NET\project\core\ProjectIntegrator.cs:line
121
[exec] ----------
[exec] 
[exec] 
[exec] ##### Unhandled Exception while running
ThoughtWorks.CruiseControl.Core.Test.ProjectIntegratorTest.ForceBuild
[exec] System.Runtime.Serialization.SerializationException: The type
NMock.VerifyException in Assembly nmock, Version=1.0.1721.15437,
Culture=neutral, PublicKeyToken=null is not marked as serializable.
[exec]
....................................................................................N....N...............................................................................................................................................................................................................................N............................................
[exec] Tests run: 473, Failures: 0, Not run: 3, Time: 9 seconds

---  END FAILURE #2  ---

On Thu, 20 Jan 2005 16:38:14 -0600, Bolles, James E
<Jam...@el...> wrote:
> Thanks for your email, Mike.  Here is a list of files that I changed and
> for what reason.  I can forward the files to someone if that would be
> easier so you can see them as well.
> 
> Located in project\core
> Project.cs
> - added IsInitialized property to check if the Initialize method has
> been called
> - In the Initialize() method, added logic to call
> SourceControl.Initialize and pass a reference to the Project so the base
> ProcessSourceControl.cs to be available to other sourcecontrol classes
> 
> ProjectIntegrator.cs
> - Added logic to check if the Project has been Initialized, if not, it
> calls the Initialize method. This was to simulate the same call used by
> CruiseServer.cs in the method AddProject.  Initialize is called here but
> not anywhere else.

Hi James,

Thanks for this again. I just want to follow up on the Initialize
stuff - what are you using this for? Initialize is currently used once
in the lifetime of a project, even across server restarts. It was
introduced to allow better remote administration by automating
environmental setups. For instance, with Perforce source control it
creates a 'Perforce Client Spec', with CVS it would do a 'cvs
checkout' (wheras normally CVS performs an 'update'). These things 
only ever need to be done once while the project is setup on that
build server.

We don't track the state of 'isInitialized' since we assume that a
project was either:
- created through the GUI and Initialize was called, or
- created manually by editting the config file, and any environment
requirements are setup manually.

Does this make sense? What were you trying to achieve? Maybe there's
an alternative I can suggest.

Mike

I'll take a look.

--- Mike Roberts <mik...@gm...> wrote:

> (re posted to ccnet-dev)
> 
> Are there any javascript experts on the list? JS is
> not one of my
> strong skills so any help would be appreciated! :)
> 
> Thanks,
> 
> Mike
> 
> On Fri, 21 Jan 2005 07:50:06 -0600, Steve Mitcham
> <Ste...@mp...> wrote:
> > When I click on the drill down arrows in the unit
> test details page.
> > The toggleDiv function is getting called twice,
> resulting in the arrow
> > remaining in the original state at the page load. 
> Can anyone tell me
> > why this is, and how to deal with it?  I know next
> to nothing about
> > javascript.
> 
> -- 
> mike roberts | http://mikeroberts.thoughtworks.net/
> |
> http://www.thoughtworks.com/
> 
> 
>
-------------------------------------------------------
> This SF.Net email is sponsored by: IntelliVIEW --
> Interactive Reporting
> Tool for open source databases. Create drag-&-drop
> reports. Save time
> by over 75%! Publish reports on the web. Export to
> DOC, XLS, RTF, etc.
> Download a FREE copy at
> http://www.intelliview.com/go/osdn_nl
> _______________________________________________
> Ccnet-devel mailing list
> Ccn...@li...
>
https://lists.sourceforge.net/lists/listinfo/ccnet-devel
>