Skip to main content

์ด ๋ฒ„์ „์˜ GitHub Enterprise Server๋Š” ๋‹ค์Œ ๋‚ ์งœ์— ์ค‘๋‹จ๋ฉ๋‹ˆ๋‹ค. 2024-09-24. ์ค‘์š”ํ•œ ๋ณด์•ˆ ๋ฌธ์ œ์— ๋Œ€ํ•ด์„œ๋„ ํŒจ์น˜ ๋ฆด๋ฆฌ์Šค๊ฐ€ ์ด๋ฃจ์–ด์ง€์ง€ ์•Š์Šต๋‹ˆ๋‹ค. ๋” ๋›ฐ์–ด๋‚œ ์„ฑ๋Šฅ, ํ–ฅ์ƒ๋œ ๋ณด์•ˆ, ์ƒˆ๋กœ์šด ๊ธฐ๋Šฅ์„ ์œ„ํ•ด ์ตœ์‹  ๋ฒ„์ „์˜ GitHub Enterprise Server๋กœ ์—…๊ทธ๋ ˆ์ด๋“œํ•ฉ๋‹ˆ๋‹ค. ์—…๊ทธ๋ ˆ์ด๋“œ์— ๋Œ€ํ•œ ๋„์›€๋ง์€ GitHub Enterprise ์ง€์›์— ๋ฌธ์˜ํ•˜์„ธ์š”.

About continuous deployment with GitHub Actions

You can create custom continuous deployment (CD) workflows directly in your GitHub repository with GitHub Actions.

์ฐธ๊ณ : GitHub ํ˜ธ์ŠคํŠธ ์‹คํ–‰๊ธฐ๋Š” ํ˜„์žฌ GitHub Enterprise Server์—์„œ ์ง€์›๋˜์ง€ ์•Š์Šต๋‹ˆ๋‹ค. GitHub public roadmap์— ์˜ˆ์ •๋œ ํ–ฅํ›„ ์ง€์›์— ๋Œ€ํ•ด ์ž์„ธํžˆ ์•Œ์•„๋ณผ ์ˆ˜ ์žˆ์Šต๋‹ˆ๋‹ค.

About continuous deployment

Continuous deployment (CD) is the practice of using automation to publish and deploy software updates. As part of the typical CD process, the code is automatically built and tested before deployment.

Continuous deployment is often coupled with continuous integration. For more information about continuous integration, see "About continuous integration with GitHub Actions".

About continuous deployment using GitHub Actions

You can set up a GitHub Actions workflow to deploy your software product. To verify that your product works as expected, your workflow can build the code in your repository and run your tests before deploying.

You can configure your CD workflow to run when a GitHub Enterprise Server event occurs (for example, when new code is pushed to the default branch of your repository), on a set schedule, manually, or when an external event occurs using the repository dispatch webhook. For more information about when your workflow can run, see "์›Œํฌํ”Œ๋กœ๋ฅผ ํŠธ๋ฆฌ๊ฑฐํ•˜๋Š” ์ด๋ฒคํŠธ."

GitHub Actions provides features that give you more control over deployments. For example, you can use environments to require approval for a job to proceed, restrict which branches can trigger a workflow, or limit access to secrets. You can use concurrency to limit your CD pipeline to a maximum of one in-progress deployment and one pending deployment. For more information about these features, see "GitHub Actions๋ฅผ ์‚ฌ์šฉํ•˜์—ฌ ๋ฐฐํฌ" and "๋ฐฐํฌ ํ™˜๊ฒฝ ๊ด€๋ฆฌ."

Using OpenID Connect to access cloud resources

GitHub Actions ์›Œํฌํ”Œ๋กœ๊ฐ€ OIDC(OpenID Connect)๋ฅผ ์ง€์›ํ•˜๋Š” ํด๋ผ์šฐ๋“œ ๊ณต๊ธ‰์ž์˜ ๋ฆฌ์†Œ์Šค์— ์•ก์„ธ์Šคํ•ด์•ผ ํ•˜๋Š” ๊ฒฝ์šฐ ํด๋ผ์šฐ๋“œ ๊ณต๊ธ‰์ž์—๊ฒŒ ์ง์ ‘ ์ธ์ฆํ•˜๋„๋ก ์›Œํฌํ”Œ๋กœ๋ฅผ ๊ตฌ์„ฑํ•  ์ˆ˜ ์žˆ์Šต๋‹ˆ๋‹ค. ์ด๋ ‡๊ฒŒ ํ•˜๋ฉด ์ด๋Ÿฌํ•œ ์ž๊ฒฉ ์ฆ๋ช…์„ ์ˆ˜๋ช…์ด ๊ธด ๋น„๋ฐ€๋กœ ์ €์žฅํ•˜์ง€ ์•Š์„ ์ˆ˜ ์žˆ๊ณ  ๋‹ค๋ฅธ ๋ณด์•ˆ ์ด์ ์„ ์ œ๊ณตํ•  ์ˆ˜ ์žˆ์Šต๋‹ˆ๋‹ค. ์ž์„ธํ•œ ๋‚ด์šฉ์€ "OpenID Connect๋ฅผ ์‚ฌ์šฉํ•œ ๋ณด์•ˆ ๊ฐ•ํ™” ์ •๋ณด"์„ ์ฐธ์กฐํ•˜์„ธ์š”.

Workflow templates and third party actions

GitHub Enterprise Server๋Š” Azure Web App๊ณผ ๊ฐ™์€ ์ธ๊ธฐ ์žˆ๋Š” ์—ฌ๋Ÿฌ ์„œ๋น„์Šค์— ๋Œ€ํ•œ ๋ฐฐํฌ ์‹œ์ž‘ ์›Œํฌํ”Œ๋กœ๋ฅผ ์ œ๊ณตํ•ฉ๋‹ˆ๋‹ค. ์‹œ์ž‘ ์›Œํฌํ”Œ๋กœ๋กœ ์‹œ์ž‘ํ•˜๋Š” ๋ฐฉ๋ฒ•์„ ์•Œ์•„๋ณด๋ ค๋ฉด โ€œUsing workflow templatesโ€์„ ์ฐธ์กฐํ•˜๊ฑฐ๋‚˜ ๋ฐฐํฌ ์‹œ์ž‘ ์›Œํฌํ”Œ๋กœ์˜ ์ „์ฒด ๋ชฉ๋ก์„ ํ™•์ธํ•˜์„ธ์š”. โ€œAzure App Service์— Node.js ๋ฐฐํฌโ€๊ณผ ๊ฐ™์€ ํŠน์ • ๋ฐฐํฌ ์›Œํฌํ”Œ๋กœ์— ๋Œ€ํ•œ ์ž์„ธํ•œ ๊ฐ€์ด๋“œ๋ฅผ ํ™•์ธํ•  ์ˆ˜๋„ ์žˆ์Šต๋‹ˆ๋‹ค.

๋˜ํ•œ ๋งŽ์€ ์„œ๋น„์Šค ๊ณต๊ธ‰์ž๋Š” ์ž์‚ฌ ์„œ๋น„์Šค์— ๋ฐฐํฌํ•˜๊ธฐ ์œ„ํ•œ GitHub Marketplace์— ๋Œ€ํ•œ ์ž‘์—…์„ ์ œ๊ณตํ•ฉ๋‹ˆ๋‹ค. ์ „์ฒด ๋ชฉ๋ก์€ GitHub Marketplace๋ฅผ ์ฐธ์กฐํ•˜์„ธ์š”.

Further reading