Re: Does Continuum 1.1-beta-3 alter permissions on checked out files?

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

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

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

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

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