We had a failed deploy last night. At minimum, we have at least 2 rules whi

adamm over 11 years ago

We had a failed deploy last night.
At minimum, we have at least 2 rules which were correct in our dev environment, but which did NOT get moved to test and from there to production in addition to other conditions that led to an abort. This is not the first time we have had deploy issues occur like this.

In short, I am looking for a way to compare between servers. Rules, models, applications, data stores, data structures (CDTs), everything.

* Version numbers are not maintained between imports. (dev version 21 when first moved to test becomes version 1 there)

* The import/export packages contain too much "meta data" that is different between the servers to do a comparison, though a script could be written to strip datetimes, non matching version numbers etc. out.

Exporting the "View documentation" pages of models and comparing those between servers is not an option either because of the elements that are dropped from those (timers in start nodes...

Discussion posts and replies are publicly visible

Parents

0 adamm over 11 years ago

a) the updated query rules were NOT in the export package from dev to test. That is the problem.

the move from Dev to Test that should have included these were overseen and run by people from Appian and they followed the model described by stefanh791. We saw issues even during that deploy where included dependencies were not caught (that has nothing to do with this issue in particular though.)

I have conceded that there is no better way to build packages, but I am not looking for that as such, or even as stefanh791 called it '"real" configuration management'.

I am looking for a way to compare what is on server (rules, models, constants, etc.) A to what is on server B.

Yes this is in the interest of supporting deploys but it would be useful for a great number of other purposes (comparing dev/test/qa/prod configurations comes to mind with a 2 second thought)

When I put that same question to the consultants (when we had similar issues during that first deploy), they seemed puzzled at why I would even ask it, but then saw what I meant after encountering the real world experience. I feel I am failing to ask the question in a meaningful way. I will try to devise another phrasing.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 adamm over 11 years ago

a) the updated query rules were NOT in the export package from dev to test. That is the problem.

the move from Dev to Test that should have included these were overseen and run by people from Appian and they followed the model described by stefanh791. We saw issues even during that deploy where included dependencies were not caught (that has nothing to do with this issue in particular though.)

I have conceded that there is no better way to build packages, but I am not looking for that as such, or even as stefanh791 called it '"real" configuration management'.

I am looking for a way to compare what is on server (rules, models, constants, etc.) A to what is on server B.

Yes this is in the interest of supporting deploys but it would be useful for a great number of other purposes (comparing dev/test/qa/prod configurations comes to mind with a 2 second thought)

When I put that same question to the consultants (when we had similar issues during that first deploy), they seemed puzzled at why I would even ask it, but then saw what I meant after encountering the real world experience. I feel I am failing to ask the question in a meaningful way. I will try to devise another phrasing.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

No Data