Deploying files using a perl script

hi All,

I am quite new to Teamsite. My problem is quite specific to deployments using a new job workflow. Is it possible to write some sort of script for the same using perl to handle heavy deployments? Any suggestions are welcome.

Thanks
mazumbha

Find more posts tagged with

Comments

Adam Stoller

hi All,

I am quite new to Teamsite. My problem is quite specific to deployments using a new job workflow. Is it possible to write some sort of script for the same using perl to handle heavy deployments? Any suggestions are welcome.

Thanks
mazumbha

Generally speaking, it's possible to do pretty much anything.

Specifically speaking:

mazumbha

hi,

I use teamsite 6.5.
Heavy deployments implies deploying files (mostly the same named files) from different subbranches.
In order to deploy, I use opendeploy. But i have a script that initates a job workflow which ultimately deploys using opendeploy. The task involves some manual tasks of approving the deployment to staging and then live servers.
The workflow files(.wft's) are written in PERL only.
I will give you an example:
If i have to delploy a file called test.asp lying in a workarea, I will check the file, click on actions->New Job. The new job option is active only for specific areas where deployments happen using these workflows. The reason is unknown to me. Moving on, I get a pop up where i select the assign-approve option and the details of the file, select the approver. Then i initiate the workflow. It is visible under the workflow tab. i then approve the job and the file gets deployed. This is a gist of what i follow to deploy files. Now, if there are many files that i have to deploy in different branches, it becomes a tidious task to do deployments. I plan to use some kind of script where, i input the path of the file in teamsite and the server path where the file has to be deployed. Any suggestions are welcome.

Regards
mazumbha

kaalraa

hi,
The new job option is active only for specific areas where deployments happen using these workflows. The reason is unknown to me.

Open your available_templates.cfg and check the workflow assigned to which all branches. If you need the workflow to be initiated from any branch put regex as .*

Moving on, I get a pop up where i select the assign-approve option and the details of the file, select the approver. Then i initiate the workflow. It is visible under the workflow tab. i then approve the job and the file gets deployed. This is a gist of what i follow to deploy files. Now, if there are many files that i have to deploy in different branches, it becomes a tidious task to do deployments. I plan to use some kind of script where, i input the path of the file in teamsite and the server path where the file has to be deployed. Any suggestions are welcome.

Can you attach your perl script along with your config file being in use for OpenDeploy?

jkm

hi,

Now, if there are many files that i have to deploy in different branches, it becomes a tidious task to do deployments. I plan to use some kind of script where, i input the path of the file in teamsite and the server path where the file has to be deployed. Any suggestions are welcome.

Regards
mazumbha

Do you mean here multiple source branches and multiple destinations nodes which you want to choose in your script.

If you have only multiple source branches that you can always get easily using areavpath paramter in the workflow.

report.zip

Adam Stoller

[...] Now, if there are many files that i have to deploy in different branches, it becomes a tidious task to do deployments. I plan to use some kind of script where, i input the path of the file in teamsite and the server path where the file has to be deployed. Any suggestions are welcome.

Regards
mazumbha

A workflow task is tied to a specific areavpath - so you cannot (easily) have one workflow that deploys files from multiple branches.

A deployment configuration, similarly, is usually intended to deploy files from one specified source area to one specified target area - however you can create multiple deployment definitions with different source/target area specifications and multiple execDeploymentTask's to initiate multiple concurrent deployments of various files from various source areas to various target areas - however I would classify this as "complex" without knowing more about the design / requirements.

I think you need to spend a bit more time with the manuals to try to gain a better understanding of both workflow and OpenDeploy before trying to do what you seem to be indicating you want to do.