Skip to content

Conversation

@HumairAK
Copy link
Collaborator

This change ensures that we are not hardcoding repo names, branches, and also ensure we pick source files from PRs in CI for integration tests.

@google-oss-prow
Copy link

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please ask for approval from humairak. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

if: ${{ steps.forward-mysql-port.outcome == 'success' }}
working-directory: ./backend/test/integration
run: go test -v ./... -args -runIntegrationTests=true -namespace=kubeflow
run: go test -v ./... -args -runIntegrationTests=true -namespace=kubeflow -repoName=${{ github.repository }} -branchName=${{ github.event.repository.default_branch }}
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we use github.ref_name instead so the release branch pushes are using the correct code? I think github.event.repository.default_branch always points to master.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants