# How to use environment Variables (jenkins =\> Maven Conflict?)

**URL:** <https://community.gatling.io/t/how-to-use-environment-variables-jenkins-maven-conflict/2005>\
**Category:** Gatling (Open-Source)\
**Created:** [February 12, 2015, 3:24pm UTC](https://community.gatling.io/t/how-to-use-environment-variables-jenkins-maven-conflict/2005 "2015-02-12T15:24:34Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![slandelle](https://dub1.discourse-cdn.com/flex013/user_avatar/community.gatling.io/slandelle/32/4_2.png) [@slandelle](https://community.gatling.io/u/slandelle)\
**Post date:** [February 12, 2015, 3:24pm UTC](https://community.gatling.io/t/how-to-use-environment-variables-jenkins-maven-conflict/2005/1 "2015-02-12T15:24:34Z")

</div>

A simulation is some Scala code that runs in a JVM. At best, you can use Java APIs to manually resolve System Properties and Environment variables (as long as they are set on the Gatling JVM), see [here](http://gatling.io/docs/2.1.4/cookbook/passing_parameters.html) for an example.

But there’s no way such an out-of-the-blue “$USER” String would be magically resolved.
