<div id="readability-page-1" class="page"><div><h2 id="github-action을-통한-spring-boot-자동-deploy"><a href="#github-action%EC%9D%84-%ED%86%B5%ED%95%9C-spring-boot-%EC%9E%90%EB%8F%99-deploy" aria-label="github action을 통한 spring boot 자동 deploy permalink"></a>Github action을 통한 Spring boot 자동 deploy</h2>
<div data-language="yml"><pre><code># This workflow will build a package using Gradle and then publish it to GitHub packages when a release is created
# For more information see: https://github.com/actions/setup-java/blob/main/docs/advanced-usage.md#Publishing-using-gradle

name: Gradle Package

# 1)
on:
 release:
 types: [created]

# 2)
jobs:
 build:

 runs-on: ubuntu-latest
 permissions:
 contents: read
 packages: write

 steps:
 # 3)
 - uses: actions/checkout@v2
 - name: Set up JDK 11
 uses: actions/setup-java@v2
 with:
 java-version: '11'
 distribution: 'adopt'
 server-id: github # Value of the distributionManagement/repository/id field of the pom.xml
 settings-path: ${{ github.workspace }} # location for the settings.xml file

 - name: Build with Gradle
 run: gradle build

 # The USERNAME and TOKEN need to correspond to the credentials environment variables used in
 # the publishing section of your build.gradle
 - name: Publish to GitHub Packages
 run: gradle publish
 env:
 USERNAME: ${{ github.actor }}
 TOKEN: ${{ secrets.GITHUB_TOKEN }}</code></pre></div>
<h2 id="1-on"><a href="#1-on" aria-label="1 on permalink"></a>1) on</h2>
<h3 id="1-1-특정-브랜치에-push가-진행되면-실행"><a href="#1-1-%ED%8A%B9%EC%A0%95-%EB%B8%8C%EB%9E%9C%EC%B9%98%EC%97%90-push%EA%B0%80-%EC%A7%84%ED%96%89%EB%90%98%EB%A9%B4-%EC%8B%A4%ED%96%89" aria-label="1 1 특정 브랜치에 push가 진행되면 실행 permalink"></a>1-1) 특정 브랜치에 push가 진행되면 실행</h3>
<div data-language="yml"><pre><code>on:
 push:
 branches:
 - main
 - release/*</code></pre></div>
<h3 id="1-2-pr이-실행되면-실행"><a href="#1-2-pr%EC%9D%B4-%EC%8B%A4%ED%96%89%EB%90%98%EB%A9%B4-%EC%8B%A4%ED%96%89" aria-label="1 2 pr이 실행되면 실행 permalink"></a>1-2) PR이 실행되면 실행</h3>
<div data-language="yml"><pre><code>on:
 pull_request:
 branches:
 - main</code></pre></div>
<h3 id="1-3-특정-시점에-cron으로-실행"><a href="#1-3-%ED%8A%B9%EC%A0%95-%EC%8B%9C%EC%A0%90%EC%97%90-cron%EC%9C%BC%EB%A1%9C-%EC%8B%A4%ED%96%89" aria-label="1 3 특정 시점에 cron으로 실행 permalink"></a>1-3) 특정 시점에 cron으로 실행</h3>
<div data-language="yml"><pre><code>on:
 schedule:
 branches:
 - cron: "0 0 * * * *"</code></pre></div>
<h3 id="1-4-수동으로-실행"><a href="#1-4-%EC%88%98%EB%8F%99%EC%9C%BC%EB%A1%9C-%EC%8B%A4%ED%96%89" aria-label="1 4 수동으로 실행 permalink"></a>1-4) 수동으로 실행</h3>

<h2 id="2-jobs"><a href="#2-jobs" aria-label="2 jobs permalink"></a>2) jobs</h2>
job은 같은 runner(workflow)위에서 실행되는 일련의 과정들이다. 기본적으로 여러 job들이 있는 workflow는 병렬로 job을 실행한다. 하지만 필요하다면 job을 순차적으로 실행하도록 설정할 수 있는데, <code>빌드</code>와 <code>테스트</code>, 순차적인 job 두개로 구성된 workflow가 있다고 가정했을 때, 테스트 job은 빌드 job 상태에 의존한다. 만약에 빌드에 실패하면 테스트 역시 run 되지 않는 것이다. 
<h2 id="3-uses-actionscheckoutv2"><a href="#3-uses-actionscheckoutv2" aria-label="3 uses actionscheckoutv2 permalink"></a>3) uses: actions/checkout@v2</h2>
git checkout 실행
출처
<ul>
<li><a href="https://velog.io/@eomttt/Github-Actions%EB%A5%BC-%EC%9D%B4%EC%9A%A9%ED%95%9C-%ED%81%B4%EB%9D%BC%EC%9D%B4%EC%96%B8%ED%8A%B8-CICD-%EA%B5%AC%EC%B6%95-Github-Actions-%EC%82%AC%EC%9A%A9%ED%95%B4%EB%B3%B4%EA%B8%B0">https://velog.io/@eomttt/Github-Actions%EB%A5%BC-%EC%9D%B4%EC%9A%A9%ED%95%9C-%ED%81%B4%EB%9D%BC%EC%9D%B4%EC%96%B8%ED%8A%B8-CICD-%EA%B5%AC%EC%B6%95-Github-Actions-%EC%82%AC%EC%9A%A9%ED%95%B4%EB%B3%B4%EA%B8%B0</a></li>
<li><a href="https://blog.naver.com/jcyber/222357094864">https://blog.naver.com/jcyber/222357094864</a></li>
<li><a href="https://docs.github.com/en/actions/learn-github-actions/introduction-to-github-actions">https://docs.github.com/en/actions/learn-github-actions/introduction-to-github-actions</a></li>
</ul></div></div>

Seulog💘

이예슬

Github action을 통한 Spring boot 자동 deploy
# This workflow will build a package using Gradle and then publish it to GitHub packages when a release is created
# For more information see: https://github.com/actions/setup-java/blob/main/docs/advanced-usage.md#Publishing-using-gradle
name: Gradle Package
# 1)
on:
  release:
    types: [created]
# 2)
jobs:
  build:
    runs-on: ubuntu-latest
    permissions:
      contents: read
      packages: write
    steps:
    # 3)
    - uses: actions/checkout@v2
    - name: Set up JDK 11
      uses: actions/setup-java@v2
      with:
        java-version: '11'
        distribution: 'adopt'
        server-id: github # Value of the distributionManagement/repository/id field of the pom.xml
        settings-path: ${{ github.workspace }} # location for the settings.xml file
    - name: Build with Gradle
      run: gradle build
    # The USERNAME and TOKEN need to correspond to the credentials environment variables used in
    # the publishing section of your build.gradle
    - name: Publish to GitHub Packages
      run: gradle publish
      env:
        USERNAME: ${{ github.actor }}
        TOKEN: ${{ secrets.GITHUB_TOKEN }}
1) on
1-1) 특정 브랜치에 push가 진행되면 실행
on:
  push:
    branches:
    - main
    - release/*
1-2) PR이 실행되면 실행
on:
    pull_request:
     branches:
     - main
1-3) 특정 시점에 cron으로 실행
on:
  schedule:
    branches:
    - cron: "0 0 * * * *"
1-4) 수동으로 실행
on:
  workflow_dispatch:
2) jobs
job은 같은 runner(workflow)위에서 실행되는 일련의 과정들이다. 기본적으로 여러 job들이 있는 workflow는 병렬로 job을 실행한다. 하지만 필요하다면 job을 순차적으로 실행하도록 설정할 수 있는데, 빌드와 테스트, 순차적인 job 두개로 구성된 workflow가 있다고 가정했을 때, 테스트 job은 빌드 job 상태에 의존한다. 만약에 빌드에 실패하면 테스트 역시 run 되지 않는 것이다. 
3) uses: actions/checkout@v2
git checkout 실행
출처
https://velog.io/@eomttt/Github-Actions%EB%A5%BC-%EC%9D%B4%EC%9A%A9%ED%95%9C-%ED%81%B4%EB%9D%BC%EC%9D%B4%EC%96%B8%ED%8A%B8-CICD-%EA%B5%AC%EC%B6%95-Github-Actions-%EC%82%AC%EC%9A%A9%ED%95%B4%EB%B3%B4%EA%B8%B0
https://blog.naver.com/jcyber/222357094864
https://docs.github.com/en/actions/learn-github-actions/introduction-to-github-actions

Github action 정리

댓글