# Handling multiple versions of Julia

**URL:** <https://discourse.julialang.org/t/handling-multiple-versions-of-julia/14035>\
**Category:** Tooling\
**Created:** [August 25, 2018, 11:33am UTC](https://discourse.julialang.org/t/handling-multiple-versions-of-julia/14035 "2018-08-25T11:33:39Z")\
**Posts on this page:** 1\
**Showing post:** 13

<div class="post-metadata">

**Author:** ![taqtiqa-mark](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/taqtiqa-mark/32/4383_2.png) [@taqtiqa-mark](https://discourse.julialang.org/u/taqtiqa-mark)\
**Post date:** [November 3, 2019, 11:45pm UTC](https://discourse.julialang.org/t/handling-multiple-versions-of-julia/14035/13 "2019-11-03T23:45:25Z")

</div>

In case anyone else is browsing this topic looking for options:

The [jlenv org](https://www.github.com/jlenv) contains a collection projects addressing the various use cases that give rise to needing to switch between different versions of Julia. These cover a range of use cases:

- `chjulia`: just switch julia versions: Simple switch and run in prod and dev.
- `jlenv` & plugins: More elaborate setups, but not complex or slow moving enough to justify the Chef/Ansible/Salt overhead.
- jlenv-cookbook: Manage more complex slow moving setups where there are some audit requirements such as ChefSpec/InSpec/ServerSpec, or their Salt/Ansible equivalents.

An [announcement](https://discourse.julialang.org/t/ann-julia-build-jlenv-jlenv-plugins-and-jlenv-cookbook/30528) in the Tools forum has more details.

---

_[View the full topic](https://discourse.julialang.org/t/handling-multiple-versions-of-julia/14035)._