3

On Velocity's GH page it mentions "easy CI integration" as one of the benefits, but I haven't seen any documentation about it.

How can I integrate Velocity with Jenkins?

Tomas Romero
  • 8,418
  • 11
  • 50
  • 72

2 Answers2

4

You should use:

meteor --test

meteor run --test

This does the same thing as the velocity-ci without the extra installation

Community
  • 1
  • 1
Xolv.io
  • 2,483
  • 1
  • 15
  • 17
  • Did you mean `meteor run --test`? This did the same as velocity-ci does, except that it doesn't exit with the status code, which is fundamental for ci. The process just stays up and running after running the tests. `meteor --test` just booted my app normally. – Tomas Romero Oct 31 '14 at 14:58
  • oh, that' a bug! I'll post it up – Xolv.io Oct 31 '14 at 15:33
  • Great, thanks! I think the best would be to have 2 modes: `meteor run --test` and `meteor run --test-single-run` (in lack of a better name) – Tomas Romero Oct 31 '14 at 15:39
  • On 0.9.4 the process stays up and running, but on 1.0 it ends with the correct status code. – Tomas Romero Nov 21 '14 at 03:09
  • Do you mean you add `meteor run --test` as a Build Step in Jenkins, under `Execute Shell`? – Philip O'Brien Jul 27 '15 at 10:56
1

You could try the velocity-ci

velocity-cli

NPM module for running your velocity test suites from the command-line

Installation

npm install -g velocity-ci

Run

From inside your project directory type velocity

How it works

The velocity-cli spawns a meteor process and connects to it using DDP. PhantomJS connects to the meteor process to trigger client side tests. Test results received via DDP are printed at the console. This process exits with the appropriate exit status code.

So the build step would be velocity inside the meteor directory

Marco de Jongh
  • 5,270
  • 3
  • 17
  • 29