From jeremystellsmith at gmail.com  Sat Dec 15 04:23:48 2007
From: jeremystellsmith at gmail.com (Jeremy Stell-Smith)
Date: Sat, 15 Dec 2007 01:23:48 -0800
Subject: [Cruisecontrolrb-developers] moving custom settings to ~/.cruise
Message-ID: <b18eecea0712150123j5a82217fwdb5eb2a03ab882c4@mail.gmail.com>

So, several of the stories left for this release have to do w/ plugins,
either accepting plugins, or creating a plugin infrastructure.  One problem
w/ our current strategy for plugins and other custom content is that the
more custom content someone has, the harder it is to upgrade.  What I
propose is this.

custom content lives in a directory (by default ~/.cruise) that looks like :

~/.cruise
  - projects
    - ...
  - builder_plugins
    - ...
  - site_config.rb
  - site.css

Any plugins that we want to continue to distribute w/ cruise would still
live in the main ccrb directory.   Maybe something like :

<ccrb>
  - app
    - controllers
    - models
    - views
    - default_builder_plugins
      - ...

To override the directory for custom content, maybe set a CRUISE_DATA
environment variable?

These are some pretty big changes, but I think they make sense.  Opinions
and/or better names for things?

Jeremy
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/cruisecontrolrb-developers/attachments/20071215/d5c4b726/attachment.html 

From thewoolleyman at gmail.com  Sat Dec 15 11:28:00 2007
From: thewoolleyman at gmail.com (Chad Woolley)
Date: Sat, 15 Dec 2007 09:28:00 -0700
Subject: [Cruisecontrolrb-developers] moving custom settings to ~/.cruise
In-Reply-To: <b18eecea0712150123j5a82217fwdb5eb2a03ab882c4@mail.gmail.com>
References: <b18eecea0712150123j5a82217fwdb5eb2a03ab882c4@mail.gmail.com>
Message-ID: <e3af97510712150828y5aa7c74fha2fddefb6fcfde00@mail.gmail.com>

On Dec 15, 2007 2:23 AM, Jeremy Stell-Smith <jeremystellsmith at gmail.com> wrote:
> custom content lives in a directory (by default ~/.cruise) that looks like :
>
> ~/.cruise
>    - projects
>     - ...
>   - builder_plugins
>     - ...
>   - site_config.rb
>   - site.css
>
> To override the directory for custom content, maybe set a CRUISE_DATA
> environment variable?
>
> These are some pretty big changes, but I think they make sense.  Opinions
> and/or better names for things?

+1.

It's a pain and error-prone to copy stuff over when upgrading, and
this would make it easier to have all cruise configs live in svn.

-- Chad

From jeremystellsmith at gmail.com  Sun Dec 30 17:36:02 2007
From: jeremystellsmith at gmail.com (Jeremy Stell-Smith)
Date: Sun, 30 Dec 2007 17:36:02 -0500
Subject: [Cruisecontrolrb-developers] where do plugins live?
Message-ID: <b18eecea0712301436g30708c99y30938f6370170b7@mail.gmail.com>

I'm working with a plugin script, and to my surprise, the growl & jabber
notifiers live in both the ccrb repos & the ccrb-contrib repos.  So, the
question is, where should they live?  Should all plugins (aside from built
in ones like the e-mail notifier) live only in the ccrb-contrib repos?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/cruisecontrolrb-developers/attachments/20071230/19f24205/attachment.html