I would create a Jenkins job and add a build step which invokes "ssh your_qnx_host your_checkout_and_build_command". The script which is your_checkout_and_build_command will run on the QNX computer and can perform the checkout and build steps which you need.
You could even consider copying the script from the slave agent host to the QNX host with an "scp" command before you call ssh. Then the build step would look like: scp your_checkout_and_build_command your_qnx_host:your_checkout_and_build_command ssh your_qnx_host your_checkout_and_build_command If you then place your_checkout_and_build_command under source control, you can configure the Jenkins job to monitor that source control system and perform the build whenever there are changes in the source control system, all without requiring the source control program on your QNX machine. Mark Waite On Tue, Dec 17, 2013 at 6:10 AM, Alexander Dikanchukov < sandy.emer...@gmail.com> wrote: > Could you please explain where i can setup this in my job? Just a simple > example would be very nice. > > -- > 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-users+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out. > -- 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-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
