Allowed to fail job, if canceled, the whole build is marked as canceled

[native-api]

@popovicsandras

I’m trying to have the Travis CI to work with a monorepo, where we don’t necessarily need to run every job, since not everything were changed. Unfortunately, as far as I know, with Travis I can’t create jobs dynamically

1. The best idea I have for a monorepo is described as “workaround” in How to skip jobs based on the files changed in a subdirectory? - #15 by native-api

   This looks like the most natural way since in monorepos, what needs to be done is decided by intelligent build tools which can do it with much finer granularity than you can achieve by manually splitting your workload into jobs.

2. Alternatively, you can check at job start if it needs to be run and quit it early (with travis_terminate or by making the rest of your logic a no-op if you need further automatic steps like saving the cache to run) if it doesn’t. Currently, you can only do this as early as at before_install: (but still, it’s better than nothing). Run a chunk of user code before the stock installation logic is an FR that would let you do it earlier with minimal wasted time.