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; } } }

Deploy files not in current work branch

sanoboy

Hi All,
In teamsite with opendeploy and workflow, is it possible that deploy files not in current work branch.

e.g Teamsite user update some files in branch A, then after he submit this file, he also want to deploy those files with the same name in Branch B and C.

I try to attach these files with the same name and corresponding path in external task, but from the deployment logs, i can only see the files in current work branch be deployed.

I think we should customize for the deploy task, but i really haven't got a clear solution for this until now, has anyone worked on this before?

Find more posts tagged with

Comments

ISCBorisB

I try to attach these files with the same name and corresponding path in external task

Don't do it. Task Object has only one 'areavpath' Attribute so only Files from that single Area can be attached

Is it possible that deploy files not in current work branch

Yes, sure. OD itself does not care about WF, Tasks and whatnot. The simplest way to do it is perhaps to build a File that contains
a list of the required Files. You will then use "File List" Deployment mode to Deploy it. See OD manual for details, File List format etc

Note that you'd have to incorporate that additional Deployment into your existing schema. How exactly to do that depends on the WF
and requirements. You can for example add new Deployment Leg(s) into existing OD Configuration or modify Deployment Task to run
several Deployments or configure additional Deployment Task.

sanoboy

Don't do it. Task Object has only one 'areavpath' Attribute so only Files from that single Area can be attached
Yes, sure. OD itself does not care about WF, Tasks and whatnot. The simplest way to do it is perhaps to build a File that contains
a list of the required Files. You will then use "File List" Deployment mode to Deploy it. See OD manual for details, File List format etc

Note that you'd have to incorporate that additional Deployment into your existing schema. How exactly to do that depends on the WF
and requirements. You can for example add new Deployment Leg(s) into existing OD Configuration or modify Deployment Task to run
several Deployments or configure additional Deployment Task.

Hi ISCBorisB,

Thanks so much for your advise, base on what you recommend, i plan to use following steps to process my requirement:

1.After submit task and before deploy task, there is a externaltask to create a filelist file under directory:

/Interwoven/OpenDeploy/files/deployFilelist.txt
e.g.If user submit templatedata/support/category/data/rigional/product_a.xml from regional branch, then it will also add following files(local branches) to deployFilelist.txt

templatedata/support/category/data/singapore/product_a.xml
templatedata/support/category/data/malaysia/product_a.xml
templatedata/support/category/data/indonesia/product_a.xml

2.Then i add 3 deploy task(singapore,malayisa,indonesia) after externaltask in the workflow. Every deploy task has an individual deployment config file(sorece area and filter rule are different).

Attachment is one deployment config file(for singapore branch).

Can you help me check is it possible by this way? Thanks

Adam Stoller

...
e.g.If user submit templatedata/support/category/data/rigional/product_a.xml from regional branch, then it will also add following files(local branches) to deployFilelist.txt

templatedata/support/category/data/singapore/product_a.xml
templatedata/support/category/data/malaysia/product_a.xml
templatedata/support/category/data/indonesia/product_a.xml

2.Then i add 3 deploy task(singapore,malayisa,indonesia) after externaltask in the workflow. Every deploy task has an individual deployment config file(sorece area and filter rule are different).

Attachment is one deployment config file(for singapore branch).

There appears to be some confusion here - the paths you listed above are all, potentially, part of the same branch - so there should be no problem attaching them to the same task in the same job, and deploying them with a single deployment configuration file. Or does the singapore sub-directory only exist on a singapore branch, and the malaysia sub-directory only exist on the malaysia branch?

If you cannot clearly communicate the environment in which you're working, it makes it very difficult for someone else to communicate reasonable solutions for your issue(s)

sanoboy

There appears to be some confusion here - the paths you listed above are all, potentially, part of the same branch - so there should be no problem attaching them to the same task in the same job, and deploying them with a single deployment configuration file. Or does the singapore sub-directory only exist on a singapore branch, and the malaysia sub-directory only exist on the malaysia branch?

If you cannot clearly communicate the environment in which you're working, it makes it very difficult for someone else to communicate reasonable solutions for your issue(s)

Sorry, maybe i lost something background.

yes,
in regional branch, under ../data/ there is only one regional sub-folder.
in singapore branch, under ../data/ there is only one singapore sub-folder.
in malaysia branch, under ../data/ there is only one malaysia sub-folder.

and in opendeploy target(livesite side), under ../data/ there will be multiple sub-folders rigional,singapore,malaysia,indonesia

base on above structure, i want to implement the deployment(deploy files no t in current work branch).

Is it possible by above filelist deployment method i post?

ISCBorisB

Sorry, maybe i lost something background.

yes,
in regional branch, under ../data/ there is only one regional sub-folder.
in singapore branch, under ../data/ there is only one singapore sub-folder.
in malaysia branch, under ../data/ there is only one malaysia sub-folder.

and in opendeploy target(livesite side), under ../data/ there will be multiple sub-folders rigional,singapore,malaysia,indonesia

base on above structure, i want to implement the deployment(deploy files no t in current work branch).

Is it possible by above filelist deployment method i post?

As a generic schema it looks sound. You will have to work out OD Configuration details though.

For example, OD Configuration source Area does not look correct, you *seem* to be missing WORKAREA, STAGING
or EDITION sub Path (unless you plan to include it into the relative Path of the list itself). Further, as far as I recall
includePath is ignored in the File List Deployment (includePattern is fine). Area + relative Path from the list itself
should provide all the Path you need.

If I were you I would've debug/modify OD Configurations first as stand-alone entities (eg, not a part of the WF or Deployment Task)
Use OD GUI or iwodcmd in CLT mode in some controlled Environment, utilize "Simulation" mode if needed. When done, you'll know
an exact OD settings you need plus related Deployment List virtual Path format to generate.

sanoboy

Hi ISCBorisB,

Now the filelist deployment works properly for my requirement. I just follow the steps you mentioned: Use OD GUI in controlled Environment, utilize "Simulation" mode to get an exact OD settings i need plus related Deployment List virtual Path format to generate.
(in singapore workbranch i just use to filter files from filelist)

Though it works fine and I implemented this requirement by adding 3 additional deploy task(individual deployment config file) after regional deploy task in workflow.
But one thing i wonder is if there are 20 local countries, then i can't add 20 additional deploy tasks in workflow. I just guess we may need use workarea src and filelist as parameters to pass to deploy task, then loop trigger deploy task for many times. Is it possible?

Adam Stoller

Hi ISCBorisB,

Now the filelist deployment works properly for my requirement. I just follow the steps you mentioned: Use OD GUI in controlled Environment, utilize "Simulation" mode to get an exact OD settings i need plus related Deployment List virtual Path format to generate.
(in singapore workbranch i just use to filter files from filelist)

Though it works fine and I implemented this requirement by adding 3 additional deploy task(individual deployment config file) after regional deploy task in workflow.
But one thing i wonder is if there are 20 local countries, then i can't add 20 additional deploy tasks in workflow. I just guess we may need use workarea src and filelist as parameters to pass to deploy task, then loop trigger deploy task for many times. Is it possible?

Is looping N times possible? Yes, if you have your own deployment script, or if you put an externaltask after the deployment task. Essentially you need to devise a 'max_loops' and 'current_loop' task or job variable and continue to loop through the deployment task until 'current_loop' is the same as 'max_loop'.

Would I advise this approach? Probably not, instead I'd consider having a deployment wrapper script that takes care of the looping itself, by having it dynamically determine the number of branches for which it should perform deployments and then, using the same file list, initiate the deployment N times passing in a different src-area (and the same file-list) each time, and checking the results each time. Then it's up to you to decide whether a failure for one branch should be considered a failure for all branches and stop right there, or to track which deployments failed and wait until the end to indicate success / failure.

Any way you go - it's up to you to provide some custom code to managing the process, which means you should do some serious design work before trying to implement it.