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

Scheduled or Timed Deployment

alanhill

Hi,

I'm no OpenDeploy expert so forgive me for a potentially stupid question - does anyone know of any way to schedule a file (or files) for deployment, so that they don't automatically go in the next scheduled deployment?

Softwaer like Tivoli allows you to schedule a job for a certain date and time and this seems like a big omission for Open Deploy (as I say, I'm no expert so it might be possible and I'm just not aware).

My thought was to put something into the workflow that could allow the business user to choose a deployment slot from a list and then save the details of the job in a db entry or text file. A scheduled job (at job etc) could then run and check which jobs were due for whatever slot was due next. For those jobs it would then put the appropriate files into the staging area, ready for the edition to be created and files deployed.

This way you would avoid having files going live before they were intended, and business wouldn't need to worry about not approving tasks until the last deployment had gone.

Anyone have any experience/hints along these lines?

many thanks

Find more posts tagged with

Comments

Adam Stoller

Hi,

I'm no OpenDeploy expert so forgive me for a potentially stupid question - does anyone know of any way to schedule a file (or files) for deployment, so that they don't automatically go in the next scheduled deployment?

Softwaer like Tivoli allows you to schedule a job for a certain date and time and this seems like a big omission for Open Deploy (as I say, I'm no expert so it might be possible and I'm just not aware).

My thought was to put something into the workflow that could allow the business user to choose a deployment slot from a list and then save the details of the job in a db entry or text file. A scheduled job (at job etc) could then run and check which jobs were due for whatever slot was due next. For those jobs it would then put the appropriate files into the staging area, ready for the edition to be created and files deployed.

This way you would avoid having files going live before they were intended, and business wouldn't need to worry about not approving tasks until the last deployment had gone.

Anyone have any experience/hints along these lines?

many thanks

OpenDeploy does provide a scheduler but it schedules an entire deployment - so if you want to do a filelist deployment you have to schedule the deployment with the filelist and use a unique name per filelist so that you don't deploy files that aren't supposed to be deployed.

Workflows provide "dummytask" elements which can be used to delay execution of the next task until a certain date/time or specified amount of time relative to when the dummytask becomes activated - this can then lead to an externaltask which can create the filelist with the files associated with the workflow and then invoke the deployment.

You can also queue the deployment (again with unique filelist) via 'cron', 'at' or Windows Scheduler if you so choose.

There are a number of ways to do what you want - some are with filelist deployments (as described above) some are with multiple branches and/or workareas in which you "queue" things to go at certain times, others may include metadata, DBs and JSP (or similar) pages that verify that content is allowed to be displayed on the web site before doing so.

CRB

Hi,

My thought was to put something into the workflow that could allow the business user to choose a deployment slot from a list and then save the details of the job in a db entry or text file. A scheduled job (at job etc) could then run and check which jobs were due for whatever slot was due next. For those jobs it would then put the appropriate files into the staging area, ready for the edition to be created and files deployed.

i have seen ,what you are thinking, implemented before... once they finish editing thier files, they select the files then invoke a anpplication "scheduler" that they created (using perl), theyselect date and time when they want to deploy then they submit it to a database... that small application passes the selected files/filelist and the date to the the database, and opendeploy invokes it when it is due...

and i think there are many ways you can do this, you just have to choose the best one based on resources and time available to you.

jsy

Hi .

I am using Teamsite 6.5 and open Deploy 6.0.0. I have a similar senario wherein I want the deployment content to web server at a specified time selected by author .

Here I need to deploy both files and database changes to target server at a selected time.I am using filelist deployment by workflow to deploy content at publish server

So in my workflow when approver approves the content ,publishing of these content should occur at selected time.

Now here I used the above approach of using dummy task with timeout . but the issue i am facing here is that once the dummy task time finishes, user need to manually go and start the next task. My need is that once the time finishes for dummy task next task should authomatically be executed at the specified task. my task senario is like below.

approver task >dummy task > submit task > CGI task (deployment task).

I have set immediate equal to true for CGI task and also the owner of all task are same .still the CGI task is not getting executed automatically .

If any one have worked on such senario . then could you please let me know the approach you have followed for content publish timing. If you have followed the same approach of dummy task then how can we automate the next task execution.

Any thoughts on this would be highly appreciated

GroupDropDown.zip

jsy

I continuation to above query I am attaching the workflow(wft) file. where i have used a dummy task to delay execution of next task

Adam Stoller

I continuation to above query I am attaching the workflow(wft) file. where i have used a dummy task to delay execution of next task

It would be nice if you didn't cross-post.
This post has been responded to within the workflow forum

Your other options, if you don't need the workflow to sit and wait for the deployment to occur, are to use a scheduler - such as the one that comes with OpenDeploy, or at on Unix or WinAt / Windows Scheduler (on Windows ;-)