nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Passing filelist on DNR script

rrose

OD 6.0.2

Hi,
Has anyone ever tired passing the filelist in a DNR script. I want to execute a script on Target before the deployment on all the files in the filelist.

<script cmd= "/usr/bin/perl /opt/Project1/scripts/run_files.ipl $myfilelist^" as="root" async="no"/>

myfilelist is in /opt/interwoven/iw-home/tmp folder. Can I pass this as filelist. I executed this script, the deployment is not receiving the filelist on Target, how can I resolve this problem.

Thanks in Advance.

Find more posts tagged with

Comments

rrose

Hi Again,

Sorry, the complete post is not published. Here is the continuation :

<script cmd= "/usr/bin/perl /opt/Project1/scripts/run_files.ipl $myfilelist^" as="root" async="no"/>

myfilelist is in /opt/interwoven/iw-home/tmp folder. Can I pass this as filelist. I executed this script, the deployment is not receiving the filelist on Target, how can I resolve this problem.

Thanks in Advance.

Adam Stoller

  <deployment transactional="no"  >
      <execDeploymentTask  useDefinition="test">
          <deployNRun>
            <dnrDeployment location="target" when="before" >
       <script   cmd= "/usr/bin/perl /opt/Project1/scripts/run_files.ipl $myfilelist^" as="root" async="no"/>
            </dnrDeployment>
          </deployNRun>    
        </execDeploymentTask>          
  </deployment>

myfilelist is in /opt/interwoven/iw-home/tmp folder. Can I pass this as filelist. I executed this script, the deployment is not receiving the filelist on Target, how can I resolve this problem.

Thanks in Advance.

There are at least two ideas that come to mind:

chartBug.png

chartWithWorkaround.png

rrose

Thanks Fish for your Reply.

Even I am trying to see which option to use. Looks like first one is little tricky to pass the filelist as filelist.
The second option is straight to use but I am seeing only one issue. In the documentation, they have cmds to get SUCCEEDED, FAILED or DELETED files. In my case I have to run the dnr script before deployment on all the files where I will not know the status of the file. Do you how know how to retrieve all the files.

Thanks Again!

Adam Stoller

Thanks Fish for your Reply.

Even I am trying to see which option to use. Looks like first one is little tricky to pass the filelist as filelist.
The second option is straight to use but I am seeing only one issue. In the documentation, they have cmds to get SUCCEEDED, FAILED or DELETED files. In my case I have to run the dnr script before deployment on all the files where I will not know the status of the file. Do you how know how to retrieve all the files.

Thanks Again!

Ah - missed the fact you were trying to run the script before deployment - in that case - the only other suggestion I could think of - if this is a deployment being run from a script which is putting together the filelist -- and -- if the filelist is relatively short - you might be able to have the script also create a single string entry of all the files that are to be deployed and pass it as a different parameter to the deployment so you can use that for the argument to your script. E.g.:

/targetdir/file1,/targetdir/dir1/file2,/targetdir/dir1/file3

Your script would then split the string up and do what it needs to do.

You might be able to build a smarter parsing mechanism so that the above could actually be condensed into:

/targetdir/{file1,dir1/file{2,3}}

The advantage is that it takes less space on the command line and is less likely to run into problems with maximum number of args and/or maximum size of command line constraints.

The disadvantage is that you need to figure out how to condense it on one side and expand it on the other (could be a kind of fun project).

Johnny

What's preventing you from deploying the files first?

Would it be possible to

1. deploy the files to a temporary location on the target
2. run the DNR and process the manifest
3. do a next deployment chain to move the files from the temporary location to the real location on the target.

If you do area type deployments, the temporary location will actually need to mirror the target location to avoid deploying the whole area each time - that obviously doubles the disk space required. This would be fine if you are only using file list deployments.

Try explaining the issue regarding the steps of your deployment... you might have other options at hand.

Johnny

A second thought was to do a simulate deployment first - but I remember that DNR's do not execute during simulate (is that still correct?). Maybe a FR to turn that on or off.

ISCBorisB

A second thought was to do a simulate deployment first - but I remember that DNR's do not execute during simulate (is that still correct?). Maybe a FR to turn that on or off.

That is still correct - for 6.0.1 at least. I hope it stays this way. FR of that nature would be
questionable IMHO. It would require an API to inform custom code that the run is in simulated mode and
then rely on the code to handle it properly. On it's own OD engine can force I/O simulation but with all that
RSCs, RMIs, HTTP, SOAP and whatnot it's nay impossible to guarantee that all changes are only simulated

rrose

Thanks everyone for your replies.

Now, I am running as two steps deployment. First deploying the filelist to tmp folder and then later running the actual deployment. I am making sure that I unlink the /tmp/filelist in my second deployment.

Thanks