Hi Lars, On Sun, 24 Apr 2016, Lars Schneider wrote: > [...] the current Git Travis CI OSX build always installs the latest > versions of Git LFS and Perforce via brew [1] and the Linux build > installs fixed versions [2]. Consequently new LFS/Perforce versions can > brake the OS X build even if there is no change in Git. > > You could argue that this is bad CI practice because CI results should > be reproducible. However, it has value to test the latest versions to > detect integration errors as the one with Git LFS 1.2. We could add > additional build jobs to test fixed versions and latest versions but > this would just burn a lot of CPU cycles... that was the reason why I > chose the way it is implemented right now. I will add a comment to the > OSX build to make the current strategy more clear (Linux fixed versions, > OS X latest versions). > > What do you think about that? Do you agree/disagree? Do you see a better > way? I agree with your reasoning. Ciao, Dscho -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html