Open natanlao opened 6 years ago
Travis log message:
Skipping a deployment with the lambda provider because this branch is not permitted: 0.0.0
Given that Travis deployed only to staging and not to dev, I think deploy to dev
was skipped because the on.tags
key was not specified for dev
. This is consistent with the Travis documentation:
When tags is not set, or set to any other value, $TRAVIS_TAG is ignored, and the branch condition is considered, if it is set.
There are a number of ways to fix this - one may be to change
branch: master
to
branch:
- master
- /^\d+\.\d+(\.\d+)?(-\S*)?$/
https://travis-ci.org/DataBiosphere/dos-azul-lambda/jobs/422793179
Travis says it won't deploy, but it did (only staging, though). Investigate
┆Issue is synchronized with this JIRA Story ┆Project Name: dos-azul-lambda ┆Issue Number: DAL-64 ┆Epic: DAL One point ohh