BuildProcessTest.groovy

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Revert "Ignore failing test for now"

This reverts commit 09f28a51ae9b673d8693b07b93f7a66cf31af982.

  1. … 1 more file in changeset.
Revert "Ignore failing test for now"

This reverts commit 09f28a51ae9b673d8693b07b93f7a66cf31af982.

  1. … 1 more file in changeset.
Revert "Ignore failing test for now"

This reverts commit 90e15b3e55fbba276f94e96aea8bfed7ab9fa85a.

  1. … 1 more file in changeset.
  1. … 1 more file in changeset.
  1. … 1 more file in changeset.
Replace some direct usages of `DefaultConfigurableFileCollection` with `FileCollectionFactory`.

  1. … 50 more files in changeset.
Replace some direct usages of `DefaultConfigurableFileCollection` with `FileCollectionFactory`.

  1. … 50 more files in changeset.
Fix for starting a single-use daemon when client has low memory

The previous logic was testing whether the daemon parameters had

a memory setting, but not whether that setting was the default or

whether it actually came from the user. The default settings are

ignored for the purpose of forking a single-use daemon, so they

also need to be ignored in the decision whether the current VM

has enough memory.

  1. … 2 more files in changeset.
Fork a single-use daemon of client VM has too little memory

We lowered the client VMs memory to 64m by default, which is plenty

for displaying log output, but not enough to run the vast majority

of builds. Users who really want to run their build inside the client

process should set a higher memory requirement via GRADLE_OPTS.

For all others we now automatically fork a single-use daemon, so their

build doesn't fail in environments that automatically append the "--no-daemon" flag.

These environments unfortunately include popular ones like Travis and TeamCity.

  1. … 1 more file in changeset.
Clean up BuildProcessTest

Clean up BuildProcessTest

Restore previous behavior: user can set daemon jvm args to empty

If the jvm args are explicitly defined (i.e. org.gradle.jvmargs="")

no defaults are applied.

  1. … 1 more file in changeset.
Match build VMs if immutable VM arguments match

  1. … 2 more files in changeset.
Revert "Match build VMs if immutable VM arguments match"

This reverts commit 79ed9184085a1d795a4c727f36b4f8673a27bfc9.

  1. … 3 more files in changeset.
Match build VMs if immutable VM arguments match

#2134

  1. … 2 more files in changeset.
next try to handle tmp directory as imutable property of the daemon

  1. … 9 more files in changeset.
Revert "add tmpdir explcit as system property"

This reverts commit 9cd1e1bc424651f9e94378dc1ce9c762794e70bf.

  1. … 5 more files in changeset.
add tmpdir explcit as system property

  1. … 5 more files in changeset.
Revert "handle java.io.tmpdir as immutable systemproperty"

This reverts commit 5e276076961faaca78b61fbc00b1964c6ad92187.

  1. … 4 more files in changeset.
handle java.io.tmpdir as immutable systemproperty

  1. … 4 more files in changeset.
Revert "handle java.io.tmpdir as immutable"

This reverts commit 72922b67b72f3ffc38b35fa31efc53d3ceb3c8e7.

  1. … 2 more files in changeset.
handle java.io.tmpdir as immutable

  1. … 2 more files in changeset.
Include the correct Jvm args in BuildEnvironment model

Moved `CurrentProcess` utility into 'core', while keeping the daemon

process configuration stuff in 'launcher'.

    • -0
    • +107
    ./BuildProcessTest.groovy
  1. … 8 more files in changeset.