HansUweRempler
commented
4 years ago 
I had an interesting discussion today at the BoCSE about how we could have our Jenkins dashboard, i.e., the CI results public available. If we connect the Beaglebones to the development network (which I think they maybe already are) using the white router boxes (transparent proxy) they could open up (and keep it open) a ssh tunnel - maybe during startup - to a Jenkins master outside BGN. I can offer to support with a Azure VM until we have the EF infrastructure and their Jenkins master available. On the VM we could quickly install and run a Jenkins instance to try out the connection to our Bosch development Beaglebones.
Is your feature request related to a problem? Please describe. The Cellular SW module has been broken during unit testing improvement and nobody realized this. Only after manual setup for the BoCSE demo this has been noticed.
Describe the solution you'd like We must have an automated (continuous integration) setup to know the health status of our master branch. This setup needs to be
Prio a) working with Bosch infrastructure
Prio b) extendable with additional reference HW
Prio c) working with future Eclipse Foundation infratructure
[ ] First Kiso RefHW Bosch CommonGateway connected to Jenkins agent (Beaglebone) for flashing and executing integration tests
[ ] write integration test spec cddk-oss/boards/CommonGateway/test/specs e.g., read out MCU id e.g., read out BMA350 id e.g., read out Ublox SARA IMEI
[ ] run integration tests on the HW cddk-oss/boards/CommonGateway/test/integration
[ ] integration test results visible to Kiso Jenkins
[ ] Hugo documentation update
Describe alternatives you've considered We have already a CI setup for unit tests etc.. The Ku server and the Beaglebones are prepared for XDK integration tests.
Additional context Whoever can participate on this task shall please do so. Only if there is now work available for making this happen another topic shall be addressed. This user story here is the main target for Kiso monthly 12.19.