CICD

• where to run:

  • github host enterprise (linux )
    • runner on docker image
  • onprem (linux, mac, windows )
    • runner

• when to run:

  • time (schedule)
  • PR
  • push
  • workflow dispatch

• what to run:

  • cicd steps

Workflows (.github/workflows/ci.yaml)

it works on yaml file as inputs

Actions

• workflow actions
  • all info
    • runner, steps, env, secrets
• composite actions:
  • inputs and steps
  • folder
    • basic-installations/actions.yaml
    • k8s-installations/actions.yaml
    • teams/actions.yaml

job: exute cmds which defined in job

• runs on
• steps

Events: fetch from github

on: push: branches: “main”

workflow_dispatch:

# This is a basic workflow to help you get started with Actions

name: CI

# Controls when the workflow will run
on:
  # Triggers the workflow on push or pull request events but only for the "main" branch
  push:
    branches: [ "main" ]
  pull_request:
    branches: [ "main" ]

  # Allows you to run this workflow manually from the Actions tab
  workflow_dispatch:

# A workflow run is made up of one or more jobs that can run sequentially or in parallel
jobs:
  # This workflow contains a single job called "build"
  build:
    # The type of runner that the job will run on
    runs-on: ubuntu-latest

    # Steps represent a sequence of tasks that will be executed as part of the job
    steps:
      # Checks-out your repository under $GITHUB_WORKSPACE, so your job can access it
      - uses: actions/checkout@v4

      # Runs a single command using the runners shell
      - name: Run a one-line script
        run: echo Hello, world!

      # Runs a set of commands using the runners shell
      - name: Run a multi-line script
        run: |
          echo Add other actions to build,
          echo test, and deploy your project.