Skip to content
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

Add step field for BuildSubtaskEvent to represent the different parts of a build for an artifact #5915

Merged
merged 3 commits into from
Jun 1, 2021

Conversation

MarlonGamez
Copy link
Contributor

Related: #5423

Description
Adds a new field to BuildSubtaskEvent to represent which part of the build phase an artifact is in (ex: Build, Cache, Push). Also emits new events to represents cache checks for an artifact.

User facing changes
Users will now see events to represent the cache check phase of skaffold.

@MarlonGamez MarlonGamez requested a review from a team as a code owner May 27, 2021 18:54
@MarlonGamez MarlonGamez requested a review from nkubala May 27, 2021 18:54
@google-cla google-cla bot added the cla: yes label May 27, 2021
@MarlonGamez MarlonGamez changed the title Build step Add step field for BuildSubtaskEvent to represent the different parts of a build for an artifact May 27, 2021
@codecov
Copy link

codecov bot commented May 27, 2021

Codecov Report

Merging #5915 (1aa1ae1) into master (621e696) will increase coverage by 0.03%.
The diff coverage is 91.89%.

Impacted file tree graph

@@            Coverage Diff             @@
##           master    #5915      +/-   ##
==========================================
+ Coverage   70.87%   70.90%   +0.03%     
==========================================
  Files         448      449       +1     
  Lines       16942    16974      +32     
==========================================
+ Hits        12007    12035      +28     
- Misses       4037     4040       +3     
- Partials      898      899       +1     
Impacted Files Coverage Δ
pkg/skaffold/build/cache/retrieve.go 65.34% <60.00%> (-0.28%) ⬇️
pkg/skaffold/build/scheduler.go 92.98% <75.00%> (ø)
pkg/skaffold/event/v2/build.go 100.00% <100.00%> (ø)
pkg/skaffold/event/v2/event.go 73.91% <100.00%> (-2.61%) ⬇️
pkg/skaffold/runner/build_deploy.go 73.95% <100.00%> (+0.27%) ⬆️
pkg/skaffold/build/gcb/docker.go 82.60% <0.00%> (-5.28%) ⬇️
pkg/skaffold/docker/parse.go 86.19% <0.00%> (-0.96%) ⬇️
pkg/skaffold/deploy/kpt/kpt.go 75.32% <0.00%> (+1.10%) ⬆️
pkg/skaffold/util/tar.go 56.00% <0.00%> (+5.33%) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 621e696...1aa1ae1. Read the comment docs.

@tejal29 tejal29 requested review from tejal29 and removed request for nkubala June 1, 2021 17:13
@@ -192,8 +192,9 @@ message BuildSubtaskEvent {
string id = 1; // id of the subtask which will be used in SkaffoldLog
string task_id = 2; // id of the task of skaffold that this event came from
string artifact = 3; // artifact name
string status = 4; // artifact build status oneof: InProgress, Completed, Failed
ActionableErr actionableErr = 5; // actionable error message
string step = 4; // which step of the build for the artifact oneof: Cache, Build, Push
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just a note: Since v2 is alpha, it is ok to change the position of the field. Usually, proto should always be backward compatible and should not change the field number.

@tejal29 tejal29 merged commit 435cd71 into GoogleContainerTools:master Jun 1, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants