RuleTaskBridgingIntegrationTest.groovy

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Introduce GradleDistributionsPlugin and multiple distribution projects

We can now have different distributions, containing different sets of

jars/functionality. For this, one subproject per distribution type is

created. Initially we introduce:

- _core_ (absolute minimum needed to run Gradle)

- _basics_ (Basic functionalities on top of core)

- _jvm_ (Everything needed for JVM ecosystem support)

- _native_ (everything for Native support)

- _publishing_ (everything to publish to Maven/Ivy repositories)

This is just an initial structure which we can now easily change. The

main point here is to enable a setup like this at all. New/different

distributions can now simply be added by adding a new subproject that

applies `gradlebuild.distribution.packaging` and defines the content of

the distribution in terms of dependencies.

Projects needing a distribution for testing, then depend on that project

e.g. `integTestDistributionRuntimeOnly(project(":distributionsJvm"))`

While introducing this, a lot of changes/improvements are done.

(See also previous commits and documentation in code.) Some major things:

- The embedded test runner now no longer supports running against a full

distribution as fallback. This has the advantage that we do not need to

assemble the distribution in embedded running, where the huge majority

of tests does not need it. To allow more tests still to run embedded,

the embedded support with TestKit/KotlinDSL involvement has been

improved. Some tests won't run with the embedded runner at all

now, but compared to the overall amount of tests, these are just a few.

And the "forking" tests always run as part of the PR pipeline.

- Cacheability of tests is highly improved. We broke some things

recently when adding inputs for distributed testing.

These regressions are addressed. Other things were

improved along the line (local Tooling API repo no longer uses timestamp

version, local bin distribution without timestamp for wrapper tests,

sample tests no longer rely on absolute path and timestamp version, ...)

- The `docs.jar` is no longer part of the distribution. It almost had no

content and what it had was runtime metadata and not documentation.

Instead, a distribution project now encapsulates all the runtime

metadata creation and produces a `runtime-api-info.jar` that is specific

to the distribution.

- In the past we had flakiness issues causes by different distributions

sharing the same user home/daemon registry. With the fixed set of

distributions defined, we now use different user home/daemon registry

for each distribution.

- Cross-project configurations are removed. There was some code

central to distribution building and runtime metadata generation that

reached into all subprojects. This is now replaced by using proper

variant aware dependency management to share artifacts between

distribution subprojects and the other subprojects.

    • -1
    • +6
    ./RuleTaskBridgingIntegrationTest.groovy
  1. … 189 more files in changeset.
Add an outgoing variants report

This commit introduces an `outgoingVariants` task which generates

a report of the outgoing variants of a project. This is useful

for debugging and understanding variant aware resolution.

It becomes possible for a plugin author to understand what variants

are already produced by a project based on the plugins applied, and

what artifacts are attached to what variant.

    • -1
    • +1
    ./RuleTaskBridgingIntegrationTest.groovy
  1. … 9 more files in changeset.
Check for already registered model in TaskContainer

A ModelMap<Task> is a shadow version of the TaskContainer inside the

software model. Although difficult, it is possible to create an element

in ModelMap<Task> before creating the same element in TaskContainer.

This creates a duplicate instance that, in some case, cause both

instance to be used in the task graph causing issues.

    • -0
    • +35
    ./RuleTaskBridgingIntegrationTest.groovy
  1. … 1 more file in changeset.
Fix integ tests after new buit-in task

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

    • -1
    • +1
    ./RuleTaskBridgingIntegrationTest.groovy
  1. … 3 more files in changeset.
Fix integration tests that relied on placeholder behavior

    • -58
    • +1
    ./RuleTaskBridgingIntegrationTest.groovy
  1. … 7 more files in changeset.
Always include a contextual 'cannot determine dependencies for task' error message when the dependencies of a task cannot be calculated. Sometimes this was not included in the logging output.

    • -1
    • +2
    ./RuleTaskBridgingIntegrationTest.groovy
  1. … 4 more files in changeset.
Review and improve tests that require exact ordering of tasks

    • -9
    • +11
    ./RuleTaskBridgingIntegrationTest.groovy
  1. … 23 more files in changeset.
Use doLast instead of left shift operator

Made this change in preparation for deprecating the left shift operator.

+review REVIEW-6236

    • -10
    • +10
    ./RuleTaskBridgingIntegrationTest.groovy
  1. … 163 more files in changeset.
Allow scalar collections and bridged tasks to be viewed as `ModelElement`.

    • -0
    • +70
    ./RuleTaskBridgingIntegrationTest.groovy
  1. … 7 more files in changeset.
Fix integration tests

+review REVIEW-5921

    • -2
    • +2
    ./RuleTaskBridgingIntegrationTest.groovy
  1. … 1 more file in changeset.
Some minor changes to test coverage for task definition from rules.

    • -6
    • +4
    ./RuleTaskBridgingIntegrationTest.groovy
  1. … 1 more file in changeset.
Changed bridging of tasks between rules and legacy land so that tasks are not made immutable when they are accessed by name from legacy land.

Instead, tasks are transitioned so that their initializer rules are executed, but mutation and later rules are not executed. These rules are executed when the tasks are added to the task execution graph.

    • -1
    • +153
    ./RuleTaskBridgingIntegrationTest.groovy
  1. … 9 more files in changeset.
Moved some tests between test cases.

    • -1
    • +112
    ./RuleTaskBridgingIntegrationTest.groovy
  1. … 1 more file in changeset.
Renamed some test classes.

    • -0
    • +368
    ./RuleTaskBridgingIntegrationTest.groovy
  1. … 5 more files in changeset.