Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 623196 - RFE: enhance selection criteria for Releases
RFE: enhance selection criteria for Releases
Status: CLOSED WONTFIX
Product: Beaker
Classification: Community
Component: scheduler (Show other bugs)
0.5
All Linux
low Severity medium (vote)
: future_maint
: ---
Assigned To: Bill Peck
:
Depends On: 600353
Blocks:
  Show dependency treegraph
 
Reported: 2010-08-11 11:05 EDT by Karel Volný
Modified: 2012-09-27 21:37 EDT (History)
8 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2012-09-27 21:37:25 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Karel Volný 2010-08-11 11:05:23 EDT
Description of problem:
I refer to bug #600353 comment #12 -

"When I have different syntax of config file, package names or even
command itself changed after long period of time I want only exclude eg.
the latest release. When the test runs perfectly on RHEL3-5 I want to
exclude only the RHEL6"

I guess this would be better resolved by allowing to specify a range of releases - otherwise, in the abovementioned case, the test would have to be modified in the future to exclude RHEL-7, then RHEL-8 etc.

from the mailing list:

> I'd also like to see a possibility to specify ranges, like "run on
> everything from RHEL-3 to RHEL-5", "run on everything until RHEL-5 (not on
> RHEL-6 and above)", "run on everything from RHEL-5.5 (also on RHEL-6 and 
> above)", "run on every RHEL-4.x from RHEL-4.6 and on everything 
> from RHEL-5.3" etc.
> 
> running a test automatically on RHEL-7 is not desired if we know 
> that the feature got removed in RHEL-6 and it will never (except 
> for "never say never") make it back again
Comment 1 Dan Callaghan 2012-09-27 21:37:25 EDT
Test metadata should be managed outside of Beaker.

Note You need to log in before you can comment on or make changes to this bug.