Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

travis: git-validation detects travis now #366

Merged
merged 1 commit into from
Apr 13, 2016

Conversation

vbatts
Copy link
Member

@vbatts vbatts commented Apr 5, 2016

Signed-off-by: Vincent Batts vbatts@hashbangbash.com

@vbatts
Copy link
Member Author

vbatts commented Apr 5, 2016

hmm. something strange happened in those failures...

@vbatts
Copy link
Member Author

vbatts commented Apr 5, 2016

ah. found it. vbatts/git-validation#6

@vbatts
Copy link
Member Author

vbatts commented Apr 5, 2016

cool. PTAL.

@jonboulle
Copy link
Contributor

but now why isn't this being tested?!?

@vbatts
Copy link
Member Author

vbatts commented Apr 5, 2016

woah. it had been. though github was seeming to choke up a bit ago.

@vbatts
Copy link
Member Author

vbatts commented Apr 5, 2016

https://travis-ci.org/opencontainers/runtime-spec/builds/120966194 ?
I think something is funky since the "specs" -> "runtime-spec" project renamed.

@vbatts
Copy link
Member Author

vbatts commented Apr 5, 2016

@caniszczyk any thoughts? ^^

@caniszczyk
Copy link
Contributor

I just kicked it again, looks good?

https://travis-ci.org/opencontainers/runtime-spec/builds/120966194

@vbatts
Copy link
Member Author

vbatts commented Apr 5, 2016

@caniszczyk the build is fine, but not sure why travis status is no longer showing on PRs. I'm wondering if the project rename did not sync with travis?

@caniszczyk
Copy link
Contributor

@vbatts ah you're right, wth! up for creating another PR to see if the issue fixed itself with a new PR?

I completely refreshed the Travis CI settings for the repos so not sure what's up yet.

@vbatts
Copy link
Member Author

vbatts commented Apr 5, 2016

looks to be back. Thanks @caniszczyk

@vbatts
Copy link
Member Author

vbatts commented Apr 12, 2016

PTAL


install: true

script:
- go vet -x ./...
- make .golint
- $HOME/gopath/bin/git-validation -run DCO,short-subject -v -range ${TRAVIS_COMMIT_RANGE}
- git-validation -run DCO,short-subject -v
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe want dangling-whitespace too (from vbatts/git-validation#7), although that somewhat of a drive-by with this PR. Still, it would be nice to avoid things like #380.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@vbatts
Copy link
Member Author

vbatts commented Apr 12, 2016

this PR should fix travis failures like this https://travis-ci.org/opencontainers/runtime-spec/jobs/122597352
when pushing a new tag

@hqhq
Copy link
Contributor

hqhq commented Apr 13, 2016

LGTM

@mrunalp
Copy link
Contributor

mrunalp commented Apr 13, 2016

Needs rebase.

The `-range` argument is not needed.

Signed-off-by: Vincent Batts <vbatts@hashbangbash.com>
@mrunalp
Copy link
Contributor

mrunalp commented Apr 13, 2016

LGTM

@mrunalp mrunalp merged commit fd9d436 into opencontainers:master Apr 13, 2016
@vbatts vbatts deleted the travis_updates branch May 2, 2016 20:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants