From mobile apps to microservices, from small startups to big enterprises, Gradle helps teams build, automate and deliver better software, faster.

Gradle Community

Hi all!
I’m having trouble with _configuration cache_ and _environment variables_. When updating an environment variable the application gets the previous value if configuration cache is reused. If I start with `--no-configuration-cache`, the application gets the updated value.

It’s reproducable from shell and IntelliJ and on other peoples machines, but not in a <https://github.com/arve0/gradle-configuration-cache|minimal viable example>.

Example in shell
```export SOME_ENV=a_value
./gradlew :project:run
# ctrl + c
export SOME_ENV=new_value
./gradlew :project:run    # application gets SOME_ENV == a_value, both from System.getEnv and ktor environment.config.peroperty (HOCON)```
In IntelliJ I edit environment variables in run-configuration and start. Same behaviour.

Can mention that when using debug mode in IntelliJ, it does break at a break-point in buildSrc when configuration cache is reused. But if I add `--no-configuration-cache` to the run-configuration, it breaks every time.

Have tried `-Dorg.gradle.caching.debug=true`, but could not see anything interesting.

Can mention that I tried <https://discuss.gradle.org/t/how-to-debug-configuration-cache-of-environment-variables/49527|forum also>, some details about the code there.

For a start, you confuse build cache and configuration cache.
For configuration cache there is a dedicated <#C013WEPGQF9|>, this is more for build cache.
`org.gradle.caching.debug` on the other hand is for build cache, so does not help you in any way regarding any issue with configuration cache.

You might get more appropriate attention if you delete your thread here and post it to <#C013WEPGQF9|> instead.

Actually, having a fresh look at your forum thread today made me recognize the situation, I answered on the forum. :slightly_smiling_face:

> For configuration cache there is a dedicated <#C013WEPGQF9|>, this is more for build cache.
Aha. Wondered about that. Read the title
> All things relevant to caching.
..and took _all_ literally. :innocent:

Thanks for you help :blush:

I created an issue: <https://github.com/gradle/gradle/issues/30790>

&gt; Aha. Wondered about that. Read the title
&gt; All things relevant to caching.
&gt; ..and took all literally. :innocent:
&gt; 
Yeah, that description pre-dates the existence of CC, and it is fine to ask CC questions in here, <#C013WEPGQF9|> might just be more appropriate and get attention of different people. 

Maybe <@U06D8R6GQ67> should mention <#C013WEPGQF9|> in topic of this channel. :-)

Thanks for flagging, I will expedite internally