Add testplans to releng-scripts and ci-management

Description

Add testplans to releng-scripts and ci-management

Environment

None

Activity

Show:

Kevin Hilman 
February 6, 2019 at 7:20 PM

ci and release test plans added to releng-scripts

Kevin Hilman 
November 9, 2018 at 1:21 AM
(edited)

I see you've been adding some templates to qa-testdefinitions/test-suites.

What do you think about having a 'common' dir there for the test defintions that are shared across ci/daily/weekly/release (like smoke-tests-basic, busybox, service-check, etc.)

Then, the ci/daily/weekly/release dirs will only contain test definitions that are unique to them.

And then, we'll keep it simple in releng-scripts.  In templates/tests, we'll just have ci, daily, weekly, release.jinja2 files which will each have a list of definitions pointing tot he various subdirs of qa-testdefintions.

 

Kevin Hilman 
November 8, 2018 at 11:29 PM

For starters, let's rely on releng-scripts templates to decide which test plans to run for each build-type instead of having it hard-coded in the ci-management jobs that call releng-scripts.

https://gerrit.automotivelinux.org/gerrit/#/c/17817/

Fixed

Details

Assignee

Reporter

Labels

Contract ID

Components

Priority

Created October 29, 2018 at 10:58 AM
Updated February 11, 2019 at 11:12 PM
Resolved February 6, 2019 at 7:20 PM

Flag notifications