Skip to content

Bug 910066 - [email/testing] Have GELAM Travis test-runs post results to ArbPL instance or other accessible server location. a=test-only #281

Merged
merged 1 commit into from Jan 15, 2014

2 participants

@asutherland
Mozilla-B2G member

No description provided.

@asutherland asutherland Bug 910066 - [email/testing] Have GELAM Travis test-runs post results…
… to ArbPL instance or other accessible server location. a=test-only
ced34b7
@asutherland asutherland merged commit eef23bf into mozilla-b2g:master Jan 15, 2014

1 check failed

Details default The Travis CI build failed
@asutherland asutherland deleted the asutherland:post-failures-to-s3 branch Jan 15, 2014
@lightsofapollo lightsofapollo commented on the diff Jan 15, 2014
.travis.yml
script: bash ./tools/ci/unit/travis.sh
+after_failure:
+- travis-artifacts upload --path test-logs --target-path artifacts/$TRAVIS_BUILD_NUMBER/$TRAVIS_JOB_NUMBER

? does this work you don't need to put the travis stuff in the path (though I suppose it should work just fine if you do)

@asutherland
Mozilla-B2G member
asutherland added a note Jan 15, 2014

I'm not sure I'm parsing your comment correctly; I'm reading it as you asking if this works because you're worried that travis-artifacts shouldn't be on the path.

It seemed to run travis-artifacts in https://travis-ci.org/mozilla-b2g/gaia-email-libs-and-more/builds/16962616# (which unfortunately was not a main-branch commit, so the secret keys didn't decrypt)

Note that we do "gem install travis-artifacts" above, which is probably why it's on the path. I just slavishly followed the blog page on what to do.

Also note that I haven't seen things actually properly work yet, because now is the one time builds aren't failing!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.