Conversation
281775e to
0afa0c5
Compare
|
travis enabled - could you push a new commit to trigger a build? |
.travis.yml
Outdated
| - "6.11.0" | ||
|
|
||
| install: | ||
| - npm install -g https://github.com/INCF/bids-validator.git |
There was a problem hiding this comment.
Let's fix it to particular version with @
|
umm ... are you sure you enabled it? I pushed a commit. Nothing happened |
|
hmm it's enabled https://travis-ci.org/INCF/bids-validator, but they are experiencing some issues https://www.traviscistatus.com/incidents/kfgyk0ygvt65 |
|
try now |
|
Yayy! worked :-) |
|
Ready for merge :-) |
.travis.yml
Outdated
| - npm install -g https://github.com/INCF/bids-validator.git#0.25.7 | ||
|
|
||
| script: | ||
| - for i in $(ls -d */); do bids-validator ${i%%/} --ignoreNiftiHeaders; done |
There was a problem hiding this comment.
I'm not 100% sure, but I'm afraid that exit code of a for loop is the same as the last command in it - this means things failing before last test will be silenced in Travis. See https://stackoverflow.com/questions/14059342/how-to-get-the-exit-status-a-loop-in-bash
|
@chrisfilo comments addressed |
|
don't ask me what I did, but it seems to work as far as I can tell :-) |
|
You're da best! |
closes #5
@chrisfilo could you enable travis so we can see if this works?