2 DnRs one after another

Greetings all,
I know it is possible to have two DnRs run, however my question is whether you can have one invoke the other or start when the other is done. I.E. Grab source code and once finished do a compile then deploy. Any help would be greatly appreciated.

--Jum

Find more posts tagged with

Comments

tvaughan

Yeah, what you describe is possible.

You could do something like this: create a reverse deployment to go grab some source code and bring it in to your OD base.

Following a succesful reverse deployment, run a DNR script that first compiles the code using ant or javac or what-have-you, then starts another process (an iwodstart process) to deploy the result of your compilation.

It wouldn't really be "two DNR scripts", it would just be 1 DNR script that executes 2 processes back-to-back. These DNR scripts can really be as complicated as you want.

Tom

Jumjum

Thanks Tom,
But clarify, I want to accomplish the following:
I have VSS that when I run a deploy, I use the cmd line to get the lastest(if any) using DnR. Then immediately following the end of the first DnR, I want to compile what is there. So in other words, sleep in between the two processes to give the first DnR a chance to finish.

Thanks,
Jum

tvaughan

Your VSS is running on a different box that your OD base, I assume?

So, when you run your initial deployment to the VSS box, what is it that you're deploying? Are you just doing a "nonsense deployment" to your VSS box expressly for the purposes of utilizing the DNR command?

Anyway, I'd develop your DNR script first and see if it works. It'll probably have the 'checkout' command to get the latest code, listen on the output stream of that checkout command, then issue the compile command once the checkout command reports some sort of 'completed' string.

I'm speaking mostly in terms of Perl here, but any 3GL language should be able to connect to a command-line process and grab the output string for processing. So, in CVS, for example, you might have your DNR script wait until it sees the string "Checkout complete." or 600 seconds, whichever is first.

Tom

Jumjum

Thank you Tom,
This is exactly what I am looking to do. I have already successfully had the the DnR perform the VSS update and am trying to get it to compile. I will give this a go. Thanks again.

-Jum

--Jum

Adam Stoller

FYI: OpenDeploy 5.6 will provide much more flexibility in defining when a DNR is to run (I think there will be 6 different possibilities) - so you might be able to use these options to specify:
a DNR to run before the deployment ever begins (dnrDeploymentJob when="before" ...)
another DNR to run prior to the connection taking place (dnrDeployment triggerPoint="connect" when="before" ...)

Although, if both activities are happening on the same side of the deployment, and you want one activity to occur after the other - you could just combine the two activities into one script - or (though not as efficient) - have the one DNR script call the other script.

--fish
(Interwoven Senior Technical Consultant)