conditional-travis-deploy
Advanced tools
Generic conditions for TravisCI deployment
Intended to be used within Travis's before_deploy block. Tries to determine
which build/deployment type to perform based on the following conventions:
develop: deploy to developmentmaster: deploy to stagingproductionThrow on all other triggers.
npm install --save conditional-travis-deploy
var conditionalTravisDeploy = require('conditional-travis-deploy')
console.log(conditionalTravisDeploy)
//=> production
conditional-travis-deploy
#=> Error: TravisCI not found in process.env
echo $?
#=> 1
TRAVIS=true TRAVIS_BRANCH=master conditional-travis-deploy
#=> staging
© 2016 Tom Vincent git@tlvince.com (https://tlvince.com)
Released under the MIT license.
FAQs
Generic conditions for TravisCI deployment
The npm package conditional-travis-deploy receives a total of 1 weekly downloads. As such, conditional-travis-deploy popularity was classified as not popular.
We found that conditional-travis-deploy demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Research
Socket researchers have discovered malicious npm packages targeting crypto developers, stealing credentials and wallet data using spyware delivered through typosquats of popular cryptographic libraries.
Security News
Socket's package search now displays weekly downloads for npm packages, helping developers quickly assess popularity and make more informed decisions.
Security News
A Stanford study reveals 9.5% of engineers contribute almost nothing, costing tech $90B annually, with remote work fueling the rise of "ghost engineers."