profiling

After the improvement of automatically rerunning and tagging, we want to manage performance test in the same way:

- Only run each performance test scenario once.

- If it fails, `GRADLE_RERUNNER` will kick in and rerun the failed scenario. The good thing is that it might be scheduled to another build agent, which mitigates the effect of bad agent.

This PR does:

- Remove all `Retry` from performance tests.

- Add `GRADLE_RERUNNER` to performance tests and refactor some code.

- Add tests for `PerformanceTest`.

- Since `GRADLE_RERUNNER` depends on reading of test binary result, write binary test result file in `RerunableDistributedPerformanceTest`.

We now get enough information out of the box about buildSrc task, we

don't need to add the custom values.

This closes https://github.com/gradle/gradle-private/issues/1774

We've been bitten by flaky tests for a long time. This PR adds an extra build step which reruns failed test classes again.

I noticed several `CACHE_MISS`es caused by asciidoctor tasks. There're two issues:

- The GE performance tests are running `CacheableAsciidoctorTask` without seed builds.

- The promotion builds' build cache is disabled so they can't fetch data from cache.

This PR fixes these two issues.

We observed some CACHE_MISSes and this PR fixes them

This fixes https://github.com/gradle/gradle-private/issues/1741

This PR does:

- Re-enables `CacheableAsciidoctorTask`

- Updates everything to the latest version.

- Fixes several broken cacheability issues.

- Tag the build `CACHE_MISS` upon unexpected cache-miss.

This fixes https://github.com/gradle/gradle-private/issues/1728

Previously we didn't check if a build is already tagged `CACHE_MISS` before tagging. This PR adds an `AtomicBoolean` as a flag to avoid duplicate tags.

Because it doesn't depend on compileAll task.

This is the first-step implementation of https://github.com/gradle/gradle-private/issues/1681

Previously sometimes we see unexpected cache misses in the build, which we want to monitor. This PR marks all non-skipped `AbstractCompile` and `ClasspathManifest` tasks as `CACHE_MISS` if current build is not `compileAll`, so that this build can be searched in build scan later.

The `BuildScanPlugin` now tries to detect if the build has been

executed from IDEA. It also tries to add the version as a custom

value.

It seems like different versions of IDEA set different properties.

For example, I didn't see `idea.registered` and `idea.active` at

the same time, yet.

- Remove report links (only works on TC)

- Remove links to `e.grdev.net` GE instance for current commit

`envValue` is now known to be non-null at that point.

Introduce Travis build for contributor PRs

This closes https://github.com/gradle/gradle-private/issues/1526

Basically, the idea is, we should run feature branch performance tests against the distribution which is built from the "fork point commit". This can reduce the effects of performance regression which is not introduced by the feature branch.

Two tasks are added into the build and depended by performance task:

- `determineForkPoint`, run `git` command to determine the fork point commit. It's done during the execution phase, then it sets the commit for `buildForkPointDistribution` task.

- `buildForkPointDistribution`, try to build a distribution from the fork point commit.

`buildForkPointDistribution` is cachable so it only needs to run once. Its input is the fork point commit, the output is two files: a binary distribution and a tooling api jar. The generated binary distribution is used to run individual worker tests.

Now there is a link to search scans for

- the same commit id

- the compile all build for the commit id

- the same build type