ParallelDownloadsPerformanceTest.groovy

Refine performance baseline selection logic

See https://github.com/gradle/gradle-private/issues/2571

* master: (77 commits)

Realized component variants need to provide all attributes

Fix TeamCity Hygiene failures

New performance process (#10361)

Publish 5.6.1-20190825230025+0000

Publish 5.6.1-20190824230038+0000

Update .com userguide links

Update .com footer links

Update .com header links

Publish 5.6.1-20190823234015+0000

Rebase to latest 6.0 nightly

Revert "Recognize contributor"

Remove use of Java 11 API from instant execution

Recognize contributor

enhanced test source folder detection for eclipse task. (#10320)

Publish 5.6.1-20190823130927+0000

Rebase performance tests with 5.7-20190812122716+0000 baseline

Upgrade wrapper to 6.0 nightly

Rebase performance tests with 5.7-20190722220035+0000 baseline

Rebaseline to lock performance improvements

Temporarily use 5.6 as the baseline for Santa Tracker `assembleDebug` case.

...

#10348 has an influence on some of these performance scenarios.

(correcting 90e852d and 85933bb)

* master: (724 commits)

Highlight Gradle Module Metadata support as feature of the release

Add note about configurations deprecations

Increase DaemonErrorFeedbackCrossVersionSpec timeout

Recognize contributor

recognize contributor

Publish 5.6-20190819230034+0000

Remove no longer necessary instant execution codecs for `EnumSet` and `EnumMap`

Improve instant execution support for Java serialization

Polish `BeanPropertyReader.kt`

Polish `BeanCodecTest`

Polish `Codec.kt`

Introduce `SerializableWriteObjectCodec`

Polish `ClosureCodec`

Prepare `BindingsBackedCodec` to accept multiple encodings for the same binding

Simplify `BindingsBackedCodec` usage

Polish `BindingsBackedCodec`

Polish `LoadDirectoryTest`

Remove unused `SerializationFixture` class

Use latest Scan plugin 2.4.1-rc-1

Move Play plugins retirement to 7.0 for now

...

To make clear that they are using the Gradle build internal

infrastructure.

This reverts commit 0625bc7420e55e87730673231af6ad45dd04f47a.

There seems to be tiny gradual regression in performance, which causes unbearable

flakiness. Rebaselining all scenarios to catch future regressions.

This reverts commit 0625bc7420e55e87730673231af6ad45dd04f47a.

This reverts commit 2f79026f5e127a8175e25844522237615b19ed52 because of a performance regression,

reversing changes made to 7f1e66079ce629ecde3e09e549e9796ab85761dc.

Signed-off-by: Jonathan Leitschuh <Jonathan.Leitschuh@gmail.com>

The test project was updated and now requires an API

introduced in Gradle 4.9

To account for minor regression due to detailed container

callback instrumentation. This information will help find

performance issues that are much bigger than the small overhead

the instrumentation adds.

We introduced a ThreadLocal in the project locking which slowed things

down a little bit (10s of ms) in several builds. Rebaselining to prevent

this from affecting all branches.

Those tests correspond to accepted performance regressions

related to enabling improved POM support by default.

The introduction of the "platform" support introduced a couple small regressions,

but also improvements in some cases. This commit re-enables the Java IDE performance

test now that we have a baseline to compare with. Work on improving performance

is going to happen later.

To lock in memory usage improvements.

There is a known performance regression due to more work done during dependency resolution. Future

commits will attempt to mitigate the regression.