nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

What is the purpose of folders created in /tmp by Bamboo

Jan Swaelens1

Hello,

We are on Bamboo 4.2 (same behavior was noticed on earlier versions too) and notice a bunch of folders being created by Bamboo in the /tmp folder of our server instance.

These folders are named [Project Key]-[Plan Key] and seem to contain no files.

We are wondering what the purpose of those files is and why they seem to be empty. Out IT staff would also like it very much to get rid of them (as they seem to contain no files).

Also, is there something to configure in terms of an alternate location?

Thanks for your insights

Accepted answers

Jan Swaelens1

Those folders are created because they are passed to java processes as value for 'java.io.tmpdir'. By default the plan key is added as a sub folder to the default system setting for 'java.io.tmpdir'.

It is possible to specify an alternate folder by means of the Java system property 'bamboo.build.parent.java.io.tmpdir' (which is what we are doing now to have the temp folders created on our data partition instead of the os partition).

All comments

Cameron Ferguso

Sounds like to me that's where your builds are happening....

If you have the miscellaneous options for your jobs set to, "Clean Working Directory after build" then it would contain no files...

How are you launching the bamboo agent? Are you specifying "-Dbamboo.home=/bamboo/dir" when launching the agent jar file?

Jan Swaelens1

We have bamboo.home set to an alternate location, the builds are happening there. I think I'm gonna deep dive in the code to see where those folders are coming from :-)

Jan Swaelens1

Those folders are created because they are passed to java processes as value for 'java.io.tmpdir'. By default the plan key is added as a sub folder to the default system setting for 'java.io.tmpdir'.

Richard Cross

Far better to launch the agent pointing at a more suitable tmp location, than to require end users to define it in their build plans. You can do this by editing the wrapper.conf and adding in the following line:

wrapper.java.additional.n=-Djava.io.tmpdir=/my/alternate/path/tmp

where n doesn't clash with similar lines in the same file.

Jan Swaelens

Thanks Richard, I had to revisit this because some plugin we are using is using that tmp location more than before.

Using the wrapper configuration file works but it is quite the hassle to apply this to all our agents. Any chance this option can be passed using a Java system variable which can be passed during agent startup, we have scripts for that which can easily pass the right one automatically.

jan

Richard Cross

We manage this by using SaltStack to provision all our agents, but you could just as easily use Puppet, Chef or Ansible.

That said, it doesn't completely solve the problem; we still have issues with NPM and Apache Spark related tasks, which leave hundreds of directories/files in /tmp, that are never cleaned up.