From 93e298a3ce47455496427b8181d1cdeb4f08dd8d Mon Sep 17 00:00:00 2001 From: achingbrain Date: Mon, 3 Feb 2020 16:20:32 +0000 Subject: [PATCH] chore: allow externals to fail We need to publish an rc for people to use to refactor their code to use the new API. The `aegir` release commands require the `last-successful` build to have run in order to update the last known good build branch. That build will not run until the external builds pass but we can't make them pass until they can be refactored to use the new API for which we need an rc. The change to the `.travis.yml` in this PR allows the overall build to pass even though the external module builds are faiilng. --- .travis.yml | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/.travis.yml b/.travis.yml index e816ea620b..3d276dc786 100644 --- a/.travis.yml +++ b/.travis.yml @@ -40,6 +40,15 @@ after_success: - npx nyc report --reporter=text-lcov > coverage.lcov && npx codecov jobs: + allow_failures: + - name: external - ipfs-companion + - name: external - npm-on-ipfs + - name: external - ipfs-pubsub-room + - name: external - peer-base + - name: external - service-worker-gateway + - name: external - orbit-db + - name: external - ipfs-log + - name: external - sidetree include: - stage: check script: