Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

🌱 Add api_hub_tests_ref to CI on PRs #559

Merged
merged 2 commits into from
Nov 29, 2023

Conversation

aufi
Copy link
Member

@aufi aufi commented Nov 15, 2023

In order to run E2E API tests with tackle2-hub API tests on matching branches, adding name of PR branch as a variable passed to CI workflow.

Depends on konveyor/ci#23

Related to konveyor/ci#22 and konveyor/go-konveyor-tests#61

In order to run E2E API tests with tackle2-hub API tests on matching
branches, adding name of PR branch as a variable passed to CI workflow.

Depends on konveyor/ci#23

Related to konveyor/ci#22 and konveyor/go-konveyor-tests#61

Signed-off-by: Marek Aufart <maufart@redhat.com>
@aufi aufi changed the title Add api_hub_tests_ref to CI on PRs 🌱 Add api_hub_tests_ref to CI on PRs Nov 15, 2023
@@ -94,3 +94,4 @@ jobs:
uses: konveyor/ci/.github/workflows/global-ci.yml@main
with:
component_name: tackle2-hub
api_hub_tests_ref: ${{ github.head_ref }}
Copy link
Contributor

Choose a reason for hiding this comment

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

I think we might want github.ref_name here instead, I think head_ref will reference just the PR branch while ref_name will reference the merged PR

Copy link
Member Author

Choose a reason for hiding this comment

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

This workflow should affect only PRs. Once the change is merged the branch name (main and e.g. release-0.3) should be driven by already existing API_TESTS_REF.

Copy link
Contributor

Choose a reason for hiding this comment

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

I think the difference is head_ref targets /refs/pull/<PR #>/head whereas ref_name targets /refs/pull/<PR #>/merge. Generally we want to test with merge so that we get the results of the tests if that PR merged. Can help catch issues that are introduced on the main branch after a PR is introduced. Let me know if I'm missing something or talking past you

Copy link
Member Author

Choose a reason for hiding this comment

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

Ah, good point, I misuderstood it before, thanks! I will update.

Signed-off-by: Marek Aufart <maufart@redhat.com>
Copy link
Contributor

@fabianvf fabianvf left a comment

Choose a reason for hiding this comment

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

LGTM

@aufi aufi merged commit f32518a into konveyor:main Nov 29, 2023
10 of 11 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants