Hi, Yes, that's the reason. If you remove the build step about SCons, you'll have to add a new step:
- Add build step > Execute shell and write the SCons command: scons -f /Users/Uma/.jenkins/jobs/Sample/workspace or in a smart way: scons -f $WORKSPACE I think you don't need to re-define an environment variable. I hope be useful. Best regards, Rachel El jueves, 13 de octubre de 2016, 10:58:47 (UTC+2), Uma escribió: > > Hi, > > I have tried removing the build step in my project->configure->Build. > > Now the console output is > > Started by user Administrator <http://localhost:8080/user/Admin> > > Building in workspace /Users/Shared/Jenkins/Home/workspace/TestProject > > git rev-parse --is-inside-work-tree # timeout=10 > Fetching changes from the remote Git repository > > git config remote.origin.url https://github.com/guma-005/JenkinsDemo.git # > timeout=10 > Fetching upstream changes from https://github.com/guma-005/JenkinsDemo.git > > git --version # timeout=10 > > git fetch --tags --progress https://github.com/guma-005/JenkinsDemo.git > +refs/heads/*:refs/remotes/origin/* > > git rev-parse refs/remotes/origin/master^{commit} # timeout=10 > > git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10 > Checking out Revision 79d8e3a80aa4b114f72ad383f985028838f26ab0 > (refs/remotes/origin/master) > > git config core.sparsecheckout # timeout=10 > > git checkout -f 79d8e3a80aa4b114f72ad383f985028838f26ab0 > > git rev-list 79d8e3a80aa4b114f72ad383f985028838f26ab0 # timeout=10 > Finished: SUCCESS > > > (Sorry I created another job with same code and everything) > > > Project Structure in Git : > — SConstruct > — Demo > — Files.cpp > — Files.hpp > > Environment variables > List of variables > Name > Value > > Delete > > > > > > > > Home directory /Users/Shared/Jenkins/Home [image: Help for feature: Home > directory] <http://localhost:8080/configure#> > Workspace Root Directory [image: Help for feature: Workspace Root > Directory] <http://localhost:8080/configure#> > Build Record Root Directory [image: Help for feature: Build Record Root > Directory] <http://localhost:8080/configure#> > > > It seems it not even running Scons script in my workspace. If so why it > return SUCCESS? > Thanks in advance. > > > On Wed, Oct 12, 2016 at 9:14 PM, Rachel <[email protected] > <javascript:>> wrote: > >> Hi Uma, >> >> I've used those steps for creating new environment variables in Jenkins, >> but not for overwriting PATH, althouth you might use: >> >> Value = $PATH:/adding/new/path/ >> >> in order not to lose previous value of PATH. Anyway, if scons is located >> in /usr/local/bin (as you indicated), Jenkins would have to find it, >> because that path is usually into PATH variable. >> >> From your output, I guess you're using SCons Plugin. Although it's not >> necessary in this case, try to configure "SCons Executable Path" in "Global >> Configuration" ( >> https://wiki.jenkins-ci.org/pages/viewpage.action?pageId=42470444) with >> /usr/local/bin (without /scons). >> >> If problem persists, maybe it's a bug of SCons Plugin. Try to execute >> SCons through: >> >> - Add build step > Execute shell >> >> Tell us if you get it. >> >> Best regards, >> Rachel >> >> >> El miércoles, 12 de octubre de 2016, 18:29:50 (UTC+2), Uma escribió: >>> >>> Hi, >>> Thanks for the reply >>> Where can I set env variable for scons path? >>> >>> I have tried setting Jenkins -> Manage Jetkins -> configure System -> >>> Global Properties -> Environment Variable : >>> Name = PATH >>> Value = /usr/local/bin/scons >>> >>> It does not seems to be work. >>> >>> regards >>> >>> On Wed, Oct 12, 2016 at 6:15 PM, Victor Martinez <[email protected] >>> > wrote: >>> >>>> Hi, >>>> Apparently scons is not part of your env variable path. >>>> >>>> Run 'which scons' and 'echo $PATH' then you will figure out what env >>>> varianles were loaded when running that job. >>>> >>>> Cheers >>>> >>>> -- >>>> You received this message because you are subscribed to a topic in the >>>> Google Groups "Jenkins Users" group. >>>> To unsubscribe from this topic, visit >>>> https://groups.google.com/d/topic/jenkinsci-users/Ofs-TV4s10Y/unsubscribe >>>> . >>>> To unsubscribe from this group and all its topics, send an email to >>>> [email protected]. >>>> To view this discussion on the web visit >>>> https://groups.google.com/d/msgid/jenkinsci-users/5f3616e9-f013-41f7-a237-95421034ef24%40googlegroups.com >>>> . >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>> >>> -- >> You received this message because you are subscribed to a topic in the >> Google Groups "Jenkins Users" group. >> To unsubscribe from this topic, visit >> https://groups.google.com/d/topic/jenkinsci-users/Ofs-TV4s10Y/unsubscribe >> . >> To unsubscribe from this group and all its topics, send an email to >> [email protected] <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/jenkinsci-users/f9bacef9-916d-4dcc-81fc-d66ebf6031b6%40googlegroups.com >> >> <https://groups.google.com/d/msgid/jenkinsci-users/f9bacef9-916d-4dcc-81fc-d66ebf6031b6%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> >> 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/e377974a-6013-4684-89a4-db92fee6378c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
