Use a simple script (e.g. Windows batch) build step instead. Then you'll have full control over your build tool invocation.
On 16.09.2013, at 23:01, Bob Bick <bb...@netjets.com> wrote: > Hi, > > Our Jenkins jobs have various command line parameters which apply to various > build steps. Some build steps (e.g. Top-level Maven build, Grails build step) > add all of the jobs input parameters to its command line. > > Q. Is there a way to limit the command line parameters that are applied to > the various build steps? That is, I don’t want every job input parameter to > be passed to the Grails and/or Maven command line. > > Thanks for any help in advance, > Bob > > *** *** *** > This message contains information which may be confidential and privileged. > Unless you are the addressee (or authorized to receive for the addressee), > you may not use, copy or disclose to anyone the message or any information > contained in the message. If you have received the message in error, please > advise the sender by reply e-mail and delete the message. > > > -- > 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.
