Support running arbitrary version of Runner code
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 enhancement
For debugging purposes, it should be possible to freeze on a specific release of the Runner code when executing it locally. Right now, if you manually change the symlinks to point to an existing older release, the agent will helpfully download and upgrade to the most recent release for you.
A recent behavior change with the Runner caused Python pipenv to break and I was not able to roll back to the previous release to confirm it was a change in Runner and not in something else (e.g. the underlying Python docker image).
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
The issue concerns local Runner execution, release symlinks, and the agent's automatic upgrade behavior. Start by tracing the local startup path and the logic that selects or downloads Runner releases. Done means a locally executed Runner can remain on a specific existing release for debugging instead of upgrading automatically.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- ci-cd, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100