Deployment from Dynamically created Editions.

Hi Friends,

I have implemented a workflow which inclueds the following task.

1.Author select a file from workarea and starts the workflow.
2.selected files submitted to the stagin area.
3.Simple perl script creates edition
4.Deployment script deploys the selected files to the web server.i am using filelist deployment here.
5.Author task to do some business operations.

Now my requirement is that If (5)Author task doesnt agree with the deployment,then there will be another external task which will deploy from previous edition.Is it possible to deploy from dynamically created editions?

Please let me know what are the available options to me.
Environment:
TS 671SP1 OD61 on solararis 10
Thanks in advance

Find more posts tagged with

Comments

ISCBorisB

Hi Friends,

I have implemented a workflow which inclueds the following task.

1.Author select a file from workarea and starts the workflow.
2.selected files submitted to the stagin area.
3.Simple perl script creates edition
4.Deployment script deploys the selected files to the web server.i am using filelist deployment here.
5.Author task to do some business operations.

Now my requirement is that If (5)Author task doesnt agree with the deployment,then there will be another external task which will deploy from previous edition.Is it possible to deploy from dynamically created editions?

Please let me know what are the available options to me.
Environment:
TS 671SP1 OD61 on solararis 10
Thanks in advance

Create OD configuration using "-k" named parameter to indicate the Deployment Source.
Then the Deployment Script, External or CGI Task may figure out required Deployment
Source on the fly an execute OD providing needed "-k" Value

nipper

I would rethink your approach. I am not a fan of potentially having the production server different from what is in Staging.

If you walk a few jobs through in your head (I change foo it get submitted and Bo rejects it. Someone else changes foo, my changes are still there - then you are screwed - either everything is rejected or my changes go out)

Garner all of your approvals first, then submit and deploy.

vikasp

I would rethink your approach. I am not a fan of potentially having the production server different from what is in Staging.

If you walk a few jobs through in your head (I change foo it get submitted and Bo rejects it. Someone else changes foo, my changes are still there - then you are screwed - either everything is rejected or my changes go out)

Garner all of your approvals first, then submit and deploy.

Thanks for your reply.I know the approach is not good but client was asking for the same.

nipper

Thanks for your reply.I know the approach is not good but client was asking for the same.

I do not care. The client is asking for something that will, I guarantee, break. And when it does it will not be pretty.

If you want to play in this space you need to be able to explain to the customer why that approach is bad and propose alternatives that still meet their needs, but will not cause long term problems.

Migrateduser

That might be difficult when your client is in a different country and you have no direct line of communication. Hypothetically, of course...

You get what you pay for.

nipper

That might be difficult when your client is in a different country and you have no direct line of communication. Hypothetically, of course...

You get what you pay for.

Good point, when it does break it wil be a great opportunity for someone like me to come in and fix it.

Migrateduser

Good point, when it does break it wil be a great opportunity for someone like me to come in and fix it.

Ahhh, the circle of life. Hakuna Matada!

vikasp

I do not care. The client is asking for something that will, I guarantee, break. And when it does it will not be pretty.

If you want to play in this space you need to be able to explain to the customer why that approach is bad and propose alternatives that still meet their needs, but will not cause long term problems.

Hi nipper,
Thanks for your reply.I have explain client about the same and he is agree now.

vikasp

Is it possible to deploy from previous edition in filelist deployment?
Any pointers on the same will help.

Adam Stoller

Is it possible to deploy from previous edition in filelist deployment?
Any pointers on the same will help.

Care to expand on what you're trying to do, and how you're trying to do it - e.g.: show some of the XML deployment configuration code (properly formatted!)?

Migrateduser

Is it possible to deploy from previous edition in filelist deployment?
Any pointers on the same will help.

It's deja vu all over again. Post #2 gave you the answer when you asked the first time.