# \[Golang\] How about modules (formerly known as vgo) support?

**URL:** <https://travis-ci.community/t/golang-how-about-modules-formerly-known-as-vgo-support/110>\
**Category:** Travis CI Discussions & Feedback\
**Created:** [August 12, 2018, 9:51pm UTC](https://travis-ci.community/t/golang-how-about-modules-formerly-known-as-vgo-support/110 "2018-08-12T21:51:11Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![keltia](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/keltia/32/59_2.png) [@keltia](https://travis-ci.community/u/keltia)\
**Post date:** [August 12, 2018, 9:51pm UTC](https://travis-ci.community/t/golang-how-about-modules-formerly-known-as-vgo-support/110/1 "2018-08-12T21:51:11Z")

</div>

Hello,

I’ve been using Travis-CI for all my #Golang builds for quite some time. As my projects evolve, I have to manually add new modules in the `.travis.yml` file all the time. Now that Go 1.11 due later this month will have real module support, isn’t it time to add modules (formerly known as `vgo`) to the #Golang part of Travis?

There are a few ways to do it:

- use 1.11 onward, it should work as-as and fetch modules during the build
- for older versions, I’d maybe add a `vgo: true` or similar to get the same behaviour.

Idea, comment?

---

<div class="post-metadata">

**Author:** ![keltia](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/keltia/32/59_2.png) [@keltia](https://travis-ci.community/u/keltia)\
**Post date:** [August 14, 2018, 11:54am UTC](https://travis-ci.community/t/golang-how-about-modules-formerly-known-as-vgo-support/110/2 "2018-08-14T11:54:31Z")

</div>

Ok, thanks to the folks on Slack in #modules, I’ve been pointed to [This article](https://dave.cheney.net/2018/07/16/using-go-modules-with-travis-ci) by Dave Cheney. If I were to stop supporting 1.10 in my builds I could do away with the `install:` section and rely on module support. That’s because I never tried to use `dep` before hence I do not have the `Gopkg.toml/.lock` that remove the need of `install:`. Oh well.

---

<div class="post-metadata">

**Author:** ![acnagy](https://sea1.discourse-cdn.com/flex015/user_avatar/travis-ci.community/acnagy/32/17_2.png) [@acnagy](https://travis-ci.community/u/acnagy)\
**Post date:** [August 15, 2018, 8:53pm UTC](https://travis-ci.community/t/golang-how-about-modules-formerly-known-as-vgo-support/110/3 "2018-08-15T20:53:43Z")

</div>

Awesome! Yeah, Dave’s article looks right for sure. As to the `install:` section - you could try evaluating it only if the go version is 1.10 ([conditions would be helpful here](https://docs.travis-ci.com/user/conditions-v1)).

In any event, I’ll check with the go folks here and see where we are on module support!