-
Notifications
You must be signed in to change notification settings - Fork 239
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
[0.9.0] Set build context default to Dockerfile dir #1184
Conversation
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.
Looks good @anukul, just one minor thing to resolve 👍
cli/cmd/create.go
Outdated
@@ -223,6 +227,10 @@ func handleSubdomainCreate(subdomain string, err error) error { | |||
} | |||
|
|||
func createFromGithub(createAgent *deploy.CreateAgent, overrideValues map[string]interface{}) error { | |||
if localPath == "" { |
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.
Is createFull
the only method that calls createFromGithub
? If so, we can remove this right?
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.
That's right.. fixed, thanks.
Hi @anukul - seems like everything is working well! One slight problem is that (as mentioned in issue #1186) the auto buildpack doesn't work for folders for some reason. I get this error specifically:
After some investigation, it seems like this happens due to Docker - I suspect something with symlinks is done to build and the way we pull/store the repository breaks things (note: I tested with absolute paths and that has the same issue). The exact line of code that fails is this one (this is in library code): if resolvedAppPath, err = filepath.EvalSymlinks(appPath); err != nil {
return "", errors.Wrap(err, "evaluate symlink")
} |
Pull request type
Please check the type of change your PR introduces:
Pull request checklist
Please check if your PR fulfills the following requirements:
go test ./...
runs successfully from the root folder.What is the current behavior?
Docker build context default is set to repository root
What is the new behavior?
Docker build context default is set to directory containing Dockerfile
Technical Spec/Implementation Notes
TODO: Allow setting build context from dashboard