-
-
Notifications
You must be signed in to change notification settings - Fork 321
Adds all lib dependencies in vendor/ #181
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
Conversation
UPDATE: remove comments based on golint as PR was updated. |
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.
Wow, this is awesome, huge thanks!
It is one of the things that are critical to the reliability of the project, making sure our builds are consistent.
I don't have time to try it out but I trust you on this.
I'll wait a bit before merging it, there isn't much to review - I wanted to ensure everything ran smoothly in a fresh environment but I didn't get the chance to test it tonight. I have reviewed other issues instead, I'll try it out later before merging |
I was wondering if the eawsy project was packaging the vendor as part of the archive. I inspected the archive but didn't learn much; according to this issue it should - however I'd like to be certain. Then I'll give it go on a small environment. |
Well considering that it builds the binary based on the sources, I believe we can merge it. |
In order to reproduce build safely and all rely on the same library versions, it is best to keep the go dependencies versioned within the project.
In order to avoid testing the govendor code (fmt,vet & lint), the rules had to be revised.
Issue Type
Summary
In order to reproduce build safely and all rely on the same library versions, it is best to keep the go dependencies versioned within the project. The Makefile has been adapted to avoid running fm/vet & lint against the vendor files.
The code was tested from scratch using a golang container.
Closes: https://github.com/cristim/autospotting/issues/154
Code contribution checklist
to it.
guidelines.
make full-test
.contribution actually resolves it.