As far as I can see, there are two possibilities here: A) Your build works fine when you run it manually, but fails when Jenkins runs it. You want us to help you understand why that happens.
or B) You are setting up a new build process executed by Jenkins. You want us to debug it for you with no other information than one error message. In the case of A, the usual advice is to study the differences in the build environment for the manually executed build and build executed by Jenkins. Usually the difference can be found in permissions or environment variables. You mentioned you believe you have problems with permissions. People on the mailing list cannot help you with that. Permissions on your system have been set by your system administrators. You need to ask them to help. In the case of B, debugging someone's build process over email is very difficult and it is not really what this mailing list is for (because it doesn't have much to do with Jenkins). You can of course describe your use case and the build process to us and ask us for opinions. The better the description you give, the better opinions you might get. It is common for people to come here and tell they have a problem like this and they plan to solve it like this and what do you think. But that requires more than one error message. Good luck with either case and hoping to hear from you again, -- Sami 2012/4/26 Bruno Neves Alves <bruno.neves.al...@eproseed.com>: > Thanks for you response. > > I'm using ant to build this. > > I have change a little bit things and now I'm building over the checkout > repository/workspace. > > The problem now is when I ant is invoking an ant target defined in a file > outside the workspace it cannot access to it... > > I believe that I'm having permission issues. Is there any advices to be > taken on this cases ? > > Thanks ! > > > On 25 April 2012 21:54, Maven User <maven.2.u...@gmail.com> wrote: >> >> >> I'm sorta reading between the lines here - but first order of business >> might be to make sure the files you're planning on editing >> (programattically) exist in some "resources" location in your source tree >> then the build should process them into their final destination. >> >> If this is a non-standard build, you could also check them out, alter them >> then when the next build triggers, remove the workspace prior to building >> (also contingent on the AMOUNT of files you have). >> >> Are you actually building these things? What does this job actually do? >> >> On Wednesday, April 25, 2012 3:48:40 PM UTC-4, b_alves wrote: >>> >>> Hi there. >>> >>> I have instaled Jenkins on red hat. >>> >>> I have one job that is chekingout to jenkins workspace. Then I'm >>> perrforming rsync -aC . desteni_folder so I can build/modify the >>> files. The destination_folder is howned by another user that not >>> jenkins. >>> >>> I receive:rsync: ERROR: cannot stat destination "destination_folder": >>> Permission denied (13) >>> >>> Can someone help me pls ? >>> >>> Thanks > > > > > -- > > > > Bruno Neves Alves > > Senior SOA Consultant > > > > Cell: +352 661 208 491 > > > > Email: bruno.neves.al...@eproseed.com > > > > eProseed Europe s.a. > > eProseed Belgium s.p.r.l. > > eProseed Middle-East Africa s.a.l. > > > > Oracle Middleware Partner of the Year 2011 > > Belgium & Luxembourg > > > > Oracle Partner of the Year 2010 > > Belgium & Luxembourg, Commercial Markets > > > > Oracle Middleware Partner of the Year 2010 > > Europe Middle-East and Africa > > > >
