Bug 242126 - build should allow multiple regex rules based on branch and build type
Summary: build should allow multiple regex rules based on branch and build type
Status: NEW
Alias: None
Product: Modeling
Classification: Modeling
Component: Releng (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Nick Boldt CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 239307
  Show dependency tree
 
Reported: 2008-07-25 17:36 EDT by Nick Boldt CLA
Modified: 2008-07-25 17:36 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Nick Boldt CLA 2008-07-25 17:36:40 EDT
This would allow, for example, different rules for M and I builds (use platform M for M builds, use platform I for I builds). (The current workaround here is to manually use the web UI to deselect I builds and select M builds... which won't scale very well.) 

In terms of scheduled builds with start_cron.sh, providing a -regex flag for M builds and no -regex for all others means that the value set in /build/_common.php will be used for I/S/R builds, and the override for M. This too works but can be cumbersome to set up for many builds.

This would also allow GMF to do N builds using Stable deps (latest milestone) and I/M builds using latest I/M deps. Same UI & crontab workarounds as above.

Data could simply be a 3D array, with assumed defaults:

$regex["HEAD"]["N"] = ...
$regex["HEAD"]["I"] = ...
$regex["R2_1_maintenance"]["M"] = ...

Web UI could change dynamically as branch and type are changed, and new rules are swapped in / view is refiltered.