Embedded software tests with Jenkins

345 views
Skip to first unread message

wiktor.r...@gmail.com

unread,
May 28, 2015, 3:08:37 AM5/28/15
to jenkins...@googlegroups.com
Hi everyone!

I'm trying to introduce CI server in my company and I'm totally new to Jenkins.
I would like to ask some questions in order to know whether Jenkins would fulfill our requirements for testing purposes.

Projects we're working on are mainly embedded software for microporcessors and microcontrollers.
We have our custom  building scripts which can be called from Linux console so building with use of Jenkins wouldn't be a problem (as far as I know).
We need to compile project, program target and run tests on target. The only tool for debugging we can use is serial port output.
Would it be easy to configure Jenkins to work with 'remote' target and parse serial port output to interpret if device is working properly?

Slide

unread,
May 28, 2015, 7:39:13 AM5/28/15
to jenkins...@googlegroups.com
In general, if you can do it from the command line, you can probably do it through Jenkins. If you want to have jenkins display test failures an so forth, you would want to generate a file in the format that one of the test running plugins expects.

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/b95a0c3d-81d3-42b2-b9d3-abfeef543e19%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Tim Jackson

unread,
May 29, 2015, 11:45:36 AM5/29/15
to jenkins...@googlegroups.com
We use Jenkins to run builds on Linux, transfer the resulting 'artifacts' (firmware build files) to Windows nodes, then use Robot Framework (RF) and ultimately our own DLL to transfer firmware files to our proprietary hardware.  Once installed, RF continues to send commands and gather results via HID and serial interfaces to our hardware and fixtures they are mounted in.

There are a lot of parts to our system, so we need to be careful that everything is ready (by checking via Jenkins and RF) before actually running tests for results.

I have no doubt you can make a system based on Jenkins work as long as you can do everything you want done , as slide says, via command line or custom interface.  There are a lot of tools out there to connect everything up.
Reply all
Reply to author
Forward
0 new messages