Public xenomai testing infrastructure
quirin.gylstorff at siemens.com
Fri Mar 6 14:05:01 CET 2020
On 3/5/20 2:51 PM, Jan Kiszka wrote:
> On 05.03.20 14:41, Gylstorff Quirin wrote:
>> Hi all,
>> As Jan mentioned in some post we have a CI infrastructure
>> - currently only internal available - based on gitlab & LAVA.
>> We plan to create a public version of this infrastructure.
>> The setup will similar to the testing in CIP project. The results
>> of a build are transferred via a public LAVA master to private
>> instances of LAVA workers to the device-under-test and executed and
>> the result displayed on the LAVA master.
>> We intend to use xenomai-images to build kernel,root file system and
>> The CI infrastructure will have the following components:
>> - Public/Private Builds with gitlab, travis or similar
>> - Public Lava Master (scheduling of test and display of results)
>> - Private Lava worker connect to Hardware targets
>> Current open topics for the CI Infrastructure
>> - where to execute the public builds?
>> - gitlab oss program
>> - can we run builds of xenomai-image
>> - travis
> (then paid, we won't scale as free project)
> - AWS, like we do in the CIP project via
>> - somewhere else
>> - Where to store the build artifacts?
>> - AWS buckets
>> - locally on the Master
> You mean the Lava Master, I suppose.
>> - How long to store the build artifacts?
>> - 1 week
> - until overwritten by a newer version - unfortunately not a feature of
> gitlab artifacts
>> - Where to run the public Lava Master?
>> - AWS or similar instance
>> - Payment of the instance
>> - Physical Server
>> - Who can host the server
>> : https://lavasoftware.org/
I tested xenomai-images with in my gitlab account and it work - slowly ;-)
You can check out the build:
Next test would be to store the results as artifacts.
More information about the Xenomai