Fix the hoodie ci s3 test failed.

[horizonzy]

Motivation

The HoodieWriterTest will run ci with s3, but the env is not set, so the test can't pass. I think we can disable the s3 in the ci.

Documentation

Check the box below.

Need to update docs?

• doc-required

  (If you need help on updating docs, create a doc issue)

• no-need-doc

  (Please explain why)

• doc

  (If this PR contains doc changes)

[hangc0276]

The CI can pass when one branch in this project wants to merge to the master, but it will fail when the forked repo wants to merge PR to the master. It is not friendly for community users to contribute PR to this repo. I think we can disable the S3 test. Do you have any ideas? @zymap

[zymap]

We can run that test when the PR is merged into the master, and for pull-request, we can skip it.

We can separate the cloud-related test, and only trigger it running using the condition:

    - name: cloud test after build
      if: github.event_name == 'push'
      env:
        CLOUD_BUCKET_NAME: ${{ secrets.CLOUD_BUCKET_NAME }}
        AWS_SECRET_KEY: ${{ secrets.AWS_SECRET_KEY }}
        AWS_ACCESS_KEY_ID: ${{ secrets.AWS_ACCESS_KEY_ID }}
      run: mvn test -Pcloud -Dtest='TestS3Cloud.java'

Then, run the remaining tests in the usual pull request checks.

[hangc0276]

We can run that test when the PR is merged into the master, and for pull-request, we can skip it.

We can separate the cloud-related test, and only trigger it running using the condition:

    - name: cloud test after build
      if: github.event_name == 'push'
      env:
        CLOUD_BUCKET_NAME: ${{ secrets.CLOUD_BUCKET_NAME }}
        AWS_SECRET_KEY: ${{ secrets.AWS_SECRET_KEY }}
        AWS_ACCESS_KEY_ID: ${{ secrets.AWS_ACCESS_KEY_ID }}
      run: mvn test -Pcloud -Dtest='TestS3Cloud.java'

Then, run the remaining tests in the usual pull request checks.

make sense
@horizonzy Would you please update this PR? thanks.

[horizonzy]

I'm not sure I got the idea clearly, please help to review it. Thanks @zymap