Page History

...

Current Tasks

1. work on cli - plan of making our own, but can use gh cli as one of tools
2. Make our own cli - can use python (for ease of development, and speed is not important since its ran from a dev's machine as just another process)
Use GNU Coding Standards section 4.8 'standards for command line interfaces'refer to CLI Tool
3. blocked waiting for s3df/db update: Create a simple hello world project,
   1. DONE Add to Jira - we can use this as the test project, upload it to github, add it to the component db
   2. try this with the mongodb for us to view - https://www.mongodb.com/products/tools/compass
   3. create a basic build environment with a 'build.sh' script copied over. Push this image, and add its url to hello world component. This build environment can be used by both developers and the build system.
   4. DONE - use the basic.yml workflow from the BuildSystem/ (which will be the workflow all 400 something repos under ad will have) 
      1. See we can move the workflow to BuildSystem repo and all other repos can call it from there, like 'actions/checkout' can do like 'adbuild/build' this way any updates we roll out any repo can easily receive it
   5. the workflow should eventually do a GET request to the db, to get the build environment image,
   6. then spin up that new build environment image, 3 options to get the actual repo itself onto the new image
      1. (ideal) Runner does an actions/checkout onto a certain directory on s3df which will be accessible to all pods 
      2. Runner does an actions/checkout and passes in the actual repo through a 'kubectl cp',
      3. or probably pass in the url to the repo which it can then clone - issue with git authorization
   7. Then signal to the new environment container to do a 'make', then we have 3 options
      1. Have the environment container copy over a 'build.sh' script which does not get invoked when the container is spun up, but when it is explicitly called with 'kubectl exec'
      2. when you do 'kubectl exec' it can wait until the make is finished, then report back to actions that the build finished
      3. it can signal the make, but report back to actions that the build continued at a certain container.
   8. CAVEATS: we can assume that if there are no additional instructions on the component entry in the db, then we just do a vanilla make. (Which is what most apps here do to build, at least for the iocs its true)
   9. Then we also want the simple project packed up as a package (src code and executable).
4. Figure out the authentication automation for the runners. (at the moment i get the blob of config from https://k8s.slac.stanford.edu/ad-build-dev)
5. Eventually we will need the runner have access to s3df, so we can build on /scratch. Then check kaniko?
6. Try to get a dockerfile for buildroot going, most of the building will be in the dockerfile (copying over files, then running make), then the gh workflow will just call docker build and start the process, and can push the image anywhere (Local registry, docker registry, github registry)
7. Get the build system container running on the kluster Deploying Self-Hosted GitHub Actions Runners with Docker | TestDriven.io (Altered to fit our situation) 
   1. Lets do it vanilla first (running build system container) 
      1. Create the image using base image: Package actions-runner (github.com)
         1. push the docker image to a registry so anyone can pull it
            1. From where the dockerfile is 
            2. 'docker build --tag pnispero/gh-runner-image:latest .'
            3. This step may change (make a docker account, then create a access token, which will allow you to login on your shell)
            4. 'docker push pnispero/gh-runner-image:latest'
            5. Output: pnispero/gh-runner-image - Docker Image | Docker Hub

         2. Dockerfile (Here temporarily, these are the only 2 files you need to get this to work)

            Code Block

            # base FROM ubuntu:22.04 # set the github runner version ARG RUNNER_VERSION="2.316.0" # update the base packages and add a non-sudo user RUN apt-get update -y && apt-get upgrade -y && useradd -m docker # install python and the packages the your code depends on along with jq so we can parse JSON # add additional packages as necessary RUN DEBIAN_FRONTEND=noninteractive apt-get install -y --no-install-recommends \ curl jq build-essential libssl-dev libffi-dev python3 python3-venv python3-dev python3-pip # cd into the user directory, download and unzip the github actions runner RUN cd /home/docker && mkdir actions-runner && cd actions-runner \ && curl -O -L https://github.com/actions/runner/releases/download/v${RUNNER_VERSION}/actions-runner-linux-x64-${RUNNER_VERSION}.tar.gz \ && tar xzf ./actions-runner-linux-x64-${RUNNER_VERSION}.tar.gz # install some additional dependencies RUN chown -R docker ~docker && /home/docker/actions-runner/bin/installdependencies.sh # copy over the start.sh script COPY start.sh start.sh # make the script executable RUN chmod +x start.sh # since the config and run script for actions are not allowed to be run by root, # set the user to "docker" so all subsequent commands are run as the docker user USER docker # set the entrypoint to the start.sh script ENTRYPOINT ["./start.sh"]

            start.sh

            Code Block

            #!/bin/bash ORGANIZATION=$ORGANIZATION ACCESS_TOKEN=$ACCESS_TOKEN # Generate organization registration token REG_TOKEN=$(curl -L \ -X POST \ -H "Accept: application/vnd.github+json" \ -H "Authorization: Bearer ${ACCESS_TOKEN}" \ -H "X-GitHub-Api-Version: 2022-11-28" \ https://api.github.com/orgs/${ORGANIZATION}/actions/runners/registration-token | jq .token --raw-output) cd /home/docker/actions-runner ./config.sh --url https://github.com/${ORGANIZATION} --token ${REG_TOKEN} cleanup() { echo "Removing runner..." ./config.sh remove --unattended --token ${REG_TOKEN} } trap 'cleanup; exit 130' INT trap 'cleanup; exit 143' TERM ./run.sh & wait $!

      2. do 'docker image ls' to ensure its there
      3. Then you must be an organization administrator, and make a personal access token with the "admin:org" and "repo" scope to create a registration token for an organization (REST API endpoints for self-hosted runners - GitHub Docs)
      4. Copy the token, and use it in the next step

      5. Run the docker image

         Code Block
         docker run \ --env ORGANIZATION=<ORG> \ --env ACCESS_TOKEN=<PERSONAL-TOKEN> \ --name runner1 \ runner-image

         Replace <ORG> with the organization name
         Replace <PERSONAL-TOKEN> with the token you created above

      6. And now your runner should be registered and running
      7. When done testing make sure to 'ctrl+c' and  'stop' and 'remove' the container
   2. Start the image using kubectl for our ad-build kubernetes cluster you created above

      1. Code Block
         # Start the image with environment variables kubectl run gh-runner1 --image=pnispero/gh-runner-image --env="ORGANIZATION=<ORG>" --env="ACCESS_TOKEN=<PERSONAL-TOKEN>"

         Replace <ORG> with the organization name
         Replace <PERSONAL-TOKEN> with the token you created above

   3. REMEMBER IF STOPPING THE CONTAINER, give it a grace period so it has some time to remove itself and from the organization

      Code Block
      kubectl delete --grace-period=15 pod gh-runner1

      Sample request - but refer to the api docs (https://accel-webapp-dev.slac.stanford.edu/api-doc/?urls.primaryName=Core%20Build%20System)

      Code Block
      # gets component list curl -X 'GET' \ 'https://accel-webapp-dev.slac.stanford.edu/api/cbs/v1/component' \ -H 'accept: application/json'

8. Then we can use that for building buildroot. One of the workflows will be it checking out on /scratch/ in s3df, then build, and output results there.

...