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

The first two easily fixed issues were due to query rules. They received 3 inputs:
a start date,
an end date,
and an array of text fields used for an "IN" clause.

In dev, the array of text fields was multiple, this was correct.
In test and prod the rule had not been copied out and had the array of text fields being fed in to a non multiple text field.

It does not appear that anything is MISSING (other than some testing, but that is a whole other essay.) but the versions/content of some of the rules do not match between servers.

I am looking for a way to identify those sorts of differences between servers so we can handle them beforehand rather than during the deployment which results in on the fly reconstruction of deploy packages.

Version control (other than including everything in a folder in an application, then dependency checking and finally sorting the package by modified date to puzzle out what to include and what not) is desperately needed.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 adamm over 10 years ago

The first two easily fixed issues were due to query rules. They received 3 inputs:
a start date,
an end date,
and an array of text fields used for an "IN" clause.

In dev, the array of text fields was multiple, this was correct.
In test and prod the rule had not been copied out and had the array of text fields being fed in to a non multiple text field.

It does not appear that anything is MISSING (other than some testing, but that is a whole other essay.) but the versions/content of some of the rules do not match between servers.

I am looking for a way to identify those sorts of differences between servers so we can handle them beforehand rather than during the deployment which results in on the fly reconstruction of deploy packages.

Version control (other than including everything in a folder in an application, then dependency checking and finally sorting the package by modified date to puzzle out what to include and what not) is desperately needed.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

No Data