New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 733011 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Last visit > 30 days ago
Closed: Jun 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

setup local autotest in devserver

Project Member Reported by shuqianz@chromium.org, Jun 13 2017

Issue description

Currently, all lab servers have local autotest setup except for devserver. When we push to prod, we are using the script under local autotest to update the servers, and using the shadow_config file to find out which service needs to be restarted. In order to use the existing script and make devserver is consistent with other servers, we need to setup local autotest in devserver too. Two benefits:
1. Do not to rewrite all the push to prod script into server lib tasks from scratch. And there is no unittest for server lib tasks
2. Devserver will have same repo checkouts with other lab servers, which makes the lab consistent 
 
Status: WontFix (was: Started)
Talked with Allen offline, we think this is not a good idea since it only serves for push purpose and it adds extra overhead to repo sync autotest code and run unless update commands like build_externals

Sign in to add a comment