You can subscribe to this list here.
2003 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
(21) |
Aug
(16) |
Sep
(9) |
Oct
(13) |
Nov
(25) |
Dec
(43) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2004 |
Jan
(89) |
Feb
(79) |
Mar
(95) |
Apr
(112) |
May
(81) |
Jun
(99) |
Jul
(82) |
Aug
(87) |
Sep
(146) |
Oct
(185) |
Nov
(120) |
Dec
(62) |
2005 |
Jan
(141) |
Feb
(148) |
Mar
(228) |
Apr
(298) |
May
(286) |
Jun
(287) |
Jul
(326) |
Aug
(334) |
Sep
(445) |
Oct
(447) |
Nov
(293) |
Dec
(261) |
2006 |
Jan
(286) |
Feb
(328) |
Mar
(356) |
Apr
(245) |
May
(216) |
Jun
(242) |
Jul
(213) |
Aug
(352) |
Sep
(263) |
Oct
(169) |
Nov
(2) |
Dec
|
From: Andy J. <an...@me...> - 2006-02-23 16:22:22
|
I ran into the same issue. Instead of letting CCnet to the labeling, I added the label via a nant script. If the build fails for any reason, I delete the label from Vault. I was having a problem with the dateLabeller; it would apply the label, try to build, and fail. Then the next time around, it tried to use the same label, and vault complains the label exists, thus causing the build to fail..I hadn't come across this before because I was using VSS when I created the dateLabeller, and VSS will automatically remove the existing label before performing the label. Andy -----Original Message----- From: Anthony Bova [mailto:ab...@we...] Sent: Thursday, February 23, 2006 11:11 AM To: ccn...@li... Subject: [Ccnet-user] Vault Label problem Today I had a problem with vault and CCNet. As far as I can figure ccnet found that it needed to do a build, labeled the repository with the next build label and then had problems getting the files to do the build. Vault having problems getting the new files is somewhat common since the repository is at another site. The next time it tired to do a build it failed with the error that the repository was already labeled with the next build number. My temporary solution was to delete the bad label. I suppose I could fix this by modifying the system to always increment the build number, but I'd rather not do that if I can avoid it. Is it possible to do something like save the folder revision number that was gotten by the get latest and do the labeling after we have a successful build? Or is this something I should add to build task after the call to msbuild? Tony Bova |
From: Anthony B. <ab...@we...> - 2006-02-23 16:10:44
|
Today I had a problem with vault and CCNet. As far as I can figure ccnet found that it needed to do a build, labeled the repository with the next build label and then had problems getting the files to do the build. Vault having problems getting the new files is somewhat common since the repository is at another site. The next time it tired to do a build it failed with the error that the repository was already labeled with the next build number. =20 =20 My temporary solution was to delete the bad label. =20 =20 I suppose I could fix this by modifying the system to always increment the build number, but I'd rather not do that if I can avoid it. Is it possible to do something like save the folder revision number that was gotten by the get latest and do the labeling after we have a successful build? Or is this something I should add to build task after the call to msbuild? =20 Tony Bova =20 |
From: Foster, R. - P. <RF...@qu...> - 2006-02-23 14:52:44
|
John, I thought that this type of problem was covered in the FAQ, but it appears not. CruiseControl.Net uses the "ErrorLevel" exit value returned by tools such as Nant and Devenv to determine if the process was successful. In this case, the operation you describe suggests that devenv is returning zero (i.e. success) when it probably shouldn't be. I notice the path to devenv.com is on the F drive. Can you verify that path is correct. I imagine if it wasn't then you would get a more significant failure, but you may not if there is a copy of devenv somewhere referenced by your path environment variable. You may also want to make sure that if it does exist it really is a copy of devenv.com. If I recall correctly, there is also a devenv.exe which *always* returns a zero ErrorLevel. Hope this helps, Regards, Richard -----Original Message----- From: ccn...@li... [mailto:ccn...@li...] On Behalf Of John Sent: Thursday, February 23, 2006 06:00 To: ccn...@li... Subject: [Ccnet-user] Why am I told my build passed when it actually failed? Hi,=20 When I build one of our applications using Source Safe the Visual Studio task <sourcecontrol type=3D"vss" autoGetSource=3D"true" applyLabel=3D"true"> <project>"$/PixDev/Product 3.2"</project> <username>******</username> <password>******</password> <ssdir>z:\</ssdir> <workingDirectory>C:\BuildIntegration\Product 3.2</workingDirectory> <culture>fr-FR</culture> </sourcecontrol> and <devenv> <solutionfile>"C:\BuildIntegration\Product 3.2\ Auditor.sln" /project "Product 3.2"</solutionfile> <configuration>Release</configuration> <executable>"F:\Program Files\Microsoft Visual Studio .NET 2003\Common7\IDE\devenv.com"</executable> <buildTimeoutSeconds>300</buildTimeoutSeconds> </devenv> CruiseContols sends me a mail telling me the build was sucessful, which is fantastic news. However when I look at the output from the CruiseContol window i can see it actually failed. Does anybody know why this happens or how i can guard against this? [Release Build:Info]: Building [Release Build:Info]: Starting build: F:\Program Files\Microsoft Visual Studio .NET 2003\Common7\IDE\devenv.com "C:\Build\Product 3.2\Product.sln" /project "Product 3.2" /rebuild Release [Release Build:Info]: Devenv build complete. Status: Failure [Release Build:Info]: Build complete: Success Kind Regards, John. ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D110944&bid=3D241720&dat=3D= 121642 _______________________________________________ Ccnet-user mailing list Ccn...@li... https://lists.sourceforge.net/lists/listinfo/ccnet-user |
From: Schouten R. <ry...@ya...> - 2006-02-23 14:37:42
|
When I have Cruise Control build a visual studio task it doesn't place the assemblies in the bin directory of the working directory. Actually the bin directory doesn't even get created. What do I need to do to get the assemblies into the bin directory of the working directory? __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com |
From: Andy J. <an...@me...> - 2006-02-23 13:11:54
|
Obliterate is something only an administrator can do, after the file was deleted. Deleting the file is sufficient to kick off the build. Obliterating is just a housekeeping measure done when you're certain you won't be needing the file again. I have nothing against builds, but I think a new build number should mean that something has changed from the previous build. Andy -----Original Message----- From: Karl Palsson [mailto:kar...@in...] Sent: Thursday, February 23, 2006 4:56 AM To: ccn...@li... Subject: RE: [Ccnet-user] Vault Obliterate triggered build > > I'm of the opinion that a hard-coded filter makes sense, but > I believe an ActionFilter will work in the mean time. (Can > anybody make a case for actually wanting to trigger a build > when something has been obliterated? I can't imagine why.) To make sure that it still builds? Joe is browsing the source, looking at things, looking for code to cleanup. He sees a file called DELETE_ME.source and after looking at the contents (empty file or something) Joe obliterates the file. This was probably a rash bold move on his behalf, (at least, if obliterate means the usual, not just delete, but also throw away all history) but it turns out that some other process uses the delete_me file after it's been checked out, to manage something else, (Presumably something where deleting the file indicates that something is finished) Joe's rash move forces a rebuild, and some people get hopping mad straight away. Ok, it's contrived, but if you can filter it out in an action filter, I'm all for leaving it in. Are you getting obliterates frequently enough that obliterates triggering the build is really bothering you? This is continuous integration, how's one more build going to hurt? Cheers, Karl P ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=k&kid0944&bid$1720&dat1642 _______________________________________________ Ccnet-user mailing list Ccn...@li... https://lists.sourceforge.net/lists/listinfo/ccnet-user |
From: Perry I. <ism...@gm...> - 2006-02-23 12:10:47
|
On 2/23/06, Karl Palsson <kar...@in...> wrote: > > > Only if he did the delete, then the obliterate. I don't know vault > specifics, just what the "common" usage of "obliterate" is. (And it's > pretty commonly a hard to find operation too :) In Vault you have to delete first. Obliterate basically means "empty recycl= e bin". There is no way to directly obliterate. I still feel that this is more of a curio than something you want to start > permanently blocking in the code. How often do you really see this > build? Obliterate is hard to do remember :) I agree. -- Perry Ismangil |
From: Karl P. <kar...@in...> - 2006-02-23 11:57:03
|
=20 Only if he did the delete, then the obliterate. I don't know vault = specifics, just what the "common" usage of "obliterate" is. (And it's = pretty commonly a hard to find operation too :) I still feel that this is more of a curio than something you want to = start permanently blocking in the code. How often do you really see = this build? Obliterate is hard to do remember :) Cheers, Karl P > -----Original Message----- > From: ccn...@li...=20 > [mailto:ccn...@li...] On Behalf Of=20 > Perry Ismangil > Sent: Thursday, February 23, 2006 11:53 AM > To: ccn...@li... > Subject: Re: [Ccnet-user] Vault Obliterate triggered build >=20 > On 2/23/06, Karl Palsson <kar...@in...> wrote: >=20 >=20 > Joe is browsing the source, looking at things, looking=20 > for code to cleanup. He sees a file called DELETE_ME.source=20 > and after looking at the contents (empty file or something)=20 > Joe obliterates the file. This was probably a rash bold move=20 > on his behalf, (at least, if obliterate means the usual, not=20 > just delete, but also throw away all history) but it turns=20 > out that some other process uses the delete_me file after=20 > it's been checked out, to manage something else, (Presumably=20 > something where deleting the file indicates that something=20 > is finished)=20 > =09 > Joe's rash move forces a rebuild, and some people get=20 > hopping mad straight away. > =09 > Ok, it's contrived, but if you can filter it out in an=20 > action filter, I'm all for leaving it in. > =09 > =09 >=20 >=20 > Karl, in your example, the build would have been triggered at=20 > "Delete" (as is the case the original poster mentioned, which=20 > is fine), so it would be found out at that stage. In Vault=20 > obliterate is by design a hard to find and hard to do task=20 > (Eric doesn't like it!).=20 >=20 > -- > Perry Ismangil=20 >=20 |
From: Perry I. <ism...@gm...> - 2006-02-23 11:53:06
|
On 2/23/06, Karl Palsson <kar...@in...> wrote: > > > Joe is browsing the source, looking at things, looking for code to > cleanup. He sees a file called DELETE_ME.source and after looking at the > contents (empty file or something) Joe obliterates the file. This was > probably a rash bold move on his behalf, (at least, if obliterate means t= he > usual, not just delete, but also throw away all history) but it turns out > that some other process uses the delete_me file after it's been checked o= ut, > to manage something else, (Presumably something where deleting the file > indicates that something is finished) > > Joe's rash move forces a rebuild, and some people get hopping mad straigh= t > away. > > Ok, it's contrived, but if you can filter it out in an action filter, I'm > all for leaving it in. > > Karl, in your example, the build would have been triggered at "Delete" (as is the case the original poster mentioned, which is fine), so it would be found out at that stage. In Vault obliterate is by design a hard to find an= d hard to do task (Eric doesn't like it!). -- Perry Ismangil |
From: Perry I. <ism...@gm...> - 2006-02-23 11:49:37
|
On 2/22/06, Andy Johnstone <an...@me...> wrote: > > Ian, > > I didn't know about ActionFilter's either. I'll put that in as a > workaround > for now...thanks! > > Yeah, no one really knows about it, I am currently on a promo tour of the feature, since I wrote it :D -- Perry Ismangil |
From: Perry I. <ism...@gm...> - 2006-02-23 11:47:17
|
On 2/23/06, Owen Rogers <exo...@gm...> wrote: Owen, yes, this is possible in the latest 1.1 builds on ccnetlive. i > recently added support for and-ing together a bunch of triggers. take > a look at the operator attribute: > http://confluence.public.thoughtworks.org/display/CCNET/Multiple+Trigger Cool stuff. What else can we expect in 1.1? -- Perry Ismangil |
From: Jonathan P. <Jon...@au...> - 2006-02-23 11:44:11
|
> From: ccn...@li...=20 > [mailto:ccn...@li...] On Behalf Of=20 > Owen Rogers > Sent: Thursday, February 23, 2006 8:04 AM > To: ccn...@li... > Subject: Re: [Ccnet-user] Invalid date formats being passed=20 > to VSS using en-AU culture? >=20 > On 22/02/06, Jonathan Perret <Jon...@au...> wrote: > > This is exactly the issue I hit and reported (with a patch) in the=20 > > CCNET Jira : > > http://jira.public.thoughtworks.org/browse/CCNET-631 > > > > SS.EXE does not exactly use the system locale (I'm not even=20 > sure such=20 > > a thing exists in Windows) but the current user locale, so besides=20 > > patching CC.NET you can also work around this issue by=20 > configuring the=20 > > locale to "English/US" for the user that runs the CCService -=20 > > unfortunately this means that all dates will be displayed=20 > by CC.NET in=20 > > the (inferior <grin>) US date format. >=20 > thomas, taliesin: i've applied this patch to the 1.0 branch=20 > and it is available in 1.0.1.1276. the new build can be=20 > downloaded from: > http://ccnetlive.thoughtworks.com/CCNet-builds/1.0.1.1276/ >=20 > hopefully this will address the issues that you are facing with vss. >=20 > jonathan: sorry that it has taken so long to process your=20 > patch. i've made a few small modifications -- specifically=20 > avoiding the strict dependency on CultureInfo.CurrentCulture=20 > which causes testing problems. my intention is to shortly=20 > release 1.0.1 to address this and some other issues. thanks=20 > again for your contribution. Thank you Owen. I'm sorry if my comment above came out as impatient; I can perfectly relate to the difficulty of making time to work on open-source projects. However I do have a minor nitpick regarding the changes you committed to VssLocale.cs. The following comment is new for VssLocale :=20 /// Keywords are output in the locale of the server and dates are output in the locale of the client, which is, in this case,=20 /// the current culture for the build server. Generally these two locales will be the same; however, if they are different, users /// can specify the server locale using the Vss.Culture property. My issue is with calling the locale used by VSS to output keywords the "server locale". Perhaps you are working under the misconception that the VSS "server" (there is no such thing actually) is in charge of generating the output. What actually happens is that the VSS client (SS.EXE in this case) outputs keywords in a language that is entirely determined by the locale of the VSS SKU that is used as a client (in other words this is set in stone when you pick up the French VSS CD to run the VSS client setup - which I would personally classify as a capital offence but that's not the point <g>). So if an English VSS and a French VSS access the same database they will each return keywords in their own language. In short, I would rather call that "server locale" the "vss executable locale", though I am not entirely satisfied by this naming either... Sorry for the nitpicking :) Cheers, --Jonathan |
From: John <joh...@pi...> - 2006-02-23 10:56:19
|
Hi, When I build one of our applications using Source Safe the Visual Studio task <sourcecontrol type="vss" autoGetSource="true" applyLabel="true"> <project>"$/PixDev/Product 3.2"</project> <username>******</username> <password>******</password> <ssdir>z:\</ssdir> <workingDirectory>C:\BuildIntegration\Product 3.2</workingDirectory> <culture>fr-FR</culture> </sourcecontrol> and <devenv> <solutionfile>"C:\BuildIntegration\Product 3.2\ Auditor.sln" /project "Product 3.2"</solutionfile> <configuration>Release</configuration> <executable>"F:\Program Files\Microsoft Visual Studio .NET 2003\Common7\IDE\devenv.com"</executable> <buildTimeoutSeconds>300</buildTimeoutSeconds> </devenv> CruiseContols sends me a mail telling me the build was sucessful, which is fantastic news. However when I look at the output from the CruiseContol window i can see it actually failed. Does anybody know why this happens or how i can guard against this? [Release Build:Info]: Building [Release Build:Info]: Starting build: F:\Program Files\Microsoft Visual Studio .NET 2003\Common7\IDE\devenv.com "C:\Build\Product 3.2\Product.sln" /project "Product 3.2" /rebuild Release [Release Build:Info]: Devenv build complete. Status: Failure [Release Build:Info]: Build complete: Success Kind Regards, John. |
From: Karl P. <kar...@in...> - 2006-02-23 09:58:35
|
>=20 > I'm of the opinion that a hard-coded filter makes sense, but=20 > I believe an ActionFilter will work in the mean time. (Can=20 > anybody make a case for actually wanting to trigger a build=20 > when something has been obliterated? I can't imagine why.) To make sure that it still builds? Joe is browsing the source, looking at things, looking for code to = cleanup. He sees a file called DELETE_ME.source and after looking at = the contents (empty file or something) Joe obliterates the file. This = was probably a rash bold move on his behalf, (at least, if obliterate = means the usual, not just delete, but also throw away all history) but = it turns out that some other process uses the delete_me file after it's = been checked out, to manage something else, (Presumably something where = deleting the file indicates that something is finished) =20 Joe's rash move forces a rebuild, and some people get hopping mad = straight away. Ok, it's contrived, but if you can filter it out in an action filter, = I'm all for leaving it in. Are you getting obliterates frequently enough that obliterates = triggering the build is really bothering you? This is continuous = integration, how's one more build going to hurt? Cheers, Karl P |
From: Duellmann C. <Car...@ka...> - 2006-02-23 08:35:13
|
Hi John, finally I found the time to look into this again, but to no avail. May I = ask where exactly you made these settings? I tried switching the machine = configuration in "Control Panel/Regional and Language Options" and put = the <culture>en-US</culture> tag into each project in the = ccnet.config-File.=20 Is this what you did? I have not yet tried Thibaud's trick with the SS[culture].dll, do you = still have that file in your VSS directory? Regards Carsten -----Urspr=FCngliche Nachricht----- Von: ccn...@li... = [mailto:ccn...@li...] Im Auftrag von Gilles = DEVAUX Gesendet: Montag, 13. Februar 2006 14:58 An: ccn...@li... Betreff: RE: [Ccnet-user] VSS not getting latest source Hi Carsten, I had the same problem with a machine configured in a French regional = environment. Switching the machine configuration to English and setting = <culture>en-US</culture> in the ccnet configuration file solved the = issue. -----Message d'origine----- De=A0: John [mailto:joh...@pi...] Envoy=E9=A0: Monday, = February 13, 2006 1:35 PM =C0=A0: ccn...@li... = Objet=A0: RE: [Ccnet-user] VSS not getting latest source Hi Carsten, We have just started seeing the same problem with our installation of = Cruisecontrol and like you we have=20 <sourcecontrol type=3D"vss" autoGetSource=3D"true" = applyLabel=3D"true">. So I would be very interested to see and ideas and solutions on why this = might be happening.=20 Thanks in advance, John.=20 -----Original Message----- From: ccn...@li... [mailto:ccn...@li...] On Behalf Of Duellmann = Carsten Sent: 13 February 2006 10:56 To: ccn...@li... Subject: [Ccnet-user] VSS not getting latest source Hi all, first I would like to thank the people at ThoghtWorks for this awesome = product!=20 I am sure that this issue must be a VSS problem... :-) We are using CCNet 1.0.0.1251 with VSS 6.0d. There are several projects = in the config file using the same VSS user. I have written a service = permanently logged in to VSS to solve the "userxy.log not found" problem. Both services run with this users Windows account (actually, = this is my own account, which is something we are still trying to avoid = somehow). When we check in changes, CCNet recognizes them and triggers a build. But the source files that CCNet uses for the build are not of the latest = version. The changes appear in the build report, but not in the source = files. These are the same versions as before the checkin. New files do = not appear in the workspace at all. After this inconsistent build, a forced build does get all the latest = source files and everything works like it should. Is this a known issue and can I do something so that CCNet forces VSS to = always get the latest source? Carsten Duellmann ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log = files for problems? Stop! Download the new AJAX search engine that = makes searching your log files as easy as surfing the web. DOWNLOAD = SPLUNK! http://sel.as-us.falkag.net/sel?cmd=3Dk&kid=103432&bid#0486&dat=121642 _______________________________________________ Ccnet-user mailing list Ccn...@li... https://lists.sourceforge.net/lists/listinfo/ccnet-user ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log = files for problems? Stop! Download the new AJAX search engine that = makes searching your log files as easy as surfing the web. DOWNLOAD = SPLUNK! http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=103432&bid#0486&dat=121642 _______________________________________________ Ccnet-user mailing list Ccn...@li... https://lists.sourceforge.net/lists/listinfo/ccnet-user 2006 - Maporama International=20 2006 - Maporama International - Outgoing mail scanned by BlackSpider ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log = files for problems? Stop! Download the new AJAX search engine that = makes searching your log files as easy as surfing the web. DOWNLOAD = SPLUNK! http://sel.as-us.falkag.net/sel?cmd=3Dk&kid=103432&bid#0486&dat=121642 _______________________________________________ Ccnet-user mailing list Ccn...@li... https://lists.sourceforge.net/lists/listinfo/ccnet-user |
From: Owen R. <exo...@gm...> - 2006-02-23 08:27:27
|
On 21/02/06, Madhusudhanan Ravisankar <mad...@ya...> wrote: > We are using CruiseControl.NET ver. 1.0 Final for build integration. Our > source control is ClearCase ver. 2003.06. After having configured the ccn= et > server to monitor our source code in the "VOB" - "wafr_viper_2435", we at > times get the following exception from ccnet. > > "ThoughtWorks.CruiseControl.Core.CruiseControlException: > Source control operation failed: db_server: RPC: Remote system error - > [WINSOCK] Connection timed out cleartool: Error: Database timed out -- > aborting transaction: "\WAFR_Viper_2435". cleartool: Error: Trouble openi= ng > VOB database: "\WAFR_Viper_2435". cleartool: Error: Not a vob object: > "ThoughtWorks.CruiseControl.Core.CruiseControlException: > Source control operation failed: cleartool: E rror: Unable to contact > albd_server on host 'cc-ent-01' cleartool: Error: Unable to contact albd > server on host cc-ent-01 cleartool: Error: Error from VOB database: > "\WAFR_Viper_2435". cleartool: Error: Trouble opening VOB database: > "\WAFR_Viper_2435". cleartool: Error: Not a vob object: > "E:\Release_6.1.2\Source\WAFR_Viper_2435\ViperUI". . > Process command: cleartool.exe lshist -r -nco -branch "r6.1.2_working_us" > -since 20-Feb-2006.15:12:25 -fmt > "%u#~#%Vd#~#%En#~#%Vn#~#%o#~#!%l#~#!%a#~#%Nc@#@#@#@#@#@#@#@#@#@#@#@\n" > "E:\Release_6.1.2\Source\WAFR_Viper_2435\ViperUI" at both of these messages seem to be errors returned from clearcase related to problems faced by clearcase. if you execute these commands from the command line can you reproduce these messages? if so, you might want to bring them to the attention of your clearcase administrator to resolve. cheers, owen. -- Owen Rogers | http://dotnetjunkies.com/weblog/exortech | CruiseControl.NET - http://ccnet.thoughtworks.com |
From: Owen R. <exo...@gm...> - 2006-02-23 08:06:42
|
hi coby, On 21/02/06, Coby Nielsen <cni...@so...> wrote: > I have a file name that has a space in it that is giving me problems in t= he > ccnet.config file. I am unable to change the name of the file because of > the loss of history that will happen. Is there any way to escape the spa= ce? > In most cases I am able to use "\" but here it just passes it through. > Any help would be great. what element in the ccnet.config file is causing this problem for you? cheers, owen. -- Owen Rogers | http://dotnetjunkies.com/weblog/exortech | CruiseControl.NET - http://ccnet.thoughtworks.com |
From: Owen R. <exo...@gm...> - 2006-02-23 07:46:18
|
hi robert, On 22/02/06, Rob...@co... <Rob...@co...> wrot= e: > I would like to build a particular label without getting the latest from > SourceControl (VSS). could you tell us a little bit more about your motivation for doing this? are you interested in reproducing a particular build from a specific label? or are you talking about setting up a ccnet project to monitor a vss branch? if it is the former: ccnet is not really designed to do this. it is a continuous integration server. it is designed to always integrate the latest changes that have been checked into the repository. one way to access historical builds is to have ccnet archive old builds using the build publisher. these archived builds can then be made available via a web share, for example, for people to access and download. this is what we do on ccnetlive: http://ccnetlive.thoughtworks.com/CCNet%2Dbuilds/ if it is the latter: in my limited understanding, branches in vss are managed by branching shared folders/projects. thus, to monitor a branch just means changing the project that ccnet is monitoring to reflect the branch. if i've misunderstood your intention, please help clarify. > In my SourceControl block I would set autoGetSource=3D"false" so that I d= on't > get the latest from Visual Source Safe. But I don't know where to set and > get a specific label. > > I think the answer is in the Filtered SourceControl Block but I haven't h= ad > any luck yet i don't believe that the filtered sourcecontrol block will help you do this= . cheers, owen. -- Owen Rogers | http://dotnetjunkies.com/weblog/exortech | CruiseControl.NET - http://ccnet.thoughtworks.com |
From: Owen R. <exo...@gm...> - 2006-02-23 07:19:44
|
hi alex, On 22/02/06, Roebuck, Alex <aro...@ea...> wrote: > It would be useful if I could combine project triggers together, i.e. onl= y > if ALL trigger events occur, then run build. Is that possible? yes, this is possible in the latest 1.1 builds on ccnetlive. i recently added support for and-ing together a bunch of triggers. take a look at the operator attribute: http://confluence.public.thoughtworks.org/display/CCNET/Multiple+Trigger one caveat: the 1.1 builds are interim builds. please feel free to download and experiment with them, but i would recommend doing so locally without disrupting your main build server until you can verify that this works to your expectations. cheers, owen. -- Owen Rogers | http://dotnetjunkies.com/weblog/exortech | CruiseControl.NET - http://ccnet.thoughtworks.com |
From: Owen R. <exo...@gm...> - 2006-02-23 07:04:03
|
On 22/02/06, Jonathan Perret <Jon...@au...> wrote: > This is exactly the issue I hit and reported (with a patch) in the CCNET > Jira : > http://jira.public.thoughtworks.org/browse/CCNET-631 > > SS.EXE does not exactly use the system locale (I'm not even sure such a > thing exists in Windows) but the current user locale, so besides patching > CC.NET you can also work around this issue by configuring the locale to > "English/US" for the user that runs the CCService - unfortunately this me= ans > that all dates will be displayed by CC.NET in the (inferior <grin>) US da= te > format. thomas, taliesin: i've applied this patch to the 1.0 branch and it is available in 1.0.1.1276. the new build can be downloaded from: http://ccnetlive.thoughtworks.com/CCNet-builds/1.0.1.1276/ hopefully this will address the issues that you are facing with vss. jonathan: sorry that it has taken so long to process your patch. i've made a few small modifications -- specifically avoiding the strict dependency on CultureInfo.CurrentCulture which causes testing problems. my intention is to shortly release 1.0.1 to address this and some other issues. thanks again for your contribution. cheers, owen. -- Owen Rogers | http://dotnetjunkies.com/weblog/exortech | CruiseControl.NET - http://ccnet.thoughtworks.com |
From: Andy J. <an...@me...> - 2006-02-22 21:37:43
|
Ian, I didn't know about ActionFilter's either. I'll put that in as a workaround for now...thanks! Andy -----Original Message----- From: Ian Olsen [mailto:ia...@so...] Sent: Wednesday, February 22, 2006 4:26 PM To: ccn...@li... Subject: RE: [Ccnet-user] Vault Obliterate triggered build Perry, I'm of the opinion that a hard-coded filter makes sense, but I believe an ActionFilter will work in the mean time. (Can anybody make a case for actually wanting to trigger a build when something has been obliterated? I can't imagine why.) Andy, If you're not familiar with ActionFilters (I wasn't), the documentation is here: http://confluence.public.thoughtworks.org/display/CCNET/Filtered+Source+Cont rol+Block#FilteredSourceControlBlock-ActionFilter. I haven't actually tested it, but a quick look at the code makes it look like obliterate will be correctly parsed from history, and you could filter out the "Obliterated" action to prevent a build from being triggered. -- Ian ________________________________ From: ccn...@li... [mailto:ccn...@li...] On Behalf Of Perry Ismangil Sent: Wednesday, February 22, 2006 10:58 AM To: ccn...@li... Subject: Re: [Ccnet-user] Vault Obliterate triggered build On 2/22/06, Ian Olsen <ia...@so...> wrote: Andy, This certainly doesn't sound like correct behavior from a build standpoint, but it does make sense that it happens. Obliterate does produce a history event and a new folder version, and we're not doing anything to filter these out, so a build would be triggered. I've added it as a CC.NET bug and I'll see what I can do to fix it. Can we hardcode a filter for Obliterate in the Vault cc.net provider? In the short term, can we use ActionFilter to filter it out? Does it even translate to an action? -- Perry Ismangil ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=k&kid3432&bid#0486&dat1642 _______________________________________________ Ccnet-user mailing list Ccn...@li... https://lists.sourceforge.net/lists/listinfo/ccnet-user |
From: Ian O. <ia...@so...> - 2006-02-22 21:25:53
|
Perry, I'm of the opinion that a hard-coded filter makes sense, but I believe = an ActionFilter will work in the mean time. (Can anybody make a case = for actually wanting to trigger a build when something has been = obliterated? I can't imagine why.) Andy, If you're not familiar with ActionFilters (I wasn't), the documentation = is here: = http://confluence.public.thoughtworks.org/display/CCNET/Filtered+Source+C= ontrol+Block#FilteredSourceControlBlock-ActionFilter. I haven't actually tested it, but a quick look at the code makes it look = like obliterate will be correctly parsed from history, and you could = filter out the "Obliterated" action to prevent a build from being = triggered. -- Ian=20 =20 ________________________________ From: ccn...@li... = [mailto:ccn...@li...] On Behalf Of Perry = Ismangil Sent: Wednesday, February 22, 2006 10:58 AM To: ccn...@li... Subject: Re: [Ccnet-user] Vault Obliterate triggered build =09 =09 On 2/22/06, Ian Olsen <ia...@so...> wrote:=20 =09 Andy, =09 This certainly doesn't sound like correct behavior from a build = standpoint, but it does make sense that it happens. Obliterate does = produce a history event and a new folder version, and we're not doing = anything to filter these out, so a build would be triggered. I've added = it as a CC.NET bug and I'll see what I can do to fix it. =09 =09 Can we hardcode a filter for Obliterate in the Vault cc.net provider?=20 =09 In the short term, can we use ActionFilter to filter it out? Does it = even translate to an action?=20 =09 --=20 Perry Ismangil=20 |
From: Gary F. <sfl...@ma...> - 2006-02-22 19:30:56
|
Rob...@Co... wrote: > > I would like to build a particular label without getting the latest > from SourceControl (VSS). > > In my SourceControl block I would set /autoGetSource="false"/ so that > I don't get the latest from Visual Source Safe. But I don't know where > to set and get a specific label. > > I think the answer is in the Filtered SourceControl Block but I > haven't had any luck yet. Nope. The CC.Net source control blocks are primarily there to control the triggering of builds; the fact that they also update the source is a secondary purpose that is often convenient, but very limited. The filtered source control block doesn't do anything of the sort; it simply limits which files in the source directory are used as triggers. If you want to get a specific label from Visual SourceSafe, you'll need to do it yourself, perhaps via NAnt. Getting CC.Net to tell your build which label to use really depends upon how you're using it, particularly how do you decide which label to use? If it's manual and rare (e.g. "I need to rebuild version xxx.") then you may want to consider fetching and building manually. If it's manual and common, you might want to specify the label through some file, have CC.Net trigger based on changes to that file, and have your script do the fetch by reading the label from the same file. Gary |
From: <Rob...@Co...> - 2006-02-22 18:57:11
|
I would like to build a particular label without getting the latest from SourceControl (VSS). In my SourceControl block I would set autoGetSource="false" so that I don't get the latest from Visual Source Safe. But I don't know where to set and get a specific label. I think the answer is in the Filtered SourceControl Block but I haven't had any luck yet. Anyone has done this before? Thanks, Robert Liem ====================================================================== Confidentiality Notice: The information contained in and transmitted with this communication is strictly confidential, is intended only for the use of the intended recipient, and is the property of Countrywide Financial Corporation or its affiliates and subsidiaries. If you are not the intended recipient, you are hereby notified that any use of the information contained in or transmitted with the communication or dissemination, distribution, or copying of this communication is strictly prohibited by law. If you have received this communication in error, please immediately return this communication to the sender and delete the original message and any copy of it in your possession. ====================================================================== |
From: Karl P. <kar...@in...> - 2006-02-22 18:19:17
|
Yeah, you make a virtual dir that maps http://localhost/<PROJECTNAME> = to=20 c:\pvcs\<project names> And then your source control all goes to one place in one hit. Cheers, Karl P =20 > -----Original Message----- > From: ccn...@li...=20 > [mailto:ccn...@li...] On Behalf Of=20 > Richard, Jeff > Sent: Wednesday, February 22, 2006 6:07 PM > To: ccn...@li... > Subject: [Ccnet-user] Source Control Project File Location Headache >=20 > Hello, >=20 > I have run into a scenario I am hoping someone else has=20 > already figured out. I have a C# ASP.NET solution with 5=20 > projects, UI, Common, BDL, DAL, Build. When I get the=20 > solution from source control (PVCS), the ASP.NET project is=20 > linked to http://localhost/<PROJECTNAME>, which points to the=20 > default location c:\inetpub\wwwroot, the remainder of my=20 > files go to the default PVCS working directory, c:\pvcs. So=20 > after getting from source control, the ASP.NET project=20 > resides under c:\inetpub\wwwroot\<project name> and the rest=20 > of the source resides under c:\pvcs\<project names>. The=20 > solution file has a tag called SccLocalPath0 which is set to=20 > " SccLocalPath0 =3D ..\\..\\..\\inetpub\\wwwroot\\<WEBPROJECT>" >=20 > My problem is that the solution file is hardwired to the=20 > physical location of the ASP.NET project, in addition to=20 > being bound to the http location. My problem is that PVCS=20 > plug-in gets to the working directory, but in my case I have=20 > 2 different working directories, I need the source get to go=20 > to the C:\PVCS directory and the c:\inetpub\wwwroot=20 > directory. CCNET only allows 1 source control block per=20 > project, so having two PVCS configuration for the project won't work. >=20 > Has anyone run into this problem and found a solution other=20 > than manual source control gets per project? >=20 >=20 > Jeff Richard > Director II > Enterprise Architecture > Phone: (617) 937-7093 > Fax: (617) 937-8448 > Mobile: (781) 820-3078 > e-mail: jef...@ib... > =20 > -----Original Message----- > From: ccn...@li... > [mailto:ccn...@li...] On Behalf Of=20 > Perry Ismangil > Sent: Tuesday, February 21, 2006 5:08 PM > To: ccn...@li... > Subject: Re: [Ccnet-user] Forcebuild >=20 > On 2/21/06, Roebuck, Alex <aro...@ea...> wrote: > > > > I have a CCNet "master" project that triggers various "sub" projects > on > > remote CCNet servers using ForceBuild. I only want the=20 > master project > to > > succeed if all the sub projects succeed; is there a way to do this? > Also, I >=20 > I don't think so. In fact for me it made sense for the "master" > project is the root dependency of all sub projects, therefore=20 > the sub projects only kicks off when the master is=20 > successful. To detect whether the "whole" build is successful=20 > or not, well, it's back to the good old eyeball method... if=20 > I see five green row then the build is successful! >=20 > > would like the master project to collate the build artefacts of the > sub > > projects into a single location; how could I do that? >=20 > To do this I added yet another project, that uses a=20 > filesystem source control, monitoring a specific file that=20 > will be 'touched' by the last project to be built in the=20 > whole build. If it detects this it knows that the build is=20 > finished and it will gather all the artefacts to the release location. >=20 > A bit arcane, but until we got full build dependency, I guess=20 > I can live with it! >=20 > -- > Perry Ismangil >=20 >=20 > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do you grep=20 > through log files for problems? Stop! Download the new AJAX=20 > search engine that makes searching your log files as easy as=20 > surfing the web. DOWNLOAD SPLUNK! > http://sel.as-us.falkag.net/sel?cmd=3Dk&kid=103432&bid#0486&dat=121642 > _______________________________________________ > Ccnet-user mailing list > Ccn...@li... > https://lists.sourceforge.net/lists/listinfo/ccnet-user >=20 >=20 >=20 > ************************************************************** > ************ > This message and any attached documents contain information=20 > which may be confidential, subject to privilege or exempt=20 > from disclosure under applicable law. These materials are=20 > solely for the use of the intended recipient. If you are not=20 > the intended recipient of this transmission, you are hereby=20 > notified that any distribution, disclosure, printing,=20 > copying, storage, modification or the taking of any action in=20 > reliance upon this transmission is strictly prohibited. =20 > Delivery of this message to any person other than the=20 > intended recipient shall not compromise or waive such=20 > confidentiality, privilege or exemption from disclosure as to=20 > this communication. =20 >=20 > If you have received this communication in error, please=20 > notify the sender immediately and delete this message from=20 > your system. > ************************************************************** > *************** >=20 >=20 >=20 > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do you grep=20 > through log files for problems? Stop! Download the new AJAX=20 > search engine that makes searching your log files as easy as=20 > surfing the web. DOWNLOAD SPLUNK! > http://sel.as-us.falkag.net/sel?cmd=3Dk&kid=103432&bid#0486&dat=121642 > _______________________________________________ > Ccnet-user mailing list > Ccn...@li... > https://lists.sourceforge.net/lists/listinfo/ccnet-user >=20 |
From: Richard, J. <Jef...@ib...> - 2006-02-22 18:07:41
|
Hello, I have run into a scenario I am hoping someone else has already figured out. I have a C# ASP.NET solution with 5 projects, UI, Common, BDL, DAL, Build. When I get the solution from source control (PVCS), the ASP.NET project is linked to http://localhost/<PROJECTNAME>, which points to the default location c:\inetpub\wwwroot, the remainder of my files go to the default PVCS working directory, c:\pvcs. So after getting from source control, the ASP.NET project resides under c:\inetpub\wwwroot\<project name> and the rest of the source resides under c:\pvcs\<project names>. The solution file has a tag called SccLocalPath0 which is set to " SccLocalPath0 =3D ..\\..\\..\\inetpub\\wwwroot\\<WEBPROJECT>" My problem is that the solution file is hardwired to the physical location of the ASP.NET project, in addition to being bound to the http location. My problem is that PVCS plug-in gets to the working directory, but in my case I have 2 different working directories, I need the source get to go to the C:\PVCS directory and the c:\inetpub\wwwroot directory. CCNET only allows 1 source control block per project, so having two PVCS configuration for the project won't work. Has anyone run into this problem and found a solution other than manual source control gets per project? Jeff Richard Director II Enterprise Architecture Phone: (617) 937-7093 Fax: (617) 937-8448 Mobile: (781) 820-3078 e-mail: jef...@ib... =20 -----Original Message----- From: ccn...@li... [mailto:ccn...@li...] On Behalf Of Perry Ismangil Sent: Tuesday, February 21, 2006 5:08 PM To: ccn...@li... Subject: Re: [Ccnet-user] Forcebuild On 2/21/06, Roebuck, Alex <aro...@ea...> wrote: > > I have a CCNet "master" project that triggers various "sub" projects on > remote CCNet servers using ForceBuild. I only want the master project to > succeed if all the sub projects succeed; is there a way to do this? Also, I I don't think so. In fact for me it made sense for the "master" project is the root dependency of all sub projects, therefore the sub projects only kicks off when the master is successful. To detect whether the "whole" build is successful or not, well, it's back to the good old eyeball method... if I see five green row then the build is successful! > would like the master project to collate the build artefacts of the sub > projects into a single location; how could I do that? To do this I added yet another project, that uses a filesystem source control, monitoring a specific file that will be 'touched' by the last project to be built in the whole build. If it detects this it knows that the build is finished and it will gather all the artefacts to the release location. A bit arcane, but until we got full build dependency, I guess I can live with it! -- Perry Ismangil ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=3Dk&kid=103432&bid#0486&dat=121642 _______________________________________________ Ccnet-user mailing list Ccn...@li... https://lists.sourceforge.net/lists/listinfo/ccnet-user ************************************************************************** This message and any attached documents contain information which may be confidential, subject to privilege or exempt from disclosure under applicable law. These materials are solely for=20 the use of the intended recipient. If you are not the intended recipient of this transmission, you are hereby notified that any distribution, disclosure, printing, copying, storage, modification=20 or the taking of any action in reliance upon this transmission is=20 strictly prohibited. Delivery of this message to any person other than the intended recipient shall not compromise or waive=20 such confidentiality, privilege or exemption from disclosure as to this communication. =20 If you have received this communication in error, please notify the sender immediately and delete this message from your system. ***************************************************************************= ** |