-
Notifications
You must be signed in to change notification settings - Fork 513
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
Build inconsistency when pushing go to Heroku #89
Comments
@brandur Looking at this now. Thanks for the detailed bug report. |
@brandur I don't think this is actually related to the go buildpack. Looking into it more with others. |
This turns out to be heroku pruning a dir rooted in your repo named |
@freeformz Hah, sweet. Thanks for taking a look into this one. Closing it out. |
@brandur the fix for this is now deployed,. |
@freeformz You rock. Thanks! |
@brandur Thanks, but all credit goes to @ojacobson for fixing and deploying the affected system. |
Hey @freeformz, I might need some expert help with one :) I have a project that I've managed to push to Heroku many times successfully in the past, but after a minor refactor, will no longer build.
It seems that the package that I refactored can't be located:
It builds fine on Travis though, and also locally:
It seems that the package is in the expected directory:
And that the files within the package correctly define their package:
Git is clean:
The project is located at heroku/midgard if you want to take a look. Any ideas? Possibly a caching issue?
The text was updated successfully, but these errors were encountered: