[Chromoting] Set ar_service_environment for Official builds

remoting/app_remoting_webapp_build.gypi

 # Copyright 2014 The Chromium Authors. All rights reserved.
 # Use of this source code is governed by a BSD-style license that can be
 # found in the LICENSE file.
 
 {
   'includes': [
     'remoting_version.gypi',
     'remoting_locales.gypi',
     'remoting_webapp_files.gypi',
     'app_remoting_webapp_files.gypi',
   ],
 
   'variables': {
     'chromium_code': 1,
 
     'run_jscompile%': 0,
 
     # This variable is used to define the target environment for the app
     # being built.  The allowed values are dev, test, staging, and prod.
     'ar_service_environment%': 'dev',

[garykac, 2015/01/28 16:48:23]

FYI: original def for ar_service_environment

[weitao, 2015/01/28 17:47:25]

Can conditions be embedded in the variables section? If so I think it is more
clear initialize ar_service_environment to the correct value here.

[garykac, 2015/01/28 18:25:55]

Done.

   },  # end of variables
 
   'target_defaults': {
     'type': 'none',
 
     'dependencies': [
       # TODO(wez): Create proper resources for shared-stub and app-specific
       # stubs.
       '<(DEPTH)/remoting/remoting.gyp:remoting_resources',
     ],
@@ skipping 52 matching lines @@
         'action_name': 'Build ">(ar_app_name)" application stub',
         'inputs': [
           '<(DEPTH)/remoting/webapp/build-webapp.py',
           '<(chrome_version_path)',
           '<(remoting_version_path)',
           '<@(ar_webapp_files)',
           '<@(remoting_webapp_locale_files)',
           '<@(ar_generated_html_files)',
           '<(ar_app_manifest_app)',
           '<(DEPTH)/remoting/<(ar_app_manifest_common)',
-       ],
+        ],
         'outputs': [
           '<(output_dir)',
           '<(zip_path)',
         ],
         'action': [
           'python', '<(DEPTH)/remoting/webapp/build-webapp.py',
           '<(buildtype)',
           '<(version_full)',
           '<(output_dir)',
           '<(zip_path)',
@@ skipping 61 matching lines @@
         # Normally, the app-id for the orchestrator is automatically extracted
         # from the webapp's extension id, but that approach doesn't work for
         # dev webapp builds (since they all share the same dev extension id).
         # The --appid arg will create a webapp that registers the given app-id
         # rather than using the extension id.
         # This is only done for Dev apps because the app-id for Release apps
         # *must* match the extension id.
         'variables': {
           'remoting_app_id': ['--appid', '>(_app_id)'],
         },
+      }, {  # buildtype != 'Dev'
+        'variables': {
+          'ar_service_environment': 'prod',
+        },
       }],
     ],  # conditions
   },  # target_defaults
 }