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

Opendeploy success or failure msg

developer2008

Hi All,

Recently I added a new workflow to deploy the files to dev,qa and prod envs in a single go. Now my question is there any way to display a message box or something to let the user know about the failure or success of the 3 deployments.Please help.

Thanks.

Find more posts tagged with

Comments

Adam Stoller

Hi All,

Recently I added a new workflow to deploy the files to dev,qa and prod envs in a single go. Now my question is there any way to display a message box or something to let the user know about the failure or success of the 3 deployments.Please help.

Thanks.

One might question the logic behind deploying to all three environments in a single go - since one would assume that the reason behind dev and qa is to verify changes before releasing them to prod.

Or are you just expressing yourself poorly?

Continuing on my understanding of what you've stated: A single deployment configuration file that performs a fan-out deployment to three different environments at once - if it is transactional, then it's all-or-nothing and you don't have to worry about distinguishing between success/failure for the different environments; if it's non-transactional then you either need to use a DNR script or process the log files - determining the log files to look at is not simplistic, if you use a DNR you'll still have to do something to retrieve the results of the DNR after the fact - so there's a lot of context missing as well.

developer2008

Thanks for the reply. If I was not clear here is what I did.

We already have 3 workflows each for dev ,qa and prod separately. Our creative team requested that if we can deploy to all envs ina single click then it would be less pain. So I wrote a 4th workflow to do the same. It is non transactional.

My question is we get the order status at the end of each deployment, right? Is there a way to display this to the CC user in some form so that they know whether it is a success or not without going through the log files. (like an alert message box)

Adam Stoller

Thanks for the reply. If I was not clear here is what I did.

We already have 3 workflows each for dev ,qa and prod separately. Our creative team requested that if we can deploy to all envs ina single click then it would be less pain. So I wrote a 4th workflow to do the same. It is non transactional.

My question is we get the order status at the end of each deployment, right? Is there a way to display this to the CC user in some form so that they know whether it is a success or not without going through the log files. (like an alert message box)

It's still not clear to me.

nipper

It's still not clear to me.
Does it really make sense to deploy to all three environments concurrently without any sense of review and/or validation before going to the next environment?

Why of course it makes sense. Why bother with the tedious reviews. We move at the speed of the web, send it out and if something incorrect goes you can always pull it back.

You are still living in the 90's Adam.

Smiley Very Happy

Sarang

I would prefer doing this as follows :
1. Make out the log files for individual deployment,
2. Read the log file and check for the word Success / ERROR in the log files.
3. Use that as a indicator for displaying deployment success/failure in custom CGI.

Sarang

Migrateduser

This is one of the weirder threads I've seen in a long time, and that's saying something. Very entertaining, though.

Going to go make out with the log files now...

developer2008

Wow you are finding this entertaining and weird and what not.

Never mind I will try once again. I am looping through for the 3 servers and pass the parameters for destination directories and nodes using a single configurtion file . After checking the odstatus as success I am deploying the files to next env.

Thanks Sarang. I will try to do that and Thanks to Ghoti too.

Adam Stoller

Wow you are finding this entertaining and weird and what not.

Never mind I will try once again. I am looping through for the 3 servers and pass the parameters for destination directories and nodes using a single configurtion file . After checking the odstatus as success I am deploying the files to next env.

Thanks Sarang. I will try to do that and Thanks to Ghoti too.

Okay - this is clearer now.
I assume you're using some form of script that does the looping - yes?
If so - the logic is pretty simple:

specify the questions you have regarding this setup.

report.rptdesign