For those of you who use G+ :
https://plus.google.com/communities/71418043218379236
cheers
Fábio
I can thing of two ways:
1) property file or
2) environment variable
On Tuesday, November 13, 2012 5:15:55 PM UTC-2, Levin, Ilya wrote:
>
> Hello,
>
>
>
> I have created a maven build project, in the Goals and Options section I
> have:
>
> ` install -P -D=VALUE`
>
>
>
> VALUE is someth
Found it!
There was a problem in the fstab entry which was responsible for mounting
the partition.
I was using *noexec* instead of *exec.*
Just had to change this:
*/dev/vg0/jenkins /jenkins ext4 defaults,auto,noatime,noexec 0 0*
*
*
for this:
*
*
*/dev/vg0/jenkins /jenkins ext4 defaults,auto,n
This is the exception I'm getting:
Building in workspace /jenkins/workspace/teste
Installing JDK jdk-6u34-oth-JPR
Downloading JDK from
http://download.oracle.com/otn/java/jdk/6u34-b04/jdk-6u34-linux-x64.bin
Downloading 72036348bytes
Installing /jenkins/tools/JDK/1.6.34/jdk.sh
[1.6.34] $ /jen
/JDK/jdk-1.6.24/jdk.sh' say?
>
> It should report the executable bits on i.e.:
>
> -rwxr-xr-x 1 tomcat6 tomcat6
>
> Replace tomcat6 with the respective group and user of your environment.
>
> regards
>
> Dirk
>
> On 10.11.2012 17:22, Fábio Ue
Forgot to mention that JENKINS_HOME was pointing to an EXT4 filesystem
created with:
mke2fs -t ext4 -F /dev/vg0/jenkins
Hi,
I'm running Jenkins as a daemon on Amazon Linux (standalone on winstone).
I changed JENKINS_HOME (/etc/sysconfig/jenkins) to point to "*/jenkins"*instead
of "
*/var/lib/jenkins".*
The "*/jenkins*" directory is a new mount based on an EBS volume attached
(/dev/sda1) to the EC2 instance.
Ever
