title: Way to persist process spawned by a task on an agent?
body: <p>I'm developing an Azure Devops extension with tasks in it. In one of the tasks, I'm  starting a process and I'm doing configurations. In another task, I'm accessing the  same process API to consume it. This is working perfectly fine, but I notice that after the job is done, my process is killed. I was planning to allow the user to do the configuration on an agent and be able to access it in another job or pipeline.</p>
  
  <p>Is there a way to persist a process on an agent? I feel like the agent is killing every child processes created on cleanup. Where can I find documentation on this?</p>
  
  <p><strong>Edit</strong>: I managed to find this <a href="https://developercommunity.visualstudio.com/content/problem/497786/release-pipeline-killed-my-node-server-process-in.html" rel="nofollow noreferrer">thread</a> that talks about a certain <code>Process.clean</code> variable but there's not any more information about it and I didn't find documentation on it.</p>