-
Notifications
You must be signed in to change notification settings - Fork 482
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
7417 - Update to Payara 5.2020.6 #7419
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I found a few more places where we should update Payara. Please see the comments I left.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
At this point I think we've identified all the instances of .2 that need to be changed to .6 but I added an additional question about upgrade docs. Basically, are we ok with linking to the official Payara docs or would it be better to write our own steps?
Co-authored-by: Philip Durbin <philip_durbin@harvard.edu>
@poikilotherm @pdurbin Tested upgrade, used backup/restore domain method. Needs an additional step for Dataverse to run: copy postgres driver from old payara to new payara glassfish/lib dir. Should this go in release notes or will it be handled by the downstream pr? Putting back into Review for comment. |
Well as the next PR about moving the Postgres driver into the WAR is already done #7420 and just waiting for review, I vote for not including a hint about that. |
So you would not confirm the upgrade worked before deploying the new war? I suppose it doesn't matter but wanted to ask. Game on! |
What this PR does / why we need it:
Stability, security, bug fixes. Good thing, aren't they? Grateful for having them now after the dark days of Glassfish 4.1
Which issue(s) this PR closes:
Closes #7417
Special notes for your reviewer:
Dunno?
Suggestions on how to test this:
Follow the instructions to update. They take extreme precautions that might not be necessary, but better safe than sorry.
Does this PR introduce a user interface change? If mockups are available, please link/include them here:
Nope.
Is there a release notes update needed for this change?:
🔋 included.
Additional documentation:
Nada.