Skip to Content.
Sympa Menu

grouper-users - RE: [grouper-users] patching the UI with grouperInstaller

Subject: Grouper Users - Open Discussion List

List archive

RE: [grouper-users] patching the UI with grouperInstaller

Chronological Thread 
  • From: Chris Hyzer <>
  • To: Andrew Morgan <>
  • Cc: John Gasper <>, "" <>
  • Subject: RE: [grouper-users] patching the UI with grouperInstaller
  • Date: Fri, 20 Feb 2015 19:47:36 +0000
  • Accept-language: en-US

Yeah, we have 4 UI and WS servers at Penn... I patch one and rsync the webapp
dir to the others. I agree that patching individual servers is not ideal :)
But I hear you on wanting to build... theres a jira :)


-----Original Message-----
From: Andrew Morgan

Sent: Friday, February 20, 2015 2:45 PM
To: Chris Hyzer
Cc: John Gasper;

Subject: RE: [grouper-users] patching the UI with grouperInstaller

On Fri, 20 Feb 2015, Chris Hyzer wrote:

> There are pros and cons to both approaches… Im not saying there is no
> value in your approach, but with the current strategy you can patch a UI
> without having to do another build. Therefore only a very small change
> will be made to the system which reduces risk in my opinion. You don’t
> have to worry about doing a build and overwriting a prior patch or doing
> something else unintended. I don’t think one is best, if the current
> way fits in your deployment model, I think you will have less risk. If
> not, then you have to do it the other way ☺ This isn’t a trivial
> change, will need to look into it.

I can see both ways being useful, maybe at different scales or deployment
models. Here at OSU we have 2 frontend servers. I prefer to patch the
base directory and then build the WAR. That way I can deploy an identify
WAR on both servers. I'd like the patches and the upgrades to work the
same way.


Archive powered by MHonArc 2.6.16.

Top of Page