# .ruby-version being ignored in some builds

**URL:** <https://travis-ci.community/t/ruby-version-being-ignored-in-some-builds/597>\
**Category:** Ruby\
**Created:** [November 1, 2018, 5:08pm UTC](https://travis-ci.community/t/ruby-version-being-ignored-in-some-builds/597 "2018-11-01T17:08:18Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![jamesremuscat](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/jamesremuscat/32/330_2.png) [@jamesremuscat](https://travis-ci.community/u/jamesremuscat)\
**Post date:** [November 1, 2018, 5:08pm UTC](https://travis-ci.community/t/ruby-version-being-ignored-in-some-builds/597/1 "2018-11-01T17:08:18Z")

</div>

Our project specifies a required Ruby version of `2.5.1` in a `.ruby-version` file in the project root. This file is used by `Gemfile` as follows:

```auto
ruby File.read(File.join(File.dirname( __FILE__ ), '.ruby-version')).chomp

```

Up until now, Travis has been correctly detecting the `.ruby-version` file and using the correct version of Ruby in our builds (e.g. [https://travis-ci.org/alces-software/alces-flight-center/builds/445766965](https://travis-ci.org/alces-software/alces-flight-center/builds/445766965) which shows a call to `rvm use` on line 442).

For some reason, builds have started to fail because Travis is using Ruby `2.4.1` instead - for example [https://travis-ci.org/alces-software/alces-flight-center/builds/449414530](https://travis-ci.org/alces-software/alces-flight-center/builds/449414530) which is missing any `rvm` call.

Has something changed?

---

<div class="post-metadata">

**Author:** ![BanzaiMan](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/banzaiman/32/67_2.png) [@BanzaiMan](https://travis-ci.community/u/BanzaiMan)\
**Post date:** [November 1, 2018, 11:33pm UTC](https://travis-ci.community/t/ruby-version-being-ignored-in-some-builds/597/2 "2018-11-01T23:33:59Z")

</div>

There was a problematic deployment that caused this, which has since been reverted. Restarting the failing jobs should fix them.

---

<div class="post-metadata">

**Author:** ![jamesremuscat](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/jamesremuscat/32/330_2.png) [@jamesremuscat](https://travis-ci.community/u/jamesremuscat)\
**Post date:** [November 2, 2018, 12:09pm UTC](https://travis-ci.community/t/ruby-version-being-ignored-in-some-builds/597/3 "2018-11-02T12:09:48Z")

</div>

Great to know - all seems to be well again. Thanks!