GitHub Actions - Self-hosted runners - Installation & Calling 

Thank you!

Yep I messed up this audio and a couple of others, sorry about that

😂

@@MickeyGousset kinda funny, but your video was great, thanks for explaination

I've tried to find instructions on how to run and self-hosted runners on GitHub, that covers what's here. I've not been able to. For example, it wasn't until I watched this video that I learned that self-hosted runners can work on repositories, organizations, and enterprises. I had thought it only worked against a repo. Can you please supply a link to that documentation on GitHub?

Hey @rodfalanga3770, that is my bad for not mentioning that in my video. The official documentation does have that listed: docs.github.com/en/actions/hosting-your-own-runners/managing-self-hosted-runners/adding-self-hosted-runners#adding-a-self-hosted-runner-to-a-repository

You need port 443 opened as the agent does long polling to GitHub. There are also some urls that the agent needs to be able to hit. Those are in the docs somewhere. But 443 and maybe 80 are all you need

@@MickeyGousset thank you

I know you asked this forever ago, but our team uses AWS codebuild for this and a shared GH repo. It doesn't offer the flexibility of accessing a common VM, but it meets security requirements.

You can see it in the Web Browser by going to settings | Actions | Runners and looking at the runner information. You can also pull it using the APIs

use secrets

Ha! Yes, I have a couple of videos that I really screwed the audio up on. Sorry about that. I’ve gotten better in my newer videos.

Heh t

1. You need to install that runner on a machine that is always going to be one and available 2. All three machines will have a label, say "self-hosted". When you build the workflow file, you use that label in the runs-on command. Then Actions will find a free machine with that label and use it.

@@MickeyGousset Thanks for the reply brother. I have given runs-on: self-hosted in ci.yml file and have 3 selfhosted runners. Sometimes it is picking the one which is active and sometimes it is picking the one which is offline and waiting in the queue. Not sure how to overcome that

Are you trying to create your own ephemeral self-hosted runner solution? The GitHub official solution for that is github.com/actions/actions-runner-controller. However, if you are trying to create your own, then you need to make an API call to get a short lived registration token: docs.github.com/en/rest/actions/self-hosted-runners?apiVersion=2022-11-28#create-a-registration-token-for-a-repository You can always just have a VM that is always available that you are running say in AWS or Azure. In that case, all you do is install the runner software. The token doesn't expire on you, meaning that the runner will keep working. I might need more details on what you are trying to do. If you want to email me at mickeygousset@github.com I'll see if I can answer them.

To be able to run multiple jobs you will need to install multiple agents. You can do that on the VM by installing them to different folders. But make sure the vm has enough resources

If you are working under your company’s enterprise account, then they may not have turned on actions for you.

I’m not sure off the top of my head. Do you have a repo you could add me to (mickeygousset) where I could take a look, or a public repo that is forkable?

@@MickeyGousset test: # needs: start-runner # needs: # - build runs-on: [self-hosted, Linux, X64] continue-on-error: true defaults: run: working-directory: . steps: - name: Checkout uses: actions/checkout@v3 with: fetch-depth: 0 - name: Install python dependencies shell: bash run: | source /home/githubuser/actions-runner/_work/bin/activate pip3 install --upgrade pip pip3 install -r requirements.txt pip3 install -r requirements.dev.txt - name: Set Environment Variable run: | echo "UNIT_TESTING_DB=${{ secrets.UNIT_TESTING_DB }}" >> $GITHUB_ENV - name: Run pytest & coverage continue-on-error: false run: | echo "export UNIT_TESTING_DB=${{ secrets.UNIT_TESTING_DB }}" >> ~/.bashrc source ~/.bashrc pip3 install pytest-cov pytest tests --cov=app --cov=services --cov-report xml

Error Log [2023-08-04 01:56:08Z WARN JobExtension] Ignore exception during read process environment variables: Access to the path '/proc/15980/environ' is denied. [2023-08-04 01:56:08Z INFO JobExtension] Inspecting process environment variables. PID: 16193 (pytest) pyest call which tries db connection but before that it fetched config string from os.environ which fails because this user do not have permission to /proc/id/environ but why ec2 or github is creating proc folder in root and not in user level folder

UNIT_TESTING_DB: str = os.getenv( "UNIT_TESTING_DB", "postgresql+psycopg2://user:pass@localhost:5432/my_db", ) Both Worker and Runner is stuck in infinite loop at this point

Two things to check: Make sure at the org level you have set it to allow your repo access. You should see the runner listed in your repo under settings | Actions at the repository level if it has access Also make sure your run-as statement matches a label on your runner

@@MickeyGousset I set allow my repo access, check all permission. But still can't use Before i add self-host under organization, it works and move self-host to enterprises and no longer works

@@PatcharaMeesawad interesting that it works at the org level but not the enterprise. I’ll have to think on that

@@MickeyGousset thank you mickey

Hi Mickey, I can setup multiple self-hosted runners on a single host ?

No self hosted runners use https to connect to GitHub

Has your repository been granted access to the runners?

Yep I screwed this audio up. I've fixed in my more current video. Thank you for letting me know!

First check and make sure the agent in the runner is actually up and running. If it is then try restarting it.

Self hosted runners do not consume minutes. You can have as many self hosted runners as you want.

@@MickeyGousset GitHub secret keys can be the same? or I need additional configure?

@@Devlogowy GitHub secrets work the same whether you use hosted or self hoted runners

@@MickeyGousset Thanks for answers :) Time to code

Actually when I run task during Xcode process terminal asks me about Mac password. Can I configure something like sudo perm access without type password every run?

Ha! I’m about to create all brand new self hosted runner content. You will be happy to know I’ve fixed the audio issues 😎

@@MickeyGousset Looking forward to it!

Yeah I messed that up. Sorry about that.

@@MickeyGousset no worries, thanks for the great walkthrough in this video 🙌🏽

>>>>>>>>>>>>>>>>>>>>>>>>>>>>