larsxschnei...@gmail.com writes:
> --- /dev/null
> +++ b/.travis.yml
> @@ -0,0 +1,46 @@
> +language: c
> +
> +os:
> + - linux
> + - osx
> +
> +compiler:
> + - clang
> + - gcc
> +
> +before_install:
> + - >
> + export GIT_TEST_OPTS=" --quiet";
> + case "${TRAVIS_OS_NAME:-linux}" in
> + linux)
> + wget -q https://package.perforce.com/perforce.pubkey -O - \
> + | sudo apt-key add -
> + echo 'deb http://package.perforce.com/apt/ubuntu precise release' \
> + | sudo tee -a /etc/apt/sources.list
> + wget -q https://packagecloud.io/gpg.key -O - | sudo apt-key add -
> + echo 'deb https://packagecloud.io/github/git-lfs/debian/ jessie main' \
> + | sudo tee -a /etc/apt/sources.list
> + sudo apt-get update -qq
> + sudo apt-get install -y apt-transport-https
> + sudo apt-get install perforce-server git-lfs
Sorry if this has been discussed already, but do you really need these
"sudo" calls?
They trigger builds on the legacy Travis CI infrastructure:
http://docs.travis-ci.com/user/migrating-from-legacy/?utm_source=legacy-notice&utm_medium=banner&utm_campaign=legacy-upgrade
No big deal, but getting rid of sudo would be cool, and documenting why
it can't easily be done in commit message and/or comments would be nice
otherwise.
Thanks for working on that!
--
Matthieu Moy
http://www-verimag.imag.fr/~moy/
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
