Current runner version: '2.331.0': Error: The template is not valid - when container.options is not set
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 6.3k
- Forks
- 1.4k
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 24
Description
Describe the bug
Jobs are run in a container and a matrix is used to set container options, so that some jobs have no container options. Such jobs without container options fail at the job setup with the error
Error: The template is not valid. .github/workflows/workflow.yml (Line: xxx, Col: yyy): Unexpected value ''
Previous runner version 2.330.0 worked without this issue.
Expected behavior
A job with empty container options run successfully.
Runner Version and Platform
2.331
OS of the machine running the runner? Linux
What's not working?
Error: The template is not valid. .github/workflows/workflow.yml (Line: xxx, Col: yyy): Unexpected value ''
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the failure with a matrix workflow where container.options is empty in some jobs, using the reported .github/workflows/workflow.yml validation error as the entry point. Compare runner versions 2.330.0 and 2.331.0 on Linux. Done means jobs without container options pass setup without the unexpected empty-value error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- ci-cd
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100