在Codeship上用速度测试流星 [英] Testing Meteor with Velocity at Codeship

问题描述

我正在尝试在Codeship上配置CI基础结构.我的本地meteor --test命令的工作原理类似于魅力，但是在Codeship上出现了一个奇怪的错误.

I'm trying to configure a CI infrastructure at Codeship. My local meteor --test command works like charm, but I'm getting a weird error at Codeship.

本地:

I20141208-12:29:42.602(2)? Started
I20141208-12:29:42.602(2)? .
I20141208-12:29:42.603(2)? 
I20141208-12:29:42.603(2)? 1 spec, 0 failures
I20141208-12:29:42.603(2)? Finished in 0.014 seconds
PASSED jasmine-server-unit : Job => Job should be created with title, description, location and isRemote

代码:

=> Started proxy.
=> Started MongoDB.
=> Errors prevented startup:

While Building the application:
node_modules/velocity-cli/velocity-cli.js:1:15: Unexpected token ILLEGAL

=> Your application has errors. Waiting for file change.

设置命令:

curl -o meteor_install_script.sh https://install.meteor.com/
chmod +x meteor_install_script.sh
sed -i "s/type sudo >\/dev\/null 2>&1/\ false /g" meteor_install_script.sh
./meteor_install_script.sh 

测试命令:

meteor --test

推荐答案

velocity-cli 需要全局安装.在调用流星可执行文件之前，可以在设置步骤中添加以下命令吗?

velocity-cli needs to be install globally. Could you add the following command to your setup steps before you call the meteor executable?

npm install -g velocity-cli

免责声明:我正在为Codeship工作

这篇关于在Codeship上用速度测试流星的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！