ccnet-devel Mailing List for CruiseControl.NET

Message:

  A new issue has been created in JIRA.

---------------------------------------------------------------------
View the issue:
  http://jira.public.thoughtworks.org/browse/CCNET-166

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: CCNET-166
    Summary: Patch to Add UserName and Password to SVN Task
       Type: Improvement

     Status: Unassigned
   Priority: Major

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

    Project: CruiseControl .NET
 Components: 
             Builder

   Assignee: 
   Reporter: 

    Created: Mon, 30 Aug 2004 6:17 PM
    Updated: Mon, 30 Aug 2004 6:17 PM

Description:
51,56d50
 < 		[ReflectorProperty("username", Required = false)]
 < 		public string Username;
 <
 < 		[ReflectorProperty("password", Required = false)]
 < 		public string Password;
 <
 114,130c108
 <
 < 			System.Text.StringBuilder sb = new System.Text.StringBuilder();
 < 			sb.Append(string.Format(HISTORY_COMMAND_FORMAT, 
 FormatCommandDate(from), FormatCommandDate(to), _trunkUrl));
 < 			
 < 			if (this.Username != null && this.Username.Trim().Length > 0)
 < 			{
 < 				sb.Append(" --username ");
 < 				sb.Append(this.Username);
 < 			}
 <
 < 			if (this.Password != null && this.Password.Trim().Length > 0)
 < 			{
 < 				sb.Append(" --password ");
 < 				sb.Append(this.Password);
 < 			}
 <
 < 			return sb.ToString();
 ---
  > 			return string.Format(HISTORY_COMMAND_FORMAT, 
 FormatCommandDate(from), FormatCommandDate(to), _trunkUrl);
 135,156c113,114
 <
 < 			System.Text.StringBuilder sb = new System.Text.StringBuilder();
 < 			sb.Append(
 < 				string.Format(
 < 				TAG_COMMAND_FORMAT, label, _trunkUrl,
 < 				this._tagBaseUrl + "/" + label
 < 				)
 < 			);
 <
 < 			if (this.Username != null && this.Username.Trim().Length > 0)
 < 			{
 < 				sb.Append(" --username ");
 < 				sb.Append(this.Username);
 < 			}
 <
 < 			if (this.Password != null && this.Password.Trim().Length > 0)
 < 			{
 < 				sb.Append(" --password ");
 < 				sb.Append(this.Password);
 < 			}
 <
 < 			return sb.ToString();
 ---
  > 			string tagUrl = _tagBaseUrl + "/" + label;
  > 			return string.Format(TAG_COMMAND_FORMAT, label, _trunkUrl, tagUrl);


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.public.thoughtworks.org/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

Hi Uros,

Thanks for all of that! A couple of things

- Please can you read 
http://confluence.public.thoughtworks.org/display/CCNET/Contributor+License+Agreement 
and follow the instructions if you agree.
- Do you think we should change the 'include / exclude' configuration? 
It gets a bit confusing with all this new composite stuff. A 'Not' kind 
of ModificationFilter proxy might make more sense. I was thinking it 
might make sense to rename the 'Accept' method on IModificationFilter to 
'Matches' as well.

Cheers,

Mike

Uros Novak wrote:

>Hi,
>
>The patch file attached to previous message was incomplete.
>This one should be ok.
>
>Regards,
>Uros
>
> <<CCNET-140.patch>> 
>
>  
>
>> -----Original Message-----
>>From: 	Uros Novak  
>>Sent:	Thursday, August 26, 2004 4:01 PM
>>To:	'ccn...@li...'
>>Subject:	CCNET-140 (UserFilter)
>>
>>Hi,
>>
>>The attached patch contains three new IModificationFilter implementations,
>>which are described bellow.
>>
>>Regards,
>>Uros
>>
>>
>>UserFilter will filter modifications based on a list of usernames.
>>In the example bellow, any checkins made by user "foo" will trigger 
>>the build and all checkins by user "bar" will be ignored. If the
>>list of usernames is empty, then the modifications are rejected by
>>default.
>>
>>    <sourcecontrol type="filtered">
>>	    <sourceControlProvider type="vss" autoGetSource="true">
>>	      <project>$/Kunigunda/ServiceLocator</project>
>>	
>><workingDirectory>C:\CCNet\Kunigunda\ServiceLocator</workingDirectory>
>>	      <username>urosn</username>
>>	      <password></password>
>>	      <ssdir>c:\localvss</ssdir>
>>	    </sourceControlProvider>
>>	    <inclusionFilters>
>>	      <userFilter>
>>		<users>
>>	      		<scUser name="foo"/>
>>		</users>
>>	      </userFilter>
>>	    </inclusionFilters>
>>	    <exclusionFilters>
>>	      <userFilter>
>>		<users>
>>	      		<scUser name="bar"/>
>>		</users>
>>	      </userFilter>
>>	    </exclusionFilters>
>>    </sourcecontrol>
>>
>>
>>CompositeAndFilter will accept a modification only if all
>>configured child filters accept it.If there are no child filters,
>>then the modification is accepted by default. The example
>>configuration bellow will match any modifications to *.cs
>>files, commited by user "johndoe".
>>
>>
>>	<andAll>
>>		<filters>
>>			<pathFilter>
>>				<pattern>**/*.cs</pattern>
>>			</pathFilter>
>>			<userFilter>
>>				<users>
>>					<scUser name="johndoe"/>
>>				</users>
>>			</userFilter>
>>		</filters>
>>	</andAll>
>>
>>CompositeOrFilter will accept a modification if any of the
>>configured child filters accept it. If there are no child filters,
>>then the modification is accepted by default. The example
>>bellow will match any modifications to *.cs and *.asmx
>>files commited by user "johndoe".
>>
>>
>>	<andAll>
>>		<filters>
>>			<orAny>
>>				<pathFilter>
>>					<pattern>**/*.cs</pattern>
>>				</pathFilter>
>>				<pathFilter>
>>					<pattern>**/*.asmx</pattern>
>>				</pathFilter>
>>			<orAny>
>>			<userFilter>
>>				<users>
>>					<scUser name="johndoe"/>
>>				</users>
>>			</userFilter>
>>		</filters>
>>	</andAll>
>>
>>    
>>

Very impressive Tony.  I believe I may use this for the coming weeks.
Do you have a roadmap or goals for the application?  I'm curious as to
you plans for it as it could be a really nice tool.

-----Original Message-----
From: ccn...@li...
[mailto:ccn...@li...] On Behalf Of Tony
Bierman
Sent: Sunday, August 29, 2004 5:32 AM
To: ccn...@li...; bie...@bi...
Subject: [Ccnet-devel] CC Build Manager - rich client interface to
CruiseControl.NET Server

CC Build Manager provides .NET software developers with a rich client=20
interface to the CruiseControl.NET continuous integrated build=20
environment. CC Build Manager is based on the cctray application which=20
is distributed with CruiseControl.NET, and extends cctray's=20
functionality with 'Artifact Viewers' which allow developers quick=20
access to compiled HTML help files and the binaries releases created=20
during the continuous integrated build process. Just right-click on any=20
of the 'Artifact Viewers' to configure setting or view more help.=20
Additionally, the 'Build Status Webs' viewer provides developers with a=20
convenient point of management and monitoring for all projects=20
configured on the CruiseControl.NET build server.

BiermanWiki Page for CC Build Manager (screenshot):
http://www.biermana.org/wiki/index.php/CC%20Build%20Manager

Sourceforge download page for CC Build Manager:
https://sourceforge.net/project/showfiles.php?group_id=3D116367


Thanks,
Tony Bierman



-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=3D5047&alloc_id=3D10808&op=3Dclick
_______________________________________________
Ccnet-devel mailing list
Ccn...@li...
https://lists.sourceforge.net/lists/listinfo/ccnet-devel

The following comment has been added to this issue:

     Author: 
    Created: Mon, 30 Aug 2004 1:18 AM
       Body:
Thanks. That's exactly what I was looking for.
---------------------------------------------------------------------
View this comment:
  http://jira.public.thoughtworks.org/browse/CCNET-160?page=comments#action_10400

---------------------------------------------------------------------
View the issue:
  http://jira.public.thoughtworks.org/browse/CCNET-160

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: CCNET-160
    Summary: Modifications to SourceControl during build shouldn't cause rebuild
       Type: New Feature

     Status: Unassigned
   Priority: Major

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

    Project: CruiseControl .NET
 Components: 
             Source Control

   Assignee: 
   Reporter: 

    Created: Mon, 23 Aug 2004 6:36 AM
    Updated: Mon, 30 Aug 2004 1:18 AM

Description:
Build process should be able to modify files in source control (for example, write current build number in some file) and these changes don't cause another build to start.


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.public.thoughtworks.org/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

Message:

   The following issue has been resolved as WON'T FIX.

   Resolver: Mike Roberts
       Date: Sun, 29 Aug 2004 7:49 AM

Hi there. Delphi is something we won't be adding explicit support for in th=
e short or medium term, however you should be able to use the 'Command Line=
' Builder to run any compiler with a command line interface. Alternatively,=
 you can implement your own Delphi plugin by implementing the IBuilder inte=
rface.
---------------------------------------------------------------------
View the issue:
  http://jira.public.thoughtworks.org/browse/CCNET-164

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: CCNET-164
    Summary: Builder=E8=83=BD=E5=90=A6=E5=A2=9E=E5=8A=A0=E5=AF=B9Delphi=E7=
=9A=84=E6=94=AF=E6=8C=81=EF=BC=9F
       Type: New Feature

     Status: Resolved
   Priority: Major
 Resolution: WON'T FIX

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

    Project: CruiseControl .NET
 Components:=20
             Builder
   Versions:
             0.7

   Assignee:=20
   Reporter:=20

    Created: Fri, 27 Aug 2004 10:39 AM
    Updated: Sun, 29 Aug 2004 7:49 AM

Description:
I hope the builder can support other develope tools such as borland delphi.


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.public.thoughtworks.org/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

Hi Tony,

Thanks for that - it looks very cool. :) I've added a link to the=20
Resources section of the website at=20
http://confluence.public.thoughtworks.org/display/CCNET/Resources.

We're starting to include more artifact knowledge within the app (e.g.=20
'Artifact Directory' is now a configuration option, but currently 
used the XML Log Publisher), so you'll probably want to keep your eyes=20
peeled on development of the remote interface for any extra work you=20
want to do on CC Build Manager.

Cheers,

Mike

Tony Bierman wrote:

> CC Build Manager provides .NET software developers with a rich client=20
> interface to the CruiseControl.NET continuous integrated build=20
> environment. CC Build Manager is based on the cctray application which=20
> is distributed with CruiseControl.NET, and extends cctray=92s=20
> functionality with =91Artifact Viewers=92 which allow developers quick=20
> access to compiled HTML help files and the binaries releases created=20
> during the continuous integrated build process. Just right-click on=20
> any of the =91Artifact Viewers=92 to configure setting or view more hel=
p.=20
> Additionally, the =91Build Status Webs=92 viewer provides developers wi=
th=20
> a convenient point of management and monitoring for all projects=20
> configured on the CruiseControl.NET build server.=20

CC Build Manager provides .NET software developers with a rich client 
interface to the CruiseControl.NET continuous integrated build 
environment. CC Build Manager is based on the cctray application which 
is distributed with CruiseControl.NET, and extends cctray’s 
functionality with ‘Artifact Viewers’ which allow developers quick 
access to compiled HTML help files and the binaries releases created 
during the continuous integrated build process. Just right-click on any 
of the ‘Artifact Viewers’ to configure setting or view more help. 
Additionally, the ‘Build Status Webs’ viewer provides developers with a 
convenient point of management and monitoring for all projects 
configured on the CruiseControl.NET build server.

BiermanWiki Page for CC Build Manager (screenshot):
http://www.biermana.org/wiki/index.php/CC%20Build%20Manager

Sourceforge download page for CC Build Manager:
https://sourceforge.net/project/showfiles.php?group_id=116367


Thanks,
Tony Bierman

Message:

  A new issue has been created in JIRA.

---------------------------------------------------------------------
View the issue:
  http://jira.public.thoughtworks.org/browse/CCNET-165

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: CCNET-165
    Summary: Allow failed build to be numbered
       Type: Improvement

     Status: Unassigned
   Priority: Major

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

    Project: CruiseControl .NET
 Components: 
             Builder
   Versions:
             0.6.1

   Assignee: 
   Reporter: 

    Created: Fri, 27 Aug 2004 12:42 PM
    Updated: Fri, 27 Aug 2004 12:42 PM

Description:
In our environment, failed build artificats are stored under a build-number directory structure. We are unable to do this with Cruise Control without source modification.

I think it will be an easy and good configurable parameter to add to cruise control to continue to increment the build number, whether the build fails or passes.


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.public.thoughtworks.org/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

Message:

  A new issue has been created in JIRA.

---------------------------------------------------------------------
View the issue:
  http://jira.public.thoughtworks.org/browse/CCNET-164

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: CCNET-164
    Summary: Builder=E8=83=BD=E5=90=A6=E5=A2=9E=E5=8A=A0=E5=AF=B9Delphi=E7=
=9A=84=E6=94=AF=E6=8C=81=EF=BC=9F
       Type: New Feature

     Status: Unassigned
   Priority: Major

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

    Project: CruiseControl .NET
 Components:=20
             Builder
   Versions:
             0.7

   Assignee:=20
   Reporter:=20

    Created: Fri, 27 Aug 2004 10:39 AM
    Updated: Fri, 27 Aug 2004 10:39 AM

Description:
I hope the builder can support other develope tools such as borland delphi.


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.public.thoughtworks.org/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

The following comment has been added to this issue:

     Author: Loren Halvorson
    Created: Thu, 26 Aug 2004 8:05 AM
       Body:
Here is the stylesheet we are using for viewing the NAnt log. It works very nicely and includes color coding for warnings and errors, and a hyperlink that jumps you down directly to the error (when used with NAnt 0.85). You are certainly welcome to incorporate it into the project.
Thanks!
--Loren


<?xml version="1.0"?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0">

<xsl:output method="html"/>

<xsl:template match="/">
  <html>
  <head>
  <head><title>Build Log</title></head>
  <style>
  body, table, form, input, td, th, p, textarea, select
  {
      font-family: verdana, helvetica, arial;
      font-size: 11px;
  }
  </style>
  </head>
  <body>
    <xsl:apply-templates select="/cruisecontrol/build"/>
  </body>
  </html>
</xsl:template>

<xsl:template match="build">
  <table cellpadding="3" cellspacing="2" border="0" width="100%">
  <tr>
    <td colspan="3">
      <xsl:if test="buildresults/failure">
        Build Failed (<a href="#builderror">click to see error</a>)
      </xsl:if>
      <xsl:if test="not(buildresults/failure)">
        Build Complete
      </xsl:if>
    </td>
  </tr>
  </table>

  <table border="0" width="100%">
  <tr>
   <td>
    <xsl:apply-templates select="buildresults"/>
   </td>
  </tr>
  </table>

</xsl:template>

<xsl:template match="buildresults">
<table border="0">
 <tr>
  <td>
   <xsl:apply-templates/>
  </td>
 </tr>
</table>
</xsl:template>

<xsl:template match="target">
<table border="0">
 <tr>
  <td valign="top" colspan="2"><b><xsl:value-of select="@name"/>:</b></td>
 </tr>
 <tr>
  <td>&#160;</td>
  <td valign="top"><xsl:apply-templates/></td>
 </tr>
</table>
</xsl:template>

<xsl:template match="task">
<xsl:if test=".//message">
<xsl:choose>
<xsl:when test="@name!=''">
<table border="0">
 <tr>
  <td valign="top" colspan="2">[<xsl:value-of select="@name"/>]</td>
 </tr>
 <tr>
  <td>&#160;</td>
  <td valign="top"><xsl:apply-templates/></td>
 </tr>
</table>
</xsl:when>
<xsl:otherwise>
  <xsl:apply-templates/>
</xsl:otherwise>
</xsl:choose>
</xsl:if>

</xsl:template>

<xsl:template match="message">
 <font color="green"><xsl:value-of select="text()"/><br/></font>
</xsl:template>

<xsl:template match="message[(contains(text(), 'error') and not (contains(text(), '0 error')))]">
 <font color="red"><xsl:value-of select="text()"/><br/></font>
</xsl:template>

<xsl:template match="message[(contains(text(), 'warning') and not (contains(text(), '0 warning')))]">
 <font color="#FFCC00"><xsl:value-of select="text()"/><br/></font>
</xsl:template>

<xsl:template match="failure">
 <xsl:apply-templates/>
</xsl:template>

<xsl:template match="builderror">
 <a name="builderror">
 <font color="red"><xsl:value-of select="type"/><br/></font>
 <font color="red"><xsl:value-of select="message"/><br/></font>
 <font color="red"><br/>
 <xsl:if test="location/filename">
    <xsl:value-of select="location/filename"/>
    line: <xsl:value-of select="location/linenumber"/>
    col: <xsl:value-of select="location/columnnumber"/><br/>
 </xsl:if>
 </font>
 </a>
</xsl:template>

</xsl:stylesheet>
---------------------------------------------------------------------
View this comment:
  http://jira.public.thoughtworks.org/browse/CCNET-60?page=comments#action_10395

---------------------------------------------------------------------
View the issue:
  http://jira.public.thoughtworks.org/browse/CCNET-60

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: CCNET-60
    Summary: NAnt log view
       Type: Improvement

     Status: Unassigned
   Priority: Minor

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

    Project: CruiseControl .NET
 Components: 
             Web App
   Fix Fors:
             1.0
   Versions:
             0.6

   Assignee: 
   Reporter: Owen Rogers

    Created: Wed, 21 Apr 2004 5:39 AM
    Updated: Thu, 26 Aug 2004 8:05 AM

Description:
We should provide a link in the web app that will render the output from NAnt in a readable format.  Trying to read through the NAnt xml output is pretty tedious.


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.public.thoughtworks.org/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

Hi,

The patch file attached to previous message was incomplete.
This one should be ok.

Regards,
Uros

 <<CCNET-140.patch>> 

>  -----Original Message-----
> From: 	Uros Novak  
> Sent:	Thursday, August 26, 2004 4:01 PM
> To:	'ccn...@li...'
> Subject:	CCNET-140 (UserFilter)
> 
> Hi,
> 
> The attached patch contains three new IModificationFilter implementations,
> which are described bellow.
> 
> Regards,
> Uros
> 
> 
> UserFilter will filter modifications based on a list of usernames.
> In the example bellow, any checkins made by user "foo" will trigger 
> the build and all checkins by user "bar" will be ignored. If the
> list of usernames is empty, then the modifications are rejected by
> default.
> 
>     <sourcecontrol type="filtered">
> 	    <sourceControlProvider type="vss" autoGetSource="true">
> 	      <project>$/Kunigunda/ServiceLocator</project>
> 	
> <workingDirectory>C:\CCNet\Kunigunda\ServiceLocator</workingDirectory>
> 	      <username>urosn</username>
> 	      <password></password>
> 	      <ssdir>c:\localvss</ssdir>
> 	    </sourceControlProvider>
> 	    <inclusionFilters>
> 	      <userFilter>
> 		<users>
> 	      		<scUser name="foo"/>
> 		</users>
> 	      </userFilter>
> 	    </inclusionFilters>
> 	    <exclusionFilters>
> 	      <userFilter>
> 		<users>
> 	      		<scUser name="bar"/>
> 		</users>
> 	      </userFilter>
> 	    </exclusionFilters>
>     </sourcecontrol>
> 
> 
> CompositeAndFilter will accept a modification only if all
> configured child filters accept it.If there are no child filters,
> then the modification is accepted by default. The example
> configuration bellow will match any modifications to *.cs
> files, commited by user "johndoe".
> 
> 
> 	<andAll>
> 		<filters>
> 			<pathFilter>
> 				<pattern>**/*.cs</pattern>
> 			</pathFilter>
> 			<userFilter>
> 				<users>
> 					<scUser name="johndoe"/>
> 				</users>
> 			</userFilter>
> 		</filters>
> 	</andAll>
> 
> CompositeOrFilter will accept a modification if any of the
> configured child filters accept it. If there are no child filters,
> then the modification is accepted by default. The example
> bellow will match any modifications to *.cs and *.asmx
> files commited by user "johndoe".
> 
> 
> 	<andAll>
> 		<filters>
> 			<orAny>
> 				<pathFilter>
> 					<pattern>**/*.cs</pattern>
> 				</pathFilter>
> 				<pathFilter>
> 					<pattern>**/*.asmx</pattern>
> 				</pathFilter>
> 			<orAny>
> 			<userFilter>
> 				<users>
> 					<scUser name="johndoe"/>
> 				</users>
> 			</userFilter>
> 		</filters>
> 	</andAll>
> 

Hi,

The attached patch contains three new IModificationFilter implementations,
which are described bellow.

Regards,
Uros


UserFilter will filter modifications based on a list of usernames.
In the example bellow, any checkins made by user "foo" will trigger 
the build and all checkins by user "bar" will be ignored. If the
list of usernames is empty, then the modifications are rejected by
default.

    <sourcecontrol type="filtered">
	    <sourceControlProvider type="vss" autoGetSource="true">
	      <project>$/Kunigunda/ServiceLocator</project>
	
<workingDirectory>C:\CCNet\Kunigunda\ServiceLocator</workingDirectory>
	      <username>urosn</username>
	      <password></password>
	      <ssdir>c:\localvss</ssdir>
	    </sourceControlProvider>
	    <inclusionFilters>
	      <userFilter>
		<users>
	      		<scUser name="foo"/>
		</users>
	      </userFilter>
	    </inclusionFilters>
	    <exclusionFilters>
	      <userFilter>
		<users>
	      		<scUser name="bar"/>
		</users>
	      </userFilter>
	    </exclusionFilters>
    </sourcecontrol>


CompositeAndFilter will accept a modification only if all
configured child filters accept it.If there are no child filters,
then the modification is accepted by default. The example
configuration bellow will match any modifications to *.cs
files, commited by user "johndoe".


	<andAll>
		<filters>
			<pathFilter>
				<pattern>**/*.cs</pattern>
			</pathFilter>
			<userFilter>
				<users>
					<scUser name="johndoe"/>
				</users>
			</userFilter>
		</filters>
	</andAll>

CompositeOrFilter will accept a modification if any of the
configured child filters accept it. If there are no child filters,
then the modification is accepted by default. The example
bellow will match any modifications to *.cs and *.asmx
files commited by user "johndoe".


	<andAll>
		<filters>
			<orAny>
				<pathFilter>
					<pattern>**/*.cs</pattern>
				</pathFilter>
				<pathFilter>
					<pattern>**/*.asmx</pattern>
				</pathFilter>
			<orAny>
			<userFilter>
				<users>
					<scUser name="johndoe"/>
				</users>
			</userFilter>
		</filters>
	</andAll>


 <<CCNET-140.patch>> 

I just reworked subject formatting. It uses xslt transformation now. It is
pretty powerful and still easy to use and maintain so I think it's reach its
goal.

To get it worked, just add:
				<email ...>
					<subject>xsl/subject.xsl</subject>
				</email>
to email publisher and copy subject.xsl into xsl directory. Maybe we could
supply one in main distribution?


just one note: it could be good to move code for XPathDocument creating
directly to IntegrationResult class, since it is created several times now
(email body formatting, subject formatting and <when> expressions). More may
come in future...

Martin

> > >  - initial implementation of subject formatting (subject)
> > >  
> > >
> > Can you give an example?
>  
> See example upwards.
> 
> > >I was thinking about subject formatting a little further and
> > don't know
> > >whether choose this scenario (custom string, replace,
> > reflection) or to
> > >use xslt somehow. It could be harder to implement but could
> > bring all
> > >power of xslt/xpath/expressions etc. Moreover, we use xslt 
> for body 
> > >formatting already so it will be more consistent. What do 
> you think?
> > >  
> > >
> > OK, I'm not entirely sure what kind of formatting you want, 
> but I'd be 
> > surprised if we needed to use reflection or XSLT to 
> generate it - can 
> > you elaborate (just giving examples may be enough)
> 
> I think about it a little further and XSLT is not such bad 
> idea after all. A little big tool into one string but why 
> not? What is goal to this is to enable what text should be in 
> the subject of sent emails and this should be configured very 
> loosely. In our development team is e.g. big call that 
> subject line contain names of modifiers. Others will have  
> another requests like localization, custom properties, 
> count-of-failed-test etc etc etc... I
> know: it is all in the body, but subject is of the same importance!
> 
> Martin

Hello all,

As I already promised, I implement new publisher <when>. It only redirects
all publishing stuff to other publishers but it checks some condition
before. Here is example what is possible:

<publishers>
      <xmllogger>
        <logDir>c:\foo\log</logDir>
	</xmllogger>
	<when>
		<isTrue>/cruisecontrol/@status='Success'</isTrue>
		<do>
			<email mailhost="foo.com" includeDetails="TRUE">
			  <from>tes...@fo...</from>
			  <toGroup>gr1</toGroup>
			  <subject>TEST: success!</subject>
			  <configFile>c:\foo\users.xml</configFile>
			</email>
		</do>
	  </when>
	<when>
		<isTrue>/cruisecontrol/@status='Failure'</isTrue>
		<do>
			<email mailhost="foo.com" includeDetails="TRUE">
			  <from>tes...@fo...</from>
			  <toGroup>gr1</toGroup>
			  <subject>TEST: failed!</subject>
			  <configFile>c:\foo\users.xml</configFile>
			</email>
		</do>
	  </when>
</publishers>

As an expression engine I use XPath over integration-results XML (exactly
one what is logged out in xmllogger). All xpath expression syntax is
possible, including functions, operators, queries, etc.


Implementation note: I add 3 new attributes to main XML tag since it was
impossible to query status of current and last integration and current label
number.

No tests/documentation in current state, but I'll add it if you like this
implementation.


Martin

Hi Mike,

> >  - allow user to be in more than 1 group (I hope for better 
> >administration)
> >
> You're right in that I'm surprised we didn't already support 
> this. My question is though what kind of situation have you 
> got that you need it?

Subscribing system again (see CCNET-154).
 
> >  - direct send to group (toGroup)
> >  
> >
> Umm, I'm not sure what you mean by this.

see this example:

<email mailhost="mailhost.foo.com" >
		  <from>tes...@fo...</from>
		  <toGroup>gr1</toGroup>
		  <subject>TEST: ${ModifiersDisplay} ${ProjectName}
${ExtendedBuildState}: Build ${Label}</subject>
		  <configFile>c:\ccnet\users.xml</configFile>
   		  <projectUrl>http://soon.to/be.removed</projectUrl>
</email>

it should email integration results to group "gr1" which is defined in
users.xml file. Not much usable today but I plan to use it with conditional
filtering publisher like:

<publishers>
  <when state="success">
    <email toGroup="gr1"/>
 </when>
 <when state="failed" containsComponent="xxx" 
whatevercondition="true" >
   <email toGroup="gr2"/>
 </when>
</publishers>

This should satisfy calls for better conditioning than always/change group
notify option (see CCNET-150, CCNET-153)

> >  - initial implementation of subject formatting (subject)
> >  
> >
> Can you give an example?
 
See example upwards.

> >I was thinking about subject formatting a little further and 
> don't know 
> >whether choose this scenario (custom string, replace, 
> reflection) or to 
> >use xslt somehow. It could be harder to implement but could 
> bring all 
> >power of xslt/xpath/expressions etc. Moreover, we use xslt for body 
> >formatting already so it will be more consistent. What do you think?
> >  
> >
> OK, I'm not entirely sure what kind of formatting you want, 
> but I'd be surprised if we needed to use reflection or XSLT 
> to generate it - can you elaborate (just giving examples may 
> be enough)

I think about it a little further and XSLT is not such bad idea after all. A
little big tool into one string but why not? What is goal to this is to
enable what text should be in the subject of sent emails and this should be
configured very loosely. In our development team is e.g. big call that
subject line contain names of modifiers. Others will have  another requests
like localization, custom properties, count-of-failed-test etc etc etc... I
know: it is all in the body, but subject is of the same importance!

Martin

The following comment has been added to this issue:

     Author: Martin Aliger
    Created: Wed, 25 Aug 2004 12:23 AM
       Body:
Situation is such that I want to make some (external) system with subscribing into ccnet builds. User should be able to subscribe all emails with e.g. successful build of project xxx or failed builds of project yyy in what subcomponent zzz was changed etc.

To enable this I have to have several groups and many users in them (possibly in more than 1). I need to generate this configuration somehow and we propably agree that is not the best idea to generate main ccnet.config file from some external system.

I also tried so fool it with <!ENTITY> xml thing but it dont work since xml parser is switched into validating mode. DTD have to contain all elements and it isn't easily possile with dynamic reflection ccnet uses.
---------------------------------------------------------------------
View this comment:
  http://jira.public.thoughtworks.org/browse/CCNET-154?page=comments#action_10393

---------------------------------------------------------------------
View the issue:
  http://jira.public.thoughtworks.org/browse/CCNET-154

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: CCNET-154
    Summary: email publisher users/groups should be configurable externally
       Type: Improvement

     Status: Unassigned
   Priority: Minor

 Original Estimate: 3 hours
 Time Spent: Unknown
  Remaining: 3 hours

    Project: CruiseControl .NET
 Components: 
             Publisher
   Versions:
             1.0

   Assignee: 
   Reporter: Martin Aliger

    Created: Wed, 18 Aug 2004 9:48 AM
    Updated: Wed, 25 Aug 2004 12:23 AM

Description:
Today users and user groups are stored in project configuration (ccnet.config file). This information is usually shared between projects so it would be better to store this in external (xml) file and give email publisher just URL to it. This could further increase usability because this xml could be generated via web service / edited by external tools etc.


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.public.thoughtworks.org/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

The following comment has been added to this issue:

     Author: Loren Halvorson
    Created: Tue, 24 Aug 2004 8:38 PM
       Body:
Thanks Mike,
I like your idea of doing a source control proxy that looks for a semaphore file, I don't think that will be too hard to implement.

As far as why, I'll try to explain as best I can. We have two builds set up in CCNET for the same application, one full, and one continuous. The builds are done in two different directories; the continuous build runs when VSS reports changes, and the full runs on a nightly schedule. The full builds are often kicked off on demand throughout the day. The full builds have additional labelling and promotion/archiving step that the continous builds do not (the continous builds are supposed to be lighter-weight throwaway builds).

It's a large application with dozens of solution files that takes about 1 hour to build start to finish. It includes several ASP.NET web apps and quite a few MSI projects. We do a majority of the building using NAnt's <solution> task which works beautifully (mostly). The biggest trouble is caused by the MSI projects because we have to <exec> devenv.com to create them.

1) it bogs down the machine greatly when you get multiple builds running, so it would be nice to serialize them.
2) the two builds compete for the same IIS virtual directory, which must exist when you open the solution in devenv, so I currently have to dynamically create the IIS VDIR just before I launch devenv, and hope the other build stays away from that part of the build until the MSI is created.
3) the MSI projects pull binaries from a single VSWebCache location (don't ask me why it doesn't pull the binary from under the built location), so again, if they happen to be at the same step of the build they could get the wrong binaries.
4) some of the C++ components are being compiled by <exec>ing VC6 (msdev) and once in a while they fail because they don't like to be kicked off from two different locations simultaneously because they act like they compete for shared temporary file space (haven't figured out exactly why but every now and then I get LINK : fatal error LNK1104: cannot open file "C:\DOCUME~1\awbuild\LOCALS~1\Temp\lnk2")

If I could guarantee the two builds never run at the same time, I could run them in the same directory and solve quite a few of these issues.

OR if you can suggest an alternate way to set up a single CCNET project that can switch between continous/full mode, it would also solve it.
Thanks
--Loren


---------------------------------------------------------------------
View this comment:
  http://jira.public.thoughtworks.org/browse/CCNET-163?page=comments#action_10392

---------------------------------------------------------------------
View the issue:
  http://jira.public.thoughtworks.org/browse/CCNET-163

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: CCNET-163
    Summary: Pausing another build while one is running
       Type: Improvement

     Status: Unassigned
   Priority: Minor

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

    Project: CruiseControl .NET
 Components: 
             Schedule
   Versions:
             0.6.1

   Assignee: 
   Reporter: Loren Halvorson

    Created: Tue, 24 Aug 2004 10:35 AM
    Updated: Tue, 24 Aug 2004 8:38 PM

Description:
I would like to have a way to prevent certain builds from running at the same time. I have no idea how this would be implemented, but essentially I'd like to specify that Builds A1 and A2 should never kick in while Build A3 is running, however B1 and B2 are free to run any time. As soon as A3 completes A1 and A2 can proceed. This would be sort of like putting a critical section around builds that compete for a shared resource or directory on the build server.

If this is possible today with some type of trickery that I am unaware of, please let me know how to do it.
Thanks


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.public.thoughtworks.org/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

The following comment has been added to this issue:

     Author: Mike Roberts
    Created: Tue, 24 Aug 2004 12:24 PM
       Body:
Hi Loren,
This is an interesting request. :) Firstly, I'd be interested in why you want to do this, but I guess that wouldn't help you.
The short answer is no, CCNet can't do this right now. Our scheduling/queueing code is probably a fair way away from doing it aswell. One 'hack' I can think of suggesting is that you write a ModificationChecker proxy, like the 'Multi' and 'Filter' source controls. Your 'A3' build could write a 'lock' file at the start of a build (and delete it at the end), and you could configure the 'CheckForLockModificationChecker' to return 0 modifications if such a lock exists.
That is a bit nasty, but I don't think we'll be implementing this kind of thing explicitally until after 1.0
---------------------------------------------------------------------
View this comment:
  http://jira.public.thoughtworks.org/browse/CCNET-163?page=comments#action_10391

---------------------------------------------------------------------
View the issue:
  http://jira.public.thoughtworks.org/browse/CCNET-163

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: CCNET-163
    Summary: Pausing another build while one is running
       Type: Improvement

     Status: Unassigned
   Priority: Minor

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

    Project: CruiseControl .NET
 Components: 
             Schedule
   Versions:
             0.6.1

   Assignee: 
   Reporter: Loren Halvorson

    Created: Tue, 24 Aug 2004 10:35 AM
    Updated: Tue, 24 Aug 2004 12:24 PM

Description:
I would like to have a way to prevent certain builds from running at the same time. I have no idea how this would be implemented, but essentially I'd like to specify that Builds A1 and A2 should never kick in while Build A3 is running, however B1 and B2 are free to run any time. As soon as A3 completes A1 and A2 can proceed. This would be sort of like putting a critical section around builds that compete for a shared resource or directory on the build server.

If this is possible today with some type of trickery that I am unaware of, please let me know how to do it.
Thanks


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.public.thoughtworks.org/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

Martin Aliger wrote:

>Hi again,
>
>I just make some more changes to email publisher:
>  - allow user to be in more than 1 group (I hope for better administation)
>  
>
You're right in that I'm surprised we didn't already support this. My 
question is though what kind of situation have you got that you need it?

>  - display name of user (not used yet - planned for subject formatting)
>  
>
Yup, sounds good

>  - direct send to group (toGroup)
>  
>
Umm, I'm not sure what you mean by this.

>  - initial implementation of subject formatting (subject)
>  
>
Can you give an example?

>I was thinking about subject formatting a little further and dont know
>whether choose this scenario (custom string, replace, reflection) or to use
>xslt somehow. It could be harder to implement but could bring all power of
>xslt/xpath/expressions etc. Moreover, we use xslt for body formatting
>already so it will be more consistent. What do you think?
>  
>
OK, I'm not entirely sure what kind of formatting you want, but I'd be 
surprised if we needed to use reflection or XSLT to generate it - can 
you elaborate (just giving examples may be enough)

Cheers,

Mike

The following comment has been added to this issue:

     Author: Mike Roberts
    Created: Tue, 24 Aug 2004 12:14 PM
       Body:
I would rather not make CCNet have to use external config files right now, but I understand your pain. 2 things I can suggest:
1 - How many instances of CCNet are you running? If its only a few, but you are running many builds on each server, we could make this kind of thing 'server config', e.g. a Server has a 'EmailDirectory' (Directory in the lookup sense, not a file sense), and this could be overridable in  the Email Task
2 - Following on, an alternative implementation of 'IEmailDirectory' could look at a file, query a web service, or integrate with a mail server (LDAP, Exchange, whatever).
---------------------------------------------------------------------
View this comment:
  http://jira.public.thoughtworks.org/browse/CCNET-154?page=comments#action_10390

---------------------------------------------------------------------
View the issue:
  http://jira.public.thoughtworks.org/browse/CCNET-154

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: CCNET-154
    Summary: email publisher users/groups should be configurable externally
       Type: Improvement

     Status: Unassigned
   Priority: Minor

 Original Estimate: 3 hours
 Time Spent: Unknown
  Remaining: 3 hours

    Project: CruiseControl .NET
 Components: 
             Publisher
   Versions:
             1.0

   Assignee: 
   Reporter: Martin Aliger

    Created: Wed, 18 Aug 2004 9:48 AM
    Updated: Tue, 24 Aug 2004 12:14 PM

Description:
Today users and user groups are stored in project configuration (ccnet.config file). This information is usually shared between projects so it would be better to store this in external (xml) file and give email publisher just URL to it. This could further increase usability because this xml could be generated via web service / edited by external tools etc.


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.public.thoughtworks.org/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

Martin Aliger wrote:

> what about to move "No modifications detected." message into Debug 
> trace-level? My log is full of this message (becouse of I have 1 
> minute schedulling). I also think that tracelevel should be set to 
> "Info" in distributed .config (developers could set it to debug). 
> CCNetlive server log seems to be same as mine ;-)

+1 for me. Anyone else?

Message:

  A new issue has been created in JIRA.

---------------------------------------------------------------------
View the issue:
  http://jira.public.thoughtworks.org/browse/CCNET-163

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: CCNET-163
    Summary: Pausing another build while one is running
       Type: Improvement

     Status: Unassigned
   Priority: Minor

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

    Project: CruiseControl .NET
 Components: 
             Schedule
   Versions:
             0.6.1

   Assignee: 
   Reporter: Loren Halvorson

    Created: Tue, 24 Aug 2004 10:35 AM
    Updated: Tue, 24 Aug 2004 10:35 AM

Description:
I would like to have a way to prevent certain builds from running at the same time. I have no idea how this would be implemented, but essentially I'd like to specify that Builds A1 and A2 should never kick in while Build A3 is running, however B1 and B2 are free to run any time. As soon as A3 completes A1 and A2 can proceed. This would be sort of like putting a critical section around builds that compete for a shared resource or directory on the build server.

If this is possible today with some type of trickery that I am unaware of, please let me know how to do it.
Thanks


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.public.thoughtworks.org/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

Hi again,

I just make some more changes to email publisher:
  - allow user to be in more than 1 group (I hope for better administation)
  - display name of user (not used yet - planned for subject formatting)
  - direct send to group (toGroup)
  - initial implementation of subject formatting (subject)

I was thinking about subject formatting a little further and dont know
whether choose this scenario (custom string, replace, reflection) or to use
xslt somehow. It could be harder to implement but could bring all power of
xslt/xpath/expressions etc. Moreover, we use xslt for body formatting
already so it will be more consistent. What do you think?

Martin

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

Hello,

attached file contains possible implementation of this request.

since NetReflector have not (or I didn't find) feature to get properties on
ReflectorHash, I implement it as distinct element named "configFile". So
with it you could have:

	<publishers>
	  <email mailhost="mailhost.foo.com" includeDetails="TRUE">
		  <from>ba...@fo...</from>
		  <projectUrl>http:/soon.to.be.removed/i.hope</projectUrl>
		  <configFile>c:\ccnet\users.xml</configFile>
      </email>
    </publishers>

and users.xml: (2 ways to specify users)

<groups>
	<group name="gr1">
          <user name="al"  address="a1...@fo..."/>
	</group>

	<user name="a2"  group="gr1" address="a2...@fo..."/>
</groups>

Martin

Hi,
 
what about to move "No modifications detected." message into Debug
trace-level? My log is full of this message (becouse of I have 1 minute
schedulling). I also think that tracelevel should be set to "Info" in
distributed .config (developers could set it to debug). CCNetlive server log
seems to be same as mine ;-)
 
 
Martin