Is the pricing for GitHub larger runners reflected in billable time stats? #121200
Replies: 2 comments
-
🕒 Discussion Activity Reminder 🕒 This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions: 1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as 2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own. 3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution. Note: This dormant notification will only apply to Discussions with the Thank you for helping bring this Discussion to a resolution! 💬 |
Beta Was this translation helpful? Give feedback.
-
The issue is still relevant. Please have a look, thanks! |
Beta Was this translation helpful? Give feedback.
-
Select Topic Area
Question
Body
(I asked the same question on stackoverflow a while ago and did not receive any answers.)
GitHub now features larger runners for GitHub actions, which provide more performance at higher costs per minute. For example, if a job runs on ubuntu-latest-4-cores instead of the standard runner ubuntu-latest, it has 4 vCPUs instead of 2 vCPUs, but also the price per minute doubles. My question is now regarding the billable time, which is displayed when I open a run of a github action: let us assume that my github action contains two jobs; one job in the action runs on ubuntu-latest for one minute, and another job runs on ubuntu-latest-4-cores for one minute, will the billable time be displayed as 3 minutes, taking the doubled price into account? Or will it be simply shown as 2 minutes (in which case the billable time is not proportional to the actual cost)?
Beta Was this translation helpful? Give feedback.
All reactions