grpc-java

Commit Graph

Author	SHA1	Message	Date
Eric Anderson	142851dcbb	buildscripts: Use full SHA for protobuf download Github used to produce tars with the full SHA in the folder name. However, now they are providing tars with just as much SHA as was in the initial request. This coincides with a change in its services: Before: Resolving github.com... 192.30.253.113, 192.30.253.112 Connecting to github.com\|192.30.253.113\|:443... connected. HTTP request sent, awaiting response... 302 Found Location: https://github-production-release-asset-2e65be.s3.amazonaws.com/23357588/88f90e58-e598-11e7-9263-ef8b1fb345b8?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSVEH53A%2F20180817%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20180817T190158Z&X-Amz-Expires=300&X-Amz-Signature=b684e1ead24a96764fd1f29ac5eb1df693d47c5fe86962088aee2ccfb8e4e72a&X-Amz-SignedHeaders=host&actor_id=0&response-content-disposition=attachment%3B%20filename%3Dprotobuf-all-3.5.1.tar.gz&response-content-type=application%2Foctet-stream [following] As of 2:00 PM PT today: Resolving github.com (github.com)... 192.30.253.113, 192.30.253.112 Connecting to github.com (github.com)\|192.30.253.113\|:443... connected. HTTP request sent, awaiting response... 302 Found Location: https://codeload.github.com/google/protobuf/tar.gz/61476b8e [following] Note that repositories.bzl isn't impacted because it already specified the full SHA.	2018-08-17 16:59:25 -07:00
Eric Anderson	7bb88de264	buildscripts: remove grpc-java-releasing docker container The buildscript was updated to pull in a fix to protoc-artifacts to support TLS 1.2 (google/protobuf#4879), which was the only remaining reason to have our own container. Docker container building was split out into a separate build_docker.sh so that people can call it blindly and get the container necessary for run_in_docker.sh.	2018-07-11 13:04:30 -07:00

Author

SHA1

Message

Date

Eric Anderson

142851dcbb

buildscripts: Use full SHA for protobuf download

Github used to produce tars with the full SHA in the folder name.
However, now they are providing tars with just as much SHA as was in the
initial request. This coincides with a change in its services:

Before:
Resolving github.com... 192.30.253.113, 192.30.253.112
Connecting to github.com|192.30.253.113|:443... connected.
HTTP request sent, awaiting response... 302 Found
Location: https://github-production-release-asset-2e65be.s3.amazonaws.com/23357588/88f90e58-e598-11e7-9263-ef8b1fb345b8?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSVEH53A%2F20180817%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20180817T190158Z&X-Amz-Expires=300&X-Amz-Signature=b684e1ead24a96764fd1f29ac5eb1df693d47c5fe86962088aee2ccfb8e4e72a&X-Amz-SignedHeaders=host&actor_id=0&response-content-disposition=attachment%3B%20filename%3Dprotobuf-all-3.5.1.tar.gz&response-content-type=application%2Foctet-stream [following]

As of 2:00 PM PT today:
Resolving github.com (github.com)... 192.30.253.113, 192.30.253.112
Connecting to github.com (github.com)|192.30.253.113|:443... connected.
HTTP request sent, awaiting response... 302 Found
Location: https://codeload.github.com/google/protobuf/tar.gz/61476b8e [following]

Note that repositories.bzl isn't impacted because it already specified
the full SHA.

2018-08-17 16:59:25 -07:00

Eric Anderson

7bb88de264

buildscripts: remove grpc-java-releasing docker container

The buildscript was updated to pull in a fix to protoc-artifacts to
support TLS 1.2 (google/protobuf#4879), which was the only remaining
reason to have our own container.

Docker container building was split out into a separate build_docker.sh
so that people can call it blindly and get the container necessary for
run_in_docker.sh.

2018-07-11 13:04:30 -07:00

2 Commits