script not executable after workspace download
I am trying to set up my build engine. I got it to download all of my components into the local workspace on the build machine, but when it went to run the build script it failed because the script was not executable (see error below). I can not find how to indicate to RTC that a file should have it's execute bit set when it is loaded into a workspace. When I select the file and view the TeamConcert properties in my Eclipse workspace it shows it as executable true.
2008-10-24 15:12:19 Should build occur?
2008-10-24 15:12:19 Yes: Always build a user initiated request.
2008-10-24 15:12:20 Invoking pre-build participant "com.ibm.team.build.jazzscm"
Accepting changes into workspace "ranger build workspace" ...
Fetching files to fetch destination "/usr/IBM/rangerBuild" ...
2008-10-24 15:16:35 Invoking build participant "com.ibm.team.build.cmdline"
java.io.IOException: java.io.IOException: /usr/IBM/rangerBuild/Ranger/nightly_builds/buildranger: cannot execute
at java.lang.UNIXProcess.<init>(UNIXProcess.java:148)
at java.lang.ProcessImpl.start(ProcessImpl.java:65)
at java.lang.ProcessBuilder.start(ProcessBuilder.java:451)
at com.ibm.team.build.internal.engine.CommandLineBuildParticipant.execute(CommandLineBuildParticipant.java:207)
at com.ibm.team.build.internal.engine.CommandLineBuildParticipant.build(CommandLineBuildParticipant.java:76)
at com.ibm.team.build.internal.engine.BuildLoop.invokeBuildParticipants(BuildLoop.java:597)
at com.ibm.team.build.internal.engine.BuildLoop$2.run(BuildLoop.java:428)
at java.lang.Thread.run(Thread.java:595)
2008-10-24 15:12:19 Should build occur?
2008-10-24 15:12:19 Yes: Always build a user initiated request.
2008-10-24 15:12:20 Invoking pre-build participant "com.ibm.team.build.jazzscm"
Accepting changes into workspace "ranger build workspace" ...
Fetching files to fetch destination "/usr/IBM/rangerBuild" ...
2008-10-24 15:16:35 Invoking build participant "com.ibm.team.build.cmdline"
java.io.IOException: java.io.IOException: /usr/IBM/rangerBuild/Ranger/nightly_builds/buildranger: cannot execute
at java.lang.UNIXProcess.<init>(UNIXProcess.java:148)
at java.lang.ProcessImpl.start(ProcessImpl.java:65)
at java.lang.ProcessBuilder.start(ProcessBuilder.java:451)
at com.ibm.team.build.internal.engine.CommandLineBuildParticipant.execute(CommandLineBuildParticipant.java:207)
at com.ibm.team.build.internal.engine.CommandLineBuildParticipant.build(CommandLineBuildParticipant.java:76)
at com.ibm.team.build.internal.engine.BuildLoop.invokeBuildParticipants(BuildLoop.java:597)
at com.ibm.team.build.internal.engine.BuildLoop$2.run(BuildLoop.java:428)
at java.lang.Thread.run(Thread.java:595)
5 answers
I am trying to set up my build engine. I got it to download all of my
components into the local workspace on the build machine, but when it
went to run the build script it failed because the script was not
executable (see error below). I can not find how to indicate to RTC
that a file should have it's execute bit set when it is loaded into a
workspace. When I select the file and view the TeamConcert properties
in my Eclipse workspace it shows it as executable true.
If you are downloading using ant, then you must use a 1.6 VM in order for
it to be able to set the executable bit.
- Dmitry
I'm not using ant to download the files, I am using the jazz build
engine. I have configured a build definition to download the components
and then configured the build definition to run a command which is to
execute a script that was downloaded in one of the components.
You need to run the build engine with a 1.6 VM in order for it to be able
to set the executable bit in this case.
- Dmitry
I'm not using ant to download the files, I am using the jazz build
engine. I have configured a build definition to download the components
and then configured the build definition to run a command which is to
execute a script that was downloaded in one of the components.
You need to run the build engine with a 1.6 VM in order for it to be able
to set the executable bit in this case.
- Dmitry
That worked, I misunderstood what you meant the first time. Does the Eclipse client use a different mechanism to change the permissions, because I am running it with a 1.5 VM and when it downloads the scripts they are exectuable?