ccnet-devel Mailing List for CruiseControl.NET

Hi all,=20

    I am trying to develop a plugin for vmware. I looked at the wiki
site for more information about NetReflector
(http://confluence.public.thoughtworks.org/display/NETREFLECTOR/NetRefle
ctor+Home+Page) and the content is empty at the moment. Is there any
reference manual that I can refer to?=20

=20

Many thanks,

chuan

Software Test Engineer

Citrix Systems
Cambourne Business Park
Cambridge CB3 6DW

=20

>
> Not sure if there is any further development planned to CruiseControl.Net,
> but if there is could I suggest that the ability to click one button on the
> dashboard to force all project builds in the order they are listed be added.
>
Hi Mitch

if you need to implement something like that you may want to have a look
here :

http://confluence.public.thoughtworks.org/display/CCNET/How+to+force+a+CCNet+build+from+a+NAnt+script

hth

Thibaut

Hi

=20

Not sure if there is any further development planned to
CruiseControl.Net, but if there is could I suggest that the ability to
click one button on the dashboard to force all project builds in the
order they are listed be added.

=20

Regards,

Mitch Wheat

On 6/26/06, Perry Ismangil <pe...@is...> wrote:
>
> There's an old issue http://jira.public.thoughtworks.org/browse/CCNET-495
> that's still bugging me.
>
>
I've been looking into this, and I noticed in IntegrationRunner.PostBuild it
published and then finish integration which is saving state. I am thinking
of moving the finish integration to before publishing, do you all think this
is the right logic. After all publishing is mean after an integration is
finished, right?

-- 
Perry Ismangil
Indonesia Quake & Flood Appeal http://www.portalinfaq.org.uk

Hi,

I was having trouble searching the archives, so I don't know if this
topic has been discussed previously.

I am having some trouble with CC.Net missing some files that I checked
into VSS. I have researched it and I think I have found the problem.

Basically, when files are retrieved from VSS the file modification date
is set to the "VSS modification date" of the file. I believe this is
incorrect. Let me give you a scenario: You kick of a build at 1PM. The
source files are retrieved. During the build you check in a file at
1:05PM. The build finishes at 1:10PM. At 1:30 you kick off the next
build. The modification date of the file you checked is set to 1:05 (the
VSS modification date). The timestamp on the assembly is 1:10 (the time
of the last build). So, even though the file has changed, the assembly
will not recompile because the modification times of the files are out
of sync.

So, long story short: by setting the date of the file to the
modification date, it is out of sync.

Solution: set the modification date of the file to the time of the get.

Source: [I'm pretty new to CC.Net, so I might be off here]
In core\sourcecontrol\vss.cs in method GetSourceArgs() Line 124 is:
    builder.AppendArgument("-I-N -W -GF- -GTM");
This should be:
    builder.AppendArgument("-I-N -W -GF- -GTC");

Here is a page on the command line args:
http://msdn2.microsoft.com/en-us/203a56wa.aspx

Please let me know if you have any questions or suggestions.

(I sent this originally from the wrong email address, so it didn't make 
it to the list. Sorry in advance if you get 2 copies.)

Thanks,
Don

Hi,

I was having trouble searching the archives, so I don't know if this 
topic has been discussed previously.

I am having some trouble with CC.Net missing some files that I checked 
into VSS. I have researched it and I think I have found the problem.

Basically, when files are retrieved from VSS the file modification date 
is set to the "VSS modification date" of the file. I believe this is 
incorrect. Let me give you a scenario: You kick of a build at 1PM. The 
source files are retrieved. During the build you check in a file at 
1:05PM. The build finishes at 1:10PM. At 1:30 you kick off the next 
build. The modification date of the file you checked is set to 1:05 (the 
VSS modification date). The timestamp on the assembly is 1:10 (the time 
of the last build). So, even though the file has changed, the assembly 
will not recompile because the modification times of the files are out 
of sync.

So, long story short: by setting the date of the file to the 
modification date, it is out of sync.

Solution: set the modification date of the file to the time of the get.

Source: [I'm pretty new to CC.Net, so I might be off here]
In core\sourcecontrol\vss.cs in method GetSourceArgs() Line 124 is:
    builder.AppendArgument("-I-N -W -GF- -GTM");
This should be:
    builder.AppendArgument("-I-N -W -GF- -GTC");

Here is a page on the command line args:
http://msdn2.microsoft.com/en-us/203a56wa.aspx

Please let me know if you have any questions or suggestions.

Thanks,

Don

Just some random unsolicited patches :)

Seemed a bit silly to just go to the first project.  Seemed more useful
to go to the project page of the first broken project.

It would be nice if with nothing broken, you could go to a top level
url, but there's no top level url config (yet?) so if no builds are
broken, it still takes you to the first project page.

The changes to the Presentation file seem excessive, all I did was
resize the label a bit to make the new (longer) description fit, but I
guess that's form designer for you.

License agreement mail is enroute.=20

Cheers,
Karl P

StarNet has recently committed some changes to the BitKeeper support in 
CCNet 1.1:

1) Force pushing of labels before a build starts.  Previously, if your 
build took 10 minutes and polled for updates every 10 minutes, and 
developers were pushing changes every 20 minutes or less for several 
hours in a row (happens all the time here), then the build labels would 
not succeed in being pushed until no changes had been made while a build 
was in progress.  This was cheesy.  We made a minor change that attempts 
to push the build labels after updates have been pulled in (giving about 
a 99% chance that the build label push will then succeed).

2) Flagging of changes as "ChangeSet", "Added", "Deleted", "Renamed", 
and "Modified", instead of lumping them all into "Modified".

3) On a somewhat related note, we also added the CCNetNumericLabel 
property to NAnt and MSBuild tasks.  This returns the right-most 
numerical portion of the build label, which is typically the part that 
is an incrementing integer.  We use this in search/replace tasks to 
patch the build number into .rc files, .h files, etc. where we don't 
have access to a programming language to parse the string (of course, we 
could write custom tasks in NAnt, but that's a pain for something so 
simple).


These changes were tested, improved, and guided through the commit 
process by Stephanie Schiel.

Harold

My summer intern, Stephanie Schiel, added support for the replyto 
attribute on the EmailPublisher. This is available in CCNet 1.1.2389 and 
later.  We're using it in-house and it works fine.

I figured there has to be someone on this list that was waiting for this 
feature (it was marked as a blocker for 1.1), thus this message.

Harold

Hello 


can you help me to publish the Build Metrics - Build availability, Longest 
running tests, frequestly broken tests etc.. in the webDashboard. 



Thanking You 


Krishna Kota

Hi,

Some time ago I had one of our interns at work add support for project
dependencies to our local version of ccnet. See here for his post to
this mailing list:
http://article.gmane.org/gmane.comp.windows.dotnet.ccnet.devel/1681

The project lay somewhat dormant for the last few weeks because our
intern has finished his internship with us. I finally have some time
to continue his work, but I'd first like to discuss some of the
changes we made or are about to make, hoping that we can contribute
them to the project.
Thus, with consent from my company, I hereby agree to the
contributor's agreement found here:
http://confluence.public.thoughtworks.org/download/attachments/1178/CC.NET+Contributor+License+Agreement.doc?version=1

We have a lot of projects running on ccnet and there are quite a few
dependencies among them. Out of the box ccnet simply integrates all
projects simultaneously, which was unacceptable for us because when
the server had to be re-started it would sometimes start integrating
20 projects at once, which made our build server come to a screeching
halt. So initially when we started to use ccnet, we added a feature
that only a certain number of ProjectIntegrator threads could run at
any given time. This is the version of ccnet we've been using ever
since (for about a year now).

However, we'd like to have a smarter system that can handle project
dependencies.
We have many base projects (libraries, tools, etc.) that might be
referenced by many others and are themselves used by dependent
projects. We currently use project triggers to represent the
relationship between projects.
Often we have the problem that a change occurs in both a base project
A and a dependent project B. Now both start building at the same time,
even though A might not be able to build until B was built
successfully. In any case, when B finishes A is triggered again. This
is unnecessary and wasteful, especially if the dependency chain
between A and B is long.

So the basic setup we're trying to achieve now is this:

- We'd like to introduce a scheduler interface and a concrete
scheduler class that maintains a directed acyclic dependency graph of
projects. We're currently creating the graph from the project triggers
defined in ccnet.config. It might be worthwhile discussing better
alternatives.
The scheduler runs on its own thread and determines when a project can
be built. It maintains a list of currently building projects and a
queue of waiting projects sorted topologically according to the
dependency graph (i.e. base projects are scheduled to build first).

- When a ProjectIntegrator has determined that it wants to run a build
(i.e. either a trigger has forced the build or modifications in source
control trigger the build), a request is made to the scheduler to
schedule the build for the project.

- If no projects or none of the project's succesors or predecessors in
the dependency graph are currently building, the modifications can be
retrieved from source control and the build can run immediately.

- Otherwise the ProjectIntegrator thread is temporarily suspended and
the build request is enqueued in the sorted queue of waiting projects.
Once a currently building project has finished building, the scheduler
starts looking through the queue of waiting projects to check if it
can start the build of a queued project. We added a new
ProjectActivity that indicates that a project integrator is waiting
for being allowed to build its project by the scheduler.

So to summarize: I propose introducing a new interface - a scheduler
of project integrators - which all project integrators must go through
before they can start building their projects. To keep current
behavior, a simple pass-through scheduler can be implemented, which
always allows any project to build immediately.
Alternative schedulers, such as our project dependency scheduler, can
be written that provide more sophisticated scheduling strategies. I
could imagine other schedulers, such as a simple scheduler that only
allows a certain number of projects to build simultaneously or a
scheduler that prioritizes certain important projects.

We already have a system as described above working and we're very
happy with it (apart from the fact that it could use a bit of
refactoring and some more tests need to be written).
One nice side effect of our scheduler is that we can now have a
special copy-build-results-to-drop project at the very end of the
dependency graph. When this project is built we can be certain that
all its parent projects have been built successfully (and are
currently not building, since they are predecessors of the project in
the dependency graph). So this project can safely copy all the build
results to a network share or - as in our case - commit it to a source
control system from which the team can retrieve a consistent build of
all our base libraries and tools at any time.

I believe this is a useful addition to ccnet that extends the
flexibility of its design, and I'm interested in hearing your thoughts.
I'm especially interested in discussing the design changes necessary
to ccnet. The most important change is breaking up the
IntegrationRunner class in order to introduce the scheduler. I'm not
happy with how we're doing this at the moment and would like to
discuss the current design and how it is best changed to accommodate
the scheduler.

Best Regards,
Martin

--
Visit my pages on the Web:
http://xengine.sourceforge.net
http://members.liwest.at/GroovingArts

> Thanks for the information, one more question, how do I do fetch 
> myself?
> Do I create an EXEC task to fire the command line to fetch, or can I 
> trigger the sourcecontrol block from a task?  Sorry if the question is 
> obvious, I am new to CCNet.

Hello,

this seems to be good idea to me! Make some <get-source/> task which do the
job of autogetsource of current sourcecontrol. Could be pretty easy to
implement, and could be handy in alot of cases.

Maybe just to check if autogetsource=true and do nothing in such case... (or
emit a warning)

Just an idea,
Martin

> Thanks for the information, one more question, how do I do 
> fetch myself?
> Do I create an EXEC task to fire the command line to fetch, 
> or can I trigger the sourcecontrol block from a task?  Sorry 
> if the question is obvious, I am new to CCNet.

Hello,

this seems to be good idea to me! Make some <get-source/> task which do the
job of autogetsource of current sourcecontrol. Could be pretty easy to
implement, and could be handy in alot of cases.

Maybe just to check if autogetsource=true and do nothing in such case... (or
emit a warning)

Just an idea,
Martin

Dear Grant,

This seems reasonable, so I just created a JIRA for it:

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

Any chance you could send me a 1x1 transparent gif?

It looks like in the source you want the file to go here:

http://svn.sourceforge.net/viewcvs.cgi/ccnet/trunk/project/WebDashboard/images/

It would then have to be added to the CC.NET installer for 1.1.

Harold

-------- Original Message --------
From: <Gra...@ba...>
To: ccn...@li...
Subject: [Ccnet-devel] Transparent gif
Date: 6/6/2006 7:18 AM
> Any chance someone might add a transparent 1x1 gif to the images folder
> for CC.Net?
>
> Would make it an awful lot easier to try to get some more nicely
> formatted output on the build log page. At the moment all the tables get
> blown in width if just one of the sections has a long message (like an
> exception).
>
> Yes I can add my own but it's "one more thing" people need to remember
> to deploy if they use customised stylesheets such as those I offer for
> NCoverExplorer for CruiseControl.Net.
>
> Many thanks,
> Grant.
> ------------------------------------------------------------------------
> For more information about Barclays Capital, please visit our web site at http://www.barcap.com.
>
> Internet communications are not secure and therefore the Barclays Group does not accept legal responsibility for the contents of this message.  Although the Barclays Group operates anti-virus programmes, it does not accept responsibility for any damage whatsoever that is caused by viruses being passed.  Any views or opinions presented are solely those of the author and do not necessarily represent those of the Barclays Group.  Replies to this email may be monitored by the Barclays Group for operational or business reasons.
> ------------------------------------------------------------------------
>
>
> _______________________________________________
> Ccnet-devel mailing list
> Ccn...@li...
> https://lists.sourceforge.net/lists/listinfo/ccnet-devel
>
>   

Any chance someone might add a transparent 1x1 gif to the images folder
for CC.Net?

Would make it an awful lot easier to try to get some more nicely
formatted output on the build log page. At the moment all the tables get
blown in width if just one of the sections has a long message (like an
exception).

Yes I can add my own but it's "one more thing" people need to remember
to deploy if they use customised stylesheets such as those I offer for
NCoverExplorer for CruiseControl.Net.

Many thanks,
Grant.
------------------------------------------------------------------------
For more information about Barclays Capital, please visit our web site at=
=20http://www.barcap.com.

Internet communications are not secure and therefore the Barclays Group d=
oes not accept legal responsibility for the contents of this message.  Al=
though the Barclays Group operates anti-virus programmes, it does not acc=
ept responsibility for any damage whatsoever that is caused by viruses be=
ing passed.  Any views or opinions presented are solely those of the auth=
or and do not necessarily represent those of the Barclays Group.  Replies=
=20to this email may be monitored by the Barclays Group for operational o=
r business reasons.
------------------------------------------------------------------------

Believe it or not there has actually been a lot of work on CI Factory over
the last 5 or 6 months.  It may not have been public but the work was
happening none the less.  I posted
<http://jayflowers.com/WordPress/?p=53>sometime ago about how many
project at my day job that we are using it on
(close to 70).  I have finally taken the time to merge it all back into the
public codeline.  I have started getting the documentation up to date as
well.  There is now a good
introduction<http://www.mertner.com/confluence/display/CIF/Introduction>
and
a good install document<http://www.mertner.com/confluence/display/CIF/Install+Document>.
There are several new packages available, most important amongst them is *
Subversion*.

Packages currently bundled with the CI Factory installer:

   - Visual Source Safe
   - Subversion
   - Assembly and product versioning
   - PVCS Tracker
   - .NET Visual Studio 2003/2005 solution compilation
   - Unit Test execution with MbUnit
   - Code Coverage with CoverageEye
   - nDepend
   - Deployment artifact publication
   - Install Shield or VS deployment packages

Independent Packages :

   - Ant
   - VB6Compile
   - LinesOfCode

It's not all done but it is closer than it ever has been.  I hope to have
some videos added this week as well as get the rest of the packages
documented.

You can download CI Factory 0.7 RC1 and independent packages
here<http://jayflowers.com/joomla/index.php?option=com_remository&Itemid=33&func=select&id=6>
.


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