We frequently find that maven-based projects fail on Jenkins, because mvn's download optimizier decides not to check for new libraries. We've taken to manually adding lc mvn -- --update-snapshots compile (or something similar) at the front of the Jenkins job. Very annoying.
a) It would be nice if a) package/test etc commands could know the were running as lc-ci.
b) the maven template were capable of adding the --update-snapshot to the first mvn invocation.
We probably don't want to build in anything that specific to one build tool. But something like an env var called LC_MVN_CI_ARGS or something, that gets passed in, maybe. I don't know.
We frequently find that maven-based projects fail on Jenkins, because mvn's download optimizier decides not to check for new libraries. We've taken to manually adding
lc mvn -- --update-snapshots compile
(or something similar) at the front of the Jenkins job. Very annoying.a) It would be nice if a) package/test etc commands could know the were running as lc-ci. b) the maven template were capable of adding the --update-snapshot to the first mvn invocation.