You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

We can implement CI workflow using GitHub's runner and SSH into our server to deploy.  However, because of our extra-tier IP restricted firewall.  We cannot use GitHub runner as it have the same IP address ranges as Azure Data centers.  Furthermore,  SSH is not possible unless we request Media3 to turn off DUO authentication for the server web user account.  I created a workflow using GitHub Action with our own self-hosted runner (which is installed under my superuser, the web user does not have enough privilege to install and run the runner ) and execute sudo command as the web user account.

  1. Adding a self-hosted runner to a repository or an organization


    I added our dev server to the organization as many repositories uses the dev server.  For prod server that only related to one repo (such as SPI), it's better to install to a repository.

You can add self-hosted runners at the organization level, where they can be used to process jobs for multiple repositories in an organization. To add a self-hosted runner to an organization, you must be an organization owner.

  1. On GitHub, navigate to the main page of the organization.

  2. Under your organization name, click  Settings.

    Organization settings button

     

  3. In the left sidebar, click Actions.

    Actions setting

     

  4. Under "Self-hosted runners," click Add new, then click New runner.

  5. Select the operating system and architecture of your self-hosted runner machine.

    Select self-hosted runner operating system

     

  6. You will see instructions showing you how to download the runner application and install it on your self-hosted runner machine.

    Open a shell on your self-hosted runner machine and run each shell command in the order shown.

    Note: On Windows, if you want to install the self-hosted runner application as a service, you must open a shell with administrator privileges. We also recommend that you use C:\actions-runner as the directory for the self-hosted runner application so that Windows system accounts can access the runner directory.

    The instructions walk you through completing these tasks:

    • Downloading and extracting the self-hosted runner application.
    • Running the config script to configure the self-hosted runner application and register it with GitHub Actions. The config script requires the destination URL and an automatically-generated time-limited token to authenticate the request.
    • Running the self-hosted runner application to connect the machine to GitHub Actions.

Checking that your self-hosted runner was successfully added

After completing the steps to add a self-hosted runner, the runner and its status are now listed under "Self-hosted runners".

The self-hosted runner application must be active for the runner to accept jobs. When the runner application is connected to GitHub and ready to receive jobs, you will see the following message on machine's terminal.

√ Connected to GitHub

2019-10-24 05:45:56Z: Listening for Jobs

For more information, see "Monitoring and troubleshooting self-hosted runners."

Adding a self-hosted runner to a repository

Adding a self-hosted runner to an organization

 

Adding a self-hosted runner to a repository or an organization

 

 

 

 

 

  • No labels