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

Calling a batch file with opendeploy after the deployment succeeds

System

Hi all,
I have briefly been searching on this. Basically I am deploying some web content (no templates) from a TeamSite 6.5 SP3 with OpenDeploy 6.1.1. I am deploying it to 3 environments TEST, QA, and PROD. Since most of the content is flat it's no big deal. However their are some files (web.config, some ini files, ect) that are environment specific. What I was hoping to do was deploy the content and have opendeploy run a little batch file after the success that would rename one of the 3 config files to be the environment file. I have the batch file and it works just fine. I just need to kick it off. I guess I could run a scheduled task but I would rather not. Soooo..... seeing how I am not a developer does anyone have some code I could steal? Pretty Please? I am guessing that this is payload or deploy and run? I just can't make sense of it. Thanks for your help in advance!

Find more posts tagged with

Comments

brizrobbo

As far as I know, the best way to do this is to use a dnrDeploymentJob element.

Example code:


<deployment transactional="yes">
  <dnrDeploymentJob  location="source" when="after" state="success">
      <script  cmd="/export/home/usr1/scipts/yourscript"
               as="usr1"
               async="no"
               />
  </dnrDeploymentJob>
  <execDeploymentTask useDefinition="edition">
  </execDeploymentTask>
</deployment>

The

state="success"

attribute is valuable, as it means that your batch won't run if the deployment didn't work.

Adam Stoller

As far as I know, the best way to do this is to use a dnrDeploymentJob element.

Example code:
<deployment transactional="yes">
  <dnrDeploymentJob  location="source" when="after" state="success">
      <script  cmd="/export/home/usr1/scipts/yourscript"
               as="usr1"
               async="no"
               />
  </dnrDeploymentJob>
  <execDeploymentTask useDefinition="edition">
  </execDeploymentTask>
</deployment>
The
state="success"
attribute is valuable, as it means that your batch won't run if the deployment didn't work.

I'm not sure if you want the dnrDeploymentJob before he execDeploymentTask - but that point is probably moot as I don't think a dnrDeploymentJob directive will do the trick here - since I'm assuming the files need to be renamed on the target (not source) side of the deployment, and dnrDeploymentJob's only run on the source side.

A regular dnrDeployment [no "Job"] should do the trick though - along the same lines as the above but like so:[html]

<script cmd="..." .../>

[/html]