-
Notifications
You must be signed in to change notification settings - Fork 385
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
CLDR-17288 vagrant/ansible: fix for openliberty / mysql #3420
Conversation
Notice: the branch changed across the force-push!
~ Your Friendly Jira-GitHub PR Checker Bot |
Notice: the branch changed across the force-push!
~ Your Friendly Jira-GitHub PR Checker Bot |
Hooray! The files in the branch are the same across the force-push. 😃 ~ Your Friendly Jira-GitHub PR Checker Bot |
Hooray! The files in the branch are the same across the force-push. 😃 ~ Your Friendly Jira-GitHub PR Checker Bot |
- also up machine size to 8G
- was ignored since CLDR-14757
Hooray! The files in the branch are the same across the force-push. 😃 ~ Your Friendly Jira-GitHub PR Checker Bot |
Notice: the branch changed across the force-push!
~ Your Friendly Jira-GitHub PR Checker Bot |
Notice: the branch changed across the force-push!
~ Your Friendly Jira-GitHub PR Checker Bot |
Notice: the branch changed across the force-push!
~ Your Friendly Jira-GitHub PR Checker Bot |
- relates some to CLDR-16735
Notice: the branch changed across the force-push!
~ Your Friendly Jira-GitHub PR Checker Bot |
Notice: the branch changed across the force-push!
~ Your Friendly Jira-GitHub PR Checker Bot |
@btangmu I'm wondering if a better way to go about this would be to actually provision and setup an azure machine as part of the testing. then we could run tests against it, and then shut it down. This could let us even spin up a new machine on request for testing. I'll try using docker, though. |
"actually provision and setup an azure machine as part of the testing" -- do you mean to integrate github with azure? |
Notice: the branch changed across the force-push!
~ Your Friendly Jira-GitHub PR Checker Bot |
@btangmu 'testprovision' now succeeds and prints:
Please review and then we can manually try |
- Ref: CLDR-17297 for future enablement
Notice: the branch changed across the force-push!
~ Your Friendly Jira-GitHub PR Checker Bot |
- this affects new ST setups only. Would fail the first time only, each time.
- finally document how to deploy locally, no tomcat anymore! - This encompasses CLDR-17279
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.
LGTM except ourConn.commit() removal -- some callers use getDBConnection not getAConnection
- XPathTable should be called with an autoclose connection only
CLDR-17288
Discussion: https://github.com/orgs/community/discussions/73013
ALLOW_MANY_COMMITS=true