Hello,
Before I begin I should say that I'm using a forked version of ccrb
which incorporates git access. It's available here:
git://github.com/benburkert/cruisecontrolrb.git
I'm trying to trigger a shell script in my cruise_config.rb . Well, I
know it's running, as I leave a log of the activities of the script.
Trouble is, the build doesn't finish.
Has anyone else seen this sort of problem? I'm aware it could be to do
with the fork itself, but I was just wondering how people were coping
with building git projects in the absence of the forthcoming ccrb release.
A relevant snippet from my config:
# Build the project by invoking rake task 'custom'
# project.rake_task = 'custom'
# Specify the branch you're testing
# This needs to be set if you used the -b option to cruse add
# project.source_control.branch = 'release'
# Build the project by invoking shell script "build_my_app.sh". Keep in
mind that when the script is invoked,
# current working directory is
<em>[cruise data]</em>/projects/your_project/work, so if you do not
keep build_my_app.sh
# in version control, it should be '../build_my_app.sh' instead
project.build_command = '../lhmu_build.sh'
The script itself:
#!/bin/sh
cd work
rm lhmu_build.log
touch lhmu_build.log
python bootstrap.py >> lhmu_build.log
#bin/buildout >> lhmu_build.log
#bin/instance test -s lhmu >> lhmu_build.log
echo "finished!" >> lhmu_build.log
exit 0
~
And, as I mentioned, the logs verify the lhmu_build.sh script.
As a side note, the git commands worked on my work's git repository
after I put in a small workaround, so if anyone is interested in it, let
me know.
Regards,
Nicholas
_______________________________________________
Cruisecontrolrb-users mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users
