@les_mikelsell Thanks for the feedback. Very good point you are making about considering reuse patterns.
In our corporate environment (where the images are actually reused) this is already working well using a network accessible file-share. Our automated microscopes write to this shared space that is then accessible to Jenkins via NFS. I'm now trying to create an open source platform for scientists outside our organization to use this functionality. Jenkins will probably be running on the cloud somewhere with limited storage, so I thought users would be uploading the images to be processed just temporarily. It got to be a relatively simple approach as most of these users are not experienced dev-ops folks. I'm also wondering whether Jenkins could authenticate to specific S3 or other cloud storage on a per build basis. People could maintain their images on these cloud storage platforms and provide authorization via Jenkins to access it for the duration of the build? Thanks again Ioannis On Saturday, February 21, 2015 at 3:53:24 PM UTC-5, LesMikesell wrote: > > On Sat, Feb 21, 2015 at 8:50 AM, Ioannis Moutsatsos > <imout...@gmail.com <javascript:>> wrote: > > Thanks Daniel; > > > > I'm assuming that by multiple file parameters you mean adding more than > one > > file parameters on the form. The issue is that the number of image files > is > > not always the same, and this number could be in the hundreds! > > > > The zip/tar archive upload makes a lot of sense but it could take a long > > time on both ends to zip and then unzip. My users would be responsible > for > > archiving on laptops that may not be up to the task, but at the end it > may > > be the idea I will go with. > > Depending on what other use you have for these files and whether any > are re-used, you might consider committing to a subversion repository > or similar version control system and letting jenkins check them out > with the job more or less as you would with source code. Or use some > common shared file space. > > -- > Les Mikesell > lesmi...@gmail.com <javascript:> > -- 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-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/d9f826de-0013-4851-8cef-c9f66b74a5dd%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
