The early stages of a CI/CD pipeline can be used to weed out bad code. In this video, learn how a few checks in the beginning can prevent problems down the line.
- [Instructor] In the first stage of our CI/CD pipeline, … we handle linting and unit tests. … With linting, we can enforce coding standards, … like naming conventions, comments, and formatting. … It can also improve code quality … by detecting dangerous constructs like race conditions, … unused libraries, or typos in variable names. … Essentially, linting helps us catch errors … and potential problems early in the design cycle … when they're easy to debug and fix. … Unit tests are often the first tests … that are run against the project. … These tests check code functionality … at the component level, … making them useful for testing functions … before they're integrated. … And because they're run at a low level, … unit tests can expose problems … closer to where they originated, … and typically unit tests are fast running. … This means we can run them along with our other build steps … without slowing things down. … Let's take a look at how we've implemented linting … and unit tests in GitHub actions for our Python web app. …
Author
Released
2/21/2020- Creating an action
- Creating a workflow
- Adding actions to a workflow
- Using an action from a repository
- Developing a CI/CD pipeline with GitHub Actions
- Building custom actions
- Publishing an action to the GitHub Marketplace
Skill Level Beginner
Duration
Views
Related Courses
-
Learning Jenkins
with Michael Jenkins1h 20m Beginner -
Learning GitHub
with Aaron Stewart2h 11m Beginner -
GitHub Essential Training
with Aaron Stewart2h 48m Intermediate
-
Introduction
-
What you should know1m 32s
-
Working with YAML files1m 25s
-
1. Your First Action
-
Your first Action2m 31s
-
-
2. Connecting Actions with Workflows
-
Create a workflow3m 11s
-
Add actions to a workflow4m 27s
-
Run a workflow2m 31s
-
Add conditions to a workflow2m 40s
-
-
3. Using Actions
-
Using secrets4m 1s
-
Using artifacts4m 7s
-
Manage pull requests3m 30s
-
4. Developing a CI/CD Workflow
-
Plan your CI/CD pipeline1m 53s
-
Linting and unit tests2m 7s
-
Testing1m 44s
-
Deploying1m 38s
-
-
5. Building Custom Actions
-
Plan a custom action4m 22s
-
Dockerfile review4m 58s
-
Add a Dockerfile2m 20s
-
Add an entry-point script2m 30s
-
Test an action locally3m 52s
-
Add a metadata file2m 50s
-
Add a README file1m 48s
-
Deploy a custom action2m 22s
-
-
Conclusion
- Mark as unwatched
- Mark all as unwatched
Are you sure you want to mark all the videos in this course as unwatched?
This will not affect your course history, your reports, or your certificates of completion for this course.
CancelTake notes with your new membership!
Type in the entry box, then click Enter to save your note.
1:30Press on any video thumbnail to jump immediately to the timecode shown.
Notes are saved with you account but can also be exported as plain text, MS Word, PDF, Google Doc, or Evernote.
Share this video
Embed this video
Video: Linting and unit tests