In a gradle project I had created a a single job cache named gradle covering three gradle cache folders, namely /root/.gradle/caches, /root/.gradle/jdks and /root/.gradle/wrapper.

Today I was logged into a docker container currently executing a build and did take a look at the caches because I wanted to check if they contain outdated data (e.g. old JDKs). I noticed that this single cache was made available under /agent/work/temp/onedev-build-17-1328/cache/1 and the contents of caches, jdks and wrapper had been merged into that single cache/1 folder. In addition that merged content was available inside the container at /root/.gradle/caches, /root/.gradle/jdks and /root/.gradle/wrapper. So all three folders had the same content.

Is that really how you want it to work? What happens if I have multiple cache folders declared in a single cache and each folder has a file at the same location with the same name but different contents? Because these folder contents have been merged by OneDev the final content of this file will be random?

I expected that OneDev will produce a tar file that looks like

tar-file
  -> caches
       -> contents
  -> jdks
      -> contents
  -> wrapper
       -> contents

Then it would be unpacked to /agent/work/temp/onedev-build-17-1328/cache/1 and the three subfolders then linked to their original locations. Currently this subfolder layer for caches, jdks and wrapper is missing and the combined content of all folders in /agent/work/temp/onedev-build-17-1328/cache/1 is linked to each declared cache folder.