Re: Does Continuum 1.1-beta-3 alter permissions on checked out files?
great, thanks, i'll give that a shot... Emmanuel Venisse wrote: > > By default continuum 1.1 use a java cvs client where 1.0.3 used the native > cvs client. > It seems they don't work on the same way. > If you want to use the native cvs client, you can add the following > property in the startup script (wrapper.conf if you use the standalone > version or the webapp container startup script if you use the > webapp): > > -Dmaven.scm.provider.cvs.implementation=cvs_native > > Emmanuel > > jmartin a écrit : >> I have a Continuum project tied to a CVS repository with a build target >> that >> uses a shell script which is checked out from that repository. In >> Continuum >> 1.0.3, this script executes without error, however in 1.1-beta-3, the >> same >> script fails with a "Permission denied" error from /bin/sh. After >> looking >> in the working directory for this project, I found out that the >> executable >> permission is no longer set on the script used by the build target (or >> any >> of the other scripts in this project). This is not the case in the >> corresponding working directory for the Continuum 1.0.3 version of this >> project, nor is it the case when I check out the scripts manually from >> CVS >> on the command line (in both of those cases the scripts are, as expected, >> marked as executable). >> >> So does Continuum 1.1-beta-3 do anything to alter the permissions of the >> files that it checks out? If so, is there some way to keep that from >> happening? >> >> Any help would be much appreciated. Thanks... >> >> -john > > > -- View this message in context: http://www.nabble.com/Does-Continuum-1.1-beta-3-alter-permissions-on-checked-out-files--tf4673550.html#a13369472 Sent from the Continuum - Users mailing list archive at Nabble.com.
Does Continuum 1.1-beta-3 alter permissions on checked out files?
I have a Continuum project tied to a CVS repository with a build target that uses a shell script which is checked out from that repository. In Continuum 1.0.3, this script executes without error, however in 1.1-beta-3, the same script fails with a "Permission denied" error from /bin/sh. After looking in the working directory for this project, I found out that the executable permission is no longer set on the script used by the build target (or any of the other scripts in this project). This is not the case in the corresponding working directory for the Continuum 1.0.3 version of this project, nor is it the case when I check out the scripts manually from CVS on the command line (in both of those cases the scripts are, as expected, marked as executable). So does Continuum 1.1-beta-3 do anything to alter the permissions of the files that it checks out? If so, is there some way to keep that from happening? Any help would be much appreciated. Thanks... -john -- View this message in context: http://www.nabble.com/Does-Continuum-1.1-beta-3-alter-permissions-on-checked-out-files--tf4673550.html#a13352221 Sent from the Continuum - Users mailing list archive at Nabble.com.
what's the process for migrating from 1.0.3 to 1.1-beta-3?
I found this: http://maven.apache.org/continuum/guides/mini/guide-data-management.html Do I follow those steps but with a version of 1.0.3 specified for the database being exported? Or are those migration steps only applicable in a 1.1-beta-2 to 1.1-beta-3 upgrade? If I follow those steps, do I have to export using the beta-2 jar and import using the beta-3 jar, or can I use the beta-3 jar for both? The output when I run the jar with the -help flag indicates that either can read a 1.0.3 database, but the above link indicates that export has to be done with the beta-2 tool. Thanks... -john -- View this message in context: http://www.nabble.com/what%27s-the-process-for-migrating-from-1.0.3-to-1.1-beta-3--tf4637830.html#a13245767 Sent from the Continuum - Users mailing list archive at Nabble.com.
Re: running build targets even when repository code is unchanged?
1.0.3, so i'll give that a shot, it sounds like what i'm looking for. thanks... Emmanuel Venisse wrote: > > What is your Continuum version? > > With Continuum 1.1-beta-3, you can run nightly builds with Build > Fresh/Always build fields in build definitions. > > Emmanuel > > jmartin a écrit : >> Apologies if this has already been answered. I searched the forums (and >> the >> web in general) as well as reading through what Continuum documentation I >> could find, but I was unable to figure this out. >> >> Is it possible to have Continuum run scheduled build targets regardless >> of >> whether the project under which the build target resides has changed? As >> far as I can tell, Continuum will only run scheduled build targets when >> files in the repository for the project have been updated (e.g., by >> adding >> or committing code in CVS). This works fine for most of our stuff, >> specifically where the project specified in Continuum is also the project >> that we want to deploy. >> >> However, we have two instances where the code in the repository specified >> for the Continuum project may change infrequently, despite needing to >> have >> the associated build targets run on a nightly basis. In one case, we're >> trying to push some code on a nightly basis to development servers, but >> the >> project specified in Continuum is a package of shell scripts that doesn't >> change often (one of the scripts in question is what does the nightly >> push). >> In the other case, we want Continuum to trigger an Ant target to perform >> nightly test harness runs (the test harness code tends to change much >> less >> frequently than the application code that's being tested). >> >> I could just do this directly with cron jobs and another wrapper script >> for >> the nightly tests, but having the web interface of Continuum is nice, >> especially since it would allow the non-developers on our team to easily >> and >> safely push newly checked in code or run the test suite without having to >> worry about pulling up a terminal and running the scripts themselves. >> >> Any help would be much appreciated. Thanks very much... >> >> -john > > > -- View this message in context: http://www.nabble.com/running-build-targets-even-when-repository-code-is-unchanged--tf4631473.html#a13238354 Sent from the Continuum - Users mailing list archive at Nabble.com.
running build targets even when repository code is unchanged?
Apologies if this has already been answered. I searched the forums (and the web in general) as well as reading through what Continuum documentation I could find, but I was unable to figure this out. Is it possible to have Continuum run scheduled build targets regardless of whether the project under which the build target resides has changed? As far as I can tell, Continuum will only run scheduled build targets when files in the repository for the project have been updated (e.g., by adding or committing code in CVS). This works fine for most of our stuff, specifically where the project specified in Continuum is also the project that we want to deploy. However, we have two instances where the code in the repository specified for the Continuum project may change infrequently, despite needing to have the associated build targets run on a nightly basis. In one case, we're trying to push some code on a nightly basis to development servers, but the project specified in Continuum is a package of shell scripts that doesn't change often (one of the scripts in question is what does the nightly push). In the other case, we want Continuum to trigger an Ant target to perform nightly test harness runs (the test harness code tends to change much less frequently than the application code that's being tested). I could just do this directly with cron jobs and another wrapper script for the nightly tests, but having the web interface of Continuum is nice, especially since it would allow the non-developers on our team to easily and safely push newly checked in code or run the test suite without having to worry about pulling up a terminal and running the scripts themselves. Any help would be much appreciated. Thanks very much... -john -- View this message in context: http://www.nabble.com/running-build-targets-even-when-repository-code-is-unchanged--tf4631473.html#a13225243 Sent from the Continuum - Users mailing list archive at Nabble.com.
