subject:"Unable To execute SCons script in jenkins"

Re: Unable To execute SCons script in jenkins

2016-10-16 Thread Umamaheswari G

Hi Rachel,

Thanks a lot. It finally works with Executing shell script option.

Regards
Uma

On Sat, Oct 15, 2016 at 3:36 PM, Rachel 
wrote:

> Hi Uma,
>
> Congrats! Jenkins executed scons command! But you might choose only an
> option between these ones:
>
>- *Use Scons Plugin* configuring options through* Add build step >
>Invoke scons* script: https://wiki.jenkins-ci.org/
>display/JENKINS/SCons+Plugin
>
>
>- *Not to use Scons Plugin* configuring command through* Add build
>step > Execute shell* and writing the same command you executes
>without Jenkins.
>
> Best regards,
> Rachel
>
>
> El viernes, 14 de octubre de 2016, 14:38:41 (UTC+2), Uma escribió:
>
>> Hi Rachel,
>>
>> Thanks for the help. It does work.  Following is the console output.
>>
>>
>>
>> [workspace] $ scons -f "scons -f /Users/Uma/.jenkins/jobs/Sample/workspace"
>> scons: Reading SConscript files ...
>>
>> scons: warning: Ignoring missing SConscript 'scons -f 
>> /Users/Uma/.jenkins/Sample/New/workspace'
>> File "/usr/local/bin/scons", line 199, in 
>> scons: done reading SConscript files.
>> scons: Building targets ...
>> scons: `.' is up to date.
>> scons: done building targets.
>> Finished: SUCCESS
>>
>>
>> I intentionally made some mistakes in my code.  What I was expecting is some 
>> error message while building with icons.
>>
>>
>> But What I was expecting is
>>
>>
>> scons: Reading SConscript files ...
>>
>> scons: done reading SConscript files.
>>
>> scons: Building targets ...
>>
>> g++ -o Demo/Bed.o -c -Wall -ansi -pedantic -O2 -lX11 -std=c++11 
>> -DSETTINGS_DEVELOPMENT -DUSER_UMA -I/opt/local/include 
>> -Iusr/include/boost/system -I/usr/include/boost -I/usr/include/boost/test 
>> -I/usr/include/boost/timer -I/opt/local/include/mariadb/mysql 
>> -I/opt/local/include/freetype2 -Irapidxml -Ilru_cache Demo/Bed.cpp
>>
>> clang: warning: -lX11: 'linker' input unused
>>
>> Demo/Bed.cpp:23:6: error: C++ requires a type specifier for all declarations
>>
>> Bed::getBedSize(){
>>
>>  ^
>>
>> 1 error generated.
>>
>> scons: *** [Demo/Bed.o] Error 1
>>
>> scons: building terminated because of errors.
>>
>>
>> I guess it is not executing the scons command in my workspace in which I 
>> have my SConstruct file.
>>
>>
>> Thanks
>>
>> Uma
>>
>>
>> On Thu, Oct 13, 2016 at 10:22 PM, Rachel  wrote:
>>
>>> 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 

 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] 
   Workspace Root Directory  [image: Help for feature: Workspace Root 
 Directory] 
   Build Record Root Directory  [image: Help for feature: Build Record Root 
 Directory]

Re: Unable To execute SCons script in jenkins

2016-10-14 Thread Umamaheswari G

Hi Rachel,

Thanks for the help. It does work.  Following is the console output.



[workspace] $ scons -f "scons -f /Users/Uma/.jenkins/jobs/Sample/workspace"
scons: Reading SConscript files ...

scons: warning: Ignoring missing SConscript 'scons -f
/Users/Uma/.jenkins/Sample/New/workspace'
File "/usr/local/bin/scons", line 199, in 
scons: done reading SConscript files.
scons: Building targets ...
scons: `.' is up to date.
scons: done building targets.
Finished: SUCCESS


I intentionally made some mistakes in my code.  What I was expecting
is some error message while building with icons.


But What I was expecting is


scons: Reading SConscript files ...

scons: done reading SConscript files.

scons: Building targets ...

g++ -o Demo/Bed.o -c -Wall -ansi -pedantic -O2 -lX11 -std=c++11
-DSETTINGS_DEVELOPMENT -DUSER_UMA -I/opt/local/include
-Iusr/include/boost/system -I/usr/include/boost
-I/usr/include/boost/test -I/usr/include/boost/timer
-I/opt/local/include/mariadb/mysql -I/opt/local/include/freetype2
-Irapidxml -Ilru_cache Demo/Bed.cpp

clang: warning: -lX11: 'linker' input unused

Demo/Bed.cpp:23:6: error: C++ requires a type specifier for all declarations

Bed::getBedSize(){

 ^

1 error generated.

scons: *** [Demo/Bed.o] Error 1

scons: building terminated because of errors.


I guess it is not executing the scons command in my workspace in which
I have my SConstruct file.


Thanks

Uma


On Thu, Oct 13, 2016 at 10:22 PM, Rachel 
wrote:

> 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 
>>
>> 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] 
>>   Workspace Root Directory  [image: Help for feature: Workspace Root 
>> Directory] 
>>   Build Record Root Directory  [image: Help for feature: Build Record Root 
>> Directory] 
>>
>>
>> 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  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/p
>>> ages/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

Re: Unable To execute SCons script in jenkins

2016-10-13 Thread Rachel

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 
>
> 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] 
>   Workspace Root Directory  [image: Help for feature: Workspace Root 
> Directory] 
>   Build Record Root Directory  [image: Help for feature: Build Record Root 
> Directory] 
>
>
> 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  > 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 >> > 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 
 jenkinsci-use...@googlegroups.com.
 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 
>>

Re: Unable To execute SCons script in jenkins

2016-10-13 Thread Umamaheswari G

Hi,

I have tried removing the build step in  my project->configure->Build.

Now the console output is

Started by user Administrator 

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] 
  Workspace Root Directory  [image: Help for feature: Workspace Root
Directory] 
  Build Record Root Directory  [image: Help for feature: Build Record
Root Directory] 


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 
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 
>> 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/to
>>> pic/jenkinsci-users/Ofs-TV4s10Y/unsubscribe.
>>> To unsubscribe from this group and all its topics, send an email to
>>> jenkinsci-use...@googlegroups.com.
>>> To view this discussion on the web visit https://groups.google.com/d/ms
>>> gid/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
> jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/jenkinsci-users/f9bacef9-916d-4dcc-81fc-d66ebf6031b6%40googlegroups.
> com
> 
> .
>
> 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

Re: Unable To execute SCons script in jenkins

2016-10-12 Thread Rachel

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  > 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 
>> jenkinsci-use...@googlegroups.com .
>> 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 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/f9bacef9-916d-4dcc-81fc-d66ebf6031b6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Unable To execute SCons script in jenkins

2016-10-12 Thread Umamaheswari G

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 <
victormartinezru...@gmail.com> 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
> jenkinsci-users+unsubscr...@googlegroups.com.
> 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 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/CALkqrus-aknJjNNZxXGhkkS-srucyYHdL4BtH_xWj5CTkurrOA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Unable To execute SCons script in jenkins

2016-10-12 Thread Victor Martinez

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 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/5f3616e9-f013-41f7-a237-95421034ef24%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Unable To execute SCons script in jenkins

2016-10-12 Thread Uma

I am trying to build git project using icons script. 

Project Name = Sample
Jenkins Home =  Users/Uma/.jenkins

Workspace root = ${ITEM_ROOTDIR}/workspace/


Project Structure in Git : 
   — SConstruct 
   — Demo
   —  Files.cpp
   —  Files.hpp


Console Output:

  > git config core.sparsecheckout # timeout=10

 > git checkout -f 79d8e3a80aa4b114f72ad383f985028838f26ab0
 > git rev-list 79d8e3a80aa4b114f72ad383f985028838f26ab0 # timeout=10
No emails were triggered.
[workspace] $ scons -f /Users/Uma/.jenkins/jobs/Sample/workspace
FATAL: command execution failedjava.io.IOException 
: Cannot run 
program "scons" (in directory "/Users/Uma/.jenkins/jobs/Sample/workspace"): 
error=2, No such file or directory
at java.lang.ProcessBuilder.start(ProcessBuilder.java:1048) 

at hudson.Proc$LocalProc.(Proc.java:243) 

at hudson.Proc$LocalProc.(Proc.java:212) 

at hudson.Launcher$LocalLauncher.launch(Launcher.java:815) 

at hudson.Launcher$ProcStarter.start(Launcher.java:381) 




I can run “ scons under "/Users/Uma/.jenkins/jobs/Sample/workspace” with 
success.

What went wrong?


Thanks in advance.

-- 
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/a30de1dc-29d1-4aa9-8d68-7b5af28f1596%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Unable To execute SCons script in jenkins

Re: Unable To execute SCons script in jenkins

Re: Unable To execute SCons script in jenkins

Re: Unable To execute SCons script in jenkins

Re: Unable To execute SCons script in jenkins

Re: Unable To execute SCons script in jenkins

Unable To execute SCons script in jenkins

Unable To execute SCons script in jenkins

8 matches

Site Navigation

Mail list logo

Footer information