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
actually, the current version of cruise in development does support git. I believe the fork you''re using uses a different strategy for git support than we do, so there may be some different behavior on corner cases. if you''d like to see if this is still happening to you with vanilla cruise, our code is at: git://github.com/thoughtworks/cruisecontrolrb.git I''m not sure what you''ll need to do to switch, I don''t know how far the code has diverged, I''d back up everything you have for your cruise stuff now before switching. Jeremy On Thu, Aug 21, 2008 at 3:55 PM, Nicholas Faiz <nicholas.faiz at gmail.com>wrote:> 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 > Cruisecontrolrb-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://rubyforge.org/pipermail/cruisecontrolrb-users/attachments/20080821/306a4bbc/attachment-0001.html>
On Thu, Aug 21, 2008 at 3:59 PM, Jeremy Lightsmith <jeremy.lightsmith at gmail.com> wrote:> actually, the current version of cruise in development does support git. I > believe the fork you''re using uses a different strategy for git support than > we do, so there may be some different behavior on corner cases.The trunk support for git is definitely not ready for prime time. I''m using it to try to get the Rails CI box up again, and it was just hung for like a month trying to do a git merge. Had to manually kill the build and command process. I''ve opened several tickets tagged with git, and put a ticket on the list, no response yet. There have been several other git-related threads too. Even worse, benburkert''s branch is off the old rubyforge Git repo, and not a "real" fork of the new github repo for ccrb. I''ve emailed benburkert off-list about maybe having him re-fork off the official one, but got no response. That is bad, because that means his branch is essentially frozen at the point he branched and not getting any new stuff. If I remember, Alexey''s original objection to this branch was that Grit used native calls, and Alexey preferred to just use the command line to be more cross-platform. So, that is in and sort of working, but needs a lot more work, obviously. It would be great if someone stepped up and did that work, and these divergent git forks went away. Unfortunately, I''m not that person... -- Chad
Hi, I might give it a go, thanks for your reply. Even if I have to clone and checkout from scratch once a day, it''s an improvement. We have no test and build visibility right now. The objection you point out to the fork is interesting, because the way I made it work was to force it to use the command line stuff (I think, it was a quick hack). And, yeh, I''m not that person you mention either. Cheers, Nicholas Chad Woolley wrote:> On Thu, Aug 21, 2008 at 3:59 PM, Jeremy Lightsmith > <jeremy.lightsmith at gmail.com> wrote: > >> actually, the current version of cruise in development does support git. I >> believe the fork you''re using uses a different strategy for git support than >> we do, so there may be some different behavior on corner cases. >> > > The trunk support for git is definitely not ready for prime time. I''m > using it to try to get the Rails CI box up again, and it was just hung > for like a month trying to do a git merge. Had to manually kill the > build and command process. > > I''ve opened several tickets tagged with git, and put a ticket on the > list, no response yet. There have been several other git-related > threads too. > > Even worse, benburkert''s branch is off the old rubyforge Git repo, and > not a "real" fork of the new github repo for ccrb. I''ve emailed > benburkert off-list about maybe having him re-fork off the official > one, but got no response. That is bad, because that means his branch > is essentially frozen at the point he branched and not getting any new > stuff. > > If I remember, Alexey''s original objection to this branch was that > Grit used native calls, and Alexey preferred to just use the command > line to be more cross-platform. So, that is in and sort of working, > but needs a lot more work, obviously. It would be great if someone > stepped up and did that work, and these divergent git forks went away. > Unfortunately, I''m not that person... > > -- Chad > _______________________________________________ > Cruisecontrolrb-users mailing list > Cruisecontrolrb-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users > >
Thanks Jeremy - I''ll check it out later today. It''s my best bet, I think. Nicholas Jeremy Lightsmith wrote:> actually, the current version of cruise in development does support > git. I believe the fork you''re using uses a different strategy for > git support than we do, so there may be some different behavior on > corner cases. > > if you''d like to see if this is still happening to you with vanilla > cruise, our code is at: > > git://github.com/thoughtworks/cruisecontrolrb.git > <http://github.com/thoughtworks/cruisecontrolrb.git> > > I''m not sure what you''ll need to do to switch, I don''t know how far > the code has diverged, I''d back up everything you have for your cruise > stuff now before switching. > > Jeremy > > On Thu, Aug 21, 2008 at 3:55 PM, Nicholas Faiz > <nicholas.faiz at gmail.com <mailto:nicholas.faiz at gmail.com>> wrote: > > 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 > <http://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 > Cruisecontrolrb-users at rubyforge.org > <mailto:Cruisecontrolrb-users at rubyforge.org> > http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users > > > ------------------------------------------------------------------------ > > _______________________________________________ > Cruisecontrolrb-users mailing list > Cruisecontrolrb-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users >
Nicholas Faiz
2008-Aug-22 10:28 UTC
[Cruisecontrolrb-users] git + Re: custom build scripts
Hi, Just to let you know that I did finally get benburket''s fork to work with git. It took a little hacking into what he had, and understanding git + ssh key auth intricacies, but it''s running. If anyone else is stuck I can share my config.. Regards, Nicholas Chad Woolley wrote:> On Thu, Aug 21, 2008 at 3:59 PM, Jeremy Lightsmith > <jeremy.lightsmith at gmail.com> wrote: > >> actually, the current version of cruise in development does support git. I >> believe the fork you''re using uses a different strategy for git support than >> we do, so there may be some different behavior on corner cases. >> > > The trunk support for git is definitely not ready for prime time. I''m > using it to try to get the Rails CI box up again, and it was just hung > for like a month trying to do a git merge. Had to manually kill the > build and command process. > > I''ve opened several tickets tagged with git, and put a ticket on the > list, no response yet. There have been several other git-related > threads too. > > Even worse, benburkert''s branch is off the old rubyforge Git repo, and > not a "real" fork of the new github repo for ccrb. I''ve emailed > benburkert off-list about maybe having him re-fork off the official > one, but got no response. That is bad, because that means his branch > is essentially frozen at the point he branched and not getting any new > stuff. > > If I remember, Alexey''s original objection to this branch was that > Grit used native calls, and Alexey preferred to just use the command > line to be more cross-platform. So, that is in and sort of working, > but needs a lot more work, obviously. It would be great if someone > stepped up and did that work, and these divergent git forks went away. > Unfortunately, I''m not that person... > > -- Chad > _______________________________________________ > Cruisecontrolrb-users mailing list > Cruisecontrolrb-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users > >
On Fri, Aug 22, 2008 at 3:28 AM, Nicholas Faiz <nicholas.faiz at gmail.com> wrote:> Hi, > > Just to let you know that I did finally get benburket''s fork to work with > git. It took a little hacking into what he had, and understanding git + ssh > key auth intricacies, but it''s running. If anyone else is stuck I can share > my config..Sure. It''s a fork on Github, right? Just send the link...