When creating rice-2.5 Jenkins jobs, lets start all the test jobs with rice-2.5-test so they are all grouped together on UI.
rice-2.5-test-integration- (daily email job, jobs broken up by rice project as in http:rice-2.5-test-functional- (selenium, ideally only Bookmark tests)
rice-2.5-test-functional-saucelabs- (selenium on saucelabs nightly only, ideally only Nav tests, include ext-email)
For the test jobs that deploy envs, have them run only a login test to verify the app has deployed before launching other test jobs.
Drop -freestyle from test names, there are no non-freestyle test jobs anymore.