Please add the upload form to QuickBuild's UI that will allow to choose a file from user's computer and then upload it somewhere (for example to configuration's workspace or some better location) and assign to a variable.
This would enable users to upload files that are required to promote a build, but should not be kept in project repositories.
Example: build produces a .zip file, but before promotion developer has to add a .pdf file to this .zip file. User would upload .pdf file and assign it to a variable, promotion step would include .pdf from variable in .zip file and do the standard work.
Description
Please add the upload form to QuickBuild's UI that will allow to choose a file from user's computer and then upload it somewhere (for example to configuration's workspace or some better location) and assign to a variable.
This would enable users to upload files that are required to promote a build, but should not be kept in project repositories.
Example: build produces a .zip file, but before promotion developer has to add a .pdf file to this .zip file. User would upload .pdf file and assign it to a variable, promotion step would include .pdf from variable in .zip file and do the standard work.
Can you reconsider adding the file upload feature please? This feature would allow us to have a user selectable file upload for builds that utilize pre-built binaries. Currently we use a "file repository" and we rely on naming conventions to get the right file. This is error prone and the file repository doesn't give us any trace-ability about who placed the file on the file system. SCM, unfortunately is not an option here because the users that produce the pre-built binaries consider their work done once the file is dropped off at the file repo .
Dan Morgan[21/Nov/15 04:24 PM]
Hi Robin.
Can you reconsider adding the file upload feature please? This feature would allow us to have a user selectable file upload for builds that utilize pre-built binaries. Currently we use a "file repository" and we rely on naming conventions to get the right file. This is error prone and the file repository doesn't give us any trace-ability about who placed the file on the file system. SCM, unfortunately is not an option here because the users that produce the pre-built binaries consider their work done once the file is dropped off at the file repo .
As you have seen already, other users would like this feature too:
http://forum.pmease.com/viewtopic.php?f=1&t=3718&p=14099&hilit=file+upload&sid=f3c05ba8c5208a83afe875e528ee1e7e#p14099http://forum.pmease.com/viewtopic.php?f=1&t=3650&hilit=upload
Other CI build systems have this feature:
https://wiki.jenkins-ci.org/display/JENKINS/Parameterized+Build
The upload could go from the users system to node running the master step and the workspace of the config.
Can you reconsider adding the file upload feature please? This feature would allow us to have a user selectable file upload for builds that utilize pre-built binaries. Currently we use a "file repository" and we rely on naming conventions to get the right file. This is error prone and the file repository doesn't give us any trace-ability about who placed the file on the file system. SCM, unfortunately is not an option here because the users that produce the pre-built binaries consider their work done once the file is dropped off at the file repo .
As you have seen already, other users would like this feature too:
http://forum.pmease.com/viewtopic.php?f=1&t=3718&p=14099&hilit=file+upload&sid=f3c05ba8c5208a83afe875e528ee1e7e#p14099
http://forum.pmease.com/viewtopic.php?f=1&t=3650&hilit=upload
Other CI build systems have this feature:
https://wiki.jenkins-ci.org/display/JENKINS/Parameterized+Build
The upload could go from the users system to node running the master step and the workspace of the config.