DependencyUnresolvedModuleIntegrationTest.groovy

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Add blacklister to repository management (#3047)

Fix https://github.com/gradle/gradle/issues/2853

Previous versions of Gradle would fall through to the next repository

if resolution in one repository failed. This may cause potentially

indeterministic resolution result. This PR changes this behaviour

and will explicitly rethrow exceptions which occur in dependency

resolution instead of quietly continue to the next repository.

What's more, this PR introduces a RepositoryBlacklister. Exceptions

thrown during dependency resolution are categoried as follows:

1. Caused by HTTP error status code (other than 2xx/3xx/404)

These exceptions would be considered as "recoverable" since

the server seems still to be able to respond.

2. Caused by other IOException/UncheckedIOException

These exceptions would be considered as "unrecoverable"

and the repository would be blacklisted in the build.

    • -0
    • +355
    ./DependencyUnresolvedModuleIntegrationTest.groovy
  1. … 19 more files in changeset.
Handle range of HTTP error codes the same way as timeouts

    • -4
    • +0
    ./DependencyUnresolvedModuleIntegrationTest.groovy
  1. … 2 more files in changeset.
Do not check other repositories if presence of module cannot be determined

    • -0
    • +315
    ./DependencyUnresolvedModuleIntegrationTest.groovy
  1. … 19 more files in changeset.
Try to get CI green

    • -0
    • +4
    ./DependencyUnresolvedModuleIntegrationTest.groovy
  1. … 2 more files in changeset.
Add tests that cover broken server behavior

    • -0
    • +311
    ./DependencyUnresolvedModuleIntegrationTest.groovy
  1. … 6 more files in changeset.