This means you can run workflow jobs in containers on OpenShift, which has many advantages, as we'll see in this section.īy default, GitHub provides infrastructure that users can run their Actions workflow jobs on. We've developed a solution for hosting GitHub Actions runners on OpenShift. Introducing self-hosted runners for Red Hat OpenShift Since GitHub runners connect outwardly to GitHub, you can run them locally or behind a firewall without worrying about networking. There is also Red Hat CodeReady Containers for a local option that runs on your workstation. If you don’t have access to an OpenShift cluster, we highly recommend checking out the free Developer Sandbox for Red Hat OpenShift. In addition to our direct work, we've implemented a way to self-host GitHub Actions runners on a Red Hat OpenShift cluster so you can run workflows on your own cluster instead of GitHub's. Since the initial announcement, we’ve been hard at work responding to community feedback to improve our existing actions as well as adding a few new ones. To date, Red Hat has released a series of GitHub Actions and an OpenShift starter workflow to ease integrating Red Hat OpenShift with GitHub’s popular CI/CD platform. If you haven’t read the December press release or the original blog post, be sure to check those out for the full context. Note: This article is an update on Red Hat’s work in the GitHub Actions ecosystem.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |