- 
                Notifications
    You must be signed in to change notification settings 
- Fork 370
Open
Labels
A-ciArea: Continuous IntegrationArea: Continuous IntegrationC-choreCategory: choreCategory: choreE-easyExperience: easy, good for newcomersExperience: easy, good for newcomersFinalize WeldP-medium
Milestone
Description
On EEST we have the concept of features for we generate specialized test releases.
These specialized test releases have the following properties:
- They define a specific subset of tests to fill (via special fillparameters).
- Marked as pre-releases rather than full releases.
- They are generated from tags that have the following naming scheme: [email protected].
When moving to EELS, this can be translated to a similar architecture:
- We retain the same tagging structure, and we tag an EELS branch with it.
- It does not generate a release on https://github.com/ethereum/execution-specs/releases, rather it creates a release only on https://github.com/ethereum/execution-spec-tests/releases with the feature-specific subset of tests.
- The definition of the tests subset is now on EELS (potentially .github/configs).
- We should be able to reuse most of the current EEST's CI workflow code.
cc @spencer-tb
spencer-tb and Carsons-Eels
Metadata
Metadata
Assignees
Labels
A-ciArea: Continuous IntegrationArea: Continuous IntegrationC-choreCategory: choreCategory: choreE-easyExperience: easy, good for newcomersExperience: easy, good for newcomersFinalize WeldP-medium