qbit/go
1
0
Fork 0
mirror of https://github.com/golang/go synced 2024-11-05 17:16:10 -07:00
Code Releases Activity
f7b8cc7bd0
go/gopls/integration/govim
History
Rob Findley 4abfd4a162 gopls/integration/govim: switch to latest, and improve artifacts 
Now that there is a tagged version of govim containing the `-gopls` test
flag, we can just use latest to pick up a relatively stable govim, and
not have to maintain the govim version.

Doing this required changing the way we fetch govim into our test
harness: there is now the assumption that /src/govim is a git
repository, so we clone using git.

Along the way, clean up some unnecessary artifacts and add a script for
downloading artifacts from GCS.

Change-Id: I6ef4dd468d6b9baf66d3adae3f1fb80c12ac9578
Reviewed-on: https://go-review.googlesource.com/c/tools/+/217730
Reviewed-by: Rebecca Stambler <rstambler@golang.org>
2020-02-05 14:18:39 +00:00
..
artifacts.go gopls/integration/govim: switch to latest, and improve artifacts 2020-02-05 14:18:39 +00:00
cloudbuild.harness.yaml gopls/integration/govim: switch to latest, and improve artifacts 2020-02-05 14:18:39 +00:00
cloudbuild.yaml gopls/integration/govim: switch to latest, and improve artifacts 2020-02-05 14:18:39 +00:00
Dockerfile gopls/integration/govim: switch to latest, and improve artifacts 2020-02-05 14:18:39 +00:00
README.md gopls/integration/govim: switch to latest, and improve artifacts 2020-02-05 14:18:39 +00:00
run_local.sh gopls/integration/govim: update build steps to capture artifacts 2020-01-15 14:49:07 +00:00
run_tests_for_cloudbuild.sh gopls/integration/govim: switch to latest, and improve artifacts 2020-02-05 14:18:39 +00:00

README.md

govim integration tests

Files in this directory configure Cloud Build to run govim integration tests against a gopls binary built from source.

Running on GCP

To run these integration tests in Cloud Build, use the following steps. Here we assume that $PROJECT_ID is a valid GCP project and $BUCKET is a cloud storage bucket owned by that project.

  • cd to the root directory of the tools project.
  • (at least once per GCP project) Build the test harness:
$ gcloud builds submit \
	--project="${PROJECT_ID}" \
	--config=gopls/integration/govim/cloudbuild.harness.yaml \
	--substitutions=_RESULT_BUCKET="${BUCKET}"
  • Run the integration tests:
$ gcloud builds submit \
	--project="${PROJECT_ID}" \
	--config=gopls/integration/govim/cloudbuild.yaml \
	--substitutions=_RESULT_BUCKET="${BUCKET}"

Fetching Artifacts

Assuming the artifacts bucket is world readable, you can fetch integration from GCS. They are located at:

  • logs: https://storage.googleapis.com/${BUCKET}/log-${EVALUATION_ID}.txt
  • artifact tarball: https://storage.googleapis.com/${BUCKET}/govim/${EVALUATION_ID}/artifacts.tar.gz

The artifacts.go command can be used to fetch both artifacts using an evaluation id.

Running locally

Run gopls/integration/govim/run_local.sh. This may take a while the first time it is run, as it will require building the test harness. Currently this script assumes that docker may be executed without sudo.