CCNetConfig

Slinky Styles was added to Q101's Local Online Music Section. You can go there and hear "Custom Reality" performed by Slinky Styles. If you like that song or other songs by them, or just want to help support local music, go to Q101 and Vote for Slinky Styles.

CCnetConfig 0.2.3.2 was released today via auto update and on CodePlex. There were a lot of little bug fixes. Also the custom ccnetconfigType attribute was removed from all elements. This attribute was used to help in the deserialization of the elements but ended up causing ccnet to complain about unused nodes so it has been removed.


Here are the issues associated with this release.

I published release 0.2.2.2 to auto update yesterday. This release fixes an issue with the multiTriggers. I swear these are the worst damn section in the entire configuration. Some other issues like a bug in the saving of a NAnt task were addressed. As of this post, these issues are still marked as open, they are resolved, I didn't close them because I have not yet released on codeplex and I want the issues to be assigned to a release. I have some other issues to look at and have some things with the Property editor that I want to address before the next release on codeplex.

CCNetConfig 0.2.1.6 has been released via automatic updates and CodePlex.

Issues resolved in this release:

Someone reported that CCNetConfig will not run on an x64 machine. I do not have access to 64 bit machine so I am asking that if anyone has access to such a machine and can attempt to run CCNetConfig on the machine and please confirm this issue. If indeed it will not run, please either contact me ( see the contact link on the home page ) or post a comment here.

Do you want to contribute to CCNetConfig? There are 4 levels of contributors for the CCNetConfig Project.

1. User
• By using CCNetConfig and using the Submit Bug Dialogs you are contributing to the project.
2. Contributor
• To become a contributor you have to create an account on CodePlex. Being a contributor does not allow you to commit changes to the source control but it does allow you to post on the forums, create issues and post patches via the issue tracker. Anyone can become a contributor, all you have to do is register on CodePlex.
3. Developer
• A developer on the CCNetConfig team must first be a contributor. This is a requirement of CodePlex, only registered users of CodePlex can be assigned as a developer on a project. A developer has all the privileges that a contributor has plus a developer has the ability to commit changes in source control. To become a developer you can request access on the Developer Access Request Forum.
4. Project Lead
• A Project Lead has all the access and roles that a developer has, plus the ability to add and remove team members, edit the wiki pages, create / edit releases etc. The Project Lead role requires a great deal of dedication, involvement, effort and initiative. Project leads are responsible for the overall direction of the project, community management (PR) and can act as a "tie breaker" in situations where a decision  can not be agreed upon. There will be no more then 3 project leads at any given time. A developer must be recommended  by another developer or project lead to be eligible for that role as well as be willing to accept the responsibility of the role. All current project leads and a majority of the developer community must approve the person to be a project lead. This is to ensure the candidate is the right person for the project.

If you are interested in becoming a developer on the CCNetConfig team please post a request on the Developer Access Request Forum.

Martin Woodward has released a new build of the TFS Plugin for CCNet 1.1. With the release of CCNet 1.1, the TFS plugin no longer worked with CCNet. You can find documentation for the TFS plugin on the CCNet Documentation site. There is also an article by Martin on how to configure CCNet with the TFS Plugin for use with CodePlex. But really, the easiest way is to use CCNetConfig, then you don't have to worry about what elements you need to set, which are required and which ones are optional, all you have to worry about is what values you need to enter for these elements.

I fixed a couple issues reported yesterday. These fixes are currently available in the latest nightly build. Below is a list of some of the fixes.

• SubVersion Source Control
  
• Fixed bug with saving. This would fail due to WebUrlBuilder not being set.
  
• Fixed bug with not being able to modify WebUrlBuilder. The TypeConverter for WebUrlBuilder was not set so there was no way to modify the WebUrlBuilder. The WebUrlBuilder works correctly in the CVS Source Control.
  
• CCNet Project
• Fixed bug with ArtifactDirectory Element created in configuration file even if this field is left blank.
• Fixed bug with WorkingDirectory Element created in configuration file even if this field is left blank.
• Fixed bug with multiTriggers not loading from configuration file. The saving of multiTriggers was fixed a while back but saving was not addressed.
  

These fixes will be part of the next beta release, which should be released by 10/28/2006.

0.2.1.3 has been released via CodePlex and automatic updates. Mostly fixes to bugs submitted via the bug submission.

• Change External Links Property text to the number of items
• IListTypeConverter displays "items" no matter how many there are
• ScrollWheel on bool? property items displays error
• Extra attributes on some xml nodes
• XmlLogger creates empty string attribute for logdir

I have also been working on the project extension example based on Jay Flowers custom CCNet build. Once I get more done with this I will start posing source and binaries for this extension.

Just wanted to say thank you to all that have been submitting Bugs, Issues, Feature requests and possible issues with CCNetConfig. By submitting these, it helps us create and maintain a better product for everyone. So please continue to submit these so we can correct, address, or implement them as quickly as possible. Again, Thank you!

Mads Kristensen has posted an interesting solution to having variables and scripting in CSS. The handler allows you to create variables and assign values to them based on the browser type and version. The output is clean CSS. He has included an .ashx and a .cs files in the article.

New release of CCNetConfig is available via Updates and CodePlex. Changes include:

• Changed copyright in documentation
• Added ability to collapse the documentation browser
• Fixed the "Report Bug" Help Menu item
• Fixed the Password field in the AlienBrain SourceControl provider
• Fixed the issue that locks and erases the config file is all required values are not complete.
• Added Unhandled Exception Bug Submission
• Added Optional Email field for bug submission
• Added Optional Config File field for bug submission
  

I wanted to talk about some of the changes I made to the latest build ( 0.2.0.5 ). Most of the changes have to do with the error trapping and bug submission to make any exceptions that may occur during your use of the application less intrusive. The first change is the "catch all" exception handler. The dialog below will appear if there is an exception that stops CCNetConfig from working correctly:



This dialog give you the option to submit this error as a bug. You can also expand the dialog to see the details of the error.



Clicking Continue will just close the dialog and the application will continue on its task. If you choose to submit the bug, it will submit the complete stack trace and it will attempt to send the configuration information, if it exists and not part of the error, as the details of the bug. The configuration is not viewable by anyone other then the developers of CCNetConfig. By adding this dialog, it will simplify the bug submission process so we can get a better description of the error and the configuration file causing the error.


Also the manual bug submission dialog has had some changes. Added is the option to add your contact email address. This will allow the CCNetConfig developers to contact you to either notify you of the issue being resolved, or to ask for further information about the bug, if you have it. The option of attaching your configuration file that you attempted to load or the configuration file that CCNetConfig created. This again will give more information on what is causing the bug and help resolve the issue faster.



Version 0.2.0.5 is available for download as a Latest Nightly Release

As i write this another build ( 0.2.0.4 ) being created by CCNet. This build fixes even more issues with loading config files. I fixed the issue with using a config like the following:

<?xml version="1.0"?>
<!DOCTYPE cruisecontrol [
<!ENTITY NDOC.PROJ SYSTEM "file:CCNet.NDOC.PROJ.xml">
]>
<cruisecontrol>
	&NDOC.PROJ;
</cruisecontrol>

and in CCNet.NDOC.PROJ.xml you have something like the following

<project name="NDOC.PROJ">
	<webURL>http://localhost/ccnet</webURL>
	<modificationDelaySeconds>60</modificationDelaySeconds>
	<publishExceptions>true</publishExceptions>
	<triggers>
		<scheduleTrigger time="08:15" buildCondition="ForceBuild">
			<weekDays>
				<weekDay>Saturday</weekDay>
			</weekDays>
		</scheduleTrigger>
	</triggers>
	<state type="state" directory="C:\CCNetState"/>	
	<labeller type="defaultlabeller">
		<prefix>NDOC-PROJ-</prefix>
	</labeller>
	
	<tasks>
		<nant>
			<baseDirectory>C:\NAnt</baseDirectory>
			<executable>bin\nant.exe</executable>
			<nologo>true</nologo>
			<buildFile>buildfiles\IS2009DocumentationMain.build</buildFile>
			<logger>NAnt.Core.XmlLogger</logger>
			<targetList>
				<target>createdoc.PROJ</target>
			</targetList>
			<buildTimeoutSeconds>54000</buildTimeoutSeconds>
		</nant>
	</tasks>
	
	<publishers>
		<merge>
			<files>
			</files>
		</merge>
		<xmllogger>
			<logDir>C:\CCNetLog</logDir>
		</xmllogger>
	</publishers>
	
	<externalLinks>
		<externalLink name="PROJ help file" url="http://localhost:20092/PROJ/PROJ.chm"/>
	</externalLinks>
</project>

I have also corrected an issue if there is no timeout configured for VSS source control. This version will come via automatic updates if you have a previous version or you can get it from the usual place.

A new version of CCNetConfig is now available on CodePlex. This version does not yet address anything for CCNet 1.1. It just has a couple bug fixes including the Visual SourceSafe save issue. I am in the process of fixing some of the SubVersion bugs that were reported as well. These should be included in the next nightly build tomorrow.

I want to say that I really like InstallPad but I wish it supported proxy authentication.

Since the announcement of CCNet 1.1 on October 1st I will be installing the latest version and testing CCNetConfig out to see if there are any changes or additions that need to be made. I am still testing and attempting to reproduce bugs that were submitted. Once I solve these issues there should be some new builds available.

I also want to say that if anyone will be in the ChicagoLand area on Friday, October 6th 2006, Slinky Styles will be part of the Emergenza Festival that will be going on at The Note ( 1565 N. Milwaukee Ave. Chicago IL  60622 ). It is $15 at the door. Stop by and help Slinky Styles move on to the next round of the Festival.

I have included a performance of Slinky Styles from 9/16/06. I think the person filming this was a little drunk...

I haven't been too active recently with checkins or builds of CCNetConfig or posting here. I have been busy with a project for work to generate random data for SQL server tables. That project has been fun and challenging. I have also been trying to work on some of the bugs that have been reported for CCNetConfig. Some have not been going to well, if you have any problems with CCNet.config files, if you could email the config file to me (removing any info you dont want me to have of course. It's not really the values but more of the structure i need anyhow) at camalot+ccnetconfig(AT)gmail.com or submit the config via the bug submission.