Continuous Integration #19
Labels
No Label
Bug
Build Problems
Discussion
Distribution
Enhancement
Far Future
Fix Later
TODO
WONTFIX
Workflow
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: BodgeMaster/FOSS-VG#19
Loading…
Reference in New Issue
There is no content yet.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may exist for a short time before cleaning up, in most cases it CANNOT be undone. Continue?
Below are just a bunch of ideas, I would like to get input on this topic.
We need automation for building and testing the following:
The test results could be presented using a web interface. Development commits would be submitted to a separate branch and the CI system would merge it into master once all the tests have passed.
The reason why I would like to have testing with so many variables is that conforming only with generally accepted standards and not with specific quirks of a specific platform is preferable imo, also building for multiple hardware platforms is supposedly good for unveiling bugs.
If we cannot figure out a good way to spin up VMs/QEMU emulators for testing, I can provide a big endian system using real hardware, though spinning up VMs when needed is generally preferable.
CI boxes and systems
Things to figure out:
Storage layout for "Beefy Pentium Box":