mirror of
https://gitlab.winehq.org/wine/wine-gecko.git
synced 2024-09-13 09:24:08 -07:00
5a27e03e0c
--HG-- extra : rebase_source : 4d2c484bc780bd20c13b9bca129bd173ac66624a extra : source : 630a93355767c7813dc7b761309f6728a79c2c80
29 lines
706 B
Markdown
29 lines
706 B
Markdown
Problems:
|
|
|
|
Not all tests work on all platforms
|
|
Many tests work on N+1 platforms
|
|
|
|
Goals:
|
|
|
|
Tests and builds should be loosely coupled (you probably need a build
|
|
but you don't always need a build!)
|
|
|
|
Workflows:
|
|
|
|
1. Try: decide upon a set of builds and tests from a matrix of checkboxes
|
|
|
|
2. Branch: decide upon a set of builds based on in tree configuration
|
|
(essentially a "fixed" version of try flags)
|
|
|
|
3. One off builds / One of tests (which require a build we created
|
|
earlier)
|
|
|
|
## Build tasks
|
|
|
|
No special logic needed but convention of generating artifacts should be followed!
|
|
|
|
## Test Tasks
|
|
|
|
Always need a build (and likely also need the tests.zip). Should know
|
|
what potential builds they can run on.
|