how do you intend to make use of this file once it is uploaded? what command are you going to run to alter the parameters ?
The file itself is the parameters list that I have built using another process.
Like process 1 creates the file and gives name to process 2.
process 2 is the one that has to upload the file to the bl job using web services.
ok, but i don't understand why you are trying to upload a file. do you have a blcli command that is going to make use of it ? i don't believe there are any blcli commands that read a file to set the nsh script params. so you probably need to iterate over the list of parameters you want to change on the client side and run the soap commands to set each parameter.
I get the param values from another place as in another group sets up the data using Jenins. I could go thru the file and in a loop set the parameter values one at a time.
The file name that I am given looks like
As an alternative, I would love to take the file that I am given and do something like this in my NSH script
if [ -f "$fileNameWithParams ];
My question is how to get the file from my jenkins box to the bl server to a given location so I can use the file as is instead of passing the params to the job.
If I am not clear I apologize. What I am looking for is how to do file asset using Webservices.
so you want to just copy the file up to the appserver into some random location, then you will run a nsh script job that will go find the file in this location and source it and do whatever the job does ?
there's an unreleased command called FileManagerMode copyFileToFileServer that may work if you can figure it out. it may be easier to:
- scp or otherwise do the copy from the jenkins box to the appserver
- have the nsh script pull the file from the jenkins server.
Thank You. You are always very helpful.
One question. Why is it that BL cannot copy a file from a NFS/Samba share ? What I mean is if our QA friends copy a file to a drive say M: and that is mapped via NFS to our jenkins server. NSHScript cannot copy that as an asset from across mounted file systems. May be I am doing something wrong but I was told that BL is not very friendly to assets across mounted file systems. Is there merit to that statement ?
Mapped drives are usually per-user-session: does your NSH Script see that same M: drive (path may look like //@/M/)?
what os is your jenkins server ?
when you say 'browse' do you mean via the gui ? if you use nsh, can you cd over to the server into the nfs mounted path ?
if it's just the former there's a blasadmin setting i think for that - something w/ 'mnt' in the setting name.