Parameterized trigger plugin: File Parameter not supported?

[Jochen Hinrichsen]

Dear group,

i have a bunch of jobs that all prepare a zip and a readme in the workspace, and those two files need to be passed to a dedicated file job that expects two files ('zipfile' and 'readme') as job parameters. Usually the parameterized trigger plugin is of great help, but it seems that 'file' parameters are not supported. I'm talking about real files, not files containing key value properties. I don't want to pass absolute filenames instead of the files themselves, because it would need some thinking about when to clean workspaces.

Along the lines i found a custom implementation in the plugin that takes care of booleans (JENKINS-15920), but nothing related to files. There's also support for triggering a job for each existing file via a parameter factory, but unfortunately i need to have two files for a job...

My gut feeling is that i am missing something very obvious here :-)

Any idea greatly appreciated

Jochen

[Jochen Hinrichsen]

Stupid me - just configured two factories, each using a distinct filename w/o wildcards, runs like a charm.

[Ginga, Dick]

Well, I don’t know about file parameters but one way to do this is to have the jobs archive the zip and readme files and then send the job name and build number to the dedicated file job and that job can then, using the Copy Artifact Plugin, copy those files to your file job workspace.

 

--
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-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/0af39f7e-38cf-4cb5-b711-fbc0f6cc4f16%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.