I like to use the approach of storing my bash based build scripts in the scm... having the Jenkins job check them out and then use the shell task to execute them.
generally speaking the shell task will then look something like: pushd <directory for the scripts> bash <script name> I've also done some interesting stuff having shell scripts generate xUnit compatible xml output and then loading that into the test result reporting in Jenkins. I think you need to install the xUnit plug-in for that to work. Ben On Thu, Mar 28, 2013 at 3:51 PM, Michael <mwpowell...@gmail.com> wrote: > Hello, > > I've got a couple of bash scripts, which I'm ashamed to admit, > "happily chug along" as the phrase goes. To get it basically working > anyway. I haven't yet added much in the way of error handling, return > exit codes, etc. > > Now, I'd like to fold that in with a CI environment and need to know a > good way of approaching it, that 1) preserves interactive (developer) > usage of the build script and 2) plays nice with the CI environment > running the shell script, facilitating the build. > > Thanks very much in advance... > > Regards, > > Michael Powell > > -- > 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.
