Skip to content

Parameterize Workflow Runners #42

Open

Description

@seantrons

One other thing I thought of is that ubuntu-slim imposes a hard 15-minute job limit and one CPU on every caller and so I'm wondering if it would be worth it to add a string runner input defaulting to the current default runners (ubuntu-latest/ubuntu-latest), and use runs-on: ${{ inputs.runner }} to change from the default. Just a thought.

Yeah... I noticed that in the docs and don't agree with the disparity (single cpu => 15 minutes, anything else => 6 hours), but rules are rules I suppose.

I'll make it parameterized as requested. Should I add any warnings? I've always been of the mindset that unit tests should only take a few minutes, while integration + e2e tests go for any sane number of hours.

Originally posted by @seantronsen in #38 (comment)

Activity

  1. self-assigned this
    on Oct 13, 2026
  2. added a commit that references this issue on Oct 19, 2026
    058941c
  3. added this to the v4.0.0 milestone on Oct 20, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions