actions/actions-runner-controller
1
0
Fork 0
Code Issues Pull Requests Actions 4 Packages Projects Releases Wiki Activity
1,662 Commits 33 Branches 147 Tags
66172ab0bd5d7237766146ad7778088a71a969ba
Commit Graph
5 Commits
Author SHA1 Message Date
Thang LeGitHubYusuke Kuoka
 		e7ec736738 Use head_branch metric (#2549) 
Co-authored-by: Yusuke Kuoka <ykuoka@gmail.com>
 2023-05-28 16:36:55 +09:00
Yusuke KuokaandGitHub bdcde44642 chore: Bump go-github and minimum GHES version to 3.6 (#1747) 
Ref https://github.com/actions-runner-controller/actions-runner-controller/issues/1574
 2022-08-24 13:08:40 +09:00
Yusuke KuokaandGitHub ddd417f756 Bump go-github to v45 (#1573) 
* Bump go-github to v45

Ref #1402

* fixup! Bump go-github to v45
 2022-06-29 06:34:58 +09:00
Yusuke Kuoka a9aea0bd9c Fix issue that visible runner groups are printed as if empty in log
Lint and Test Charts / Lint Chart (push) Has been cancelled
Details
2022-02-19 14:43:41 +09:00
Felipe Galindo SanchezGitHubYusuke Kuoka
 		d0d316252e Option to consider runner group visibility on scale based on webhook (#1062) 
This will work on GHES but GitHub Enterprise Cloud due to excessive GitHub API calls required.
More work is needed, like adding a cache layer to the GitHub client, to make it usable on GitHub Enterprise Cloud.

Fixes additional cases from https://github.com/actions-runner-controller/actions-runner-controller/pull/1012

If GitHub auth is provided in the webhooks controller then runner groups with custom visibility are supported. Otherwise, all runner groups will be assumed to be visible to all repositories

`getScaleUpTargetWithFunction()` will check if there is an HRA available with the following flow:

1. Search for **repository** HRAs - if so it ends here
2. Get available HRAs in k8s
3. Compute visible runner groups
  a. If GitHub auth is provided - get all the runner groups that are visible to the repository of the incoming webhook using GitHub API calls.  
  b. If GitHub auth is not provided - assume all runner groups are visible to all repositories
4. Search for **default organization** runners (a.k.a runners from organization's visible default runner group) with matching labels
5. Search for **default enterprise** runners (a.k.a runners from enterprise's visible default runner group) with matching labels
6. Search for **custom organization runner groups** with matching labels
7. Search for **custom enterprise runner groups** with matching labels

Co-authored-by: Yusuke Kuoka <ykuoka@gmail.com>
 2022-02-16 19:08:56 +09:00