Ahampton updates #16
Open
Ahampton updates #16
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ibility_fix selenium upgrade compatibility fix
fix platform type issue due to selenium upgrade
- Bumped up to Java 8 - Added new task to dynamically spin up nodes as needed instead of just at the beginning of a run - Improved automation status page to include the Instance ID in the node metadata - Tweaked startup times for the various Tasks - Added logic to handle terminating nodes with hung sessions - Increased lookback window to terminate orphaned nodes
Unit test fixes
- Updated readme to reflect minor updates - Added Maven Enforcer Plugin to prevent dependency convergence issues
Improving ad-hoc scale logic
Modifies AwsVmManager in the following ways: - CHROME_THREAD_COUNT becomes non-final. - FIREFOX_IE_THREAD_COUNT becomes non final. New values are applied at runtime if the awsProperties contain keys like: - node_max_processes_chrome=8 - node_max_processes_firefox=1
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adding support for the ratio of browsers to EC2 host instances to be configurable. Previously the ratios were hard-coded at 5 chrome instances per host and 1 firefox instance. Some users/organizations may want to change this ratio. The previous behavior remains the default.
New values are applied at runtime if the awsProperties contain keys like:
Example config might look like:
node_max_processes_chrome=8
node_instance_type_chrome=c4.large
node_max_processes_firefox=1
node_instance_type_firefox=t2.small
node_instance_type_internetexplorer=t2.small
`