Update test-results Makefile and README to use gae.py upload |
||||
Issue descriptionNow that test-results has separate Python and Go apps, it can use gae like the rest of our appengine apps. Because gae upload takes care of deploying crons, etc. much of that makefile will probably be able to be replaced with `deploy staging|production`. To deploy to production the command will be `gae.py upload` for staging `gae.py upload test-results-test-hrd`. gae also takes care of version generation. This is important because when I tried to deploy with the current Makefile I ran into many problems. It ended up taking 2+ hours and multiple engineers time to debug.
,
Oct 4 2017
Actually, I can just go ahead and do this. :)
,
Oct 4 2017
,
Oct 4 2017
The following revision refers to this bug: https://chromium.googlesource.com/infra/infra/+/42863f2c1345f4b04f9f7481522743b0ca74249d commit 42863f2c1345f4b04f9f7481522743b0ca74249d Author: Katie Thomas <katthomas@google.com> Date: Wed Oct 04 16:56:50 2017 Update deployment for test-results to use gae Bug:770850 Change-Id: I6baba298701a40d9b62eaf814deec140cf448cb9 Reviewed-on: https://chromium-review.googlesource.com/699739 Reviewed-by: Nodir Turakulov <nodir@chromium.org> Commit-Queue: Katie Thomas <katthomas@google.com> [modify] https://crrev.com/42863f2c1345f4b04f9f7481522743b0ca74249d/go/src/infra/appengine/test-results/Makefile [modify] https://crrev.com/42863f2c1345f4b04f9f7481522743b0ca74249d/go/src/infra/appengine/test-results/README.md
,
Oct 4 2017
|
||||
►
Sign in to add a comment |
||||
Comment 1 by katthomas@chromium.org
, Oct 2 2017