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. On Thursday, May 28, 2015 at 1:08:37 AM UTC-6, [email protected] wrote: > > 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? > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/6182c114-8e63-40ce-b7d3-e6d22cbcf48b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
