[SVC-3123] feat: upload binaries to an other Object Storage as well

.goreleaser.yaml

@@ -23,22 +23,36 @@ builds:
 archives:
   # GitHub release should contain the raw binaries (no zip or tar.gz)
 - format: binary
+  id: default
   # Name format should match the curl install script
   name_template: >-
     {{ .ProjectName }}-
     {{- title .Os }}-
     {{- if eq .Arch "amd64" }}x86_64
     {{- else }}{{ .Arch }}{{ end }}
 
+- format: binary
+  id: s3
+  name_template: "{{ .ProjectName }}-cli-{{ .Os }}-{{ .Arch }}-v{{ .Tag }}"
+
 blobs:
 - provider: gs
   bucket: bitrise-cli-releases-prod
   folder: /{{ .Tag }}
+  ids:
+    - default
+- provider: s3
+  bucket: bitrise-cli-releases-prod
+  folder: /
+  ids:
+    - s3
 
 release:
   github:
     owner: bitrise-io
     name: bitrise
+  ids:
+    - default
   draft: true
   mode: replace
   footer: |

bitrise.yml

@@ -54,6 +54,9 @@ workflows:
     description: Creates Linux and Darwin binaries, then publishes a GitHub release
     envs:
     - GITHUB_TOKEN: $GIT_BOT_USER_ACCESS_TOKEN  # Goreleaser expects this env var
+    - AWS_ENDPOINT_URL: $AWS_ENDPOINT_PROD
+    - AWS_ACCESS_KEY_ID: $AWS_ACCESS_KEY_ID_PROD
+    - AWS_SECRET_ACCESS_KEY: $AWS_SECRET_ACCESS_KEY_PROD
     steps:
     - script:
         title: Fetch GCS bucket credentials