Marcin,
Thanks for the reply! So do you have Jenkins run go get -u, run tests, and
then commit the changes? Does it automatically only update private repos or
does it update both? Is there any review process each week to validate the
updates?
I'm leaning towards a combination of what you sugge
I have the same kind of setup at my company, and we use go modules in the
same way that we would use public modules. We periodically do a "go get -u"
to update them. Jenkins does that once a week, so at worst, we're a week
behind. If someone needs to manually pull in changes more urgently, they
can
What's the best way to automatically always pull the latest release/commit
for certain repos? We use gerrit internally so all of our import paths for
internal packages start with something like gerrit.corp. We have over 50
different repos and it would be painstaking to have to update (pull lates
