Skip to main content
Beta
This lesson is in the beta phase, which means that it is ready for teaching by instructors outside of the original author team.
CI/CD
- CI/CD is crucial for any reproducibility and testing
- Take advantage of automation to reduce your workload
Exit CodesStart by ExitingPrinting Exit CodesSetting Exit CodesIgnoring Exit Codes
- Exit codes are used to identify if a command or script executed with
errors or not
- Not everyone respects exit codes
- YAML is a plain-text format, similar to JSON, useful for
configuration
- YAML is used in many CI/CD tools and solutions
- You should bookmark the GitHub
Actions reference. You’ll visit that page often.
- Actions are standalone commands that are combined into steps to
create a job.
- Workflows are made up of one or more jobs and can be scheduled or
triggered.
- Creating
.github/workflows/main.yml
is the first step
to CI/CD.
- Pipelines are made of jobs with steps.
- GitHub has a Marketplace of reusable Actions
- CI can help automated running tests for code changes to your Python
package
- Matrix can help DRY your CI for multi-version and cross-platform
testing
- Using
matrix
allows to test the code against a
combination of versions.
- GitHub Actions can also help you deploy your package to a registry
for distribution.
- Documentation and website artifacts are different than package
artifacts
- Containers are a very common packaging artifact for web-based
applications
- GitHub provides resources to publish container images