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

OD- DNR with multiple execDeploymentTasks

fuzzy

could someone check the configuration files bellow and let me know if there is any way arround my problem?
regards
from old OD (4.5.1)

deployment=docs_and_src
remote_server=otherserver
remote_port=1701
area=//IWSERVER/default/main/www/area/EDITION/editionnum
local_directory=.
remote_directory=/otherareacontent/deploy
;
area=//IWSERVER/default/main/www/otherarea/EDITION/editionnum
local_directory=live
remote_directory=/otherareacode/deploy
;
deploy_run_script=before_deploy_cmd.sh
as=root
when=server_before_deploy on_success
;
;

in the 5.5.2 if you look bellow for the deploy and run section, it will run on success of the code deployment, even if the content part was not successfull.
is there a way arround this? only executing if both definitions are successfull

<definition name="content">
<source>
<sourceFilesystem area="/default/main/www/area/EDITION/editionnum">
<pathSpecification>
<path name="."/>
</pathSpecification>
</sourceFilesystem>
</source>
<target useReplicationFarm="otherserver">
<comparisonRules dateDifferent="yes"/>
<targetFilesystem area="/contentarea/deploy"/>
</target>
</definition>
<definition name="code">
<source>
<sourceFilesystem area="/default/main/www/another_area/EDITION/another_edition">
<pathSpecification>
<path name="live"/>
</pathSpecification>
</sourceFilesystem>
</source>
<target useReplicationFarm="otherserver">
<targetFilesystem area="/digitalservice/icommerce/src/deploy"/>
</target>
</definition>
<deployment name="docs_dynamo_metadata" transactional="no">
<execDeploymentTask useDefinition="content"/>
<execDeploymentTask useDefinition="code">
<deployNRun >
<dnrDeployment location="target" when="before" state="always" >
<script cmd="before_deploy_cmd.sh" as="root" async="no" />
</dnrDeployment>
</deployNRun>
</execDeploymentTask>
</deployment>

Find more posts tagged with

Comments

Adam Stoller

Unfortunately, in OpenDeploy 5.5.1 I do not believe you can remedy this situation.

Fortunately, OpenDeploy 5.6 will soon be released - and contains a rich set of "trigger points" for DNR scripts that will allow you to specify this more accurately.

--fish
(Interwoven Senior Technical Consultant)

fuzzy

So as I understand it the functionality that was in OD4.5.1 is no longer available in OD 5.5.1 (executing deployment scripts )

Adam Stoller

Pardon the double-negative, but I did NOT say you could NOT execute DNRs in OpenDeploy 5.5.1 - I said you didn't have as much control over when the DNR script is executed.

In OpenDeploy 4.x the deployment processes were serialized so specifying a DNR after the last deployment specification meant that it only ran when that part of the deployment ran, which wouldn't happen if the previous deployment failed.

In OpenDeploy 5.x the deployment processes are running concurrenly, and thus the 4.x semantics of DNRs stopped being sufficient for what you are asking.

OpenDeploy 5.6 fixes this by expanding the ability to specify when a DNR should be executed.

--fish
(Interwoven Senior Technical Consultant)