Github共享和自主跑步者
我最近出现了一个有趣的情况，但我找不到一些东西，所以也许知道有人可以分享此信息。
我们在GitHub组织中有一个GitHub存储库。它具有一组GHA作业（例如Release.YAML），这些作业应该在GitHub共享跑步者上运行：
runs-on: ubuntu-latest
这些作业被拾取了，直到我添加了一份作业，我想在一个自主跑步者上运行它：
runs-on: self-hosted
所以我注册了自主跑步者，后者的工作很好。 但是，当我回来经营第一阶段作业之一（即reparter.yaml）时，该作业并没有被Github共享的跑步者所吸引可用的自主跑步者。
有人看过吗？是标准行为还是我应该对GitHub提出问题？
PS：从存储库设置中解除自托管跑步者的问题解决了问题，但仍然，这是否意味着我们不能拥有一组作业，有些人使用自托管，有些人使用github shared跑步者？
I came up an interesting situation recently and I couldn't find something on that, so maybe someone who knows can share this info.
We have a github repository in a github organization. This has a set of GHA jobs (eg release.yaml) which are supposed to run on github shared runners:
runs-on: ubuntu-latest
The jobs were picked up fine, until I added a job that I wanted to run it on a self-hosted runner:
runs-on: self-hosted
So I registered the self-hosted runner, the latter job got picked up just fine.
But when I came back to run one of the 1st stage jobs (ie release.yaml), the job wasn't getting picked up by the github shared runner as it is supposed to by the code, but was getting queued and waiting for a self-hosted runner to be available.
Has anyone seen this before? Is it standard behaviour or I should commit an issue with github?
PS: Deregistering the self-hosted runner from repository settings resolved the issue, but still, does this mean we can't have a set of jobs that some use self-hosted and some use github-shared runners?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论