I looked at how the Google Cloud Java client libraries are packaged and found some issues. gcp-java-sdk-auth and gcp-java-sdk-storage exist, but they have several problems. gcp-java-sdk-auth bundles GSON (should be a plugin-to-plugin dependency on the GSON library Jenkins plugin), Guava (should be omitted because it is provided by Jenkins core), and Apache Commons HttpClient 4.x (should be a plugin-to-plugin dependency on the corresponding Jenkins library plugin as well). gcp-java-sdk-storage bundles a bunch of libraries that are duplicated from gcp-java-sdk-auth (e.g., google-auth-library-credentials, google-auth-library-oauth2-http, google-http-client, google-http-client-gson, and grpc-context); these should be factored out into a common library plugin (similar to aws-java-sdk2-core). Once all that is done, the google-compute-engine, google-kubernetes-engine, google-login, google-metadata, google-oauth, and google-storage Jenkins plugins should be refactored to consume the abovementioned Jenkins library plugins.
Is anyone interested in working on this? -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion visit https://groups.google.com/d/msgid/jenkinsci-dev/CAFwNDjo0tz%3D498cx1Ar4q3xQRkWhTJQ8qRa9v5gyJ24L0vE93w%40mail.gmail.com.
