GitHub Community
How do we deploy GitHub Action artifacts to on-prem servers? #55778
-
Select Topic AreaQuestion BodyWe're migrating all our source code out of an old TFS instance into a new GitHub Enterprise Organization. I've been learning how to do GH Actions to build artifacts. But soon we'll have to take the created artifacts and deploy them to servers on-prem. I don't even know where to begin learning how to do that. Every tutorial I've seen deploys to Azure, or AWS, etc. This isn't going to a cloud environment. I'm sure there must be some way, or maybe ways, of doing this. I'm asking that I be directed to where I can learn how to do this, please. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 3 replies
-
|
You'll probably want to use an automation tool like Ansible (there are alternatives, Ansible is what I'm familiar with) and define in there how to deploy your software. Then call that when you need to deploy. One important thing to consider: Are the servers you're deploying from reachable from the Actions runners you use? If not you can't deploy directly from Actions, you'd have to create an internal tool that retrieves the right artifacts and deploys them. |
Beta Was this translation helpful? Give feedback.
-
|
Thank you for your reply. The servers I need to deploy to are not reachable from GitHub Actions runners. And this is the crux of the matter. I tried doing this with an Azure DevOps Services self-hosted agent. Does GitHub have anything similar? If not, then how do I go about an internal tool to retrieve the artifacts and deploy them? |
Beta Was this translation helpful? Give feedback.
-
|
Using self-hosted runners is an option, so you could run one inside the right network and orchestrate the deployment from there. What I'd strongly recommend against is running the self-hosted runner on the machine to deploy to, use a proper automation tool to do the actual deployment remotely from the right network instead.
Use the API to find the right artifacts (or release assets, depending on how your builds provide them), and download them. Then automate the deployment internally from there. |
Beta Was this translation helpful? Give feedback.
-
|
Good advice, @airtower-luna. I believe I've found the correct documentation for this. At the moment I'm trying to get proof of concept going, to prove this is the right way to go. |
Beta Was this translation helpful? Give feedback.
-
|
If this is not already too late, TFS now Azure DevOps Server (still on-prem) supports all things Git. Why move to GitHub? |
Beta Was this translation helpful? Give feedback.
Using self-hosted runners is an option, so you could run one inside the right network and orchestrate the deployment from there.
What I'd strongly recommend against is running the self-hosted runner on the machine to deploy to, use a proper automation tool to do the actual deployment remotely from the right network instead.
Use the API to find the right artifacts (or release assets, depending on how your builds provide them), and download them. Then automate the deployment internally from there.