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

AI Lab Recipe Catalog change test pipeline #2360

Merged

Conversation

ScrewTSW
Copy link
Member

@ScrewTSW ScrewTSW commented Jan 13, 2025

What does this PR do?

  • Adds windows tests to be executed on catalog recipe change

Screenshot / video of UI

N/A

What issues does this PR fix or reference?

#2134

How to test this PR?

  • create a branch with changes in packages/backend/src/assets/ai.json (e.g.: duplicate an entry)
  • can only be tested after merge, or triggered in a local fork, though, azure instance won't be created from those and tests will fail
  • pipeline Run recipe tests on catalog change should trigger

@ScrewTSW ScrewTSW requested review from benoitf, jeffmaury and a team as code owners January 13, 2025 12:13
@ScrewTSW ScrewTSW requested review from cdrage and gastoner January 13, 2025 12:13
.github/workflows/recipe-catalog-change.yaml Outdated Show resolved Hide resolved
.github/workflows/recipe-catalog-change.yaml Outdated Show resolved Hide resolved
.github/workflows/recipe-catalog-change.yaml Outdated Show resolved Hide resolved
.github/workflows/recipe-catalog-change.yaml Outdated Show resolved Hide resolved
Copy link
Contributor

@gastoner gastoner left a comment

Choose a reason for hiding this comment

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

LGTM on my test branch:

image

@ScrewTSW ScrewTSW force-pushed the 2134-run-recipe-tests-on-catalog-change branch 5 times, most recently from 164664d to 322d85a Compare January 21, 2025 12:04
@ScrewTSW ScrewTSW force-pushed the 2134-run-recipe-tests-on-catalog-change branch from 322d85a to ba4c97d Compare January 21, 2025 12:59
windows:
name: recipe-catalog-windows-${{ matrix.windows-version }}-${{ matrix.windows-featurepack }}
runs-on: ubuntu-latest
permissions:
Copy link
Contributor

Choose a reason for hiding this comment

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

remove permission, no need if annontate_only: true is set.

Copy link
Member Author

Choose a reason for hiding this comment

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

done.

uses: mikepenz/action-junit-report@v5
if: always() # always run even if the previous step fails
with:
fail_on_failure: true
Copy link
Contributor

Choose a reason for hiding this comment

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

Add annotate_only: true

Copy link
Member Author

Choose a reason for hiding this comment

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

done.

-start ${{ env.PODMAN_START }} \
-userNetworking ${{ env.PODMAN_NETWORKING }} \
-envVars ${{ env.ENV_VARS }} \
-runAsAdmin ${{ env.PODMAN_ADMIN }} \
Copy link
Contributor

Choose a reason for hiding this comment

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

env var is not set anywhere. I would not call it PODMAN, just RUN_AS_ADMIN. Remove the backslash.

Copy link
Member Author

Choose a reason for hiding this comment

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

shouldn't this be parsed by this though?

        DEFAULT_PODMAN_OPTIONS: 'INIT=1,START=1,ROOTFUL=1,NETWORKING=0,ADMIN=1'
...
        echo "${{ env.DEFAULT_PODMAN_OPTIONS }}" | awk -F ',' \
         '{for (i=1; i<=NF; i++) {split($i, kv, "="); print "PODMAN_"kv[1]"="kv[2]}}' >> $GITHUB_ENV

Copy link
Contributor

Choose a reason for hiding this comment

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

we should not hide it within podman setup parameters.

Copy link
Member Author

Choose a reason for hiding this comment

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

ACK

Copy link
Member Author

Choose a reason for hiding this comment

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

fixed

@ScrewTSW ScrewTSW force-pushed the 2134-run-recipe-tests-on-catalog-change branch 2 times, most recently from 3241de5 to d2d7417 Compare January 21, 2025 16:42
@ScrewTSW ScrewTSW force-pushed the 2134-run-recipe-tests-on-catalog-change branch from d2d7417 to 78fb086 Compare January 21, 2025 16:45
Copy link
Contributor

@odockal odockal left a comment

Choose a reason for hiding this comment

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

I am approving the PR.

Follow up: the workflow is called template, although it cannot be run or parametrized from any other trigger/call. So the next steps would be to make the workflow parametrized so we can reuse it.

@ScrewTSW ScrewTSW merged commit a33c8ea into containers:main Jan 22, 2025
7 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.

4 participants