Set up AWS EC2 instance for generating Debian packages nightly #3417
Labels
type:build
Tooling and infrastructure around building the Autoware.
type:installation
Issues or improvements related to the installation process of the software.
type:new-feature
New functionalities or additions, feature requests.
Checklist
Description
With the latest changes in the Debian builder GitHub action and the fixes in Autoware, it is now possible to build Debian packages in a GitHub action. However, the process takes longer than 6 hours, and so GitHub cancels the job (see https://github.com/esteve/autoware_packages/actions/runs/4640002506/jobs/8211476529 for a failing job).
The limits for GitHub-hosted runners can be found in https://docs.github.com/en/actions/learn-github-actions/usage-limits-billing-and-administration#usage-limits
Whereas the limits for self-hosted runners (e.g. AWS) can be consulted in https://docs.github.com/en/actions/hosting-your-own-runners/about-self-hosted-runners#usage-limits
Purpose
Being able to generate Debian packages every night.
Possible approaches
Integrate the on-demand self-hosted AWS EC2 runner action (https://github.com/marketplace/actions/on-demand-self-hosted-aws-ec2-runner-for-github-actions) to start an EC2 instance, generate the Debian packages and then shut down the EC2 instance.
Alternatively, there are some speedups that could be accomplished in the GitHub action, but those may require significant rewrites. Nevertheless, the GitHub-hosted runners are quite resource limited so having an AWS EC2 instance generating the Debian packages is still a sensible approach.
Definition of done
Debian packages for all the buildable packages (i.e. no CUDA for now) are generated nightly.
The text was updated successfully, but these errors were encountered: