From jeremystellsmith at gmail.com Sun Jan 21 10:45:31 2007 From: jeremystellsmith at gmail.com (Jeremy Stell-Smith) Date: Sun, 21 Jan 2007 09:45:31 -0600 Subject: [Cruisecontrolrb-developers] Version 0.1 is released! Message-ID: so download it, check it out. also, the source is now moved to the cruisecontrolrb project in rubyforge, so do a new checkout and enjoy -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/cruisecontrolrb-developers/attachments/20070121/c77375be/attachment.html From jeremystellsmith at gmail.com Sun Jan 21 21:47:23 2007 From: jeremystellsmith at gmail.com (Jeremy Stell-Smith) Date: Sun, 21 Jan 2007 20:47:23 -0600 Subject: [Cruisecontrolrb-developers] rake.cmd vs rake.bat Message-ID: so after some investigation, it looks like rake.cmd and rake.bat are actually different. I think alex or someone already figured this out, but they weren't around. I suspect that you need a newer version of rake to use cruise, though I don't know which version that is. Rolf, it was breaking for you, so could you do a gem list rake note the version and then do a gem update rake and try it again? it should be fixed after that -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/cruisecontrolrb-developers/attachments/20070121/0bd52f7c/attachment.html From RRussell at thoughtworks.com Mon Jan 22 00:04:40 2007 From: RRussell at thoughtworks.com (Rolf Russell) Date: Sun, 21 Jan 2007 23:04:40 -0600 Subject: [Cruisecontrolrb-developers] rake.cmd vs rake.bat In-Reply-To: Message-ID: It worked. Thanks. Can't tell what changed in the install though: >gem list rake *** LOCAL GEMS *** rake (0.7.1) Ruby based make-like utility. >gem update rake Updating installed gems... Need to update 4 gems from http://gems.rubyforge.org .... complete Attempting remote update of rake Successfully installed rake-0.7.1 Installing ri documentation for rake-0.7.1... Installing RDoc documentation for rake-0.7.1... Gems: [rake] updated "Jeremy Stell-Smith" 01/21/2007 08:47 PM To cruisecontrolrb-developers at rubyforge.org, "Rolf Russell" cc Subject rake.cmd vs rake.bat so after some investigation, it looks like rake.cmd and rake.bat are actually different. I think alex or someone already figured this out, but they weren't around. I suspect that you need a newer version of rake to use cruise, though I don't know which version that is. Rolf, it was breaking for you, so could you do a gem list rake note the version and then do a gem update rake and try it again? it should be fixed after that -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/cruisecontrolrb-developers/attachments/20070121/13a4e5fb/attachment.html From RRussell at thoughtworks.com Mon Jan 22 00:33:25 2007 From: RRussell at thoughtworks.com (Rolf Russell) Date: Sun, 21 Jan 2007 23:33:25 -0600 Subject: [Cruisecontrolrb-developers] [Lipid-developers] Version 0.1 is released! In-Reply-To: Message-ID: Ok, I decided to give the release a real challenge before we announce it. I (and my complete ruby naivete) have downloaded it, taken Alexey's documentation and set it up to run builds against cruisecontrol.rb at rubyforge. Here's what I found: 1. at some point we should change the port from 3000 to avoid conflicting with other rails apps on same box 2. didn't see message "No projects found". I've updated README and deleted the message 3. I ran the build with 'rake' after I checked it out .... and it failed. The error is below. I commented out the test test_build_new_checkin and checked in. This got the build working. 4. When I started the builder the build immediately failed: C:/cruisecontrol-0.1/builds/cruisecontrol.rb/work rrussell$ rake.cmd 'rake.cmd' is not recognized as an internal or external command, operable program or batch file. Jeremy fixed it. I set up an FAQ on the wiki for issues like the 'rake.cmd' issue: http://cruisecontrolrb.rubyforge.org/wiki/wiki.pl?FAQ After that all was good. If I can use this tool, then I think our projects can. And the documentation is great. (We should move it to the wiki at some point though). Does anyone have a reason to wait? If not then I'll email all the guinea pigs tomorrow and tell them to start using it .... --Rolf 1) Failure: test_build_new_checkin(IntegrationTest) [./test/integration/builder_integration_test.rb:46:in `test_build_new_checkin' ./test/integration/builder_integration_test.rb:93:in `with_project' ./test/integration/../sandbox.rb:19:in `create' ./test/integration/../sandbox.rb:19:in `create' ./test/integration/builder_integration_test.rb:84:in `with_project' ./test/integration/builder_integration_test.rb:38:in `test_build_new_checkin' C:/work/innovation/cruisecontrol-ruby/cruisecontrol-0.1/builds/cruisecontrol.rb/work/trunk/config/../vendor/plugins/mocha/lib/mocha/test_case_adapter.rb:19:in `run']: expected but was . 6 tests, 13 assertions, 1 failures, 0 errors rake aborted! Test failures "Jeremy Stell-Smith" Sent by: lipid-developers-bounces at rubyforge.org 01/21/2007 09:45 AM To lipid-developers at rubyforge.org, cruisecontrolrb-developers at rubyforge.org cc Subject [Lipid-developers] Version 0.1 is released! so download it, check it out. also, the source is now moved to the cruisecontrolrb project in rubyforge, so do a new checkout and enjoy _______________________________________________ Lipid-developers mailing list Lipid-developers at rubyforge.org http://rubyforge.org/mailman/listinfo/lipid-developers -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/cruisecontrolrb-developers/attachments/20070121/8dcad041/attachment.html From jeremystellsmith at gmail.com Mon Jan 22 02:52:23 2007 From: jeremystellsmith at gmail.com (Jeremy Stell-Smith) Date: Mon, 22 Jan 2007 01:52:23 -0600 Subject: [Cruisecontrolrb-developers] [Lipid-developers] Version 0.1 is released! In-Reply-To: References: Message-ID: sounds good to me. I walked someone through the install and I saw you hit your bug, rolf. We still have a ways to go before I would say it had "good" usability, but as you say it's definitely working and useful even now. There's always more to add, and I think we should release what we have now. As for the more, I have a lot of the things that I wanted in the EasyStart story more or less working. This even includes a gem. However, it's all minimally tested (it's all command line stuff) and still a bit rough. I would like someone (alex?) to have a look at what I did and give some suggestions. Anyway, stuff to talk about over tomorrow's standup. jeremy On 1/21/07, Rolf Russell wrote: > > > Ok, I decided to give the release a real challenge before we announce it. > I (and my complete ruby naivete) have downloaded it, taken Alexey's > documentation and set it up to run builds against cruisecontrol.rb at > rubyforge. Here's what I found: > > 1. at some point we should change the port from 3000 to avoid conflicting > with other rails apps on same box > 2. didn't see message "No projects found". I've updated README and > deleted the message > 3. I ran the build with 'rake' after I checked it out .... and it failed. > The error is below. *I commented out the test test_build_new_checkin and > checked in*. This got the build working. > 4. When I started the builder the build immediately failed: > C:/cruisecontrol-0.1/builds/cruisecontrol.rb/work rrussell$ > rake.cmd > 'rake.cmd' is not recognized as an internal or external command, > operable program or batch file. > Jeremy fixed it. > > I set up an FAQ on the wiki for issues like the 'rake.cmd' issue: > http://cruisecontrolrb.rubyforge.org/wiki/wiki.pl?FAQ > > After that all was good. If I can use this tool, then I think our > projects can. And the documentation is great. (We should move it to the > wiki at some point though). > > Does anyone have a reason to wait? If not then I'll email all the guinea > pigs tomorrow and tell them to start using it .... > > --Rolf > > > > > 1) Failure: > test_build_new_checkin(IntegrationTest) > [./test/integration/builder_integration_test.rb:46:in > `test_build_new_checkin' > ./test/integration/builder_integration_test.rb:93:in `with_project' > ./test/integration/../sandbox.rb:19:in `create' > ./test/integration/../sandbox.rb:19:in `create' > ./test/integration/builder_integration_test.rb:84:in `with_project' > ./test/integration/builder_integration_test.rb:38:in > `test_build_new_checkin' > C:/work/innovation/cruisecontrol-ruby/cruisecontrol-0.1/builds/cruisecontrol.rb/work/trunk/config/../vendor/plugins/mocha/lib/mocha/test_case_adapter.rb:19:in > `run']: > expected but was > . > > 6 tests, 13 assertions, 1 failures, 0 errors > rake aborted! > Test failures > > > > > > *"Jeremy Stell-Smith" * > Sent by: lipid-developers-bounces at rubyforge.org > > 01/21/2007 09:45 AM > To > lipid-developers at rubyforge.org, cruisecontrolrb-developers at rubyforge.org > cc > Subject > [Lipid-developers] Version 0.1 is released! > > > > > so download it, check it out. > > also, the source is now moved to the cruisecontrolrb project in rubyforge, > so do a new checkout and enjoy > _______________________________________________ > Lipid-developers mailing list > Lipid-developers at rubyforge.org > http://rubyforge.org/mailman/listinfo/lipid-developers > > > _______________________________________________ > Lipid-developers mailing list > Lipid-developers at rubyforge.org > http://rubyforge.org/mailman/listinfo/lipid-developers > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/cruisecontrolrb-developers/attachments/20070122/8218883e/attachment-0001.html From averkhov at thoughtworks.com Mon Jan 22 14:55:46 2007 From: averkhov at thoughtworks.com (Alexey Verkhovsky) Date: Mon, 22 Jan 2007 13:55:46 -0600 Subject: [Cruisecontrolrb-developers] Why port 99 is not a good default Message-ID: Hey, guys, I've changed default port of CC.rb app from 99 to 3333. The reason is in a document called "Well Known Port Numbers". It's published here: http://www.iana.org/assignments/port-numbers As this document says: "The Well Known Ports are assigned by the IANA and on most systems can only be used by system (or root) processes or by programs executed by privileged users." Somewhere else, it says "The range for assigned ports managed by the IANA is 0-1023." So, making default port of your app bigger than 1023 allows regular users run it without root privileges on some unixes. Alex -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/cruisecontrolrb-developers/attachments/20070122/98cbaf65/attachment.html From averkhov at thoughtworks.com Mon Jan 22 20:36:09 2007 From: averkhov at thoughtworks.com (Alexey Verkhovsky) Date: Mon, 22 Jan 2007 19:36:09 -0600 Subject: [Cruisecontrolrb-developers] Bugfixes galore Message-ID: Hey, guys, Revision 22 has all known heinous bugs fixed. This includes rake.cmd on Windows and polluting OS variable RAILS_ENV (which was reason #2 that prevented Stephen from using CC.rb on his project today). The same bug would be a show-stopper for any Rails project that uses standard database tasks. So, I think we should make it release 0.2. Any objections? Also, derelict is upgraded to rev 22. Alex -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/cruisecontrolrb-developers/attachments/20070122/72fd1d8c/attachment.html From jeremystellsmith at gmail.com Tue Jan 23 08:36:55 2007 From: jeremystellsmith at gmail.com (Jeremy Stell-Smith) Date: Tue, 23 Jan 2007 07:36:55 -0600 Subject: [Cruisecontrolrb-developers] Fwd: [Rubygems-developers] where does persistent data go in a gem? In-Reply-To: References: Message-ID: so I have an answer I'm comfortable with for the gem story. the answer is install gems regularly and have a directory in the user's home directory : ~/.cruisecontrol ~/.cruisecontrol/site_config.yml ~/.cruisecontrol/plugins - user & 3rd party plugins ~/.cruisecontrol/builds ~/.cruisecontrol/builds/project_one - etc this sounds like it addresses our biggest concern. a persistent directory that is writeable by the user. the benefit would be : a) "gem install cruisecontrol" is incredibly simple, standard, and painless b) "gem update cruisecontrol" is even more so we might have had to do something like this anyway, otherwise when you update you have to keep "builds", "cruise_plugins", and "site_config.rb" around, and you have to know that you have to do this. it would be nice to make updates up (and down) as painless as possible while we're working with pre-alpha testers what do y'all think? Jeremy ---------- Forwarded message ---------- From: Chad Woolley Date: Jan 22, 2007 12:19 PM Subject: Re: [Rubygems-developers] where does persistent data go in a gem? To: rubygems-developers at rubyforge.org In general, I'd say to create a directory in the user's home directory (possibly starting with a dot and hidden, or maybe not). The user's home dir and /tmp are really the only places you can count on having write access, and /tmp is out because it's likely to go away on reboot. Make sure it's descriptively named (probably containing your gem name), so the user knows what it is when they see a new directory they don't recognize in their home dir. -- Chad On 1/22/07, Jeremy Stell-Smith wrote: > I have a little continuous integration server that I want to release as a > gem. It's a rails app that looks at a folder instead of a db. It all works > rather well, except I'm not sure where this folder should live. > > Assumptions right now are : > 1) the application runs in it's entirety from it's gem home > 2) there's a "cruise" executable that is accessibly from anywhere to do > "cruise start", "cruise add_project", etc > 3) it prompts the user for where to put place it's build directory on it's > first install and subsequent updates. > > 1 & 2 make sense, but 3 kind of sucks. a user could care less where this > stuff lives, and even if they do, they want to specify it once, not on every > install, what if they don't remember where it lives? > > I guess this is a problem others have faced and solved. What's the > conventional wisdom about where to put these types of things? > > Jeremy > > _______________________________________________ > Rubygems-developers mailing list > Rubygems-developers at rubyforge.org > http://rubyforge.org/mailman/listinfo/rubygems-developers > > _______________________________________________ Rubygems-developers mailing list Rubygems-developers at rubyforge.org http://rubyforge.org/mailman/listinfo/rubygems-developers -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/cruisecontrolrb-developers/attachments/20070123/de9e356f/attachment.html From RRussell at thoughtworks.com Tue Jan 23 09:10:14 2007 From: RRussell at thoughtworks.com (Rolf Russell) Date: Tue, 23 Jan 2007 08:10:14 -0600 Subject: [Cruisecontrolrb-developers] Fwd: [Rubygems-developers] where does persistent data go in a gem? In-Reply-To: Message-ID: Makes sense to me. I'm not sure about making it a hidden folder though. Looking at the builds/project folders will be a pretty common activity for the developer. Hidden to me implies something you rarely look at. Do you see an eventual common usage pattern where the plugin & site_config.yml are separated from the builds/project directories? They feel like different kinds of things that a developer might want to separate. --Rolf "Jeremy Stell-Smith" Sent by: cruisecontrolrb-developers-bounces at rubyforge.org 01/23/2007 07:36 AM To cruisecontrolrb-developers at rubyforge.org cc Subject [Cruisecontrolrb-developers] Fwd: [Rubygems-developers] where does persistent data go in a gem? so I have an answer I'm comfortable with for the gem story. the answer is install gems regularly and have a directory in the user's home directory : ~/.cruisecontrol ~/.cruisecontrol/site_config.yml ~/.cruisecontrol/plugins - user & 3rd party plugins ~/.cruisecontrol/builds ~/.cruisecontrol/builds/project_one - etc this sounds like it addresses our biggest concern. a persistent directory that is writeable by the user. the benefit would be : a) "gem install cruisecontrol" is incredibly simple, standard, and painless b) "gem update cruisecontrol" is even more so we might have had to do something like this anyway, otherwise when you update you have to keep "builds", "cruise_plugins", and "site_config.rb" around, and you have to know that you have to do this. it would be nice to make updates up (and down) as painless as possible while we're working with pre-alpha testers what do y'all think? Jeremy ---------- Forwarded message ---------- From: Chad Woolley < thewoolleyman at gmail.com> Date: Jan 22, 2007 12:19 PM Subject: Re: [Rubygems-developers] where does persistent data go in a gem? To: rubygems-developers at rubyforge.org In general, I'd say to create a directory in the user's home directory (possibly starting with a dot and hidden, or maybe not). The user's home dir and /tmp are really the only places you can count on having write access, and /tmp is out because it's likely to go away on reboot. Make sure it's descriptively named (probably containing your gem name), so the user knows what it is when they see a new directory they don't recognize in their home dir. -- Chad On 1/22/07, Jeremy Stell-Smith wrote: > I have a little continuous integration server that I want to release as a > gem. It's a rails app that looks at a folder instead of a db. It all works > rather well, except I'm not sure where this folder should live. > > Assumptions right now are : > 1) the application runs in it's entirety from it's gem home > 2) there's a "cruise" executable that is accessibly from anywhere to do > "cruise start", "cruise add_project", etc > 3) it prompts the user for where to put place it's build directory on it's > first install and subsequent updates. > > 1 & 2 make sense, but 3 kind of sucks. a user could care less where this > stuff lives, and even if they do, they want to specify it once, not on every > install, what if they don't remember where it lives? > > I guess this is a problem others have faced and solved. What's the > conventional wisdom about where to put these types of things? > > Jeremy > > _______________________________________________ > Rubygems-developers mailing list > Rubygems-developers at rubyforge.org > http://rubyforge.org/mailman/listinfo/rubygems-developers > > _______________________________________________ Rubygems-developers mailing list Rubygems-developers at rubyforge.org http://rubyforge.org/mailman/listinfo/rubygems-developers _______________________________________________ Cruisecontrolrb-developers mailing list Cruisecontrolrb-developers at rubyforge.org http://rubyforge.org/mailman/listinfo/cruisecontrolrb-developers -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/cruisecontrolrb-developers/attachments/20070123/d0bf0d37/attachment.html From jeremystellsmith at gmail.com Tue Jan 23 12:17:30 2007 From: jeremystellsmith at gmail.com (Jeremy Stell-Smith) Date: Tue, 23 Jan 2007 11:17:30 -0600 Subject: [Cruisecontrolrb-developers] --password doesn't work for svn+ssh projects Message-ID: I believe this is because ssh is actually the one asking for the password, not svn. In any case, we need to fix this. also, small thing, cruise --help still says builder instead of build -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/cruisecontrolrb-developers/attachments/20070123/821d18f5/attachment-0001.html From RRussell at thoughtworks.com Thu Jan 25 18:13:43 2007 From: RRussell at thoughtworks.com (Rolf Russell) Date: Thu, 25 Jan 2007 17:13:43 -0600 Subject: [Cruisecontrolrb-developers] user feedback? Message-ID: Have we gotten any feedback from users other than Stephen? --Rolf __________________ Rolf Russell Innovation Facilitator ThoughtWorks Inc +1 312 925 0608 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/cruisecontrolrb-developers/attachments/20070125/76f04d8d/attachment.html From talrep at gmail.com Fri Jan 26 09:24:36 2007 From: talrep at gmail.com (Dmitry Verkhovsky) Date: Fri, 26 Jan 2007 17:24:36 +0300 Subject: [Cruisecontrolrb-developers] user feedback? In-Reply-To: References: Message-ID: <86182907-DBFC-4075-BECB-DADF005BDE06@gmail.com> Hi, I've tried it and only had problem with cruise build command. It appeared that subversion_log_parser model doesn't like SVN usernames that contain spaces (if you do an anonymous commit to SVN it will show you in the log as "(no author)"). Please find a patch attached. ? D. On Jan 26, 2007, at 2:13 AM, Rolf Russell wrote: > > Have we gotten any feedback from users other than Stephen? > > --Rolf > > > > > __________________ > Rolf Russell > Innovation Facilitator > ThoughtWorks Inc > +1 312 925 0608 > _______________________________________________ > Cruisecontrolrb-developers mailing list > Cruisecontrolrb-developers at rubyforge.org > http://rubyforge.org/mailman/listinfo/cruisecontrolrb-developers -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/cruisecontrolrb-developers/attachments/20070126/9c9d3ccc/attachment.html -------------- next part -------------- A non-text attachment was scrubbed... Name: patch_to_r34 Type: application/octet-stream Size: 2037 bytes Desc: not available Url : http://rubyforge.org/pipermail/cruisecontrolrb-developers/attachments/20070126/9c9d3ccc/attachment.obj -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/cruisecontrolrb-developers/attachments/20070126/9c9d3ccc/attachment-0001.html From RRussell at thoughtworks.com Fri Jan 26 14:41:22 2007 From: RRussell at thoughtworks.com (Rolf Russell) Date: Fri, 26 Jan 2007 13:41:22 -0600 Subject: [Cruisecontrolrb-developers] problem running build Message-ID: Having a problem with cruisecontrol.rb. Getting the error below. Can you help? I've got it checked out to C:/work/innovation/cruisecontrol.rb/svn, and it is building itself. --Rolf C:/work/innovation/cruisecontrol.rb/svn/trunk/builds/cruisecontrolrb/work rrussell$ ruby -e "require 'rubygems' rescue nil; require 'rake'; load 'C:/work/innovation/cruisecontrol.rb/svn/trunk/tasks/cc_build.rake'; ARGV << '--nosearch' << 'cc:build'; Rake.application.run" rake aborted! No Rakefile found (looking for: rakefile, Rakefile, rakefile.rb, Rakefile.rb) c:/ruby/ruby184-20/lib/ruby/gems/1.8/gems/rake-0.7.1/lib/rake.rb:1822:in `load_rakefile' (See full trace by running task with --trace) -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/cruisecontrolrb-developers/attachments/20070126/c8dca8a1/attachment.html From averkhov at thoughtworks.com Fri Jan 26 15:10:44 2007 From: averkhov at thoughtworks.com (Alexey Verkhovsky) Date: Fri, 26 Jan 2007 14:10:44 -0600 Subject: [Cruisecontrolrb-developers] problem running build In-Reply-To: Message-ID: It doesn't find the Rakefile in the work directory. That's probably because you gave 'cruise add' a URL of Subversion repository root, and not the trunk directory inside it. Alex Rolf Russell Sent by: cruisecontrolrb-developers-bounces at rubyforge.org 01/26/2007 12:41 PM To cruisecontrolrb-developers at rubyforge.org cc Subject [Cruisecontrolrb-developers] problem running build Having a problem with cruisecontrol.rb. Getting the error below. Can you help? I've got it checked out to C:/work/innovation/cruisecontrol.rb/svn, and it is building itself. --Rolf C:/work/innovation/cruisecontrol.rb/svn/trunk/builds/cruisecontrolrb/work rrussell$ ruby -e "require 'rubygems' rescue nil; require 'rake'; load 'C:/work/innovation/cruisecontrol.rb/svn/trunk/tasks/cc_build.rake'; ARGV << '--nosearch' << 'cc:build'; Rake.application.run" rake aborted! No Rakefile found (looking for: rakefile, Rakefile, rakefile.rb, Rakefile.rb) c:/ruby/ruby184-20/lib/ruby/gems/1.8/gems/rake-0.7.1/lib/rake.rb:1822:in `load_rakefile' (See full trace by running task with --trace) _______________________________________________ Cruisecontrolrb-developers mailing list Cruisecontrolrb-developers at rubyforge.org http://rubyforge.org/mailman/listinfo/cruisecontrolrb-developers -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/cruisecontrolrb-developers/attachments/20070126/53a3387c/attachment.html From averkhov at thoughtworks.com Fri Jan 26 17:54:04 2007 From: averkhov at thoughtworks.com (Alexey Verkhovsky) Date: Fri, 26 Jan 2007 16:54:04 -0600 Subject: [Cruisecontrolrb-developers] CI server on derelict is upgraded to rev 59 (EOM) Message-ID: {subj} -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/cruisecontrolrb-developers/attachments/20070126/f34c8798/attachment.html From averkhov at thoughtworks.com Fri Jan 26 19:16:03 2007 From: averkhov at thoughtworks.com (Alexey Verkhovsky) Date: Fri, 26 Jan 2007 18:16:03 -0600 Subject: [Cruisecontrolrb-developers] CI server on derelict is upgraded to rev 63 (EOM) In-Reply-To: Message-ID: -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/cruisecontrolrb-developers/attachments/20070126/8d4cd61c/attachment.html From averkhov at thoughtworks.com Fri Jan 26 19:17:08 2007 From: averkhov at thoughtworks.com (Alexey Verkhovsky) Date: Fri, 26 Jan 2007 18:17:08 -0600 Subject: [Cruisecontrolrb-developers] user feedback? In-Reply-To: <86182907-DBFC-4075-BECB-DADF005BDE06@gmail.com> Message-ID: Patch checked in. Thanks, bro! Alex Dmitry Verkhovsky Sent by: cruisecontrolrb-developers-bounces at rubyforge.org 01/26/2007 07:24 AM To cruisecontrolrb-developers at rubyforge.org cc Subject Re: [Cruisecontrolrb-developers] user feedback? Hi, I've tried it and only had problem with cruise build command. It appeared that subversion_log_parser model doesn't like SVN usernames that contain spaces (if you do an anonymous commit to SVN it will show you in the log as "(no author)"). Please find a patch attached. D. On Jan 26, 2007, at 2:13 AM, Rolf Russell wrote: Have we gotten any feedback from users other than Stephen? --Rolf __________________ Rolf Russell Innovation Facilitator ThoughtWorks Inc +1 312 925 0608 _______________________________________________ Cruisecontrolrb-developers mailing list Cruisecontrolrb-developers at rubyforge.org http://rubyforge.org/mailman/listinfo/cruisecontrolrb-developers _______________________________________________ Cruisecontrolrb-developers mailing list Cruisecontrolrb-developers at rubyforge.org http://rubyforge.org/mailman/listinfo/cruisecontrolrb-developers -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/cruisecontrolrb-developers/attachments/20070126/8b9cd37a/attachment-0001.html -------------- next part -------------- A non-text attachment was scrubbed... Name: patch_to_r34 Type: application/octet-stream Size: 2037 bytes Desc: not available Url : http://rubyforge.org/pipermail/cruisecontrolrb-developers/attachments/20070126/8b9cd37a/attachment-0001.obj From averkhov at thoughtworks.com Sat Jan 27 13:18:04 2007 From: averkhov at thoughtworks.com (Alexey Verkhovsky) Date: Sat, 27 Jan 2007 12:18:04 -0600 Subject: [Cruisecontrolrb-developers] Release 0.3.0 Message-ID: Hey guys, I've made rev 66 into another RubyForge release last night, in case somebody decides to try it out on the weekend. Alex -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/cruisecontrolrb-developers/attachments/20070127/c01736c5/attachment.html From jeremystellsmith at gmail.com Sat Jan 27 21:25:48 2007 From: jeremystellsmith at gmail.com (Jeremy Stell-Smith) Date: Sat, 27 Jan 2007 18:25:48 -0800 Subject: [Cruisecontrolrb-developers] Release 0.3.0 In-Reply-To: References: Message-ID: awesome, good job. btw, did you see the task to package and release from rake? you might have to tweak it to not include my user, but it works pretty well On 1/27/07, Alexey Verkhovsky wrote: > > > Hey guys, > > I've made rev 66 into another RubyForge release last night, in case > somebody decides to try it out on the weekend. > > Alex > _______________________________________________ > Cruisecontrolrb-developers mailing list > Cruisecontrolrb-developers at rubyforge.org > http://rubyforge.org/mailman/listinfo/cruisecontrolrb-developers > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/cruisecontrolrb-developers/attachments/20070127/725b0068/attachment.html From averkhov at thoughtworks.com Mon Jan 29 13:47:47 2007 From: averkhov at thoughtworks.com (Alexey Verkhovsky) Date: Mon, 29 Jan 2007 12:47:47 -0600 Subject: [Cruisecontrolrb-developers] XMPP4R (Jabber library) license = Ruby license Message-ID: I just figured out that XMPP4R's non-GPL license is the Ruby license. So, instead of asking the author for a permission to distribute under some other license, we should be figuring out if Apache 2.0 is compatible with Ruby license (below). For the time being, let's assume that it is. Alex 1. You may make and give away verbatim copies of the source form of the software without restriction, provided that you duplicate all of the original copyright notices and associated disclaimers. 2. You may modify your copy of the software in any way, provided that you do at least ONE of the following: a) place your modifications in the Public Domain or otherwise make them Freely Available, such as by posting said modifications to Usenet or an equivalent medium, or by allowing the author to include your modifications in the software. b) use the modified software only within your corporation or organization. c) rename any non-standard executables so the names do not conflict with standard executables, which must also be provided. d) make other distribution arrangements with the author. 3. You may distribute the software in object code or executable form, provided that you do at least ONE of the following: a) distribute the executables and library files of the software, together with instructions (in the manual page or equivalent) on where to get the original distribution. b) accompany the distribution with the machine-readable source of the software. c) give non-standard executables non-standard names, with instructions on where to get the original software distribution. d) make other distribution arrangements with the author. 4. You may modify and include the part of the software into any other software (possibly commercial). But some files in the distribution are not written by the author, so that they are not under this terms. They are gc.c(partly), utils.c(partly), regex.[ch], st.[ch] and some files under the ./missing directory. See each file for the copying condition. 5. The scripts and library files supplied as input to or produced as output from the software do not automatically fall under the copyright of the software, but belong to whomever generated them, and may be sold commercially, and may be aggregated with this software. 6. THIS SOFTWARE IS PROVIDED "AS IS" AND WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/cruisecontrolrb-developers/attachments/20070129/137ca074/attachment.html From RRussell at thoughtworks.com Mon Jan 29 16:39:47 2007 From: RRussell at thoughtworks.com (Rolf Russell) Date: Mon, 29 Jan 2007 15:39:47 -0600 Subject: [Cruisecontrolrb-developers] XMPP4R (Jabber library) license = Ruby license In-Reply-To: Message-ID: Shall we run this past Legal? I'd be happy to. --Rolf __________________ Rolf Russell Innovation Facilitator ThoughtWorks Inc +1 312 925 0608 Alexey Verkhovsky Sent by: cruisecontrolrb-developers-bounces at rubyforge.org 01/29/2007 12:47 PM To cruisecontrolrb-developers at rubyforge.org cc Subject [Cruisecontrolrb-developers] XMPP4R (Jabber library) license = Ruby license I just figured out that XMPP4R's non-GPL license is the Ruby license. So, instead of asking the author for a permission to distribute under some other license, we should be figuring out if Apache 2.0 is compatible with Ruby license (below). For the time being, let's assume that it is. Alex 1. You may make and give away verbatim copies of the source form of the software without restriction, provided that you duplicate all of the original copyright notices and associated disclaimers. 2. You may modify your copy of the software in any way, provided that you do at least ONE of the following: a) place your modifications in the Public Domain or otherwise make them Freely Available, such as by posting said modifications to Usenet or an equivalent medium, or by allowing the author to include your modifications in the software. b) use the modified software only within your corporation or organization. c) rename any non-standard executables so the names do not conflict with standard executables, which must also be provided. d) make other distribution arrangements with the author. 3. You may distribute the software in object code or executable form, provided that you do at least ONE of the following: a) distribute the executables and library files of the software, together with instructions (in the manual page or equivalent) on where to get the original distribution. b) accompany the distribution with the machine-readable source of the software. c) give non-standard executables non-standard names, with instructions on where to get the original software distribution. d) make other distribution arrangements with the author. 4. You may modify and include the part of the software into any other software (possibly commercial). But some files in the distribution are not written by the author, so that they are not under this terms. They are gc.c(partly), utils.c(partly), regex.[ch], st.[ch] and some files under the ./missing directory. See each file for the copying condition. 5. The scripts and library files supplied as input to or produced as output from the software do not automatically fall under the copyright of the software, but belong to whomever generated them, and may be sold commercially, and may be aggregated with this software. 6. THIS SOFTWARE IS PROVIDED "AS IS" AND WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. _______________________________________________ Cruisecontrolrb-developers mailing list Cruisecontrolrb-developers at rubyforge.org http://rubyforge.org/mailman/listinfo/cruisecontrolrb-developers -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/cruisecontrolrb-developers/attachments/20070129/25757f65/attachment.html From averkhov at thoughtworks.com Tue Jan 30 12:33:18 2007 From: averkhov at thoughtworks.com (Alexey Verkhovsky) Date: Tue, 30 Jan 2007 11:33:18 -0600 Subject: [Cruisecontrolrb-developers] Formatting dates Message-ID: Hey guys, In the process of cleaning up the web frontend, I want to change the format of dates displayed from North American to ISO (i.e. "2007-01-29 19:32" instead of "07:32 PM Jan 29, 2007"). Reason: it's culture-agnostic and much easier to screen scrape I'm also extracting the format_time method into application_helper. Models should deal with values, not formats. Agree? Alex -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/cruisecontrolrb-developers/attachments/20070130/08ffa93f/attachment-0001.html From jeremystellsmith at gmail.com Wed Jan 31 12:40:35 2007 From: jeremystellsmith at gmail.com (Jeremy Stell-Smith) Date: Wed, 31 Jan 2007 09:40:35 -0800 Subject: [Cruisecontrolrb-developers] new logo Message-ID: As part of the new look and feel story, Arthur and I talked to Josh Evnin & Darci Dutcher about the look and usability of the site this morning. Among a bunch of very helpful questions and comments, they had these logos that they'd drafted for the cruise control.rb. I wanted to send them out to the list for some feedback. my vote is for the first one w/ the color scheme of the 3rd. what do other people think? Jeremy -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/cruisecontrolrb-developers/attachments/20070131/d9d777a2/attachment.html -------------- next part -------------- A non-text attachment was scrubbed... Name: cruise_logo.gif Type: image/gif Size: 7904 bytes Desc: not available Url : http://rubyforge.org/pipermail/cruisecontrolrb-developers/attachments/20070131/d9d777a2/attachment.gif From RRussell at thoughtworks.com Wed Jan 31 22:58:18 2007 From: RRussell at thoughtworks.com (Rolf Russell) Date: Wed, 31 Jan 2007 21:58:18 -0600 Subject: [Cruisecontrolrb-developers] new logo In-Reply-To: Message-ID: Defintely like the color scheme of the 3rd. Would vote for the 3rd font, but like the 1st too. "Jeremy Stell-Smith" Sent by: cruisecontrolrb-developers-bounces at rubyforge.org 01/31/2007 11:40 AM To cruisecontrolrb-developers at rubyforge.org, josh.evnin at thoughtworks.com, darci.dutcher at thoughtworks.com cc Subject [Cruisecontrolrb-developers] new logo As part of the new look and feel story, Arthur and I talked to Josh Evnin & Darci Dutcher about the look and usability of the site this morning. Among a bunch of very helpful questions and comments, they had these logos that they'd drafted for the cruise control.rb. I wanted to send them out to the list for some feedback. my vote is for the first one w/ the color scheme of the 3rd. what do other people think? Jeremy _______________________________________________ Cruisecontrolrb-developers mailing list Cruisecontrolrb-developers at rubyforge.org http://rubyforge.org/mailman/listinfo/cruisecontrolrb-developers -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/cruisecontrolrb-developers/attachments/20070131/6ff7d147/attachment.html -------------- next part -------------- A non-text attachment was scrubbed... Name: cruise_logo.gif Type: image/gif Size: 7904 bytes Desc: not available Url : http://rubyforge.org/pipermail/cruisecontrolrb-developers/attachments/20070131/6ff7d147/attachment.gif From talrep at gmail.com Wed Jan 31 14:07:04 2007 From: talrep at gmail.com (Dmitry Verkhovsky) Date: Wed, 31 Jan 2007 22:07:04 +0300 Subject: [Cruisecontrolrb-developers] jabber_notifier plugin Message-ID: <436B324B-49D6-489A-94D5-BB2E039DD4B4@gmail.com> Hi, Please find the subj attached. Im also sending a patch that moves the logic of distinguishing between failed/fixed builds from plugins to the project.rb model. Project.build is now calling new build_failed and build_fixed actions. Regards, Dmitry -------------- next part -------------- A non-text attachment was scrubbed... Name: jabber_notifier.tar.gz Type: application/x-gzip Size: 124779 bytes Desc: not available Url : http://rubyforge.org/pipermail/cruisecontrolrb-developers/attachments/20070131/acb66944/attachment-0001.gz -------------- next part -------------- A non-text attachment was scrubbed... Name: patch_to_r79 Type: application/octet-stream Size: 4063 bytes Desc: not available Url : http://rubyforge.org/pipermail/cruisecontrolrb-developers/attachments/20070131/acb66944/attachment-0001.obj