-
Notifications
You must be signed in to change notification settings - Fork 72
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
make build fails #34
Comments
hi , will try to incorporate the comments, this might take some time. right now we have no preferred CI tool, will have to go through both and investigate |
@NickLarsenNZ like you were saying in previous issue , if you could raise a PR that would help us as well |
Can you once check on the issue ? As of now we see build is successful. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When I run the steps as outlined in the README, the build fails on a vendored dependency:
I notice that
pwd
is a symlink to a non existant file in the directory above:To get around it, I do the following:
Finally:
I think by tagging and producing release artifacts using CI/CD as discussed in #33, users will not be tripped up by this. I also think by moving away from vendoring (to go modules), the problem will disappear, the repo will be smaller, and the dependency download process will be much faster.
The text was updated successfully, but these errors were encountered: