We are also exploring the possibility of having our own hosted runners. Regarding the management - I've learned recently that as of April you can manage secrets in the repository vi API - even if they are not present in the UI, without Infra doing it for you, so maybe self-hosted runners can also be configured this way?
BTW, In case you would like to - https://github.com/anomaly/github-secrets-cli - this is a nice CLI that allows you to easily manage secrets in your GitHub repository. J, On Tue, Oct 13, 2020 at 2:41 PM Vladimir Sitnikov < sitnikov.vladi...@gmail.com> wrote: > >We have - apparently 180 concurrency limit for all Apache projects. > > Is there a way to get per project / per job breakdown? > > >including a custom cancel-workflow-run Action I developed: > >https://github.com/potiuk/cancel-workflow-runs > > That sounds amazing. I often cancel runs manually, however, making that > automatic would > be great. > > >Guaranteed number of runners per project? > > I'm afraid that works only the other way around: "implement a per TLP > limit". > However, I don't think GitHub knows ASF TLPs :-/ > > Vladimir > -- Jarek Potiuk Polidea <https://www.polidea.com/> | Principal Software Engineer M: +48 660 796 129 <+48660796129> [image: Polidea] <https://www.polidea.com/>
