[Webkit-unassigned] [Bug 62372] [CSSRegions] Add build slave

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=62372





--- Comment #7 from Mihnea Ovidenie <mihnea at adobe.com>  2011-06-22 04:45:12 PST ---
(In reply to comment #5)
> (From update of attachment 96585 [details])
> View in context: https://bugs.webkit.org/attachment.cgi?id=96585&action=review
> 
> > Tools/BuildSlaveSupport/build.webkit.org-config/config.json:242
> > +                    { "name": "Adobe SnowLeopard Intel Release (Build)", "type": "Build", "builddir": "adobe-snowleopard-intel-release",
> 
> We don't currently have any builders with company names in them. The important thing is the flavor of WebKit that runs on the builder and what kinds of operations it performs, not who maintains the slaves used by that builder. (In fact, you could have multiple different companies that maintain slaves that are used by a single builder.) I'd recommend giving this builder a name that that indicates its purpose.

Hi Adam,

Thanks for your suggestions. We are thinking to use the following steps for this machine for the near future:
Step1: configure it like a SnowLeopard slave build bot to do Mac WebKit Builds
Step2: configure it like a SnowLeopard slave build bot to do Mac WebKit Builds with css-regions/css-exclusions enabled(they are disabled by default)
Step3: configure it like a SnowLeopard slave build bot to do Mac WebKit Builds and Tests with css-regions/css-exclusions enabled. This bot would also run css-regions/css-exclusions specific tests, that are skipped in WebKit main trunk.

Does this sound ok to you?

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.