DependencyVerificationWritingIntegTest.groovy

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Fix test flakiness

Sometimes the `.sha1` for module files wasn't fetched because the

HTTP test fixture server would report a `LastModified` timestamp

unchanged even if the underlying file did. That's because we're

just relying on the file last modified timestamp which unfortunately

isn't reliable.

    • -2
    • +2
    ./DependencyVerificationWritingIntegTest.groovy
  1. … 3 more files in changeset.
Fix test flakiness

Sometimes the `.sha1` for module files wasn't fetched because the

HTTP test fixture server would report a `LastModified` timestamp

unchanged even if the underlying file did. That's because we're

just relying on the file last modified timestamp which unfortunately

isn't reliable.

    • -2
    • +2
    ./DependencyVerificationWritingIntegTest.groovy
  1. … 3 more files in changeset.
Fix test flakiness

Sometimes the `.sha1` for module files wasn't fetched because the

HTTP test fixture server would report a `LastModified` timestamp

unchanged even if the underlying file did. That's because we're

just relying on the file last modified timestamp which unfortunately

isn't reliable.

    • -2
    • +2
    ./DependencyVerificationWritingIntegTest.groovy
  1. … 3 more files in changeset.
Fix test flakiness

Sometimes the `.sha1` for module files wasn't fetched because the

HTTP test fixture server would report a `LastModified` timestamp

unchanged even if the underlying file did. That's because we're

just relying on the file last modified timestamp which unfortunately

isn't reliable.

    • -2
    • +2
    ./DependencyVerificationWritingIntegTest.groovy
  1. … 3 more files in changeset.
Fix test flakiness

Sometimes the `.sha1` for module files wasn't fetched because the

HTTP test fixture server would report a `LastModified` timestamp

unchanged even if the underlying file did. That's because we're

just relying on the file last modified timestamp which unfortunately

isn't reliable.

    • -2
    • +2
    ./DependencyVerificationWritingIntegTest.groovy
  1. … 3 more files in changeset.
Fix test flakiness

Sometimes the `.sha1` for module files wasn't fetched because the

HTTP test fixture server would report a `LastModified` timestamp

unchanged even if the underlying file did. That's because we're

just relying on the file last modified timestamp which unfortunately

isn't reliable.

    • -2
    • +2
    ./DependencyVerificationWritingIntegTest.groovy
  1. … 3 more files in changeset.
Fix test flakiness

Sometimes the `.sha1` for module files wasn't fetched because the

HTTP test fixture server would report a `LastModified` timestamp

unchanged even if the underlying file did. That's because we're

just relying on the file last modified timestamp which unfortunately

isn't reliable.

    • -2
    • +2
    ./DependencyVerificationWritingIntegTest.groovy
  1. … 3 more files in changeset.
Fix verification of dependencies resolved in buildFinished

Previously it was possible that a user hook (buildFinished)

was executed _after_ the verification code was done. With

this commit this is no longer possible.

    • -3
    • +3
    ./DependencyVerificationWritingIntegTest.groovy
  1. … 10 more files in changeset.
Fix verification of dependencies resolved in buildFinished

Previously it was possible that a user hook (buildFinished)

was executed _after_ the verification code was done. With

this commit this is no longer possible.

    • -3
    • +3
    ./DependencyVerificationWritingIntegTest.groovy
  1. … 7 more files in changeset.
Fix verification of dependencies resolved in buildFinished

Previously it was possible that a user hook (buildFinished)

was executed _after_ the verification code was done. With

this commit this is no longer possible.

    • -3
    • +3
    ./DependencyVerificationWritingIntegTest.groovy
  1. … 10 more files in changeset.
Mark tests as failing with instant execution

    • -0
    • +1
    ./DependencyVerificationWritingIntegTest.groovy
  1. … 1 more file in changeset.
Mark tests as failing with instant execution

    • -0
    • +1
    ./DependencyVerificationWritingIntegTest.groovy
  1. … 1 more file in changeset.
Mark tests as failing with instant execution

    • -0
    • +1
    ./DependencyVerificationWritingIntegTest.groovy
  1. … 1 more file in changeset.
Mark tests as failing with instant execution

    • -0
    • +1
    ./DependencyVerificationWritingIntegTest.groovy
  1. … 1 more file in changeset.
Mark tests as failing with instant execution

    • -0
    • +1
    ./DependencyVerificationWritingIntegTest.groovy
  1. … 1 more file in changeset.
Add API to disable dependency verification

This commit adds an API to disable verification on a specific

configuration (using `resolutionStrategy.disableDependencyVerification`.

This would let tasks which perform special dependency resolution (like

checking newer versions of dependencies) to pass even if dependency

verification is enabled.

    • -0
    • +35
    ./DependencyVerificationWritingIntegTest.groovy
  1. … 11 more files in changeset.
Add API to disable dependency verification

This commit adds an API to disable verification on a specific

configuration (using `resolutionStrategy.disableDependencyVerification`.

This would let tasks which perform special dependency resolution (like

checking newer versions of dependencies) to pass even if dependency

verification is enabled.

    • -0
    • +35
    ./DependencyVerificationWritingIntegTest.groovy
  1. … 11 more files in changeset.
Add API to disable dependency verification

This commit adds an API to disable verification on a specific

configuration (using `resolutionStrategy.disableDependencyVerification`.

This would let tasks which perform special dependency resolution (like

checking newer versions of dependencies) to pass even if dependency

verification is enabled.

    • -0
    • +35
    ./DependencyVerificationWritingIntegTest.groovy
  1. … 11 more files in changeset.
Add API to disable dependency verification

This commit adds an API to disable verification on a specific

configuration (using `resolutionStrategy.disableDependencyVerification`.

This would let tasks which perform special dependency resolution (like

checking newer versions of dependencies) to pass even if dependency

verification is enabled.

    • -0
    • +35
    ./DependencyVerificationWritingIntegTest.groovy
  1. … 11 more files in changeset.
Add API to disable dependency verification

This commit adds an API to disable verification on a specific

configuration (using `resolutionStrategy.disableDependencyVerification`.

This would let tasks which perform special dependency resolution (like

checking newer versions of dependencies) to pass even if dependency

verification is enabled.

    • -0
    • +35
    ./DependencyVerificationWritingIntegTest.groovy
  1. … 11 more files in changeset.
Allow signature verification file generation

This commit adds the ability to generate a verification file which relies

on PGP signature verification. With this mode, Gradle will download the

signatures and verify them. Depending on the result of verification,

Gradle will either:

- automatically add trusted keys if verification passed

- automatically ignore keys if they couldn't be downloaded

- automatically ignore keys if verification failed

If verification failed or that a key couldn't be downloaded, a

WARNING will be issued to encourage the user to verify what

happened.

In order to reduce the size of the verification file, Gradle will

also automatically perform "normalization" of verifications by

configuring globally trusted keys for artifacts which share the same

group or a common super group.

    • -2
    • +2
    ./DependencyVerificationWritingIntegTest.groovy
  1. … 20 more files in changeset.
Allow signature verification file generation

This commit adds the ability to generate a verification file which relies

on PGP signature verification. With this mode, Gradle will download the

signatures and verify them. Depending on the result of verification,

Gradle will either:

- automatically add trusted keys if verification passed

- automatically ignore keys if they couldn't be downloaded

- automatically ignore keys if verification failed

If verification failed or that a key couldn't be downloaded, a

WARNING will be issued to encourage the user to verify what

happened.

In order to reduce the size of the verification file, Gradle will

also automatically perform "normalization" of verifications by

configuring globally trusted keys for artifacts which share the same

group or a common super group.

    • -2
    • +2
    ./DependencyVerificationWritingIntegTest.groovy
  1. … 22 more files in changeset.
Allow signature verification file generation

This commit adds the ability to generate a verification file which relies

on PGP signature verification. With this mode, Gradle will download the

signatures and verify them. Depending on the result of verification,

Gradle will either:

- automatically add trusted keys if verification passed

- automatically ignore keys if they couldn't be downloaded

- automatically ignore keys if verification failed

If verification failed or that a key couldn't be downloaded, a

WARNING will be issued to encourage the user to verify what

happened.

In order to reduce the size of the verification file, Gradle will

also automatically perform "normalization" of verifications by

configuring globally trusted keys for artifacts which share the same

group or a common super group.

    • -2
    • +2
    ./DependencyVerificationWritingIntegTest.groovy
  1. … 22 more files in changeset.
Allow signature verification file generation

This commit adds the ability to generate a verification file which relies

on PGP signature verification. With this mode, Gradle will download the

signatures and verify them. Depending on the result of verification,

Gradle will either:

- automatically add trusted keys if verification passed

- automatically ignore keys if they couldn't be downloaded

- automatically ignore keys if verification failed

If verification failed or that a key couldn't be downloaded, a

WARNING will be issued to encourage the user to verify what

happened.

In order to reduce the size of the verification file, Gradle will

also automatically perform "normalization" of verifications by

configuring globally trusted keys for artifacts which share the same

group or a common super group.

    • -2
    • +2
    ./DependencyVerificationWritingIntegTest.groovy
  1. … 22 more files in changeset.
Allow signature verification file generation

This commit adds the ability to generate a verification file which relies

on PGP signature verification. With this mode, Gradle will download the

signatures and verify them. Depending on the result of verification,

Gradle will either:

- automatically add trusted keys if verification passed

- automatically ignore keys if they couldn't be downloaded

- automatically ignore keys if verification failed

If verification failed or that a key couldn't be downloaded, a

WARNING will be issued to encourage the user to verify what

happened.

In order to reduce the size of the verification file, Gradle will

also automatically perform "normalization" of verifications by

configuring globally trusted keys for artifacts which share the same

group or a common super group.

    • -2
    • +2
    ./DependencyVerificationWritingIntegTest.groovy
  1. … 22 more files in changeset.
Allow signature verification file generation

This commit adds the ability to generate a verification file which relies

on PGP signature verification. With this mode, Gradle will download the

signatures and verify them. Depending on the result of verification,

Gradle will either:

- automatically add trusted keys if verification passed

- automatically ignore keys if they couldn't be downloaded

- automatically ignore keys if verification failed

If verification failed or that a key couldn't be downloaded, a

WARNING will be issued to encourage the user to verify what

happened.

In order to reduce the size of the verification file, Gradle will

also automatically perform "normalization" of verifications by

configuring globally trusted keys for artifacts which share the same

group or a common super group.

    • -2
    • +2
    ./DependencyVerificationWritingIntegTest.groovy
  1. … 22 more files in changeset.
Remove `@ToBeFixedForInstantExecution` annotation

    • -1
    • +0
    ./DependencyVerificationWritingIntegTest.groovy
Remove `@ToBeFixedForInstantExecution` annotation

    • -1
    • +0
    ./DependencyVerificationWritingIntegTest.groovy
Remove `@ToBeFixedForInstantExecution` annotation

    • -1
    • +0
    ./DependencyVerificationWritingIntegTest.groovy
Remove `@ToBeFixedForInstantExecution` annotation

    • -1
    • +0
    ./DependencyVerificationWritingIntegTest.groovy