search

rbeckman-nextgen / test-mc6

0 stars 0 forks source link

Make the global deploy and shutdown scripts run per channel, similar to how the global preprocessor and postprocessor works #3274

Open rbeckman-nextgen opened 4 years ago

rbeckman-nextgen commented 4 years ago

This means that the global deploy and shutdown scripts will have access to the global channel map and whatever other scope variables that the channel deploy and shutdown scripts have.

Imported Issue. Original Details: Jira Issue Key: MIRTH-3397 Reporter: wayneh Created: 2014-08-11T17:38:37.000-0700

rbeckman-nextgen commented 4 years ago

-The global deploy and shutdown scripts now run for each channel independently, similar to how the global preprocessor and postprocessor works. This will require users migrate their code.-

Currently though I am not stopping the deploy task if an error occurs from the global deploy script, even though we do stop the deploy if an error occurs on the channel deploy script. I'm not sure which is really correct since no one is really expecting a channel to fail to deploy if the global deploy script fails currently.

Imported Comment. Original Details: Author: wayneh Created: 2014-08-11T20:10:53.000-0700

rbeckman-nextgen commented 4 years ago

Deferring this possible change down the line. MIRTH-3312 is a possible sister change.

Imported Comment. Original Details: Author: wayneh Created: 2014-08-12T17:03:58.000-0700

rbeckman-nextgen commented 4 years ago

Not sure when we can feasibly make this change. Migration is always going to be an issue but currently MIRTH-2913 is dependent on it. We could explore other ways of accomplishing MIRTH-2913 without the need for this such as creating a job pane that shows all instances of the global scripts that are running and kill them from there.

Imported Comment. Original Details: Author: wayneh Created: 2015-01-08T14:36:38.000-0800