-
Notifications
You must be signed in to change notification settings - Fork 7
Create CI with hardware #30
Comments
Seems to be the easiest with the Nezha D1. It has:
|
|
I'm Wei Wu, the director of PLCT Lab, which is a development partner of RVI. We're building and maintaining the first RISC-V Lab. There are hundreds of D1 and Unmatched machines for RISC-V CI in open source projects. I'd like to contribute to this issue if remote CI is possible. (The devices are located in Nanjing, China.) (There is only one BeagleV Starlight in my lab, so I'm afraid that it may need more help from others.) |
That sounds great, @lazyparser, thanks! You (are going to) have an API to flash and reset the system, as well as to get the serial output? |
Yes sure. I've found your [anything] email address :) I'll write a short manual after the new year holiday. Basically developers can login to these boards directly using ssh.
Sure. The idea is to leverage a Jenkins instance for the triggering and log downloading. (e.g. https://ci.rvperf.org/ . the Jenkins itself does not save scripts. it pulls scripts from https://github.com/plctlab/riscv-ci . so we can use github PR for adding and updating build scripts) |
Oh good, I thought you were someone else.
Since EDK2 is the firmware (like u-boot), we need to flash the SD card from outside the board and get the console using physical serial port (UART). |
Can use https://github.com/HewlettPackard/osfci.
Need to figure out:
Possibly for:
The text was updated successfully, but these errors were encountered: