Continuous deployment automates the path from a repository change to validated software delivery. A push triggers a cloud workflow, which provisions a temporary runner, retrieves the code, executes build logic, and then removes the runner. The practical implementation keeps most logic in portable scripts rather than provider-specific workflow actions. section 16.1
A small implementation follows this sequence:
- Define the workflow in YAML and trigger it from repository changes. section 16.1
- Run a portable PowerShell build script on an Ubuntu runner. section 16.1
- Build Docker images and run unit tests as part of the build. section 16.1
- Stop the workflow when a test fails, preventing an invalid build from continuing. section 16.1
A minimal GitHub Actions workflow
The workflow checks out the repository and runs the build script from the cicd directory using PowerShell: `jobs: build: runs-on: ubuntu-latest; steps: - uses: actions/checkout@master; - name: build; working-directory: cicd; run: ./build.ps1; shell: pwsh`. Committing and pushing this file triggers the cloud build. section 16.1
# check your dependencies are available: git version pwsh -version # launch PowerShell: pwsh # and make sure your Docker setup is using Linux containers: $info = docker version -f json | ConvertFrom-Json echo "Platform: $($info.Server.Os)/$($info.Server.Arch)"
Verify Git, PowerShell, and Docker before running the workflow exercises; the commands also confirm that Docker uses Linux containers. section 16.1
