From RRussell at thoughtworks.com Fri Jan 12 15:47:52 2007 From: RRussell at thoughtworks.com (Rolf Russell) Date: Fri, 12 Jan 2007 14:47:52 -0600 Subject: [Lipid-developers] Fw: feature request for cruisecontrol.rb Message-ID: Hi guys, Julian is suggesting integrating with the existing cctray for cc.net. He says it is pretty simple to work with. An option for our first notification story (along with jabber and ym). --Rolf ----- Forwarded by Rolf Russell/UK/ThoughtWorks on 01/12/2007 02:35 PM ----- Julian Simpson/UK/ThoughtWorks 01/11/2007 03:31 AM To Rolf Russell/UK/ThoughtWorks at ThoughtWorks cc Subject Re: feature request for cruisecontrol.rb cc.net has a cctray. I have a patch that will allow cctray to report on projects for a cc.java server. There is the python tray app that came with cc.java, but it's really ugly. There was also a .net based tray app that came with damage control. But I'd prefer to see that rot in favour of one tool working for 3 CI servers. Julian Simpson ThoughtWorks VOIP: +44 7624 000794 PSTN: +44 207 497 4651 Rolf Russell/UK/ThoughtWorks wrote on 10/01/2007 22:11:22: > Do cc.java and cc.net use the same cctray implementation? > > --Rolf > > __________________ > Rolf Russell > Innovation Facilitator > ThoughtWorks Inc > +1 312 925 0608 > > > > > Julian Simpson/UK/ThoughtWorks > > 01/10/2007 08:51 AM > > > > To > > > > Rolf Russell/UK/ThoughtWorks at ThoughtWorks > > > > cc > > > > Subject > > > > feature request for cruisecontrol.rb > > > > support the cctray protocol - it's just an xml document over http; > > this will mean that cc.NET cc.Java and cc.rb could all use the same > > system tray notification tool. > > > > J. > > > > Julian Simpson > > ThoughtWorks > > VOIP: +44 7624 000794 > > PSTN: +44 207 497 4651 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/lipid-developers/attachments/20070112/a2908e38/attachment.html From RRussell at thoughtworks.com Fri Jan 12 16:54:50 2007 From: RRussell at thoughtworks.com (Rolf Russell) Date: Fri, 12 Jan 2007 15:54:50 -0600 Subject: [Lipid-developers] Fw: feature request for cruisecontrol.rb In-Reply-To: Message-ID: >From Julian's email it is xml over http. Julian any more details? --Rolf Alexey Verkhovsky/Canada/ThoughtWorks 01/12/2007 03:26 PM To Rolf Russell/UK/ThoughtWorks at ThoughtWorks cc Julian Simpson/UK/ThoughtWorks at ThoughtWorks, lipid-developers at rubyforge.org Subject Re: Fw: feature request for cruisecontrol.rb Something like CCTray is practically a must-have. What protocol is it using to poll the server? Alex Rolf Russell/UK/ThoughtWorks 01/12/2007 01:47 PM To lipid-developers at rubyforge.org, Alexey Verkhovsky/Canada/ThoughtWorks at ThoughtWorks cc Julian Simpson/UK/ThoughtWorks at ThoughtWorks Subject Fw: feature request for cruisecontrol.rb Hi guys, Julian is suggesting integrating with the existing cctray for cc.net. He says it is pretty simple to work with. An option for our first notification story (along with jabber and ym). --Rolf ----- Forwarded by Rolf Russell/UK/ThoughtWorks on 01/12/2007 02:35 PM ----- Julian Simpson/UK/ThoughtWorks 01/11/2007 03:31 AM To Rolf Russell/UK/ThoughtWorks at ThoughtWorks cc Subject Re: feature request for cruisecontrol.rb cc.net has a cctray. I have a patch that will allow cctray to report on projects for a cc.java server. There is the python tray app that came with cc.java, but it's really ugly. There was also a .net based tray app that came with damage control. But I'd prefer to see that rot in favour of one tool working for 3 CI servers. Julian Simpson ThoughtWorks VOIP: +44 7624 000794 PSTN: +44 207 497 4651 Rolf Russell/UK/ThoughtWorks wrote on 10/01/2007 22:11:22: > Do cc.java and cc.net use the same cctray implementation? > > --Rolf > > __________________ > Rolf Russell > Innovation Facilitator > ThoughtWorks Inc > +1 312 925 0608 > > > > > Julian Simpson/UK/ThoughtWorks > > 01/10/2007 08:51 AM > > > > To > > > > Rolf Russell/UK/ThoughtWorks at ThoughtWorks > > > > cc > > > > Subject > > > > feature request for cruisecontrol.rb > > > > support the cctray protocol - it's just an xml document over http; > > this will mean that cc.NET cc.Java and cc.rb could all use the same > > system tray notification tool. > > > > J. > > > > Julian Simpson > > ThoughtWorks > > VOIP: +44 7624 000794 > > PSTN: +44 207 497 4651 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/lipid-developers/attachments/20070112/e4c6ecb4/attachment.html From averkhov at thoughtworks.com Fri Jan 12 19:44:22 2007 From: averkhov at thoughtworks.com (Alexey Verkhovsky) Date: Fri, 12 Jan 2007 18:44:22 -0600 Subject: [Lipid-developers] First approximation of a working builder is in SVN Message-ID: Revision 37 contains a builder that works (at the "barely useful" level of functionality, but still). Alex -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/lipid-developers/attachments/20070112/3fbb8540/attachment.html From averkhov at thoughtworks.com Mon Jan 15 12:23:34 2007 From: averkhov at thoughtworks.com (Alexey Verkhovsky) Date: Mon, 15 Jan 2007 11:23:34 -0600 Subject: [Lipid-developers] Fw: feature request for cruisecontrol.rb In-Reply-To: Message-ID: Thanks, Julian. Looks straightforward. Two questions, if I may: 1. What is the list of valid values for lastBuildStatus ? 2. What format is lastBuildTime? Looks like RFC3339 to me (http://www.ietf.org/rfc/rfc3339.txt), but without the timezone element. Alex Julian Simpson/UK/ThoughtWorks 01/15/2007 03:13 AM To Alexey Verkhovsky/Canada/ThoughtWorks at ThoughtWorks cc lipid-developers at rubyforge.org, Rolf Russell/UK/ThoughtWorks at ThoughtWorks Subject Re: Fw: feature request for cruisecontrol.rb Here's what the (partial - look at next build tim)> CC implementation does : Julian Simpson ThoughtWorks VOIP: +44 7624 000794 PSTN: +44 207 497 4651 Alexey Verkhovsky/Canada/ThoughtWorks wrote on 12/01/2007 22:03:24: > Good old plain XML over good old plain HTTP? Bliss. > As soon as we have our web app aware of build statuses, we can roll > something like this out in under an hour. > All we need is an example or two of the XML in question. > > Alex > > Rolf Russell/UK/ThoughtWorks > 01/12/2007 02:54 PM > > To > > Alexey Verkhovsky/Canada/ThoughtWorks at ThoughtWorks > > cc > > Julian Simpson/UK/ThoughtWorks at ThoughtWorks, lipid-developers at rubyforge.org > > Subject > > Re: Fw: feature request for cruisecontrol.rb > > From Julian's email it is xml over http. Julian any more details? > > --Rolf > > > > Alexey Verkhovsky/Canada/ThoughtWorks > 01/12/2007 03:26 PM > > To > > Rolf Russell/UK/ThoughtWorks at ThoughtWorks > > cc > > Julian Simpson/UK/ThoughtWorks at ThoughtWorks, lipid-developers at rubyforge.org > > Subject > > Re: Fw: feature request for cruisecontrol.rb > > Something like CCTray is practically a must-have. What protocol is it > using to poll the server? > > Alex > > Rolf Russell/UK/ThoughtWorks > 01/12/2007 01:47 PM > > To > > lipid-developers at rubyforge.org, Alexey > Verkhovsky/Canada/ThoughtWorks at ThoughtWorks > > cc > > Julian Simpson/UK/ThoughtWorks at ThoughtWorks > > Subject > > Fw: feature request for cruisecontrol.rb > > Hi guys, > > Julian is suggesting integrating with the existing cctray for cc.net. > He says it is pretty simple to work with. An option for our first > notification story (along with jabber and ym). > > --Rolf > > ----- Forwarded by Rolf Russell/UK/ThoughtWorks on 01/12/2007 02:35 PM ----- > > Julian Simpson/UK/ThoughtWorks > 01/11/2007 03:31 AM > > To > > Rolf Russell/UK/ThoughtWorks at ThoughtWorks > > cc > > Subject > > Re: feature request for cruisecontrol.rb > > cc.net has a cctray. I have a patch that will allow cctray to report > on projects for a cc.java server. > > There is the python tray app that came with cc.java, but it's really ugly. > > There was also a .net based tray app that came with damage control. > But I'd prefer to see that rot in favour of one tool working for 3 CI servers. > > Julian Simpson > ThoughtWorks > VOIP: +44 7624 000794 > PSTN: +44 207 497 4651 > > Rolf Russell/UK/ThoughtWorks wrote on 10/01/2007 22:11:22: > > > Do cc.java and cc.net use the same cctray implementation? > > > > --Rolf > > > > __________________ > > Rolf Russell > > Innovation Facilitator > > ThoughtWorks Inc > > +1 312 925 0608 > > > > > > > > Julian Simpson/UK/ThoughtWorks > > > 01/10/2007 08:51 AM > > > > > > To > > > > > > Rolf Russell/UK/ThoughtWorks at ThoughtWorks > > > > > > cc > > > > > > Subject > > > > > > feature request for cruisecontrol.rb > > > > > > support the cctray protocol - it's just an xml document over http; > > > this will mean that cc.NET cc.Java and cc.rb could all use the same > > > system tray notification tool. > > > > > > J. > > > > > > Julian Simpson > > > ThoughtWorks > > > VOIP: +44 7624 000794 > > > PSTN: +44 207 497 4651 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/lipid-developers/attachments/20070115/00c8af82/attachment-0001.html From RRussell at thoughtworks.com Mon Jan 15 17:35:19 2007 From: RRussell at thoughtworks.com (Rolf Russell) Date: Mon, 15 Jan 2007 16:35:19 -0600 Subject: [Lipid-developers] can't make today's meeting Message-ID: Sorry - I'll be at the meeting tomorrow. --Rolf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/lipid-developers/attachments/20070115/d2e06792/attachment.html From averkhov at thoughtworks.com Mon Jan 15 18:34:15 2007 From: averkhov at thoughtworks.com (Alexey Verkhovsky) Date: Mon, 15 Jan 2007 17:34:15 -0600 Subject: [Lipid-developers] Filing changeset and build output is now working Message-ID: Hi all, Revision 43 knows how to log all revisions between this and previous build (including the files changed at each revision). It also preserves build output in a file. These outputs go to changeset.log and build.log in the build artifacts directory. The only thing that stands between revision 42 and having enough functionality for EVO-1 release is notification. Which Jeremy spiked out, but it needs to be integrated with the builder. On the subject of using Gmail for notification. We don't (and shouldn't) have any hard-coded assumption of GMail in our app. It's also not a good default configuration. In default configuration, email notification should be simply disabled. It will be good to write in the docs something to the tune of "if you don't have an SMTP server at hand, create yourself a GMail account and use their SMTP service". I, for one, never heard that GMail provides this service. Other webmail services don't (spam prevention). Alex -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/lipid-developers/attachments/20070115/c40e34eb/attachment.html From jeremystellsmith at gmail.com Mon Jan 15 21:06:33 2007 From: jeremystellsmith at gmail.com (Jeremy Stell-Smith) Date: Mon, 15 Jan 2007 21:06:33 -0500 Subject: [Lipid-developers] name change to rocomotive Message-ID: Neal Ford suggested the name Rocomotive for this project. It sounds really good to me and I've already gotten the rubyforge account for the same. Seems to me that it's only going to get much, much harder to change this in the future, so I'd like to do it now. Any objections to doing it later this week like wed/thurs? I can do it during the night, and whoever owns this list (rolf?) can add uses to the corresponding Rocomotive list. Jeremy From averkhov at thoughtworks.com Mon Jan 15 21:23:50 2007 From: averkhov at thoughtworks.com (Alexey Verkhovsky) Date: Mon, 15 Jan 2007 20:23:50 -0600 Subject: [Lipid-developers] We rock Message-ID: By the end of today, it looks like we are about a day away from OVE-1 release. Alex -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/lipid-developers/attachments/20070115/65f2f6f4/attachment.html From RRussell at thoughtworks.com Mon Jan 15 22:16:43 2007 From: RRussell at thoughtworks.com (Rolf Russell) Date: Mon, 15 Jan 2007 21:16:43 -0600 Subject: [Lipid-developers] name change to rocomotive In-Reply-To: Message-ID: Before we change the name we should consider the options. Right now I know of Rocomotive and CruiseControl. Are there other suggestions? I think we should consider CruiseControl. It has recognition, could lend us immediate credibility and is associated with TW. Part of the goal of this project is to increase the reputation of TW in the ruby world. What do you think? The other thing is that if we are going to choose a final name we need to involve the powers that be. They may just want us to use the CruiseControl name since it is associated with TW. Once we have a proposal for the name I'll run it past them. --Rolf "Jeremy Stell-Smith" Sent by: lipid-developers-bounces at rubyforge.org 01/15/2007 08:06 PM To lipid-developers at rubyforge.org cc Subject [Lipid-developers] name change to rocomotive Neal Ford suggested the name Rocomotive for this project. It sounds really good to me and I've already gotten the rubyforge account for the same. Seems to me that it's only going to get much, much harder to change this in the future, so I'd like to do it now. Any objections to doing it later this week like wed/thurs? I can do it during the night, and whoever owns this list (rolf?) can add uses to the corresponding Rocomotive list. Jeremy _______________________________________________ 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/lipid-developers/attachments/20070115/bd2591bb/attachment.html From RRussell at thoughtworks.com Mon Jan 15 22:23:20 2007 From: RRussell at thoughtworks.com (Rolf Russell) Date: Mon, 15 Jan 2007 21:23:20 -0600 Subject: [Lipid-developers] CI for lipid story Message-ID: Hi all, I moved the "CI for lipid" story into OVE release 1 because on further thinking I don't believe we should deploy a tool at a client site that we haven't had running for a couple days at home. Would you agree? --Rolf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/lipid-developers/attachments/20070115/37071be6/attachment.html From RRussell at thoughtworks.com Mon Jan 15 22:29:28 2007 From: RRussell at thoughtworks.com (Rolf Russell) Date: Mon, 15 Jan 2007 21:29:28 -0600 Subject: [Lipid-developers] OVE project Message-ID: Hi guys, Just a heads-up. I received an email from Jonathan Harley who is tech-lead over at OVE. I wasn't aware that the project was already running and so he was a bit surprised to see that I was claiming he would be rolling out Ruby CI. He was unsure if this would work out but was willing to look into it. So there is a chance that we will need to look for another first customer. Stephen can you keep us updated so that we can start looking for another customer immediately if OVE doesn't work out? --Rolf __________________ Rolf Russell Innovation Facilitator ThoughtWorks Inc +1 312 925 0608 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/lipid-developers/attachments/20070115/c2669204/attachment.html From jeremystellsmith at gmail.com Tue Jan 16 00:40:54 2007 From: jeremystellsmith at gmail.com (Jeremy Stell-Smith) Date: Tue, 16 Jan 2007 00:40:54 -0500 Subject: [Lipid-developers] CI for lipid story In-Reply-To: References: Message-ID: makes sense to me On 1/15/07, Rolf Russell wrote: > > Hi all, > > I moved the "CI for lipid" story into OVE release 1 because on further > thinking I don't believe we should deploy a tool at a client site that we > haven't had running for a couple days at home. Would you agree? > > --Rolf > > > _______________________________________________ > Lipid-developers mailing list > Lipid-developers at rubyforge.org > http://rubyforge.org/mailman/listinfo/lipid-developers > > > From jeremystellsmith at gmail.com Tue Jan 16 02:39:11 2007 From: jeremystellsmith at gmail.com (Jeremy Stell-Smith) Date: Tue, 16 Jan 2007 02:39:11 -0500 Subject: [Lipid-developers] Filing changeset and build output is now working In-Reply-To: References: Message-ID: Alex, ping me tomorrow when you get online, I should catch you up personally. I got a lot done. The builder is now reading the configuration from the project_config.rb file. Notification works - I'd like to leave the gmail hardcoding in there until we have a simple way to do it from the webapp. once the web app can do it w/ just a user / password, then maybe we can take it out. - at least that's my vote I was testing all this out on lipid itself, so it IS bootstrappable - I was getting e-mails and everything, it was way cool. still some holes, have a look at /doc/tasks.txt for my thoughts. I also added a new story "Easy Start" on the stories page (http://lipid.rubyforge.org/wiki/wiki.pl?HomePage) I think it should be part of this first release, though maybe it belongs in the second. it might require us to have decided on a name for the project though. night, Jeremy Stell-Smith From averkhov at thoughtworks.com Tue Jan 16 19:19:37 2007 From: averkhov at thoughtworks.com (Alexey Verkhovsky) Date: Tue, 16 Jan 2007 18:19:37 -0600 Subject: [Lipid-developers] Mother of All Refactorings finished Message-ID: Dear all, Revision 56 is the end of merging builder classes with web app models. All tests pass, the builder seems to be working, and so does the web app. At this point, as far as I can say, OVE-1 release is feature-complete. We still have some technical debts to pay on OVE-1 features. It's mostly about making builder's output and the web pages look decent. Also, first thing tomorrow morning, I am setting this tool up to do continuous builds of itself. Plus, we need a name. Alex -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/lipid-developers/attachments/20070116/33ad62f0/attachment-0001.html From averkhov at thoughtworks.com Wed Jan 17 15:27:38 2007 From: averkhov at thoughtworks.com (Alexey Verkhovsky) Date: Wed, 17 Jan 2007 14:27:38 -0600 Subject: [Lipid-developers] Eating our own dog food Message-ID: I've set up continuos integration builds for Lipid trunk itself. Turned out that stuff we copy/pasted from RSCM is not compatible with Linux, so it took us some time to sort this out. If you want to receive email notification for the failing build, please send me a note. Alex, The Build Artist -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/lipid-developers/attachments/20070117/bb020998/attachment.html From jeremystellsmith at gmail.com Wed Jan 17 15:44:56 2007 From: jeremystellsmith at gmail.com (Jeremy Stell-Smith) Date: Wed, 17 Jan 2007 12:44:56 -0800 Subject: [Lipid-developers] Eating our own dog food In-Reply-To: References: Message-ID: is there a way to access the website from the dmz? if not can we get put it somewhere that is accesible? when it is, we can add ourselves to the mailing list through the website, yeah? On 1/17/07, Alexey Verkhovsky wrote: > > I've set up continuos integration builds for Lipid trunk itself. Turned out > that stuff we copy/pasted from RSCM is not compatible with Linux, so it took > us some time to sort this out. > If you want to receive email notification for the failing build, please send > me a note. > > Alex, The Build Artist > _______________________________________________ > Lipid-developers mailing list > Lipid-developers at rubyforge.org > http://rubyforge.org/mailman/listinfo/lipid-developers > > > From averkhov at thoughtworks.com Wed Jan 17 16:18:09 2007 From: averkhov at thoughtworks.com (Alexey Verkhovsky) Date: Wed, 17 Jan 2007 15:18:09 -0600 Subject: [Lipid-developers] Eating our own dog food In-Reply-To: Message-ID: try http://10.8.1.4:3010 "Jeremy Stell-Smith" 01/17/2007 01:44 PM To "Alexey Verkhovsky" cc lipid-developers at rubyforge.org Subject Re: [Lipid-developers] Eating our own dog food is there a way to access the website from the dmz? if not can we get put it somewhere that is accesible? when it is, we can add ourselves to the mailing list through the website, yeah? On 1/17/07, Alexey Verkhovsky wrote: > > I've set up continuos integration builds for Lipid trunk itself. Turned out > that stuff we copy/pasted from RSCM is not compatible with Linux, so it took > us some time to sort this out. > If you want to receive email notification for the failing build, please send > me a note. > > Alex, The Build Artist > _______________________________________________ > 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/lipid-developers/attachments/20070117/0abd7d3b/attachment.html From jeremystellsmith at gmail.com Thu Jan 18 05:17:55 2007 From: jeremystellsmith at gmail.com (Jeremy Stell-Smith) Date: Thu, 18 Jan 2007 02:17:55 -0800 Subject: [Lipid-developers] instead of straight observers... Message-ID: how about something more like this : we'd have an extensions folder, and all the files in the extensions folder would get auto loaded. for example, email_notifier.rb would look something like : class Project plugin :email_notifier end class EmailNotifier attr_accessor :emails def initialize @emails = [] end def build_finished(build) return if @emails.empty? if build.failed? ... end end def memento return nil if emails.empty? " project.email_notifier.emails = [\n" + @emails.map{ |email| ' ' + email.to_s.strip.inspect }.join(",\n") + "\n" + " ]" end end so basically, in each extension file we would : 1) add our extension class as a "plugin" to project, that is something that could be referred to directly and is ALWAYS instantiated (though it may be disabled for most extensions unless explicitly enabled in the config file) the purpose of this is that it's a lot easier to configure something that already exists both from the config file and the web app as well 2) our extension class relies on public methods having special names (convention over configuration). the "plugin" method would also register our extension with the project. for every "event" like build_started, build_finished, checking_for_modifications, etc, it would see if any extension "responds_to?" the event. if so, it will call its method. 3) memento will be required for all plugins so we can persist - however save as little as possible - in some cases, this will be nothing 4) additionally, if this plugin is configurable from the web, we should put calls in here to extend the controller / views to support it, but that's for later, I'm totally cool hardcoding for now. I'm going to sleep but I wanted to get feedback and see if I could change our direction a bit w/o actually implementing it. Good work on the refactorings, Alex, Jeremy -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/lipid-developers/attachments/20070118/28cd29f7/attachment.html From averkhov at thoughtworks.com Thu Jan 18 12:10:26 2007 From: averkhov at thoughtworks.com (Alexey Verkhovsky) Date: Thu, 18 Jan 2007 11:10:26 -0600 Subject: [Lipid-developers] instead of straight observers... In-Reply-To: Message-ID: I think, what you propose deals with the pains of using standard library observers. Let's do this. Alex "Jeremy Stell-Smith" Sent by: lipid-developers-bounces at rubyforge.org 01/18/2007 03:17 AM To lipid-developers at rubyforge.org cc Subject [Lipid-developers] instead of straight observers... how about something more like this : we'd have an extensions folder, and all the files in the extensions folder would get auto loaded. for example, email_notifier.rb would look something like : class Project plugin :email_notifier end class EmailNotifier attr_accessor :emails def initialize @emails = [] end def build_finished(build) return if @emails.empty? if build.failed? ... end end def memento return nil if emails.empty? " project.email_notifier.emails = [\n" + @emails.map{ |email| ' ' + email.to_s.strip.inspect }.join(",\n") + "\n" + " ]" end end so basically, in each extension file we would : 1) add our extension class as a "plugin" to project, that is something that could be referred to directly and is ALWAYS instantiated (though it may be disabled for most extensions unless explicitly enabled in the config file) the purpose of this is that it's a lot easier to configure something that already exists both from the config file and the web app as well 2) our extension class relies on public methods having special names (convention over configuration). the "plugin" method would also register our extension with the project. for every "event" like build_started, build_finished, checking_for_modifications, etc, it would see if any extension "responds_to?" the event. if so, it will call its method. 3) memento will be required for all plugins so we can persist - however save as little as possible - in some cases, this will be nothing 4) additionally, if this plugin is configurable from the web, we should put calls in here to extend the controller / views to support it, but that's for later, I'm totally cool hardcoding for now. I'm going to sleep but I wanted to get feedback and see if I could change our direction a bit w/o actually implementing it. Good work on the refactorings, Alex, Jeremy _______________________________________________ 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/lipid-developers/attachments/20070118/bacc95c3/attachment.html From averkhov at thoughtworks.com Thu Jan 18 13:34:16 2007 From: averkhov at thoughtworks.com (Alexey Verkhovsky) Date: Thu, 18 Jan 2007 12:34:16 -0600 Subject: [Lipid-developers] End of line style attributes Message-ID: revision 76 sets svn:eol-style attribute to native on all source files. It ensures that: (a) when you check a file out, it comes with the right end-of-line sequences for your platform (\n on a Linux, \r on a Mac, \n\r on Windows). (b) when you edit a file in a text editor that is not smart enough to preserve the EOL style of that file, and then commit it to SVN, this doesn't become an "all content out - all content in" change. For an example of what I am talking about, do 'svn diff test\unit\project_test.rb -r 74:73' I think, we should try to make sure that all our source files have this property set in future. Unfortunately, the new files are not going to be created with this property set by default. However, you can configure your SVN client to do so. Make sure that you have the following in it: enable-auto-props = yes [auto-props] *.rb = svn:eol-style=native *.rhtml = svn:eol-style=native *.html = svn:eol-style=native *.rjs = svn:eol-style=native *.js = svn:eol-style=native *.rxml = svn:eol-style=native Location of SVN client config depends on the platform and is described here: http://svnbook.red-bean.com/en/1.1/ch07.html#svn-ch-7-sect-1 Alex -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/lipid-developers/attachments/20070118/cb3bc028/attachment-0001.html From averkhov at thoughtworks.com Thu Jan 18 19:01:03 2007 From: averkhov at thoughtworks.com (Alexey Verkhovsky) Date: Thu, 18 Jan 2007 18:01:03 -0600 Subject: [Lipid-developers] Plugins infrastructure and logging are in Message-ID: Hey, guys, Since there was no standup today, here is my progress report for the day. The way a Project instance communicates events to interested parties (like EmailNotifier) has been refactored along the lines of what Jeremy suggested last night. Also, we added a ProjectLogger class, that listens for project events and logs them using Log class from lib/log.rb. Any other place that needed to say something is doing so via the Log, too. Log is a rather dumb decorator for RAILS_DEFAULT_LOGGER, that knows how to timestamp log entries, e.g.: Log.event("Something good just happened", :debug) otherwise, it just passes every message it receives to RAILS_DEFAULT_LOGGER, e.g.: Log.debug "Moo" Command-line interface to script/builder has a new option -v (--verbose). I've also upgraded our own continuous integration server on derelict to revision 86. Talk to you all tomorrow morning. Alex -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/lipid-developers/attachments/20070118/57d4c621/attachment.html From averkhov at thoughtworks.com Fri Jan 19 17:46:30 2007 From: averkhov at thoughtworks.com (Alexey Verkhovsky) Date: Fri, 19 Jan 2007 16:46:30 -0600 Subject: [Lipid-developers] Interesting problem when reading svn log Message-ID: Hi all, Here is an explanation for rev 92: A couple of times today, I've seen the following situation on derelict: 1. There is a new revision waiting to be built. 2. The builder fails to notice it. 3. stderr of the builder contains lines such as: svn error: Broken pipe So far, I failed to establish the root cause or even just re-create this situation. However, the "Broken pipe" message indicates that svn tries to write something into its stdout when nobody is reading from it anymore. So, I changed the Subversion class to read everything from stdout of svn command into memory, close the pipe, and only then try to parse it. CC.rb installation running on derelict is updated to rev 94. Alex -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/lipid-developers/attachments/20070119/6ae78dc4/attachment.html From averkhov at thoughtworks.com Fri Jan 19 18:27:23 2007 From: averkhov at thoughtworks.com (Alexey Verkhovsky) Date: Fri, 19 Jan 2007 17:27:23 -0600 Subject: [Lipid-developers] Handling locked files in Sandbox#cleanup Message-ID: Something worth mentioning. Sandbox#cleanup will raise an error when there is a locked file in the __sandbox directory after a test is over. This is intentional. There should be no locked files in the sandbox at the end of any test. Alex -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/lipid-developers/attachments/20070119/475d13e2/attachment.html From averkhov at thoughtworks.com Fri Jan 19 19:16:56 2007 From: averkhov at thoughtworks.com (Alexey Verkhovsky) Date: Fri, 19 Jan 2007 18:16:56 -0600 Subject: [Lipid-developers] config/site_config.rb is removed Message-ID: I have deleted config/site_config.rb (that contains details of rocomotive Gmail account) from SVN, because it's not a safe thing to do. Please take care not to check it back in by accident. Next time you do svn up, the file will be removed from your local copy. Then you can restore it right back (it's listed in svn:ignore), and here is what was in the file before deletion: ActionMailer::Base.server_settings = { :address => "smtp.gmail.com", :port => 587, :domain => "yourdomain.com", :authentication => :plain, :user_name => "rocomotive", :password => "r0c0m0tive" } Just do not check it in. Alex -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/lipid-developers/attachments/20070119/9eb56a12/attachment.html From averkhov at thoughtworks.com Fri Jan 19 20:57:14 2007 From: averkhov at thoughtworks.com (Alexey Verkhovsky) Date: Fri, 19 Jan 2007 19:57:14 -0600 Subject: [Lipid-developers] README for 0.1 release Message-ID: Dear all, I just checked in a README which is documentation for 0.1 release. Please have a look and a go at it. One caveat: before you start crossing t's and dotting i's there, remember that this text is NOT supposed to be "professional". Instead, it's supposed to be fun and make you smile. We are talking about a 0.1 release of an open source project, after all. Alex -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/lipid-developers/attachments/20070119/20e13495/attachment.html From RRussell at thoughtworks.com Sun Jan 21 02:13:31 2007 From: RRussell at thoughtworks.com (Rolf Russell) Date: Sun, 21 Jan 2007 01:13:31 -0600 Subject: [Lipid-developers] Fw: RubyForge Project Approved Message-ID: We have the real project. I've added you all as admins. Add yourselves to the developer mailing list. Then we can kill this list. --Rolf ----- Forwarded by Rolf Russell/UK/ThoughtWorks on 01/21/2007 01:11 AM ----- 01/20/2007 09:03 PM To rrussell at thoughtworks.com cc Subject RubyForge Project Approved Your project registration for RubyForge has been approved! Project Full Name: CruiseControl.rb Project Unix Name: cruisecontrolrb Virtual host: cruisecontrolrb.rubyforge.org If after an hour your CVS/Subversion account doesn't work, please open a support ticket ( http://rubyforge.org/tracker/?atid=102&group_id=5&func=browse) so that we can look at the problem. Please note that all shell accounts are restricted to CVS/Subversion/SCP/SFTP. There's a bunch of good information on configuring mailing lists, twiddling your project settings to save bandwidth, setting up commit emails for CVS and Subversion, and much more in the project admin guide here: http://rubyforge.org/docman/?group_id=5 Enjoy, and please tell others about RubyForge. Let us know if there is anything we can do to help you. Welcome aboard! -- The RubyForge admin team (Tom Copeland, Rich Kilmer) -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/lipid-developers/attachments/20070121/45715537/attachment.html 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: [Lipid-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/lipid-developers/attachments/20070121/c77375be/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: [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/lipid-developers/attachments/20070121/8dcad041/attachment-0001.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: [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/lipid-developers/attachments/20070122/8218883e/attachment.html