-
New Feature
-
Resolution: Done
-
Major
JENKINS-27295 discusses getting values from various kinds of parameters. Handling FileParameterValue is another matter. buildEnvironment (what is called today) is useless since it gives only a file name. createBuildWrapper is the way this works in a freestyle project, but this cannot work in a workflow; even if it were to return a SimpleBuildWrapper (JENKINS-24673) it is not clear where that would be called, since we can only use it from a workspace. getValue as currently implemented is useless since a FileItem does not have whitelisted methods, and anyway we would not want the flow itself to be copying streams to the workspace; this needs to be done by infrastructure. The only way forward I can see at the moment is for getValue to return a SimpleBuildWrapper, so that your flow could read
node {
wrap([$delegate: parameters.myFileParam]) {
sh 'cat myFileParam'
}
}
- depends on
-
JENKINS-24673 SimpleBuildWrapper
-
- Resolved
-
-
JENKINS-27295 Boolean parameters injected as String
-
- Resolved
-
- is duplicated by
-
JENKINS-47333 file parameter not working in pipeline job
-
- Closed
-
-
JENKINS-51245 file parameter issue in jenkins pipeline
-
- Closed
-
- is related to
-
JENKINS-29289 InputStep doesn't support File Parameters
-
- Resolved
-
-
JENKINS-47333 file parameter not working in pipeline job
-
- Closed
-
- relates to
-
JENKINS-12699 Temp upload files from file param not removed after transferred to slave
-
- In Review
-
- links to
I don't quite understand if this is just not implemented yet, or if it's impossible to implement at all. If it is possible, we might be able to fund the development of this feature, as we need it too. As I am still rather new to the Jenkins community: Can anyone recommend me any companies that could do that?