Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Process PID / Long Lived Processes #3

Open
johnrengelman opened this issue Dec 5, 2013 · 0 comments
Open

Process PID / Long Lived Processes #3

johnrengelman opened this issue Dec 5, 2013 · 0 comments

Comments

@johnrengelman
Copy link
Owner

This covers forking of processes that outlive the Gradle build process itself. Is it possible? Would termination of the build cause the child processes to terminate? How to work around that?

What about terminating the process in a subsequent Gradle build execution? For example:

task start << {
  project.procs.fork { }
}

task stop << {
  //somehow terminate the process
}

Currently the API only exposes a waitForFinish, how do we term the program? How do we pick up the right process in the subsequent build? Do we do pattern matching? Is there a way to get the PID (PIDs are not exposed through the Java Process API, how do we merge the concepts between *nix and Windows?)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant