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

Get result of Scheduled Deployment

Vishakha

Hi,
We want to track the result of our scheduled deployment. To know whether the deployment completed or failed. However after the schedadd command is executed we can see only the schedule details. This does not solve the purpose as we actually want the deployment result. How can we get it?
We cannot run a DNR as the deployment is getting executed through a external script and it has to get the results and continue with the workflow to send the notification.
Please help...

Find more posts tagged with

Comments

BlueWhale

Hello Vishaka,

How the users are able to schedule a deployment? Is this through a CGI task (to select the date and time)? If so you can have a dummy task which times out when the scheduled deployment task is trigggered. And the scheduled deployment task is going to be a regular external task which runs the deployment and you can capture the result of it.

In order to get specific answer to your question, please elaborate your workflow.

Adam Stoller

Hi,
We want to track the result of our scheduled deployment. To know whether the deployment completed or failed. However after the schedadd command is executed we can see only the schedule details. This does not solve the purpose as we actually want the deployment result. How can we get it?
We cannot run a DNR as the deployment is getting executed through a external script and it has to get the results and continue with the workflow to send the notification.
Please help...

schedadd registers a deployment to be executed at a certain time with a certain repetitiveness - it does not execute the deployment itself, so there are no results to show.
If you have the AdminServer and CSF installed and have OD configured to use a DB for reporting and have reporting enabled on your BaseServer - then you should be able to go through the GUI and look through Reports to find out the results of any scheduled deployments - though you'll have to know which deployment(s) you're looking for because the Reports will not, by itself, distinguish between manually run, workflow run, and/or scheduled deployments.

BusStopChart.zip

Vishakha

Thanks to everyone for your input.
Ghoti, we want to check the results through the script for deployment status emails and hence cannot use the interface approach.
Goverdhan, the task that executes deployments has to deploy multiple files as per their respective scheduled deployment. The dummy task approach would be applicable for a single file deployment.

We have ultimately executed the below approach.
We now execute normal deployments. As we can trace their results. The deployment scheduling is handled at the perl end where the script sleeps for time interval and then gets executed for the scheduled time. This goes on till the file with the latest scheduled time gets deployed.
The only drawback of the approach being that the email notification for deployment status of various files is sent only after the last deployment is done.

Adam Stoller

Thanks to everyone for your input.
Ghoti, we want to check the results through the script for deployment status emails and hence cannot use the interface approach.
Goverdhan, the task that executes deployments has to deploy multiple files as per their respective scheduled deployment. The dummy task approach would be applicable for a single file deployment.

We have ultimately executed the below approach.
We now execute normal deployments. As we can trace their results. The deployment scheduling is handled at the perl end where the script sleeps for time interval and then gets executed for the scheduled time. This goes on till the file with the latest scheduled time gets deployed.
The only drawback of the approach being that the email notification for deployment status of various files is sent only after the last deployment is done.

You could use a DNR script in the deployments that would send email for each deployment - pass a parameter from the workflow into the deployment scheduling process so that the name of the recipient(s) for the email is handed off through the deployment configuration file to the DNR script.