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

..., truncated queries, etc.) and this would not encompass the rules, constants, etc.

Please, are there any recommended techniques to do cross server comparison? Some sort of basic, fundamental version control tools?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 adamm over 11 years ago

..., truncated queries, etc.) and this would not encompass the rules, constants, etc.

Please, are there any recommended techniques to do cross server comparison? Some sort of basic, fundamental version control tools?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

No Data