ADD support for custom output folder in FileZipOperation

[KevinHagen]

We wanted to use this plugin for zipping our build files before uploading them to our server. Doing so, we've realized that you can not specify an output directory and instead the zip operation always just throws the zip file into the root workspace directory.

It would be great if you could specify the output directory instead.

[KevinHagen]

Hey @pskumar448, any news on if this pr can be merged?
We would really like to have this feature in our pipeline!

[mwinfie]

It looks like this has broken some of our builds using fileZipOperation. Was it intentional to introduce the output directory parameter without setting a default value if the user does not set it? That is a breaking change.

[wreggyl]

this change changed the interface not in a backwards compatible way
worked in 1.9 but not in 1.10

FileZipOperation(myPath)
maybe it is better to to have a fallback if no outputFolderPath is specified that it chooses the current directory as fallback like it was the default in all previous releases?

if only one parameter is given without name, treat it as folderPath and choose outPutFolderPath as current directory: FileZipOperation(myPath) => FileZipOperation(folderPath: myPath, outputFolderPath: ".")
FileZipOperation(folderPath: myPath) => FileZipOperation(folderPath: myPath, outputFolderPath: ".")
FileZipOperation(folderPath: myPath, outputFolderPath: myOutPutPath) => FileZipOperation(folderPath: myPath, outputFolderPath: myOutPutPath)

[relyafi]

@wreggyl I agree with your comments - it looks like in earlier versions it used to output files to the workspace directory. I've raised a PR to restore this behaviour by default, as well as tackle other bugs that seem to have been introduced by this change.

#14

[KevinHagen]

Thanks for clearing this out. I was in a hurry fixing this for our use-case and since it worked I filed the PR. With @relyafi s changes we should be fine again :)