Creating a deployment command on the fly

We have a cgi that's called from a custom menu item that we're trying to rewrite as it's a bit out-dated. It is a script that deploys selected files out. It uses iwodstart to run the deploy.

I know about using the iwodstart command for an existing deploy to kick it off and use an existing deployment definition. Is there a way to deploy via the command-line without an existing config file? If not, I would assume I could write the xml file to a temp file and call it with a command-line arguement.

Has anyone done anything similar to this?

TS 6.7.1 / OD 6.1.1 on Linux

Find more posts tagged with

Comments

Bill Klish

Wouldn't this just be a file list deployment, where your menu item writes the selected files out to a temp file which becomes the file list for the deployment?

dlsoderberg

Yes, but it can also be an edition deploy, as well. There is currently a deploy config file that is extrememly large that lists all of the deployment definitions. We're trying to rewrite this so that the maintanance on that file is eliminated, and the cgi will build the target path on the fly based on the current branch path. I just wasn't sure if iwodstart is the only option for the command line call, and if there was a way to do it without the deployment config file.

Adam Stoller

Yes, but it can also be an edition deploy, as well. There is currently a deploy config file that is extrememly large that lists all of the deployment definitions. We're trying to rewrite this so that the maintanance on that file is eliminated, and the cgi will build the target path on the fly based on the current branch path. I just wasn't sure if iwodstart is the only option for the command line call, and if there was a way to do it without the deployment config file.

Well you should probably switch from iwodstart to iwodcmd start and you should add parameters to your configuration which you can then supply on the command line with -k flags - e.g.:

For some of this you have to make sure you're using the 6.x DTD for the configuration files instead of the 5.x DTD (OD6 accepts both, but the newer features are only available in the 6.x DTD).