Create a workflow that links and tests new code on each push to a repository.
- [Instructor] The main goal of continuous integration … is to find and resolve problems early … in the development cycle. … With continuous integration, developers work on their code … in a local environment and then commit their changes … to a shared repository. … The code can then be combined or in other words integrated … with code from other members of the team … or any existing code. … In this scenario, we'll use a workflow … that gets triggered on each PUSH to the repository. … The workflow will call two actions. … One, to automatically lint the code … and run predefined tests … and another to build a Docker image … using a Dockerfile in the repo. … We won't store the Docker image anywhere. … We'll just be running the BUILD step … to make sure we haven't introduced any bugs. … Using this approach, we'll be better positioned … to find and resolve problems … well before the code is ready to be released. … To explore this scenario, … I've created a repo hosting a Python web application. …
- Creating an action
- Creating a workflow
- Adding actions to a workflow
- Using an action from a repository
- Using environment variables
- Building custom actions
- Use cases for actions and workflows
Skill Level Beginner
1. Your first Action
2. Connecting Actions with Workflows
3. Using Actions
4. Building Custom Actions
5. Use Cases
- 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.Cancel
Take 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.