You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Only the Ansible repository is covered by the CI. We propose to extend the CI usage to all Ansible, cukinia, FAI and Yocto repositories.
Current status
Only the Ansible repository uses the CI directly.
The CI and cukinia-test repositories can be indirectly tested
Other repositories are not tested
FAI and Yocto SEAPATH images are not tested and update are not automatic and require physical access to the CI machines
On GitHub, meta-seapath is not built tested when pulling modification, and there are no weekly build without cache
Detailed Description
With the Ansible collection refactor, all collection's repositories became testable on CI.
To test and update FAI and Yocto images, we can use a USB drive plug on all CI machines.
When the images change, we can reflash the USB drive with the latest images for FAI or update the SEAPATH images stored inside the driver for the Yocto version and force the reboot on the drive with the efibootmgr --bootnext command, as it is already done on the Yocto standalone CI.
Abstract
Only the Ansible repository is covered by the CI. We propose to extend the CI usage to all Ansible, cukinia, FAI and Yocto repositories.
Current status
Detailed Description
With the Ansible collection refactor, all collection's repositories became testable on CI.
To test and update FAI and Yocto images, we can use a USB drive plug on all CI machines.
When the images change, we can reflash the USB drive with the latest images for FAI or update the SEAPATH images stored inside the driver for the Yocto version and force the reboot on the drive with the
efibootmgr --bootnext
command, as it is already done on the Yocto standalone CI.Benefit to SEAPATH
Dependency
Works to be done
The text was updated successfully, but these errors were encountered: