My notes to wrap my head around the similarities and disimilarities between GitHub's and BitBucket's CI system as I migrate over.
- BitBucket Pipelines has a single YAML file
<project_root>/bitbucket-pipelines.yml
- GitHub Actions breaks that apart into multiple YAML files
<project_root>/.github/workflows/<whatever>.yml
which they callworkflows
- BitBucket Pipelines and GitHub Actions both have a platform where you can easily install and use scripts in your container made by others (or yourself) in a way that abstracts and simplifies your code.
- BitBucket Pipelines calls these "pipes" (as
pipe
property) while GitHub Actions calls these "actions" (asuses
property).
- BitBucket Pipelines calls these "pipes" (as