MavenPublishS3IntegrationTest.groovy

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Rename @FailsWithInstantExecution to @ToBeFixedForInstantExecution

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

    • -3
    • +3
    ./MavenPublishS3IntegrationTest.groovy
  1. … 872 more files in changeset.
Move skip reasons to @FailsWithInstantExecution and drop @IgnoreWithInstantExecution

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

    • -3
    • +3
    ./MavenPublishS3IntegrationTest.groovy
  1. … 45 more files in changeset.
Annotate integ tests failing to cleanup with instant execution in :resourcesS3

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

    • -3
    • +3
    ./MavenPublishS3IntegrationTest.groovy
  1. … 2 more files in changeset.
Annotate integ tests failing with instant execution in various projects

removing most of @IgnoreWithInstantExecution annotations

after fixing the @FailsWithInstantExecution rule

and more ci feedback

also make @IgnoreWithInstantExecution require a reason from a fixed set

and add it to the remaining ignores

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

    • -3
    • +3
    ./MavenPublishS3IntegrationTest.groovy
  1. … 126 more files in changeset.
Annotate integ tests failing with instant execution in :resourcesS3

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

    • -0
    • +3
    ./MavenPublishS3IntegrationTest.groovy
  1. … 4 more files in changeset.
Annotate integ tests failing with instant execution in :resourcesS3

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

    • -0
    • +3
    ./MavenPublishS3IntegrationTest.groovy
  1. … 4 more files in changeset.
Add sha-256 and sha-512 checksums to `maven-publish`

This commit adds the SHA-256 and SHA-512 checksums in:

- Gradle Module Metadata

- uploads to Maven repositories using the `maven-publish` plugin

The upload of those additional files is failsafe, just in case some

repositories don't support those checksum files.

    • -0
    • +2
    ./MavenPublishS3IntegrationTest.groovy
  1. … 33 more files in changeset.
Add sha-256 and sha-512 checksums to `maven-publish`

This commit adds the SHA-256 and SHA-512 checksums in:

- Gradle Module Metadata

- uploads to Maven repositories using the `maven-publish` plugin

The upload of those additional files is failsafe, just in case some

repositories don't support those checksum files.

    • -0
    • +2
    ./MavenPublishS3IntegrationTest.groovy
  1. … 33 more files in changeset.
Add sha-256 and sha-512 checksums to `maven-publish`

This commit adds the SHA-256 and SHA-512 checksums in:

- Gradle Module Metadata

- uploads to Maven repositories using the `maven-publish` plugin

The upload of those additional files is failsafe, just in case some

repositories don't support those checksum files.

    • -0
    • +2
    ./MavenPublishS3IntegrationTest.groovy
  1. … 33 more files in changeset.
Add sha-256 and sha-512 checksums to `maven-publish`

This commit adds the SHA-256 and SHA-512 checksums in:

- Gradle Module Metadata

- uploads to Maven repositories using the `maven-publish` plugin

The upload of those additional files is failsafe, just in case some

repositories don't support those checksum files.

    • -0
    • +2
    ./MavenPublishS3IntegrationTest.groovy
  1. … 33 more files in changeset.
Add sha-256 and sha-512 checksums to `maven-publish`

This commit adds the SHA-256 and SHA-512 checksums in:

- Gradle Module Metadata

- uploads to Maven repositories using the `maven-publish` plugin

The upload of those additional files is failsafe, just in case some

repositories don't support those checksum files.

    • -0
    • +2
    ./MavenPublishS3IntegrationTest.groovy
  1. … 33 more files in changeset.
Merge resources integration tests

    • -132
    • +0
    ./MavenPublishS3IntegrationTest.groovy
  1. … 123 more files in changeset.
Bundle JAXB into Gradle distribution and use it on Java 9 and above

In order to use S3 backed artifact repositories, it was previously

required to add `--add-modules java.xml.bind` to `org.gradle.jvmargs`

when running on Java 9 and above. Since Java 11 no longer contains the

`java.xml.bind` module, Gradle now bundles JAXB 2.3.1

(`com.sun.xml.bind:jaxb-impl`) and uses it on Java 9 and above.

    • -3
    • +4
    ./MavenPublishS3IntegrationTest.groovy
  1. … 16 more files in changeset.
Add extra --add-modules parameters to forking GradleExecuter

    • -1
    • +3
    ./MavenPublishS3IntegrationTest.groovy
  1. … 4 more files in changeset.
Make `MavenModule.rootMetaData` more consistent with other artifacts

- Can now use it consistently with other resource fixtures

- Use in GCS/S3/SFTP maven-publish tests for consistency

    • -4
    • +4
    ./MavenPublishS3IntegrationTest.groovy
  1. … 9 more files in changeset.
Update tests for maven-publish with other repository transports

    • -21
    • +18
    ./MavenPublishS3IntegrationTest.groovy
  1. … 5 more files in changeset.
Merge pull request #690 from kiddouk:story/S3-repository-can-be-configured-to-authenticate-using-AWS-EC2-instance-metadata

S3 repository can authenticate using AWS EC2 instance metadata

* This is related to https://github.com/gradle/gradle/blob/c2dc9979706e6b3beca13f1de860834e9255fb1b/design-docs/finding-and-using-credentials.md#story-an-s3-repository-can-be-configured-to-authenticate-using-awss-ec2-instance-metadata

* Note that the AWS S3 Client implementation will now use the following

credentials (in this specific order)

- Environment (AWS_ACCESS_KEY, AWS_SECRET_ACCESS_KEY,

AWS_SESSION_TOKEN)

- Java System Properties - aws.accessKeyId and aws.secretKey

- Credential profiles file at the default

location (~/.aws/credentials) shared by all AWS SDKs and the AWS CLI

- Instance Profile Credentials - delivered through the Amazon EC2

metadata service

* The implementation assumes that only ONE authentication can be used

per s3-resource at a time

* This patch enforces that each Authentication now declares

`requiresCredentials` to be explicit

Integration tests:

Note that we cannot mock the instance meta data since it uses the ip

169.254.169.254 so we mock the system properties that the client

CredentialsProviderChain will look for.

    • -0
    • +52
    ./MavenPublishS3IntegrationTest.groovy
  1. … 22 more files in changeset.
Revert "Add s3 repository transport support for authenticating with EC2 instance metadata"

This reverts commit 3f138d2dbda259768d1d3ac91f18c192baacb5d1.

    • -0
    • +1
    ./MavenPublishS3IntegrationTest.groovy
  1. … 14 more files in changeset.
Add s3 repository transport support for authenticating with EC2 instance metadata

+review

    • -1
    • +0
    ./MavenPublishS3IntegrationTest.groovy
  1. … 14 more files in changeset.
Changed S3Server upload expectation to work the same way as the HttpServer and SftpServer upload. Removed S3FileBackedServer with request expectations in the int tests.

    • -9
    • +16
    ./MavenPublishS3IntegrationTest.groovy
  1. … 9 more files in changeset.
Some tidy-ups of S3 int tests.

    • -4
    • +5
    ./MavenPublishS3IntegrationTest.groovy
  1. … 6 more files in changeset.
moved all s3 related resources, fixtures, tests and integration tests into resourceS3 subproject

- required to add maven/ivy testfixtures (only compiling one class each atm)

+review REVIEW-5361

    • -0
    • +72
    ./MavenPublishS3IntegrationTest.groovy
  1. … 69 more files in changeset.