ci: add timeout-minutes to all jobs in functions.yaml

[Ankitsinghsisodya]

Summary

• Adds timeout-minutes to all 11 jobs in .github/workflows/functions.yaml
• Without explicit timeouts, GitHub Actions defaults to 6 hours per job; a hung cluster or stuck step would burn runner minutes until the default limit

Timeouts set:

Job	Timeout
precheck	15m
test-unit	30m
test-templates	60m
test-integration	120m
test-e2e	120m
test-e2e-podman	120m
test-e2e-runtimes	90m
test-e2e-config-ci	120m
build	30m
publish-utils-image	30m
publish-image	30m

These are conservative upper bounds — happy to adjust based on observed p99 runtimes.

Test plan

• Confirm no jobs time out prematurely on a normal PR run

Fixes #3530

[knative-prow]

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

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

Details

Needs approval from an approver in each of these files:

• OWNERS

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

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: Ankitsinghsisodya / name: Ankit sisodya (80e7560)

[knative-prow]

Hi @Ankitsinghsisodya. Thanks for your PR.

I'm waiting for a knative member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[Copilot]

Pull request overview

Adds explicit GitHub Actions job timeouts to .github/workflows/functions.yaml to prevent hung/stuck CI jobs from consuming runner minutes up to the default 6-hour limit.

Changes:

• Set timeout-minutes for all jobs in functions.yaml (precheck, tests, build, publish).
• Establish conservative upper bounds per job category (unit/templates vs. integration/e2e vs. build/publish).

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

test-e2e-podman defines a strategy.matrix.os, but runs-on is hardcoded to ubuntu-latest, so both matrix entries run on the same runner label. This likely defeats the intent of testing on ARM (ubuntu-24.04-arm) and also duplicates CI work. Consider changing runs-on to use matrix.os (or removing the matrix if only one runner is intended).

Suggested change

	runs-on: ubuntu-latest
	runs-on: ${{ matrix.os }}

[Ankitsinghsisodya]

Good catch — this is a pre-existing issue in the workflow, not introduced by this PR. The test-e2e-podman job hardcodes runs-on: ubuntu-latest while defining a matrix with both ubuntu-latest and ubuntu-24.04-arm, so both matrix entries run on the same x86_64 runner. This should be fixed separately. I'll keep this PR scoped to adding timeout-minutes only.