We’ve been experiencing the same issue for the last 8 days or so - pure speculation, but I’m wondering if this bug fix created the issue for the rest of us: Job triggered by tag but TRAVIS_BRANCH is different to TRAVIS_TAG
The behavior we’re seeing is that we no longer receive a TRAVIS_TAG and the TRAVIS_BRANCH is set to master instead of how it previously was set to the release tag.
@MarkvM - do you have a link to where Travis mentioned they are working on a support ticket for this?