* upgrade ruby docker images to debian 11
* upgrade C# docker images to debian11
* update sanity dockerimage to debian11
* upgrade cxx interop to debian11
* add ccache to python interop images
* enable use of ccache for interop tests
* adjust run_tests.py to new docker images
* add ccache to rake-compiler-dock docker images
* improve prepare_ccache_symlinks_rc
* enable use of ccache in rake-compiler-dock docker containers
* add ccache support for python_manylinux2014_aarch64
* add ccache support for python_linux_armv7
* deduplicate python3.9 install
* ccache for crosscompiled darwin gems is broken
* fix bash -l resetting of PATH in grpc_artifact_python_linux_armv7
* Let's see if the aarch64 manylinux bug is fixed or not
* rename aarch64 image back to manylinux2014 for consistency
* fix C# aarch64 artifact build
Co-authored-by: Lidi Zheng <lidiz@google.com>
* Add Python 3.10.0rc1 binary wheels
* Drop Python 3.5 artifacts
* Document the drop of 3.5
* Fix the wrong pip pointer
* Update manylinux2014 to a newer version, remove 3.5 distribtest
* Update manylinux aarch64 to see if the absl error go away
* Use the preferred alias
* Allow different wheel library to produce different tag order
* Remove unused shell var and log produced wheels
* Use copy instead of move
* Make bash happy about the wildcard
* Upgrade the debian image to use 3.5+ Python
* Polish the comments for the Dockerfiles
* generate separate .so with/without debug symbols for grpc_csharp_ext
* add linux .dbginfo.so libraries to Grpc.Core.NativeDebug package
* fix aarch64 grpc_csharp_ext stripping
* lots of linux artifact build jobs are currently timing out
In order to build Python3.7 packages for manylinux1
platform, we need our Docker image to include
Python3.7. Unfortunately, since Python 3.7 is still
in RC1 stage, the official docker image does not
include that Python release, so we temporarily
rely on our own underlying docker image to build.
In order to build Python3.7 packages for manylinux1
platform, we need our Docker image to include
Python3.7. Unfortunately, since Python 3.7 is still
in RC1 stage, the official docker image does not
include that Python release, so we temporarily
rely on our own underlying docker image to build.
89ce16b removed a few package installations from the dockerfiles for
building python artifacts. Revert them.
Revert certain package install removal from python artifact dockerfiles
Due to a recent change (Feb 2018) in Github's policy to discontinue
support for weak cryptographic standards, older git versions stopped
working with Github repositories. The Dockerfiles for building python
artifacts currently uses git 2.0.5, that fails with an error `tlsv1
alert protocol version`.
The CentOS image by the latest source Dockerfile, `manylinux` comes
with the latest version of git as well, removing the need to manually
build git from source.
Before, namespace packages would break in auditwheel due to a
superfluous check (fixed in the commit referenced in the Dockerfiles).
Now, the auditwheel used in the manylinux1-support Docker images can
handle namespace packages, and we may thus use them. This should
alleviate future user pain w.r.t. installation of grpcio-tools causing
loss of grpcio files and vice versa (e.g. requiring a reinstall of
grpcio following installation of grpcio-tools).
The source code is moved from src/python to
src/python/src. A setup.py is added at
src/python. The build_python.sh and
run_python.sh scripts are updated to build
and run the Python tests by building a
package and installing it in the developer's
Python 2.7 virtual environment.