Starting October 1, App Engine will not allow apps using the 1.9
runtime to be deployed.
In module mode on go111 AppEngine, paths have changed to be relative to
the go.mod file.
More information can be found at
https://cloud.google.com/appengine/docs/standard/go111/go-differences
Change-Id: I3e291f20559ec8d3c5e8f51b756bd3b23b0c70bd
Reviewed-on: https://go-review.googlesource.com/c/build/+/192103
Run-TryBot: Alexander Rakoczy <alex@golang.org>
TryBot-Result: Gobot Gobot <gobot@golang.org>
Reviewed-by: Andrew Bonventre <andybons@golang.org>
This reverts commit CL 190902.
Reason for revert: it breaks deploys due to filesystem changes in go111
Change-Id: Ic357050da2707be1c53d79af6f0062ff4feaffbb
Reviewed-on: https://go-review.googlesource.com/c/build/+/191974
Reviewed-by: Alexander Rakoczy <alex@golang.org>
+ Renames build/ to appengine/ as it contains the main entry point
for the app.
+ Moves app.yaml files to the appengine/ folder as gcloud app deploy
will complain if it can’t find any go files to build in the same
directory as the app.yaml file (previously I think it recursively
looked for them in the directory tree).
+ Update deploy steps in app.yaml.
+ Remove application and version fields in app.yaml as gcloud deploy
doesn’t allow them anymore.
+ Update to use go1.8, including using the context package as
appropriate. In some cases the x/net/context package must be
used to match the function types specified by GAE.
Change-Id: Ib38563ba7245f37de1a2f8d7f034f02c0cd77863
Reviewed-on: https://go-review.googlesource.com/70410
Reviewed-by: Chris Broadfoot <cbro@golang.org>
Alexander Rakoczy
Andrew Bonventre
Andrew Gerrand