grpc / grpc/grpc-java

upload_artifacts.sh is hard to manually test

Offen
#4,576 1 Kommentar 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen
code health
Vorherrschende Sprache
Java
Sterne
12.1k
Forks
4k
Ø Merge
2 T. 17 Std.
Gemergte PRs (30 T.)
37

Beschreibung

Currently it can only be run on Kokoro and only for tagged releases. @zpencer, has a kokoro job that lets him kick off a job against a private (fake) tagged release but this doesn't scale to more users and is slow as it requires building all dependent artifacts.

We need a way to be able to run the majority of the script from our workstations. This is generally not too hard with a little bit of reorganization, with the exception of gpg. While with gnupg 2.x we could leverage the gpg-agent to split kokoro-specific code out, there's not an easy way for gnupg 1.x. We either need to use something similar to the release key for testing or require gnupg 2.x. Since Kokoro is using Ubuntu 14.04 which has gnupg 1.x, we could use a docker container to get gnupg 2.x.

Beitragsleitfaden

Beitragsleitfaden öffnen

Bewertung

Dieses Issue wurde noch nicht bewertet.

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.