tag:help.appveyor.com,2012-11-13:/discussions/questions/46808-persistence-of-project-directory-for-a-processremote-process-build-workerAppVeyor: Discussion 2020-04-28T21:04:57Ztag:help.appveyor.com,2012-11-13:Comment/481175852020-02-26T18:27:58Z2020-02-26T18:27:58ZPersistence of project directory for a Process/Remote Process build worker<div><p>Hi Oliver,</p>
<p>If you open <code>appsettings.build-agent.json</code> in the root of Host Agent installation folder (<code>C:\Program Files\AppVeyor\HostAgent</code>) there is an option <code>DoNotDeleteBuildFolderOnFinish</code> which allows you to control cleanup logic on build completion. But, of course, <code>clone_script</code> should be used anyway. Let me know if that worked for you.</p></div>Feodor Fitsnertag:help.appveyor.com,2012-11-13:Comment/481175852020-02-27T09:12:49Z2020-02-27T09:12:50ZPersistence of project directory for a Process/Remote Process build worker<div><p>Thanks for this - is there an equivalent setting when the AppVeyor server is running a build in “Process”?</p>
<p>I can see it uses the TEMP user for the build in this case (whereas Remote Process uses the “appveyor” user it seems), and clears down the build folder each time. Is there a way to stop it clearing down the build folder - there is no HostAgent folder on the server in the program data folder.</p>
<p>Alternatively, maybe I can just use %APPDATA% and do everything in my own workspace folder and bypass the build folder completely?</p></div>Oliver Collyertag:help.appveyor.com,2012-11-13:Comment/481175852020-02-27T19:14:02Z2020-02-27T19:14:17ZPersistence of project directory for a Process/Remote Process build worker<div><p>Well, if you can use some external directory to clone the sources then I'd do that.</p></div>Feodor Fitsner