Feat: update dependecies for latest release #97
Workflow file for this run
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| # This workflow runs integration tests installing runtime and shared from PyPI | |
| # The purpose of this workflow is to see if current SDK is compatible with the latest | |
| # released shared and runtime. If it is not, we should release new major version | |
| # of Shared and/or Runtime and bump minimal requirement on SDK | |
| # Also Note: Due to the possibility of 1 commit being done across all 3 packages | |
| # making it incompatible, this check is NOT mandatory on github CI so changes can be | |
| # merged, and then shared/runtime packages can be released. | |
| # Those integration tests are used to test compatibility between our 3 packages. | |
| # In contrast to unit-tests, this workflow installs all 3 packages | |
| # We need a workflow name to be able to schedule it from Github UI | |
| name: Integration Tests PyPI | |
| on: | |
| # Triggers the workflow on push to main | |
| push: | |
| branches: | |
| - main | |
| # Triggers the workflow on any PR | |
| pull_request: | |
| # Allows you to run this workflow manually from the Actions tab | |
| workflow_dispatch: | |
| concurrency: | |
| group: ${{ github.workflow }}-${{ github.ref }} | |
| cancel-in-progress: true | |
| jobs: | |
| # The job ID has to match repo settings for PR required checks | |
| PyPiTestIntegration: | |
| runs-on: ubuntu-latest | |
| defaults: | |
| run: | |
| working-directory: ${{ github.workspace }}/projects/orquestra-sdk | |
| timeout-minutes: 25 | |
| steps: | |
| - uses: actions/checkout@v4 | |
| - uses: actions/setup-python@v5 | |
| with: | |
| python-version: 3.11 | |
| architecture: x64 | |
| cache: "pip" | |
| # Installation method (venv/system/etc) affects Ray behavior. We're | |
| # installing deps to a venv to align with the most common use case. | |
| # Hence, we'll need to ensure the venv is always activated. More info: | |
| # https://stackoverflow.com/questions/74668349/how-to-activate-a-virtualenv-in-a-github-action | |
| - name: Install deps | |
| shell: bash | |
| run: | | |
| python3 -m venv ./venv | |
| source ./venv/bin/activate | |
| make github-actions-integration-pypi | |
| - name: Run performance test | |
| shell: bash | |
| run: | | |
| source ./venv/bin/activate | |
| make integration |