Skip to content

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

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

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

name: Func E2E OnCluster Test
on: [pull_request]
jobs:
test:
name: On Cluster Test
strategy:
matrix:
go: [1.20.2]
os: ["ubuntu-latest"]
runs-on: ${{ matrix.os }}
steps:
- uses: actions/checkout@v3
- uses: actions/setup-go@v3
with:
go-version: ${{ matrix.go }}
- uses: imjasonh/[email protected]
- name: Install Binaries
run: ./hack/binaries.sh
- name: Setup testing func image
run: ./hack/create-testing-func-image.sh
- name: Allocate Cluster
run: ./hack/allocate.sh
- name: Install RH pull secrets for KinD cluster
env:
RH_REG_USR: ${{ secrets.RH_REG_USR }}
RH_REG_PWD: ${{ secrets.RH_REG_PWD }}
run: ./hack/install-pull-secrets.sh
- name: Deploy Tekton
run: ./hack/tekton.sh
- name: Deploy Test Git Server
run: ./test/gitserver.sh
- name: E2E On Cluster Test
env:
E2E_RUNTIMES: ""
FUNC_REPO_REF: ${{ github.event.pull_request.head.repo.full_name }}
FUNC_REPO_BRANCH_REF: ${{ github.head_ref }}
run: make test-e2e-on-cluster
- uses: codecov/codecov-action@v3
with:
files: ./coverage.txt
flags: e2e-test-oncluster