The problem will most likely be that sudo requires (in the default configuration) a password to be entered before sudo commands can be run. The only way to fix this is probably going to be to get the guys who have access to the /etc/sudoers file to allow the user that needs to run the sudo command (i.e. the user under which Jenkins is running) to run a password-less sudo session for either all commands (unlikely I'd imagine) or for the particular commands being run.
Richard. On Mon, Oct 13, 2014 at 6:15 PM, niraj nandane <[email protected]> wrote: > I have one build machine which have a user "abc" which is not a root user > and have limited sudo access. when I checkout source code and run build > script it works fine. The build script contains sudo command for which it > does not say "sudo: no tty present and no askpass program specified". But > when did same thing from jenkins on that build machine added as slave,it > shows "sudo: no tty present and no askpass program specified". > > I have got one solution saying comment "Default requiretty" in > /etc/sudoers file. But I don’t have access to this file. > > How I can overcome this problem? > > -- > 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/d/optout. > -- 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/d/optout.
