-
Notifications
You must be signed in to change notification settings - Fork 46
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
[BUG] github-workflows-require-timeout.json
: timeout-minutes
should allow expressions
#354
Comments
Yep; accepted! The schema was written with |
This is where I'm trying to stick it, by the way: https://github.com/aio-libs/yarl/blob/3a5e605/.github/workflows/reusable-build-wheel.yml#L38. |
github-workflows-require-timeout now supports expression eval blocks in the value for the timeout. Two test-cases ensure that such workflows will pass, based on the example provided in #354 resolves #354 There is also a small refinement to test outputs here, which was added while testing this addition.
I just got around to this today and handled it in v0.27.2, freshly released! |
Previously, the jsonschema for non-raw number values was incomplete but has been fixed in check-jsonschema v0.27.2. Refs: * python-jsonschema/check-jsonschema#354 * python-jsonschema/check-jsonschema#356
@sirosen yes, thank you! Just got to verifying and it does work for me: aio-libs/frozenlist@a1c0e49 / aio-libs/frozenlist@3367693. Though, there was one problem with my example above: the numbers should be unquoted. So it must be Anyway, the schema looks good to me now. |
Previously, the jsonschema for non-raw number values was incomplete but has been fixed in check-jsonschema v0.27.2. Refs: * python-jsonschema/check-jsonschema#354 * python-jsonschema/check-jsonschema#356
$sbj. I want to have
timeout-minutes: ${{ inputs.qemu && '60' || '20' }}
set for a job. Theinputs
is a context that exists in reusable workflows. Here's the table of context availability FTR: https://docs.github.com/en/actions/learn-github-actions/contexts.Here's how it fails for me:
Approximate reusable workflow look:
Haven't looked into how to fix this, but the upstream
github-workflow.json
doesn't error out, so this custom schema must be too strict...The text was updated successfully, but these errors were encountered: