potiuk commented on a change in pull request #12541: URL: https://github.com/apache/beam/pull/12541#discussion_r471542050
########## File path: .github/workflows/java_tests.yml ########## @@ -0,0 +1,160 @@ +# Licensed to the Apache Software Foundation (ASF) under one +# or more contributor license agreements. See the NOTICE file +# distributed with this work for additional information +# regarding copyright ownership. The ASF licenses this file +# to you under the Apache License, Version 2.0 (the +# "License"); you may not use this file except in compliance +# with the License. You may obtain a copy of the License at +# +# http://www.apache.org/licenses/LICENSE-2.0 +# +# Unless required by applicable law or agreed to in writing, +# software distributed under the License is distributed on an +# "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY +# KIND, either express or implied. See the License for the +# specific language governing permissions and limitations +# under the License. + +# To learn more about GitHub Actions in Apache Beam check the CI.md + +name: Java Tests + +on: + workflow_dispatch: + inputs: + runDataflow: + description: 'Type "true" if you want to run Dataflow tests (GCP variables must be configured, check CI.md)' + default: false + schedule: + - cron: '10 2 * * *' + push: + branches: ['master', 'release-*'] + tags: 'v*' + pull_request: + branches: ['master', 'release-*'] + tags: 'v*' + paths: ['sdks/java/**', 'model/**', 'runners/**', 'examples/java/**', 'examples/kotlin/**', 'release/**'] + + +jobs: + + check_gcp_variables: + timeout-minutes: 5 + name: "Check GCP variables set" + runs-on: ubuntu-latest + outputs: + gcp-variables-set: ${{ steps.check_gcp_variables.outputs.gcp-variables-set }} + steps: + - uses: actions/checkout@v2 + - name: "Check are GCP variables set" + run: "./scripts/ci/ci_check_are_gcp_variables_set.sh" + id: check_gcp_variables + env: + GCP_PROJECT_ID: ${{ secrets.GCP_PROJECT_ID }} + GCP_SA_EMAIL: ${{ secrets.GCP_SA_EMAIL }} + GCP_SA_KEY: ${{ secrets.GCP_SA_KEY }} + GCP_TESTING_BUCKET: ${{ secrets.GCP_TESTING_BUCKET }} + + java_unit_tests: + name: 'Java Unit Tests' + runs-on: ${{ matrix.os }} + strategy: + fail-fast: false + matrix: + os: [ubuntu-latest, macos-latest, windows-latest] + steps: + - name: Checkout code + uses: actions/checkout@v2 + # :sdks:java:core:test + - name: Run :sdks:java:core:test + run: ./gradlew :sdks:java:core:test + - name: Upload test logs for :sdks:java:core:test + uses: actions/upload-artifact@v2 + if: always() + with: + name: java_unit_tests-sdks-java-core-test-${{ matrix.os }} Review comment: Each run has its own set of artifacts. GithubActions for artifact upload/dowload work for the "current run" only. You can download artifacts for other runs via APIS, but I believe you can't upload them from a different run than current. It even works in the way that you actually cannot see the artifacts via the API before the run is finished unless you are with the current run. This allows to share artifacts between different jobs in the same run, but you cannot use the artifacts between the runs. That effectively makes the artifacts immutable after the run completes (been there done that) ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
