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

model: better support for no-build no-push custom_builds #3747

Merged
merged 1 commit into from Sep 3, 2020

Conversation

nicks
Copy link
Member

@nicks nicks commented Sep 2, 2020

Hello @maiamcc,

Please review the following commits I made in branch nicks/no-push:

881e7b7 (2020-09-02 17:50:04 -0400)
model: better support for no-build no-push custom_builds

Code review reminders, by giving a LGTM you attest that:

  • Commits are adequately tested
  • Code is easy to understand and conforms to style guides
  • Incomplete code is marked with TODOs
  • Code is suitably instrumented with logging and metrics

@nicks nicks requested a review from maiamcc September 2, 2020 21:53
@nicks
Copy link
Member Author

nicks commented Sep 2, 2020

this is in response to the discussion here
tilt-dev/tilt-extensions#78
and here
tilt-dev/tilt-extensions#77

i understand this change is pretty weird. But I think it might be the kind of weird that cancels out existing weird, so that we're net less weird.

@nicks nicks force-pushed the nicks/no-push branch 5 times, most recently from 65a2ede to 38ce9a0 Compare September 2, 2020 22:15
Copy link
Contributor

@maiamcc maiamcc left a comment

Choose a reason for hiding this comment

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

I am deeply afraid, but as far as being deeply afraid, this lgtm

@@ -4029,6 +4029,24 @@ k8s_yaml('foo.yaml')
f.assertNextManifest("foo").ImageTargets[0].OverrideArgs)
}

// See comments on ImageTarget#MaybeIgnoreRegistry()
func TestCustomBuildNoBuildNoPush(t *testing.T) {
Copy link
Contributor

Choose a reason for hiding this comment

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

not apparent what you're testing here b/c "no build no push" is a kinda wibbly translation of "skips local docker and doesn't use expected ref", and also since it's not immediately obvious what the behavior SHOULD be, I'd love it in the test name. How about:
TestCustomBuildSkipsLocalDockerAndTagPassedIgnoresLocalRegistry or something? Wordier but much easier to tell what's going on.

Copy link
Member Author

Choose a reason for hiding this comment

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

done!

someday we'll come up with a custom_build v2!!!

@nicks nicks merged commit b91ba1c into master Sep 3, 2020
@nicks nicks deleted the nicks/no-push branch September 3, 2020 21:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants