Gradle

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Replace several more usages of direct `FileCollection` implementation instantiation with a factory method.

Remove/deprecate a couple of `FileCollection` implementations, as these can now be replaced with public API factory methods instead.

The deprecation is intended to be tempory, until the play plugin can be updated to use public APIs instead, then the implementation will be removed.

  1. … 31 more files in changeset.
Replace several more usages of direct `FileCollection` implementation instantiation with a factory method.

Remove/deprecate a couple of `FileCollection` implementations, as these can now be replaced with public API factory methods instead.

The deprecation is intended to be tempory, until the play plugin can be updated to use public APIs instead, then the implementation will be removed.

  1. … 31 more files in changeset.
Added integration tests to make sure retries happen for maven and ivy publication

Signed-off-by: Roberto Perez Alcolea <rperezalcolea@netflix.com>

Fixes for previous commit.

Fixes for previous commit.

Fixes for previous commit.

Update code quality tools to latest version

Merge pull request #12124 from gradle/bamboo/master/ie/report-changed-build-logic-input

Report changed build logic inputs

Merge pull request #12101 from gradle/bamboo/master/ie/improve-gradle-properties-coverage

Add test coverage for the interaction between `gradle.properties` and included builds

Wait longer on Windows

recognize contributor

    • -0
    • +1
    /subprojects/docs/src/docs/release/notes.md
Merge pull request #12120 from jeffalder/patch-1

Typo

Fixes for previous commit.

Fixes for previous commit.

Fixes for previous commit.

Merge pull request #12123 from gradle/eskatos/ie/smoked-dog-food

Add more checks and assertions to GradleBuildInstantExecutionSmokeTest

Report changed configuration file causing the ie cache not to be reused

Remove special casing of `SystemPropertyValueSource` when checking the ie cache fingerprint

As it's no longer needed since the change to load the properties very early in

the build.

Report changed environment variable causing the ie cache not to be reused

Report changed Gradle property causing the ie cache not to be reused

Polish `InstantExecutionBuildOptionsIntegrationTest`

- Dedupe `Greet` task definition

Let GradleBuildInstantExecutionSmokeTest run buildSrc checks

Signed-off-by: Paul Merlin <paul@gradle.com>

Add assertions to GradleBuildInstantExecutionSmokeTest

Signed-off-by: Paul Merlin <paul@gradle.com>

Merge pull request #12119 from gradle/bamboo/master/ie/improve-build-logic-input-change-report

Improve build logic input change report

Wait some more for continuous build

so all changes are picked up.

Performance optimization for verification

Dependency verification may produce a number of

verification events which are only relevant if,

eventually, a fatal verification failure occurs.

If it's not the case, there will not be any

verification failure, therefore it's unnecessary

to perform formatting of an error message.

Previously, we would always check for verification

failures even if, in the end, there would only

be non fatal ones, which slows down IDE syncing.

Performance optimization for verification

Dependency verification may produce a number of

verification events which are only relevant if,

eventually, a fatal verification failure occurs.

If it's not the case, there will not be any

verification failure, therefore it's unnecessary

to perform formatting of an error message.

Previously, we would always check for verification

failures even if, in the end, there would only

be non fatal ones, which slows down IDE syncing.

Performance optimization for verification

Dependency verification may produce a number of

verification events which are only relevant if,

eventually, a fatal verification failure occurs.

If it's not the case, there will not be any

verification failure, therefore it's unnecessary

to perform formatting of an error message.

Previously, we would always check for verification

failures even if, in the end, there would only

be non fatal ones, which slows down IDE syncing.

Performance optimization for verification

Dependency verification may produce a number of

verification events which are only relevant if,

eventually, a fatal verification failure occurs.

If it's not the case, there will not be any

verification failure, therefore it's unnecessary

to perform formatting of an error message.

Previously, we would always check for verification

failures even if, in the end, there would only

be non fatal ones, which slows down IDE syncing.

Performance optimization for verification

Dependency verification may produce a number of

verification events which are only relevant if,

eventually, a fatal verification failure occurs.

If it's not the case, there will not be any

verification failure, therefore it's unnecessary

to perform formatting of an error message.

Previously, we would always check for verification

failures even if, in the end, there would only

be non fatal ones, which slows down IDE syncing.