On Wed, Feb 22, 2012 at 3:36 PM, Les Mikesell <lesmikes...@gmail.com> wrote:
> On Wed, Feb 22, 2012 at 3:29 PM, Andrew Melo <andrew.m...@gmail.com> > wrote: > > > > > > On Wed, Feb 22, 2012 at 2:35 PM, Sami Tikka <sjti...@gmail.com> wrote: > >> > >> Funny... I just created a test job with one file parameter and > >> triggered without specifying a file. The job ran fine and there was no > >> file in the workspace. > >> > >> I'm running Jenkins 1.451 on Mac OS X 10.7. My Jenkins is not wrapped > >> in any servlet container. > > > > > > Hey Sami- > > > > Were you submitting using a browser? This is what I get on the command > line > > when I try to submit a job with a file parameterization (note, it works > fine > > and builds properly when there's no file parameterization). When > submitting > > a form on a browser and there is no file selected, it will silently do > the > > equivalent of submitting an empty file. When triggering the REST > interface > > directly, that doesn't happen and Jenkins barfs on the input. The > stacktrace > > is below. > > So can you make whatever you are using to hit the REST interface > submit an empty file when you don't have a real one? > That would be the easiest option. But we already have a bunch of different scripts that are hitting it. It's weird that jenkins will let you ignore posting all other types of parameterizations (the sandbox-melo-matrixtest job has a bunch of parameters, for instance), but will blow up on missing a file. I'm terrible at java, but i'm going to walk through the stacktrace and see if I can't find what's barfing. Thanks, Andrew > > -- > Les Mikesell > lesmikes...@gmail.com > -- -- Andrew Melo
