[GRADLE-1748] Cannot run more than one build at a time when using the daemon Created: 14/Aug/11  Updated: 04/Jan/13  Resolved: 11/Oct/11

Status: Resolved
Project: Gradle
Affects Version/s: None
Fix Version/s: 1.0-milestone-5

Type: Bug
Reporter: Adam Murdoch Assignee: Szczepan Faber
Resolution: Fixed Votes: 0

Comment by Szczepan Faber [ 17/Aug/11 ]

Potential approaches:

  1. single daemon per user, has multiple threads (cons: a heavyweight daemon, needs smart thread management)
  2. single daemon per concurrent gradle build per user (cons: needs smart suicide mechanism to avoid proliferation of daemons)
  3. single daemon manager + one daemon per concurrent gradle build per user (cons: seems like an overkill)
  4. something else?

I'm leaning towards #2, making daemons fairly lightweight, cheap to kill & create.

Comment by Adam Murdoch [ 17/Aug/11 ]

Another option is to run the build in the client if the daemon happens to be busy.

I think option 2 is the best option.

Comment by Peter Niederwieser [ 18/Aug/11 ]

What's the difference between 2. and 3.?

Comment by Szczepan Faber [ 18/Aug/11 ]

#3 introduces a 'power daemon' that somehow manages other daemons and traffic.

Generated at Wed Jun 30 12:03:21 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.