-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[V3] New V3 SkaffoldRunner #5692
Conversation
1. Refactored the runner directory. 2. Create a New SkaffoldRunner for V3. Both runner.SkaffoldRunner and v3.SkaffoldRunner implements the Runner interface. 2. Build, Test, Prune and other shared methods are moved from SkaffoldRunner to several individual structs (BuildRunner, TestRunner). 3. Both SkaffoldRunner and the V3 SkaffoldRunner have the shared structs as components. 4. Unittests are updated. 5. Add placeholders (not implemented error) in v3 SkaffoldRunner for later implementation.
Codecov Report
@@ Coverage Diff @@
## master #5692 +/- ##
==========================================
- Coverage 70.64% 70.48% -0.17%
==========================================
Files 411 421 +10
Lines 15860 16001 +141
==========================================
+ Hits 11205 11279 +74
- Misses 3827 3889 +62
- Partials 828 833 +5
Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks good to me, I think the thing I'm confused about is the v3 package naming. I understand that it's named off the schema, but is kinda confusing since skaffold's major version number is still 1
yeah, when changing the schema from v1 to v2, I think we actually should bump the skaffold version to v2 at that time. Do you suggest using v2 here or re-align the schema and master version in this new skaffold render? |
…r.Tester and runner.Pruner
Related: #5673
Description