Publish iso workflow #9
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "publish-iso-workflow"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Motivation
We need to publish the final iso somewhere, so we need a workflow that does that on main branch.
We also need to create a base VM image using this iso that can be used for testing, the first example being the state manager tests
Solution
The process of publishing the iso file is just making a new file in
/tank/local/isos/. I decided this was easier then trying to upload a 2.5GB file as a release. Can revisit later if necessaryI decided to pull out the start process code from the sim test package. I needed a simpler system for creating a pseudo terminal for programmatically accessing a VM. This could be useful as a separate package later — this need keeps coming up.
For some reason running commands as sudo in jobs doesn't work, with the exception of starting deno as sudo. And so I had to implement the logic of the jobs in deno.
Also started using a self hosted RPM repo to improve workflow speed since downloading the packages took several minutes.
I also realized that leaving VMs running from other workflows in other repositories was slowing everything down. Now the vms are shutdown at the end of each workflow. If the workflow fails, the vm will still be running for investigation
Publish iso workflowto WIP: Publish iso workflowWIP: Publish iso workflowto Publish iso workflow