From the course: GitHub Actions for CI/CD
Unlock the full course today
Join today to access over 24,900 courses taught by industry experts.
Continuous Deployment for infrastructure as code - GitHub Tutorial
From the course: GitHub Actions for CI/CD
Continuous Deployment for infrastructure as code
- [Instructor] In this lesson, we'll learn how to create job summaries while running a CI/CD workflow for a project using infrastructure as code. As we develop more complex workflows, it may become difficult to locate details by searching through jobs, steps, and the logs they contain. To overcome this, GitHub allows each step in a workflow to send text to the actions interface using a variable called GITHUB_STEP_SUMMARY. GITHUB_STEP_SUMMARY is a variable that contains a path to a file where each step can store text. If the file contains any text at the end of a step's run, the text is written to the workflow summary and styled as GitHub-flavored Markdown. Along with Markdown, we can also use emojis to add extra flair to the step summary. For example, we can have a job that runs a series of steps and then uses one step to report the final results. The results can be appended to the summary by redirecting content to…
Contents
-
-
-
-
-
-
(Locked)
Continuous deployment45s
-
(Locked)
Deploying software with GitHub Actions4m 40s
-
(Locked)
Continuous deployment for GitHub Pages4m 55s
-
(Locked)
Create a service account for deployments6m 20s
-
(Locked)
Continuous deployment for container images11m 46s
-
(Locked)
Continuous Deployment for infrastructure as code7m 53s
-
(Locked)
Challenge: Develop a CI/CD pipeline1m 52s
-
(Locked)
Solution: Develop a CI/CD pipeline13m 1s
-
(Locked)
-