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

adamm over 10 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 elizabeth.epstein over 10 years ago

When you say "the rule had not been copied out":

a) Can you verify that the updated query rules were in your export/import package? (You can check export-log from when you exported or inspect the zipfile manually.)
b) Can you verify whether or not the updated query rules imported at all? (I.e. new versions were created at Import time.)
c) Did you run package inspection and if so, did it indicate everything would import successfully?

If you are sure that your query rules were in the import package, and appeared to import successfully, but do NOT match the definitions you expect, this sounds like a bug and should be reported through a support case.

If the rules were not in the import package, then either not all suggested dependencies were added, or the dependency wasn't caught by the dependency checker (in some cases that might be a bug). But it would be good to know if this was an export bug, an export configuration-management issue, or an import bug.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 elizabeth.epstein over 10 years ago

When you say "the rule had not been copied out":

a) Can you verify that the updated query rules were in your export/import package? (You can check export-log from when you exported or inspect the zipfile manually.)
b) Can you verify whether or not the updated query rules imported at all? (I.e. new versions were created at Import time.)
c) Did you run package inspection and if so, did it indicate everything would import successfully?

If you are sure that your query rules were in the import package, and appeared to import successfully, but do NOT match the definitions you expect, this sounds like a bug and should be reported through a support case.

If the rules were not in the import package, then either not all suggested dependencies were added, or the dependency wasn't caught by the dependency checker (in some cases that might be a bug). But it would be good to know if this was an export bug, an export configuration-management issue, or an import bug.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

No Data