This website uses cookies to ensure you get the best experience.
Learn more.
A company autoscaling platform should create a clean self-hosted runner for one job and dispose of it afterward. Which runner registration mode best matches that lifecycle?
Published
- Register one long-lived runner for all teams and delete only its workflow logs.
- Register an ephemeral runner and arrange its cleanup and external log collection.
- Use a persistent runner and assume GitHub reimages its operating system after each job.
- Make every runner repository administrator so it can reset itself between jobs.
Comments — 0
Sign in to comment