Viewing the logfile
While developing/testing my build processes I like to have a dynamic view of my logfile as it is produced, so I use BareTail controlled by the following lines in my ANT build file: This works fine except for one small thing: the Continuum job hangs on to the log file view until it is closed. I would like the Continuum job to terminate even though the logfile view is still open. Can anybody suggest a workaround for this? -- View this message in context: http://www.nabble.com/Viewing-the-logfile-tp15560570p15560570.html Sent from the Continuum - Users mailing list archive at Nabble.com.
Re: Replaceable parameters in a shell build definition
I've found a solution: a variation of the %1 %2 %3 ... notation that I've never come across before: %* which passes all the command line parameters in one chunk. A perfect workaround, but there nevertheless appears to be a shortcoming in Continuum in that double quotes get stripped out where they shouldn't be. -- View this message in context: http://www.nabble.com/Replaceable-parameters-in-a-shell-build-definition-tp15496153p15540745.html Sent from the Continuum - Users mailing list archive at Nabble.com.
Replaceable parameters in a shell build definition
I have a build definition which uses a .BAT file to pass parameters to ANT using the %1 %2 %3 ... notation. Several of the parameters are of the type -Dpropertyname=value, and I have discovered that when running the job from a command prompt it is necessary to enclose the parameter in double quotation marks, i.e. -D"propertyname=value". To assist in monitoring this I have temporarily inserted the following line into my BAT file: echo %1: %2: %3: %4: %5: %6: %7: %8: %9>c:\echo.txt This is an example of the file echo.txt when running from the command prompt with quotes: -D"DeploymentTarget=dev": -D"ConfirmDeploymentTarget=y": -D"GUIDeployOrNot=t": -D"SVSDeployOrNot=t": -D"BPELDeployOrNot=t": DeployTRIPSGUI: DeployTRIPSServices: DeployBPEL: and this is without the quotes: -DDeploymentTarget: dev: -DConfirmDeploymentTarget: y: -DGUIDeployOrNot: t: -DSVSDeployOrNot: t: -DBPELDeployOrNot It appears that without the quotes, DOS replaces the = sign with a space, and so each parameter effectively becomes two parameters, and I start losing some parameters altogether because the maximum number you can have is 9. OK, so far the problem is not a Continuum one. However I have replicated the above example in a Continuum shell build definition, and discovered that even with double quotes the file echo.txt is identical to the second example above. I therefore conclude that somewhere down the line Continuum is stripping out my double quotes, and my build falls over. What to do? -- View this message in context: http://www.nabble.com/Replaceable-parameters-in-a-shell-build-definition-tp15496153p15496153.html Sent from the Continuum - Users mailing list archive at Nabble.com.
Customisation of Notification email
I understand that the text of the main body of the notification email is controlled from the file COMMON.VM in CONTINUUM-CORE.JAR in \apps\continuum\webapp\WEB-INF\lib. My builds have associated with them a build number (independent of Continuum's build number) which lives in a file BUILD.NUMBER which contains an entry such as STLabel=0.1.0.85. The value of the STLabel property also becomes a label in my Source Configuration Manager (StarTeam). I would very much like to incorporate this build number into the notification email. Can anybody tell me how I could achieve this? -- View this message in context: http://www.nabble.com/Customisation-of-Notification-email-tp15353066p15353066.html Sent from the Continuum - Users mailing list archive at Nabble.com.
Re: Strange behaviour with StarTeam
Oliver I wasn't very sure how to go about "using the full distrib" as requested, but here's what I did: 1. I downloaded continuum-20080102-12.war into my directory C:\continuum-1.1\apps\continuum\lib 2. I amended my application.xml file so that webapp.file pointed to continuum-20080102-12.war 3. I deleted the contents of my C:\continuum-1.1\apps\continuum\webapp\WEB-INF\lib directory. 4. I restarted the Continuum webapp, and confirmed that the contents of continuum-20080102-12.war were now populated into C:\continuum-1.1\apps\continuum\webapp\WEB-INF\lib 5. I tried some more builds. So far I have been unable to reproduce the error; it looks as though you have solved the problem :jumping: Many thanks for your help! -- View this message in context: http://www.nabble.com/Strange-behaviour-with-StarTeam-tp14527241p14580229.html Sent from the Continuum - Users mailing list archive at Nabble.com.
Re: Strange behaviour with StarTeam
Dan I've had a look at your snapshot file maven-scm-provider-starteam-1.1-20071231.234738-4.jar. What I did was to download it into my C:\continuum-1.1\apps\continuum\webapp\WEB-INF\lib directory, and renamed the 'old' version to maven-scm-provider-starteam-1.0.jarhold. As I mentioned earlier I'm very new to Java stuff, so I'm not clear about the mechanism employed to pick up all the required library files, so after restarting the Continuum webapp, I attempted to rename the snapshot file, and Windows complained that it was already in use, so that assured me that the application was indeed picking it up correctly. I hope that makes sense! However when I then attempted some builds, I'm still seeing the same errors :-(. -- View this message in context: http://www.nabble.com/Strange-behaviour-with-StarTeam-tp14527241p14576128.html Sent from the Continuum - Users mailing list archive at Nabble.com.
Re: Upgrade from Continuum 1.0.3 to 1.1
Toli, "Let me know if you've figured out a way to migrate from 1.0.3 to 1.1. i'd be interested to know." Well I gave up pretty quickly, and worked around the problem by having both versions up at the same time, and copy/pasted all the info from 1.0.3 to 1.1. Fortunately this wasn't a big job for me because I've only got about 12 builds. It does of course mean that I have lost all my history, but that's not too serious. You can fairly easily look at the underlying databases, using for example, SQuirrel SQL Client, and you might be able to figure out a way of transferring the data from 1.0.3 to 1.1 using SQL. Good luck! Ken -- View this message in context: http://www.nabble.com/Upgrade-from-Continuum-1.0.3-to-1.1-tf4897583.html#a14187547 Sent from the Continuum - Users mailing list archive at Nabble.com.
Re: How to include logo
Johnathan Gifford wrote: > > A link to a site that talks specifically about how the xml schema for a > company pom looks would be nice. Doing a search for 'maven company pom' > turns up nothing. Is the information shown in the link suppose to be > include in a project pom file? > > Thanks, > > Johnathan > Johnathan: Try doing a search for 'maven super pom'. http://maven.apache.org/guides/introduction/introduction-to-the-pom.html#Super%20POM This will probably answer your question. -- View this message in context: http://www.nabble.com/How-to-include-logo-tf4900471.html#a14125523 Sent from the Continuum - Users mailing list archive at Nabble.com.
Re: Continuum 1.1: Appearance feature
OK have done. It's JIRA CONTINUUM-1584. -- View this message in context: http://www.nabble.com/Continuum-1.1%3A-Appearance-feature-tf4897268.html#a14027958 Sent from the Continuum - Users mailing list archive at Nabble.com.
Re: Continuum 1.1: Release feature
I confess to never having looked at Maven's Release feature. I will do so now. Thanks for your help. -- View this message in context: http://www.nabble.com/Continuum-1.1%3A-Release-feature-tf4897585.html#a14027439 Sent from the Continuum - Users mailing list archive at Nabble.com.
Continuum 1.1: Release feature
Does anybody know what the Release feature does? I can find nothing in the help pages, and when I tried pushing the Release button on a project that I had successfully built, I got an error java.lang.NullPointerException: groupId was null -- View this message in context: http://www.nabble.com/Continuum-1.1%3A-Release-feature-tf4897585.html#a14026933 Sent from the Continuum - Users mailing list archive at Nabble.com.
Upgrade from Continuum 1.0.3 to 1.1
I've tried following the instructions given
http://maven.apache.org/continuum/documentation/1_1/installation/upgrade.html
here to convert my 1.0.3 database to 1.1, but none of it makes very much
sense in the context of my existing 1.0.3 directory structure:
1. There aren't two databases, only one.
2. The jdbc:derby:${old.continuum.home}/data/continuum/database and
jdbc:derby:${old.continuum.home}/data/users/database parameters provided
don't match my structure.
3. The section entitled Specific steps to do before to import also make no
sense: I cannot trace the builds.xml file under backup directory in my
structure.
Am I missing something here?
--
View this message in context:
http://www.nabble.com/Upgrade-from-Continuum-1.0.3-to-1.1-tf4897583.html#a14026930
Sent from the Continuum - Users mailing list archive at Nabble.com.
