Skip to content

🤖 triggering CI on branch 'release-next' after synching from upstream/main #1101

🤖 triggering CI on branch 'release-next' after synching from upstream/main

🤖 triggering CI on branch 'release-next' after synching from upstream/main #1101

Workflow file for this run

name: Func E2E Test
on: [pull_request]
jobs:
test:
name: E2E Test
strategy:
matrix:
os: ["ubuntu-latest"]
runs-on: ${{ matrix.os }}
steps:
- name: Set Environment Variables
run: |
echo "KUBECONFIG=${{ github.workspace }}/hack/bin/kubeconfig.yaml" >> "$GITHUB_ENV"
echo "PATH=${{ github.workspace }}/hack/bin:$PATH" >> "$GITHUB_ENV"
- uses: actions/checkout@v4
- uses: ./.github/composite/go-setup
- name: Install Binaries
run: ./hack/install-binaries.sh
- name: Allocate Cluster
run: ./hack/allocate.sh
- name: Local Registry
run: ./hack/registry.sh
- name: E2E Test
run: make test-e2e
- uses: codecov/codecov-action@v4
with:
files: ./coverage.txt
flags: e2e-test