Web Testing/Automation/automation-05-08-2011: Difference between revisions

Line 14: Line 14:
* Jenkins: we're now launching with java jar -Xms8g -Xmx8g -XX:MaxPermSize=512M jenkins.war, and it's fixed our OOM issues; it just increases the heap allocation
* Jenkins: we're now launching with java jar -Xms8g -Xmx8g -XX:MaxPermSize=512M jenkins.war, and it's fixed our OOM issues; it just increases the heap allocation
** I've documented this: https://wiki.mozilla.org/QA/Execution/Web_Testing/Automation/Selenium_Grid#Starting_Jenkins
** I've documented this: https://wiki.mozilla.org/QA/Execution/Web_Testing/Automation/Selenium_Grid#Starting_Jenkins
* Can someone own trying to figure out how to surpress username/password logging in Jenkins' console output?  I'd like us to at least open-up our CI outside the VPN, or perhaps merge w/Webdev
* Can someone own trying to figure out how to surpress username/password logging in Jenkins' workspace?  I'd like us to at least open-up our CI outside the VPN, or perhaps merge w/Webdev
* We could prioritize code reviews/merges made on pull requests. Refactoring pulls should have a higher priority because they can block writing tests in the refactored area. Also, further refactoring might be needed if a test is merged before a refactoring pull that covers the same area.
* We could prioritize code reviews/merges made on pull requests. Refactoring pulls should have a higher priority because they can block writing tests in the refactored area. Also, further refactoring might be needed if a test is merged before a refactoring pull that covers the same area.
* Update on fixing test execution duration in reports
* Update on fixing test execution duration in reports
Confirmed users
9,511

edits