mirrors
/
git-validation
mirror of https://github.com/vbatts/git-validation.git
1
0
Fork 0
Code Releases Activity
git-validation/.travis.yml

29 lines
572 B
YAML
Raw Normal View History

travis: adding checks for basic regressions * go vet * golint * whether the tool builds * tests (there are none yet) Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2016-04-05 17:16:40 +00:00
language: go
go:
travis: bump the golang versions Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2017-01-27 14:30:21 +00:00
- tip
- 1.7
travis: adding checks for basic regressions * go vet * golint * whether the tool builds * tests (there are none yet) Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2016-04-05 17:16:40 +00:00
- 1.6
sudo: false
before_install:
- go get -u github.com/golang/lint/golint
- mkdir -p $GOPATH/src/github.com/vbatts && ln -sf $(pwd) $GOPATH/src/github.com/vbatts/git-validation && go get ./...
main: default travis commit range is unreliable https://github.com/opencontainers/runc/pull/1378#issuecomment-287920287 points to an alternate approach. Reported-by: Mrunal Patel <mrunalp@gmail.com> Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2017-03-21 13:41:59 +00:00
before_script:
main: Return to using TRAVIS_COMMIT_RANGE (with ... -> .. fix) Master builds only have a 'git clone ...' [1] so FETCH_HEAD isn't defined and git-validation crashes [2]. This commit partially reverts 8a12a8fc (main: default travis commit range is unreliable, 2017-03-21, #13) to avoid that crash. If TRAVIS_COMMIT_RANGE is unset [3], falling back to TRAVIS_COMMIT may be fine. The ... -> .. replacement works around travis-ci/travis-ci#4596 until that is fixed upstream [4]. This avoids pulling in commits from the base tip that aren't reachable from the head tip (e.g. if master has advanced since the PR branched off, and the PR is against master). We only want to check commits that are in the head branch but not in the base branch (more details on the range syntax in [5]). Once the Travis bug does get fixed, the shell replacement will be a no-op. So we don't have to worry about checks breaking once the bug gets fixed, and can periodically poll the bug and remove the workaround at out leisure after the fix. [1]: https://travis-ci.org/opencontainers/runc/jobs/213508696#L243 [2]: https://travis-ci.org/opencontainers/runc/jobs/213508696#L347 [3]: https://github.com/opencontainers/runc/pull/1378#issuecomment-287903471 [4]: https://github.com/travis-ci/travis-ci/issues/4596 [5]: http://git-scm.com/docs/gitrevisions#_specifying_ranges Signed-off-by: W. Trevor King <wking@tremily.us>
2017-03-21 18:56:45 +00:00
- echo $TRAVIS_COMMIT_RANGE
main: default travis commit range is unreliable https://github.com/opencontainers/runc/pull/1378#issuecomment-287920287 points to an alternate approach. Reported-by: Mrunal Patel <mrunalp@gmail.com> Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2017-03-21 13:41:59 +00:00
- echo $TRAVIS_COMMIT
- echo $TRAVIS_BRANCH
- echo $TRAVIS_TAG
- echo $TRAVIS_BUILD_NUMBER
- echo $TRAVIS_REPO_SLUG
travis: adding checks for basic regressions * go vet * golint * whether the tool builds * tests (there are none yet) Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
2016-04-05 17:16:40 +00:00
install: true
script:
- go vet -x ./...
- golint ./...
- go build .
.travis.yml: Dogfood git-validation This makes it easier to test the script and avoids leaking dangling whitespace, etc. into the repo. Signed-off-by: W. Trevor King <wking@tremily.us>
2017-03-21 19:27:53 +00:00
- go test -v ./...
- ./git-validation -run DCO,short-subject,dangling-whitespace -v