We can start by having you trim 14 pages out of your signature :-) Ok - really - does sound like a bit of a mess - again - not sure if you're building up an application or package for deployment, but generally, either you have a dependency on an artifact or the bits you need are inside the code base you're having jenkins check out for you.
You'll likely have to chmod or even chown the file that you're trying to execute (I have my fingers crossed you're jenkins server/slaves are *nix, not windows) to either way more rwx or to the group the user is that is running jenkins. Sometimes it not what you CAN do with jenkins (which is pretty amazing these days), but it's a trip back to dev or release engineering to say "hey, if you put this file here and we perform this operation on it during the build, our lives will be 300% better"..... On Wednesday, April 25, 2012 5:28:18 PM UTC-4, b_alves wrote: > > 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 ! > ** > > > >
