[Mono-bugs] [Bug 507917] New: parent lanes

[bugzilla_noreply at novell.com]

http://bugzilla.novell.com/show_bug.cgi?id=507917


           Summary: parent lanes
    Classification: Mono
           Product: Mono: Tools
           Version: unspecified
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Enhancement
          Priority: P5 - None
         Component: MonkeyWrench
        AssignedTo: rkvinge at novell.com
        ReportedBy: ajorgensen at novell.com
         QAContact: mono-bugs at lists.ximian.com
          Found By: ---


> As I work more with MonkeyWrench (and add more lanes) I'm starting to
> think that scripts and commands should be a per-host configuration for a
> lane.  Rather than have a lane that's mono-trunk-dist and another that's
> mono-trunk-rpm I'd like to have just mono-trunk and on dist it will do
> svn-update and make-dist but on opensuse-i586 it will do osc-build.
>
> I realize that's a bit of an overhaul but I think it would serve us a
> lot better.  It will also mean that one lane-host will need to be able
> to depend on another lane-host.  I think it will make it much easier to
> visualize the relationships between different builds.

I'm not quite sure about this, mostly because you can sort of do it already by
only using one host per lane.

Though I see your problem, and I think I have a better solution: adding the
idea of a "parent lane", so that for instance you have mono-trunk-dist and
mono-trunk-rpm lanes, and then a "parent lane" called mono-trunk for both of
them. This would be presented in the ui as a tree structure:

mono-trunk
  mono-trunk-dist
  mono-trunk-rpm

this tree structure could be arbitrarily deep, and it's easy to implement (one
more field in the db, and the rest is purely ui changes).

-- 
Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.