Thanks for your response guys. MY problem seems to be running tomcat 
(Jenkins is running as a war in tomcat) as root. This is causing all these 
problems. If I run tomcat as myself and the permissions on the jenkins 
folder are say 774 or 777, then it would all work, I suppose. I will give 
it a shot

On Friday, March 8, 2013 3:52:48 AM UTC-6, Varghese Renny wrote:
>
> Hi dilip,
>
>  You can go with
>   setacl to the directory(get inherit to subfolders automatically)
>   umask to newly creating file
>   chown change the owner to who is running the jenkins
>   
>   Regards
>
>
>
> On Fri, Mar 8, 2013 at 2:18 PM, <[email protected] <javascript:>>wrote:
>
>>  Subversion records the permissions settings of files, and when you 
>> check out, they are set. I presume that what you need to do is tell 
>> subversion that this file should be executable.****
>>
>> ** **
>>
>> Here’s my instructions for Eclipse, I’m sure you can look up the command 
>> line equivalent now that you know what to google:****
>>
>> Setting svn:executable for old files (already in the subversion 
>> repository)****
>>
>> In your Eclipse workspace,****
>>
>>     right click on the file, select Team / Set Property****
>>
>>     select the property name svn:executable****
>>
>>     specify a property value of the character "*" (without the quotes)***
>> *
>>
>>     commit your change****
>>
>> ** **
>>
>> By the way, I notice that the gradlew file is owned by root. You’re not 
>> doing the checkout as root, are you? That’s bad.****
>>
>> ** **
>>
>> Hope that helps****
>>
>> Matthew****
>>
>> ** **
>>   
>> *From:* [email protected] <javascript:> [mailto:
>> [email protected] <javascript:>] *On Behalf Of *Dilip
>> *Sent:* 08 March 2013 00:13
>> *To:* [email protected] <javascript:>
>> *Subject:* Jenkins checkout of Subversion code --read only****
>>  
>> ** **
>>
>> Hey guys,****
>>  
>> ** **
>>  
>> Need to throw a quick question to this group.****
>>  
>> Have been using Jenkins for a while, but am trying to configure Jenkins 
>> (1.5 latest) on linux (CentOS) pull a project built using GradleW (version 
>> 1.0)****
>>  
>> All's fine and the job works in windows where the permission structure is 
>> different, but on linux, I get an error. The code is pulled down all fine, 
>> from subversion along with the gradlew file, but....****
>>  
>> ** **
>>  
>> java.io.IOException: Cannot run program "<
>> http://jenkinsboxname:8080/jenkins/job/projname/ws/gradlew";<http://mpbuild01:8080/jenkins/job/AppHub/ws/gradlew%22>>
>>  
>> (in directory "<http://<http://mpbuild01:8080/jenkins/job/AppHub/ws/%22)>
>> enkinsboxname <http://mpbuild01:8080/jenkins/job/AppHub/ws/gradlew%22>
>> :8080/jenkins/job/projname/ws/")<http://mpbuild01:8080/jenkins/job/AppHub/ws/%22)>>:
>>  
>> error=13, Permission denied****
>>  
>> ** **
>>  
>> Looking at permissions on the above gradlew file****
>>  
>> -rw-r--r--.  1 root root  5283 Mar  6 15:00 gradlew****
>>  
>> ** **
>>  
>> So I understand the user (running tomcat, on which jenkins is running) 
>> doesn't have execute permissions on gradlew. How can I pull this file so 
>> everyone (preferably) has permissions? Is there a subversion param I 
>> specify which does this?****
>>  
>> ** **
>>  
>> Or am I totally off and need to do something different?****
>>  
>> ** **
>>  
>> ** **
>>  
>> ** **
>>  
>> Thanks so much****
>>  
>>
>>  ****
>>  
>>  
>>
>> --  
>>
>> This e-mail and any attachments may contain confidential, copyright and 
>> or privileged material, and are for the use of the intended addressee only. 
>> If you are not the intended addressee or an authorised recipient of the 
>> addressee please notify us of receipt by returning the e-mail and do not 
>> use, copy, retain, distribute or disclose the information in or attached to 
>> the e-mail.
>> Any opinions expressed within this e-mail are those of the individual and 
>> not necessarily of Diamond Light Source Ltd. 
>> Diamond Light Source Ltd. cannot guarantee that this e-mail or any 
>> attachments are free from viruses and we cannot accept liability for any 
>> damage which you may sustain as a result of software viruses which may be 
>> transmitted in or with the message.
>> Diamond Light Source Limited (company no. 4375679). Registered in England 
>> and Wales with its registered office at Diamond House, Harwell Science and 
>> Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom
>>  
>>
>>  -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Jenkins Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to [email protected] <javascript:>.
>> For more options, visit https://groups.google.com/groups/opt_out.
>>  
>>  
>>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to