In CI, Journey Test failing to iterate over exercises

[jtigger]

When I run bin/journey_test.sh locally, it works perfectly.

However, reviewing the logs in Travis, in the solve_all_exercises() function, the for-loop that would iterate over the exercises simply does not execute... as if the exercises variable were empty.

[jtigger]

Hey @FridaTveit, I suspect you did everything right and that there's something different in the Travis CI environment. Since you were in here last, you get dibs at taking point tackling this. Of course, lean on the group if it gets hairy. We're all in this together. ;)

[FridaTveit]

Okay, will have a look! :)

[FridaTveit]

It looks like it's happening because --join-output isn't a jq option in the version of jq being run... will look into finding another option to use. Is there a way of finding out which version of jq it's running?

[FridaTveit]

Or is it possible to update the version of jq it's running, @jtigger?

[stkent]

Travis looks to have a global version (not sure what that is), but I wonder if we could override that with a before_install instruction?

https://docs.travis-ci.com/user/installing-dependencies/

[jtigger]

Is there a way of finding out which version of jq it's running?

One trick I like is to put a little bit in the build script that tells each tool used which version it is. Something like jq --version. With that in the script, it is included in the build output. In fact, would have been a good thing to have in there in the first place. :)

Or is it possible to update the version of jq it's running, @jtigger?

Yeah, unless there's some restriction about pre-installed tools, sounds like the tack @stkent is suggestion is a good angle. Give it a whirl!

[FridaTveit]

Okay, so what exactly do I need to add to .travis.yml (assuming that's where I need to add it)? sudo apt-get -y install jq? And is there any other way of testing that it works other than making a PR and checking the travis logs?

[stkent]

That install command looks good to me! And yes, since this issue is specific to the Travis environment, I think testing by opening and modifying a PR is probably the best option :)

[jtigger]

Great question.

Yup, that's the right file: .travis.yml!

Personally, I'd look to see if adding jq to the addons section would install a newer version.

addons:
  apt:
    packages:
      - tree

Yeah, one great way to do this is to enable Travis for your personal account and then on your fork of xjava. You'll find a bank of switches in your "Accounts"/"Profile" page.

Once enabled, you'll see that Travis builds even your branches. So you can continue to do your work on a branch as you normally do. When you push to your own repo, Travis kicks off the build on that branch.

[jtigger]

@stkent: jinx!

[stkent]

@FridaTveit listen to @jtigger not me 😄

[jtigger]

hehehehehe! All good advice, 'round. :)

[FridaTveit]

Okay, will try that! Thanks :)