Closed advayDev1 closed 8 years ago
Alright, I think you can take a look @brunobowden
travis is finally working again - all green @brunobowden
My main question is why offer flexibility on which tasks you run? For now, you're only running "build". Hopefully that should remain the case. Please explain why you want to offer more?
@brunobowden ptal. Re flexibility: I'd had a plan to allow 2 travis entries for a single TEST_DIR:
- TEST_DIR=com.google.code.gson-gson TEST_TASKS=assemble
- TEST_DIR=com.google.code.gson-gson TEST_TASKS=check
this would allow you to have unit tests in the allowed failures but have translation/compilation in the required successes. I'll put that in the Gson cl itself though - removed from this PR.
LGTM - please ignore my last comments about the assemble / build ordering. I'd do that on the next PR.
your suggestion is why i had added that code in the first place. unfortunately, it doesn't work as expected because we made a decision long ago that j2objc translation depends on Java unit-testing.
we may want to reconsider that.
Does Travis have a feature where you can mark a certain checkpoint in the build? E.g. "Complete Stages 1&2, Failed at Stage 3"? I searched but couldn't see anything.
No it doesn't. The only distinction is 'install' vs 'build'. You cannot distinguish between steps of 'build' which is what we'd like
Also adds a common script to get test repos from github.
Issue #30