From da2a149bfe482edf162e1111bf9e077a64028ad0 Mon Sep 17 00:00:00 2001 From: Clay Johnson Date: Thu, 7 Sep 2023 11:01:55 -0500 Subject: [PATCH] Document reason for deletion of ~/.m2/settings.xml in Beam experiment --- .github/workflows/run-experiments-apache-beam.yml | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/.github/workflows/run-experiments-apache-beam.yml b/.github/workflows/run-experiments-apache-beam.yml index 702ea19..c37b49a 100644 --- a/.github/workflows/run-experiments-apache-beam.yml +++ b/.github/workflows/run-experiments-apache-beam.yml @@ -39,6 +39,11 @@ jobs: with: token: ${{ secrets.GITHUB_TOKEN }} - name: Remove Maven Settings + # Beam uses the [gradle-maven-settings-plugin](https://github.com/mark-vieira/gradle-maven-settings-plugin/) + # to read repo authentication from Maven settings and use it in their Gradle build. It seems that plugin does not + # [support encrypted credentials](https://github.com/mark-vieira/gradle-maven-settings-plugin/issues/15), + # but this is what GitHub Actions provides by default. Deleting `settings.xml` is what Beam do in their own CI + # builds on GitHub Actions: https://github.com/apache/beam/blob/ca0345b8acc7dd5ebc0506d48faa6474fe0b3ca0/.github/workflows/java_tests.yml#L89 run: rm $HOME/.m2/settings.xml - name: Ignore Test Failures run: |