ccnet-devel Mailing List for CruiseControl.NET

Thanks Owen.  That did the trick.  I can do what I needed to.

On 7/28/05, Martin Aliger <mar...@go...> wrote:
> Oh - cool. I'm sorry - didn't look to 9.2 yet!! Mine bad!
>=20
> I'll look asap and try to make custom <property> task. It should be fun t=
o
> play with that!
>=20
> Martin Aliger
>=20
>=20
> > -----Original Message-----
> > From: ccn...@li...
> > [mailto:ccn...@li...] On Behalf Of
> > Owen Rogers
> > Sent: Wednesday, July 27, 2005 2:05 PM
> > To: ccn...@li...
> > Subject: Re: [Ccnet-devel] CCNET Info passed to nAnt
> >
> > hi martin,
> >
> > > I wrote patch to nanttask which pass all information from
> > > IIntegrationResult into NAnt (including label and result of prev.
> > > build). Unfortunatelly it do not find its way to distribution, it
> > > seems. Label should be accessible right now (see
> > label-to-apply), but I also needed LastIntegrationStatus as you do.
> > > In any case, modificationwritertask is great addition.
> >
> > have you seen the updated documentation describing all of the
> > extra properties that are now passed to nant (as of 0.92)?
> >
> > http://confluence.public.thoughtworks.org/display/CCNET/NAnt+Task
> > (see the bottom of the page)
> >
> > > There was also discussion about custom "properties", which
> > could be handy.
> > > Maybe that could change view to this problem a little. Mike, Owen,
> > > other - how do you see this properties stuff?
> >
> > as per the earlier discussion, i have changed the
> > integrationresult to operate on a collection of properties.
> > tasks can now add their own properties into the integration
> > result which will be passed to external programs via the
> > nant/exec or msbuild.
> > it's not quite custom properties a la nant, but it's getting there.
> > have a look at the latest nanttask code.
> >
> > cheers,
> > owen.
> > --
> > Owen Rogers | http://dotnetjunkies.com/weblog/exortech |
> > CruiseControl.NET - http://ccnet.thoughtworks.com
> >
> >
> > -------------------------------------------------------
> > SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> > from IBM. Find simple to follow Roadmaps, straightforward articles,
> > informative Webcasts and more! Get everything you need to get up to
> > speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id=16492&op=3Dick
> > _______________________________________________
> > Ccnet-devel mailing list
> > Ccn...@li...
> > https://lists.sourceforge.net/lists/listinfo/ccnet-devel
> >
>=20
>=20
>=20
> -------------------------------------------------------
> SF.Net email is Sponsored by the Better Software Conference & EXPO Septem=
ber
> 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
> Agile & Plan-Driven Development * Managing Projects & Teams * Testing & Q=
A
> Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
> _______________________________________________
> Ccnet-devel mailing list
> Ccn...@li...
> https://lists.sourceforge.net/lists/listinfo/ccnet-devel
>=20


--=20
Jay Flowers
----------------------------------------------------------------------
Blog: http://jflowers.blogspot.com
---------------------------------------------------------------------

I did not have a state element.  I added one "<state type=3D"state" />".
 This did not change the behaviour.  There is no problem with label
information being lost.  I have attached the config.

Thanks

On 7/26/05, Owen Rogers <exo...@gm...> wrote:
> > I am just now getting around to trying this.  I see a state file there
> > already.  There have been several builds already so the state file
> > exists.  If I bring down the build server and the start it up again it
> > will force a build.  It is this forced build immediately after a
> > shutdown start up that I do not want.
>=20
> this should not be happening.  do you have the <state> element
> specified in your ccnet.config file?  there were some changes made to
> this element in the 0.9.2 release, such that it no longer supports
> specifying an alternate filename for the state file.  when you restart
> the server does it use the last build label?  or does it start the
> build label from 0 again?
> if you are still having issues with this, could you please send over a
> copy of your ccnet.config file?
> cheers,
> owen.
>=20
> --
> Owen Rogers | http://dotnetjunkies.com/weblog/exortech |
> CruiseControl.NET - http://ccnet.thoughtworks.com
>=20
>=20
> -------------------------------------------------------
> SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> from IBM. Find simple to follow Roadmaps, straightforward articles,
> informative Webcasts and more! Get everything you need to get up to
> speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id=16492&opclick
> _______________________________________________
> Ccnet-devel mailing list
> Ccn...@li...
> https://lists.sourceforge.net/lists/listinfo/ccnet-devel
>=20


--=20
Jay Flowers
----------------------------------------------------------------------
Blog: http://jflowers.blogspot.com
---------------------------------------------------------------------

Hi

my customer is ok to have me implementing this during my day time=20
("Champagne!"). Granted, Surround doesn't seem very widely used AFAIK, and=
=20
we're heavily relying on CCNet, plus the switch to Surround is already=20
decided in the corporation.

Before I start implementing this (which should happen in two or three weeks=
=20
time), does anyone has recommendations about implementing a source control=
=20
provider in CCNet ? Are there expected changes in the providers behavior, o=
r=20
anything else I should know about ?


cheers

Thibaut=20
--=20
[blog] http://www.dotnetguru2.org/tbarrere

Oh - cool. I'm sorry - didn't look to 9.2 yet!! Mine bad!

I'll look asap and try to make custom <property> task. It should be fun =
to
play with that!

Martin Aliger
=20

> -----Original Message-----
> From: ccn...@li...=20
> [mailto:ccn...@li...] On Behalf Of=20
> Owen Rogers
> Sent: Wednesday, July 27, 2005 2:05 PM
> To: ccn...@li...
> Subject: Re: [Ccnet-devel] CCNET Info passed to nAnt
>=20
> hi martin,
>=20
> > I wrote patch to nanttask which pass all information from=20
> > IIntegrationResult into NAnt (including label and result of prev.=20
> > build). Unfortunatelly it do not find its way to distribution, it=20
> > seems. Label should be accessible right now (see=20
> label-to-apply), but I also needed LastIntegrationStatus as you do.
> > In any case, modificationwritertask is great addition.
>=20
> have you seen the updated documentation describing all of the=20
> extra properties that are now passed to nant (as of 0.92)?
>=20
> http://confluence.public.thoughtworks.org/display/CCNET/NAnt+Task
> (see the bottom of the page)
>=20
> > There was also discussion about custom "properties", which=20
> could be handy.
> > Maybe that could change view to this problem a little. Mike, Owen,=20
> > other - how do you see this properties stuff?
>=20
> as per the earlier discussion, i have changed the=20
> integrationresult to operate on a collection of properties. =20
> tasks can now add their own properties into the integration=20
> result which will be passed to external programs via the=20
> nant/exec or msbuild.
> it's not quite custom properties a la nant, but it's getting there.=20
> have a look at the latest nanttask code.
>=20
> cheers,
> owen.
> --
> Owen Rogers | http://dotnetjunkies.com/weblog/exortech |=20
> CruiseControl.NET - http://ccnet.thoughtworks.com
>=20
>=20
> -------------------------------------------------------
> SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> from IBM. Find simple to follow Roadmaps, straightforward articles,
> informative Webcasts and more! Get everything you need to get up to
> speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id=16492&op=3Dick
> _______________________________________________
> Ccnet-devel mailing list
> Ccn...@li...
> https://lists.sourceforge.net/lists/listinfo/ccnet-devel
>=20

> thanks steve.  this is a bug/limitation of the StateFileLabeller: the
state file needs to be in the current directory (ie. the directory
where you are launching ccnet from) for the labeller to be able to
locate the state file.

this actually begs the question: where's the right location for the state f=
ile?
1) the current directory? =20
   - well, this could be pretty much anywhere.  if you run ccnet from
a different location than usual, then the state file won't be found
   - however, changing this will be a breaking change for upgrading users
   - this also gets a bit confused when running ccnet as a service
2) the working directory?
   - this is good because it is associated with a specific project
   - however, it's also generally the root source directory.  do we
want the state file in there?
3) the artifact directory?
   - is the state file really an artifact?  kind of, but not really.
4) the executing assembly directory?
   - this i kind of like.  it's a well-known location.
   - it does mean that project-specific info is going to be stored
outside of the project

any other options?  what do you think?

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


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

hi martin,

> I wrote patch to nanttask which pass all information from IIntegrationRes=
ult
> into NAnt (including label and result of prev. build). Unfortunatelly it =
do
> not find its way to distribution, it seems. Label should be accessible ri=
ght
> now (see label-to-apply), but I also needed LastIntegrationStatus as you =
do.
> In any case, modificationwritertask is great addition.

have you seen the updated documentation describing all of the extra
properties that are now passed to nant (as of 0.92)?

http://confluence.public.thoughtworks.org/display/CCNET/NAnt+Task
(see the bottom of the page)

> There was also discussion about custom "properties", which could be handy=
.
> Maybe that could change view to this problem a little. Mike, Owen, other =
-
> how do you see this properties stuff?

as per the earlier discussion, i have changed the integrationresult to
operate on a collection of properties.  tasks can now add their own
properties into the integration result which will be passed to
external programs via the nant/exec or msbuild.
it's not quite custom properties a la nant, but it's getting there.=20
have a look at the latest nanttask code.

cheers,
owen.
--=20
Owen Rogers | http://dotnetjunkies.com/weblog/exortech |
CruiseControl.NET - http://ccnet.thoughtworks.com

Hi all

It seems that the recent checkins for SystemTrayMonitor.cs removed the
_statusMonitor event handlers, making the tray not very helpful.

I've attached a patch to put them back in (after a hair tearing
afternoon, that will teach me to live on the edge with latest source
;).. )

Also, can somebody please commit the patch for the cvs useHistory
absolute path bug that Craig posted on the 22nd, it makes such a
difference :)

There is also a xsl + javascript issue I've had to fix with every
release, I've attached a patch for this as well. When you expand test
details in the web dashboard it redirects you to the homepage.

Thanks for all your work guys!

Damian

I wrote patch to nanttask which pass all information from =
IIntegrationResult
into NAnt (including label and result of prev. build). Unfortunatelly it =
do
not find its way to distribution, it seems. Label should be accessible =
right
now (see label-to-apply), but I also needed LastIntegrationStatus as you =
do.
In any case, modificationwritertask is great addition.

There was also discussion about custom "properties", which could be =
handy.
Maybe that could change view to this problem a little. Mike, Owen, other =
-
how do you see this properties stuff?

Martin Aliger
=20

> -----Original Message-----
> From: ccn...@li...=20
> [mailto:ccn...@li...] On Behalf Of=20
> Jay Flowers
> Sent: Wednesday, July 27, 2005 4:10 AM
> To: ccn...@li...
> Subject: Re: [Ccnet-devel] CCNET Info passed to nAnt
>=20
> No I had not.  Mark that one of the list. :)
>=20
> On 7/26/05, Owen Rogers <exo...@gm...> wrote:
> > > I general these deal with passing information from ccnet=20
> to a nAnt=20
> > > script.  the information in question:
> > >
> > > - Modification(s) detected
> > > -- File(s)
> > > -- User
> > > - Label/Tag applied to source control
> > > - Result of previous build
> >=20
> > jay,
> > have you seen the modificationwritertask?
> >=20
> http://confluence.public.thoughtworks.org/display/CCNET/Modification+W
> > riter+Task
> >=20
> > cheers,
> > owen.
> > --
> > Owen Rogers | http://dotnetjunkies.com/weblog/exortech |=20
> > CruiseControl.NET - http://ccnet.thoughtworks.com
> >=20
> >=20
> > -------------------------------------------------------
> > SF.Net email is sponsored by: Discover Easy Linux Migration=20
> Strategies=20
> > from IBM. Find simple to follow Roadmaps, straightforward articles,=20
> > informative Webcasts and more! Get everything you need to get up to=20
> > speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id=16492&opclick
> > _______________________________________________
> > Ccnet-devel mailing list
> > Ccn...@li...
> > https://lists.sourceforge.net/lists/listinfo/ccnet-devel
> >=20
>=20
>=20
> --
> Jay Flowers
> ----------------------------------------------------------------------
> Blog: http://jflowers.blogspot.com
> ---------------------------------------------------------------------
>=20
>=20
> -------------------------------------------------------
> SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> from IBM. Find simple to follow Roadmaps, straightforward articles,
> informative Webcasts and more! Get everything you need to get up to
> speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id=16492&op=3Dick
> _______________________________________________
> Ccnet-devel mailing list
> Ccn...@li...
> https://lists.sourceforge.net/lists/listinfo/ccnet-devel
>=20

No I had not.  Mark that one of the list. :)

On 7/26/05, Owen Rogers <exo...@gm...> wrote:
> > I general these deal with passing information from ccnet to a nAnt
> > script.  the information in question:
> >
> > - Modification(s) detected
> > -- File(s)
> > -- User
> > - Label/Tag applied to source control
> > - Result of previous build
>=20
> jay,
> have you seen the modificationwritertask?
> http://confluence.public.thoughtworks.org/display/CCNET/Modification+Writ=
er+Task
>=20
> cheers,
> owen.
> --
> Owen Rogers | http://dotnetjunkies.com/weblog/exortech |
> CruiseControl.NET - http://ccnet.thoughtworks.com
>=20
>=20
> -------------------------------------------------------
> SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> from IBM. Find simple to follow Roadmaps, straightforward articles,
> informative Webcasts and more! Get everything you need to get up to
> speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id=16492&opclick
> _______________________________________________
> Ccnet-devel mailing list
> Ccn...@li...
> https://lists.sourceforge.net/lists/listinfo/ccnet-devel
>=20


--=20
Jay Flowers
----------------------------------------------------------------------
Blog: http://jflowers.blogspot.com
---------------------------------------------------------------------

> I general these deal with passing information from ccnet to a nAnt
> script.  the information in question:
>=20
> - Modification(s) detected
> -- File(s)
> -- User
> - Label/Tag applied to source control
> - Result of previous build

jay,
have you seen the modificationwritertask?
http://confluence.public.thoughtworks.org/display/CCNET/Modification+Writer=
+Task
=20
cheers,
owen.
--=20
Owen Rogers | http://dotnetjunkies.com/weblog/exortech |
CruiseControl.NET - http://ccnet.thoughtworks.com

I was wondering if anyone else might benefit from some of these
change/enhancements.

I general these deal with passing information from ccnet to a nAnt
script.  the information in question:

- Modification(s) detected
-- File(s)
-- User
- Label/Tag applied to source control
- Result of previous build

The one I am not sure of the best way to implement is the
Modifications.  How to represent a list of File(s) and just in case
Users, even though we like just one at a time.  I think the best way
is the xml that is already written to the build log.

--=20
Jay Flowers
----------------------------------------------------------------------
Blog: http://jflowers.blogspot.com
---------------------------------------------------------------------

> I am just now getting around to trying this.  I see a state file there
> already.  There have been several builds already so the state file
> exists.  If I bring down the build server and the start it up again it
> will force a build.  It is this forced build immediately after a
> shutdown start up that I do not want.

this should not be happening.  do you have the <state> element
specified in your ccnet.config file?  there were some changes made to
this element in the 0.9.2 release, such that it no longer supports
specifying an alternate filename for the state file.  when you restart
the server does it use the last build label?  or does it start the
build label from 0 again?
if you are still having issues with this, could you please send over a
copy of your ccnet.config file?
cheers,
owen.=20

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

I am just now getting around to trying this.  I see a state file there
already.  There have been several builds already so the state file
exists.  If I bring down the build server and the start it up again it
will force a build.  It is this forced build immediately after a
shutdown start up that I do not want.

On 7/22/05, Jay Flowers <jay...@gm...> wrote:
> You understand.  Thanks I will try that.
>=20
> On 7/21/05, Owen Rogers <exo...@gm...> wrote:
> > > When I start a CCNET process the and there are not modifications
> > > detected the build is forced. I do not want this to happen.  I don't
> > > remember this being the case in previous version.  Have I forget ten
> > > something?  How do I make this not happen?
> >
> > by design, ccnet will force a build the first time a new ccnet project
> > is created.  this is just to ensure that everything works with the
> > build process.  thereafter, builds will only occur when triggered.
> > this functionality has been in place for quite a while.  is this what
> > you are seeing?  or am i misunderstanding?
> >
> > if you really want to bypass the initial forcebuild, you can just
> > create an initial state file for the project.  this will make ccnet
> > think that a build has occurred previously.
> >
> > cheers,
> > owen.
> > --
> > Owen Rogers | http://dotnetjunkies.com/weblog/exortech |
> > CruiseControl.NET - http://ccnet.thoughtworks.com
> >
> >
> > -------------------------------------------------------
> > SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> > from IBM. Find simple to follow Roadmaps, straightforward articles,
> > informative Webcasts and more! Get everything you need to get up to
> > speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id=16492&opclick
> > _______________________________________________
> > Ccnet-devel mailing list
> > Ccn...@li...
> > https://lists.sourceforge.net/lists/listinfo/ccnet-devel
> >
>=20
>=20
> --
> Jay Flowers
> ----------------------------------------------------------------------
> Blog: http://jflowers.blogspot.com
> ---------------------------------------------------------------------
>=20


--=20
Jay Flowers
----------------------------------------------------------------------
Blog: http://jflowers.blogspot.com
---------------------------------------------------------------------

> I just tried to scan mine compute with Microsoft Antispyware product and =
it
> found those two items. Maybe its just false positive, dont know, but I th=
ink
> you should know.=20

i think that it's fine.  see:
http://nsis.sourceforge.net/index.php?id=3D2&backPID=3D2&tt_news=3D24
cheers,
owen.
--=20
Owen Rogers | http://dotnetjunkies.com/weblog/exortech |
CruiseControl.NET - http://ccnet.thoughtworks.com

Hello,
 
I just tried to scan mine compute with Microsoft Antispyware product and it
found those two items. Maybe its just false positive, dont know, but I think
you should know.
 
Martin
 
 
CoolWebSearch.CameUp Browser Modifier
<http://www.spynet.com/details_threat.aspx?sc=10615&id=4093> more
information...
Details: CoolWebSearch.CameUp is an Internet Explorer toolbar. If you browse
the Web when the toolbar is enabled, certain URLs can trigger the display of
pop-up ads.
Status: Removed
Severe threat - Severe-risk items have an extreme potential for harm, such
as a security exploit, and should be removed.

Infected files detected
c:\z-e\src\extern\ccnet.8.0.827\tools\nsis\plugins\system.dll


AntivirusGold Potentially Unwanted Software
<http://www.spynet.com/details_threat.aspx?sc=10615&id=15694> more
information...
Status: Removed
High threat - High-risk items have a large potential for harm, such as loss
of computer control, and should be removed unless knowingly installed.

Infected files detected
c:\z-e\src\extern\ccnet.8.0.827\tools\nsis\plugins\dialer.dll

 

Hi Owen,

I hereby agree to the CruiseControl.NET Contributor License Agreement as
outlined in the file "CC.NET Contributor License Agreement.doc" in the CC.NET
distribution.

> are you looping through the array to call devenv for each project? 
> sounds slow to me, but i don't that devenv supports any alternatives. 

Yes, I'm looping through, and no, devenv doesn't support any alternatives.

> of course, a simpler option would be to just have a solution file that
> contains only the specific projects that you want to build.

I disagree. I think it's easier to just specify the projects in the ccnet.config
file and not bother with having to create a new solution file that needs to be
kept around as separate file on the build server - just to be able to build
specific projects of a solution. Anyway, this feature is not of utmost
importance to us, so I can just remove it, if there's no interest.

> ok.  though i'm not sure that most people want to build at least 2
> configurations.  why not have ccnet only build release builds? 

Most of our projects are C++ with a lot of templates (STL, Boost, template
metaprogramming). The build times for our entire system clocks in at around
60-70 minutes. So we use our build server (which is the best machine we have) to
also build debug builds for internal use by all of our programmers in the
department. When they come in in the morning they can grab an up-to-date debug
build from a file drop server.

Additionally, we have projects that have quite a few solution configurations
(again, consider we're mostly doing C++ development where this is quite common).
For example, we have a project that has these solution configurations:
Release DLL
Release LIB
Debug DLL
Debug LIB
Release DLL VTune
Release LIB VTune

Having to specify separate devenv sections in ccnet.config as it was until now
is a lot of unnecessary copy & paste.

> it also seems to get a bit complicated as you could have multiple
> projects and multiple configurations specified.  would you iterate
> through the combination of both?

Yes, that's what I'm doing. See the attached code.

> we don't use the SF patch tracker.  we do all issue tracking through
> our jira server:
> http://jira.public.thoughtworks.org/secure/Dashboard.jspa

Ok. Should I create a new issue there? How do I upload files (couldn't find
anything in the form that I got when I tried to create a new issue)?

I've attached my DevenvTask modifications as zip file to this e-mail (rename
.archive to .zip). It includes DevenvTask.cs, DevenvTaskTest.cs where I've added
some unit tests, and Visual Studio Task.html where I've added documentation.
This HTML file should probably also contain a sample of specifying projects and
multiple configurations, but it seems unnecessarily complex to do this in HTML,
so I'll just post one further down below in this mail.

The enhancements of this patch in particular are:
- A boolean rebuild flag that tells devenv to either do a full rebuild or just a
regular rebuild
- Possibility to specify multiple solution configurations
- Possibility to specify to build only certain projects in a solution
- Fixed a bug in the old DevenvTask when a solution configuration name would
contain more than one space. In such a case the configuration name must be put
under quotes on the command line.

Here's a full example of the new devenv task in action:

<devenv>
       <solutionfile>src\MyProject.sln</solutionfile>
       <rebuild>false</rebuild>
       <configurations>
	<configuration>Debug DLL</configuration>
	<configuration>Release DLL</configuration>
	<configuration>Debug LIB</configuration>
	<configuration>Release LIB</configuration>
       </configurations>
       <solutionprojects>
	<solutionproject>myProject1</solutionproject>
	<solutionproject>myProject2</solutionproject>
       </solutionprojects>
       <executable>c:\program files\Microsoft Visual Studio
.NET\Common7\IDE\devenv.com</executable>
       <buildTimeoutSeconds>10</buildTimeoutSeconds>
</devenv>

Best Regards,
Martin

mar...@li... wrote:
> 
> This is very nice indeed. It certainly replaces the current CCTray and
> we're
> already using CCTrayMutli successfully at my company.

Very pleased to hear it.

> 
> Two things I'd like to see added:
> 
> - When adding a ccnet server it would be nice to be able to select
> multiple
> projets to add at once. Currently I can click 'Fetch List' and I get a
> combobox
> of projects on the server of which only one can be added. It would be
nice
> to
> get a listbox that allows to select multiple projects to be added from
> that server.

Yes, good suggestion.  (I admit I tend to do this by editing the settings
file directly, but it'd be much better if the gui supported it.)  I've
created http://jira.public.thoughtworks.org/browse/CCNET-489 to track.

> 
> - Similarly, in the main window it would be nice to be able to select
> multiple
> projects and force a build for them.

I've had similar feedback from elsewhere.  I've created
http://jira.public.thoughtworks.org/browse/CCNET-490 to track.

g

Hi Mike

I'm stuck on this.

In the previous patch I added a new function on the IFarmService, because a=
t=20
that time=20
an IFarmService object was the only one I had available in the plugin=20
(besides the linkfactory and the IVelocityViewGenerator).
I based the historyplugin on other plugins, which have the same constructor=
,=20

but different actions.

Now you did not like the new added function, and you got a point,=20
getting the log was already available. But here is my problem :

All the ccnet build related actions are stored in 'ICruiseManagerWrapper'.
The only object which implements this in the dashboard is=20
'ServerAggregatingCruiseManagerWrapper'

I tried instantiating this object in the plugin, but that was way to nasty,=
=20
--> to many dummy objects involved and way to many copied code.
So this can not be the way.

for the moment my constructor is :
public ProjectHistoryPlugin(IFarmService farmService,=20
IVelocityViewGenerator viewGenerator,=20
ILinkFactory linkFactory)

The only object I need is an instance of a=20
'ServerAggregatingCruiseManagerWrapper'.

Any thoughts on how to accomplish this?

Maybe there is another way to get a build,=20
you mentioned the IBuildRetriever.GetBuild() .

I've looked in this, and the only thing that implements this interface is
ServerQueryingBuildRetriever.
To create a 'ServerQueryingBuildRetriever', you need a=20
'ICruiseManagerWrapper'.
and the only object doing this in the dashboard is :
ServerAggregatingCruiseManagerWrapper
and so I am back to square 1 :-((


Changing the Getlog() in the other modules (core, remote, ...) so it fetche=
s=20
only the
modifications is not the problem. Getting it to show in the Dashboard is.
For me this is typically a case when the floor collapses on the last step=
=20
:-((

- any hints on how to bypass this?
- is there a way I can get more/other objects in the constructor?
- is there a guide or so which has some information?

any help is greatly appreciated

with kind regards



















On 7/19/05, Mike Roberts <mik...@gm...> wrote:
>=20
> Hi Ruben,
>=20
> Many thanks thanks for this, but sorry to be a pain - I don't want to
> accept patch this as given, I'll explain why.
>=20
> You've added an extra method to the remote interface of the build
> server for GetModifications(projectName, buildName). My issue with
> this is that modification details are already in the log returned by
> GetLog(projectName, buildName) . The Dashboard plugin would need to be
> more intelligent because it would need to parse the Log XML, but
> overall there'd be less need for the CruiseServer to be tied to a
> specific Dashboard function.
>=20
> In time, I hope that we will have better ways of accessing things like
> build state in the build server, but I don't think that this
> server-side change is the right way of progressing.
>=20
> I think you forgot to include your 'ProjectHistory' class, but it
> would need to do something with IBuildRetriever.GetBuild() rather than
> your new IFarmService.GetProjectModifications() method. Some XPath
> retrieval of all the 'modification' tags would do it : look in the
> existing modifications.xsl file for inspiration.
>=20
> Thanks again for looking at this though,
>=20
> Mike
>=20
> On 7/14/05, Ruben Willems <rub...@gm...> wrote:
> > Hi
> >
> > Rrename the .archive to .zip
> >
> > There are 2 extra files :
> > ProjectReportChangeHistoryProjectPlugin.cs
> > copy to
> > \project\WebDashboard\Plugins\ProjectReport
> >
> > ProjectHistory.vm
> > copy to
> > \project\WebDashboard\templates
> >
> >
> > if there are any questions, feel free to contact me
> >
> > with kind regards
> >
> >
> >
>=20
>=20
> --
> mike roberts | http://mikeroberts.thoughtworks.net/ |
> http://www.thoughtworks.com/
>=20
>=20
> -------------------------------------------------------
> SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> from IBM. Find simple to follow Roadmaps, straightforward articles,
> informative Webcasts and more! Get everything you need to get up to
> speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id=16492&opclick
> _______________________________________________
> Ccnet-devel mailing list
> Ccn...@li...
> https://lists.sourceforge.net/lists/listinfo/ccnet-devel
>

> Just out of curiosity.  We have just implemented an iteration labeler
> which mirrors the DefaultLabeller except that it increments the
> iteration as well as the build number. =20

thanks craig!  i've committed the IterationLabeller in build 1053.
cheers,
owen.
--=20
Owen Rogers | http://dotnetjunkies.com/weblog/exortech |
CruiseControl.NET - http://ccnet.thoughtworks.com

hi tim,

> This problem only manifests itself the first time the project is modified=
, i.e
> when the 'from' argument is null. Code should work fine the rest of the t=
ime.
> A unit test should be trivial.

i had a look at the code and your patch; however, as far as i can
tell, there is no way that the initial IntegrationResult should ever
be null.  if this were ever the case it would break all of the other
sourcecontrol providers as well.  are you using any kind of custom
state manager?  or are you manipulating the state file by hand?  i
can't see that anything would be different for the Synergy provider.=20
are you using the 0.92 release?

cheers,
owen.
--=20
Owen Rogers | http://dotnetjunkies.com/weblog/exortech |
CruiseControl.NET - http://ccnet.thoughtworks.com

hi martin,

> First of all I'm very new to ccnet and .NET development in general.
> Nevertheless, I've made some modifications to DevenvTask in order to make=
 it a
> bit more general.

thanks for the offer of your patch.  the enhancements all sound good.=20
as mike mentioned previously, we need you to agree to the CCNet
contributors license [1] (a simple email stating your agreement to the
ccnet-devel list will suffice).  the license is to just to protect us
from potential copyright infringements and to keep the lawyers happy.

[1] http://confluence.thoughtworks.com/display/CCNET/Contributor+License+Ag=
reement

> - Added <solutionprojects> array element that allows specifying selective=
ly
> which projects in a solution are to be built. (I would like to simply cal=
l this
> element <projects> but it seems NetReflector then has problems with the a=
rray
> element <project> since that's used at a higher level in ccnet.config
> already...is there a way around this?)

unfortunately not.  NetReflector requires the element names to be
unique in order to identify which type to deserialise to.  you could
still go with the property name of <projects> and you can actually
call the child elements whatever you want (ie. <p> or <proj> or ...)
as long as it doesn't conflict with an existing NetReflector name.

are you looping through the array to call devenv for each project?=20
sounds slow to me, but i don't that devenv supports any alternatives.=20
of course, a simpler option would be to just have a solution file that
contains only the specific projects that you want to build.

> - Added <configurations> array element that allows specifying multiple so=
lution
> configurations in one <devenv> task. This avoids some copy & pasting beca=
use
> usually you will want to build at least two configurations - Debug and Re=
lease.
> The <configuration> element is kept for backwards compatibility. Both ele=
ments,
> however, cannot be specified.

ok.  though i'm not sure that most people want to build at least 2
configurations.  why not have ccnet only build release builds?  it
also seems to get a bit complicated as you could have multiple
projects and multiple configurations specified.  would you iterate
through the combination of both?

> I'd like to get some feedback on my changes and then contribute them if t=
here is
> enough interest. I tried to adhere to the programming guidelines outlined=
 here
> http://ccnet.sourceforge.net/CCNET/Developer%20Guidelines.html
> My modifications are against latest CVS (from yesterday).

great!  thanks.  does that include having unit tests for all enhancements?

> Some questions:
> How do I update the documentation for the <devenv> task? Do I edit the Vi=
sual
> Studio Task.html file in the /doc/CCNET folder directly or are these HTML=
 files
> automatically generated?

these html files are exported from the main confluence site.  if
you're keen, you can modify the content of the page to reflect your
changes and send it out to the list.

> Should I post my modifications as attachments to this list or submit a pa=
tch to
> the SF patch tracker?

we don't use the SF patch tracker.  we do all issue tracking through
our jira server:
http://jira.public.thoughtworks.org/secure/Dashboard.jspa

we can create a new issue on the jira and upload the files.
cheers,
owen.

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

Owen,

Sorry it has taken so long to get this back to you.

> > > i) do these changes address issue ccnet-436?
> > > http://jira.public.thoughtworks.org/browse/CCNET-436  .  i assume
that
> > > they do.
> >=20
> > Yes, I believe it will.
>
> ok, cool.  i've now marked the issue as closed; however it would be
> nice to have a unit test that demonstrates that it was fixed.

I believe there is already one present.

> > ii) what is the purpose of the LocalOnly property?  i need to
include
> > it in the updated documentation

I need to look into this more.  I tried removing it from my code and
found really quickly that the solution source control that uses it
ceased to function correctly.  That is not saying it doesn't work
without it in a normal running environment.

I would like to propose that we create an AbstractSourceControl class
that contains the property Recurse (instead of LocalOnly as that has
connotation to CVS only), as well as the empty implementation of those
methods that aren't used by all SourceControls (LabelSourceControl,
GetSource, UpdateSource, Initialize, Purge), and move the Properties
(WorkingDirectory, IntegrationRunnerTarget, Recurse) to this class.
With this class we can remove a lot of empty methods from the source
control classes.  I have attached my implementation.

> i spent some time refactoring the code over the weekend in order to
> implement working directory functionality properly in cvs and to
> handle the conversion of dots in label names.  in the process i
> refactored some of the implementation of CvsHistoryCommandParser.  i
> moved all functionality related to invoking the cvs command line back
> out into the main Cvs class.  this makes the Parser only responsible
> for parsing the results of the history command -- so it's job is much
> clearer and simpler.  in the process i noticed that the bottom 3 unit
> tests in CvsHistoryCommandParserTest seem to all be testing pretty
> much the same thing.  i might have screwed something up when i
> refactored it.
> do you mind taking a look at the latest cvs source and letting me know
> what you think?

Not at all.  I found two issues that are causing problems.

Cvs.patch contains a fix for passing an absolute path to the cvs
command.
CvsHistoryCommandParser.patch contains a fix for using a wrong
repository in cases where another class uses the Cvs object in a loop.


This email, and any files or previous email messages included with it, =
may contain confidential and/or privileged material. If you are not the =
intended recipient please contact the sender and delete all copies.

Owen, Simon, et. All,

I would like to make an argument for not making this change, but rather
add this information to the documentation (i.e. CruiseControl.NET is
case-sensitive).  My reasoning is, do we really want to code for all the
different nuances between operating systems?  Of course checking whether
we are running under Windows or any other operating system and adjusting
the case-sensitivity is relatively small, it's the principal of the
thing.  I assume (and yes, I know what happens when somebody assumes),
that one goal of CruiseControl.NET is to be able to run cross-platform.
So do we want to start making little tweaks here and there for these
differences?

Maybe I am making a mountain out of a mole hill, but I at least wanted
to bring it up.

I will be bringing up a Linux box and mono to see how it performs.  So I
have an interest in keeping OS specific code out as much as possible.

--Craig


> > My project called "PROJECT1" in CVS (names changed to protect the
innocent)
> > was checked out into a directory (for some reason) with the name
"project1"
> > - possibly because we use cvsnt and when the checkout command was
used it
> > was given "project1" as the module name and the cvsnt server is not
fussy.
> >=20
> > The Cvs.AcceptEntry function uses String.Equals to compare path
parts, and
> > thus unless the original checkout directory matches the remote
repository
> > exactly for case, no modifications are found.

> thanks for raising this. i've created a new issue in jira to track
> it's implementation:
> http://jira.public.thoughtworks.org/browse/CCNET-484

This email, and any files or previous email messages included with it, =
may contain confidential and/or privileged material. If you are not the =
intended recipient please contact the sender and delete all copies.

You understand.  Thanks I will try that.

On 7/21/05, Owen Rogers <exo...@gm...> wrote:
> > When I start a CCNET process the and there are not modifications
> > detected the build is forced. I do not want this to happen.  I don't
> > remember this being the case in previous version.  Have I forget ten
> > something?  How do I make this not happen?
>=20
> by design, ccnet will force a build the first time a new ccnet project
> is created.  this is just to ensure that everything works with the
> build process.  thereafter, builds will only occur when triggered.
> this functionality has been in place for quite a while.  is this what
> you are seeing?  or am i misunderstanding?
>=20
> if you really want to bypass the initial forcebuild, you can just
> create an initial state file for the project.  this will make ccnet
> think that a build has occurred previously.
>=20
> cheers,
> owen.
> --
> Owen Rogers | http://dotnetjunkies.com/weblog/exortech |
> CruiseControl.NET - http://ccnet.thoughtworks.com
>=20
>=20
> -------------------------------------------------------
> SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> from IBM. Find simple to follow Roadmaps, straightforward articles,
> informative Webcasts and more! Get everything you need to get up to
> speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id=16492&opclick
> _______________________________________________
> Ccnet-devel mailing list
> Ccn...@li...
> https://lists.sourceforge.net/lists/listinfo/ccnet-devel
>=20


--=20
Jay Flowers
----------------------------------------------------------------------
Blog: http://jflowers.blogspot.com
---------------------------------------------------------------------

> When I start a CCNET process the and there are not modifications
> detected the build is forced. I do not want this to happen.  I don't
> remember this being the case in previous version.  Have I forget ten
> something?  How do I make this not happen?

by design, ccnet will force a build the first time a new ccnet project
is created.  this is just to ensure that everything works with the
build process.  thereafter, builds will only occur when triggered.=20
this functionality has been in place for quite a while.  is this what
you are seeing?  or am i misunderstanding?

if you really want to bypass the initial forcebuild, you can just
create an initial state file for the project.  this will make ccnet
think that a build has occurred previously.

cheers,
owen.
--=20
Owen Rogers | http://dotnetjunkies.com/weblog/exortech |
CruiseControl.NET - http://ccnet.thoughtworks.com