Have you tried this? 
=> 
http://stackoverflow.com/questions/670191/getting-a-source-not-found-error-when-using-source-in-a-bash-script
Put it as first line .... "#!/bin/bash"


On Wednesday, April 13, 2016 at 10:17:56 AM UTC+2, morty wrote:
>
> I have installed Jenkins on Ubuntu 15.10. In a Jenkins job I have a single 
> Execute Shell step with:
>
> virtualenv --no-site-packages virtual_django
> cd virtual_django/bin
> pwd
> dir
> source activate
>
> When I run the job I get:
>
>
> + virtualenv --no-site-packages virtual_djangoNew python executable in 
> virtual_django/bin/python2Also creating executable in 
> virtual_django/bin/pythonInstalling setuptools, pip...done.Running virtualenv 
> with interpreter /usr/bin/python2+ cd virtual_django/bin+ 
> pwd/var/lib/jenkins/workspace/django-demo/virtual_django/bin+ dir
> activate      activate.fish easy_install      pip   pip2.7  python2
> activate.csh  activate_this.py  easy_install-2.7  pip2  python  python2.7+ 
> source activate*/tmp/hudson4515625893361069094.sh: 9: 
> /tmp/hudson4515625893361069094.sh: source: not** found*Build step 'Execute 
> shell' marked build as failure
>
>
>
>
> So in the Jenkins job the *source* command is not found. It works fine 
> from a terminal where I have logged in as the jenkins user. 
>
> Why can't the above script find the *source* command when run inside the 
> Jenkins job?
>

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/1ac3ac17-7e1a-483f-85eb-f4ed383e6b1b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to