I have a simple config for CI deployment and yet it fails to deploy every time. Here is my config:
language: node_js
node_js:
- "8"
- "iojs"
before_install:
- npm install -g firebase-tools
after_success:
- firebase deploy -m "build $TRAVIS_BUILD_NUMBER $TRAVIS_BRANCH/$COMMIT_HASH" --non-interactive --token $FIREBASE_TOKEN
and my build output is as follow:
Setting environment variables from repository settings
$ export FIREBASE_TOKEN=[secure]
nvm.install
2.65s$ nvm install 8
Downloading and installing node v8.14.0...
Downloading https://nodejs.org/dist/v8.14.0/node-v8.14.0-linux-x64.tar.xz...
Computing checksum with sha256sum
Checksums matched!
Now using node v8.14.0 (npm v6.4.1)
$ node --version
v8.14.0
$ npm --version
6.4.1
$ nvm --version
0.33.11
before_install
17.17s$ npm install -g firebase-tools
/home/travis/.nvm/versions/node/v8.14.0/bin/firebase -> /home/travis/.nvm/versions/node/v8.14.0/lib/node_modules/firebase-tools/lib/bin/firebase.js
> @google-cloud/functions-emulator@1.0.0-beta.5 postinstall /home/travis/.nvm/versions/node/v8.14.0/lib/node_modules/firebase-tools/node_modules/@google-cloud/functions-emulator
> node scripts/upgrade-warning
If you're using the Emulator via the Firebase CLI, you can
disregard this message.
If you're upgrading @google-cloud/functions-emulator, these
are the recommended upgrade steps:
1. Stop the currently running emulator, if any:
functions stop
2. Uninstall the current emulator, if any:
npm uninstall -g @google-cloud/functions-emulator
3. Install the new version of the emulator:
npm install -g @google-cloud/functions-emulator
If you have trouble after upgrading, try deleting the config
directory found in:
~/.config/configstore/@google-cloud/functions-emulator
Then restart the emulator. You can also check for any renegade
Node.js emulator processes that may need to be killed:
ps aux | grep node
+ firebase-tools@6.1.2
added 537 packages from 268 contributors in 16.748s
0.01s$ make test
make: *** No rule to make target `test'. Stop.
The command "make test" exited with 2.
Done. Your build exited with 1.
I am not sure why make test command fails and why is it included and running which is not part of my deployment script
So I have tried to follow the steps as mentioned in travis ci for firebase
deploy:
provider: firebase
token:
secure: $FIREBASE_TOKEN
message: "build $TRAVIS_BUILD_NUMBER $TRAVIS_BRANCH/$COMMIT_HASH"
and even that gave me errors:
Setting environment variables from repository settings
$ export FIREBASE_TOKEN=[secure]
rvm
4.08s$ rvm use default
Using /home/travis/.rvm/gems/ruby-2.4.1
** Updating RubyGems to the latest version for security reasons. **
** If you need an older version, you can downgrade with 'gem update --system OLD_VERSION'. **
ruby.versions
$ ruby --version
ruby 2.4.1p111 (2017-03-22 revision 58053) [x86_64-linux]
$ rvm --version
rvm 1.29.3 (latest) by Michal Papis, Piotr Kuczynski, Wayne E. Seguin [https://rvm.io]
$ bundle --version
Bundler version 1.16.6
$ gem --version
2.7.8
No Gemfile found, skipping bundle install
0.16s$ rake
rake aborted!
No Rakefile found (looking for: rakefile, Rakefile, rakefile.rb, Rakefile.rb)
/home/travis/.rvm/gems/ruby-2.4.1@global/gems/rake-12.3.0/exe/rake:27:in `<top (required)>'
(See full trace by running task with --trace)
The command "rake" exited with 1.
Done. Your build exited with 1.