-
Notifications
You must be signed in to change notification settings - Fork 198
[CI] Methodology to test MeshKit builds #434
Copy link
Copy link
Open
Labels
area/ciContinuous integration | Build and releaseContinuous integration | Build and releasehelp wantedExtra attention is neededExtra attention is neededissue/willfixThis issue will be worked onThis issue will be worked onkind/enhancementImprovement in current featureImprovement in current featurelanguage/goGolang relatedGolang related
Metadata
Metadata
Assignees
Labels
area/ciContinuous integration | Build and releaseContinuous integration | Build and releasehelp wantedExtra attention is neededExtra attention is neededissue/willfixThis issue will be worked onThis issue will be worked onkind/enhancementImprovement in current featureImprovement in current featurelanguage/goGolang relatedGolang related
Current Behavior
When Dependabot stops by and suggests an upgraded dependency, we don't know if that dependency upgrade is compatible given a lack of integration test workflows.
Desired Behavior
Improved workflow to validate MeshKit functions.
Integration and functional test workflows can be borrowed from meshery/meshery.
Resources
Alternatives / Additional Context