Failed to download from bitrise-steplib-collection.s3.amazonaws.com

Question & Answer Builds
1

Description of the issue

Builds are failing on xcode-test@1.18.9, set-xcode-build-number@1.0.5, xcode-archive@2.4.4, among others due to:

Failed to download step.zip: Get https://bitrise-steplib-collection.s3.amazonaws.com/step-archives/xcode-test/1.18.9/step.zip: dial tcp: i/o timeout
Cloning into '/Users/vagrant/.stepman/step_collections/1512490479/cache/xcode-test/1.18.9'...
fatal: unable to access 'https://github.com/bitrise-io/steps-xcode-test.git/': Could not resolve host: github.com

Environment:

Bitrise.io, Xcode 9.2.x, on macOS 10.12 (Sierra)

Steps:

  • xcode-test@1.18.9
  • set-xcode-build-number@1.0.5
  • xcode-archive@2.4.4
  • deploy-to-bitrise-io@1.3.10

Reproducibility

  • Does a ā€œRebuildā€ help? : NO
  • Does a rebuild without caches help? : NO (no cache being used)
  • Does the issue happen sporadically, or every time? : EVERYTIME
  • Does upgrading the build Step to the latest version help? : NO
  • When did the issue start? : January 5th, 2018

Local reproduction

Locally steps work correctly.

Build log

Failed to download step.zip: Get https://bitrise-steplib-collection.s3.amazonaws.com/step-archives/xcode-test/1.18.9/step.zip: dial tcp: i/o timeout
Cloning into '/Users/vagrant/.stepman/step_collections/1512490479/cache/xcode-test/1.18.9'...
fatal: unable to access 'https://github.com/bitrise-io/steps-xcode-test.git/': Could not resolve host: github.com
Cloning into '/Users/vagrant/.stepman/step_collections/1512490479/cache/xcode-test/1.18.9'...
fatal: unable to access 'https://github.com/bitrise-io/steps-xcode-test.git/': Could not resolve host: github.com
Cloning into '/Users/vagrant/.stepman/step_collections/1512490479/cache/xcode-test/1.18.9'...
fatal: unable to access 'https://github.com/bitrise-io/steps-xcode-test.git/': Could not resolve host: github.com
Failed to clone step (https://github.com/bitrise-io/steps-xcode-test.git): (git "clone" "--recursive" "--branch" "1.18.9" "https://github.com/bitrise-io/steps-xcode-test.git" "/Users/vagrant/.stepman/step_collections/1512490479/cache/xcode-test/1.18.9") failed, error: exit status 128
FATA[15:02:45] Failed to download step, error: Failed to download step 
+------------------------------------------------------------------------------+

| (0) xcode-test@1.18.9                                                        |
+------------------------------------------------------------------------------+
| id: xcode-test                                                               |
| version: 1.18.9                                                              |
| collection: https://github.com/bitrise-io/bitrise-steplib.git                |
| toolkit: bash                                                                |
| time: 2018-01-08T15:02:45-08:00                                              |
+------------------------------------------------------------------------------+
|                                                                              |
|                                                                              |
+---+---------------------------------------------------------------+----------+
| x | xcode-test@1.18.9 (exit code: 1)                              | 194 sec  |
+---+---------------------------------------------------------------+----------+
| Issue tracker: Not provided                                                  |
| Source: Not provided                                                         |
+---+---------------------------------------------------------------+----------+
2

Hi @lopsae,

Thanks for reporting the issue!

So it happens every time?

Can you please copy paste one of these buildā€™s bitrise.io URL? Possibly also enable Support Access for the app.

From the error it seems you somehow modify network settings so that neither Amazon S3 nor GitHub can be accessed (maybe via /etc/hosts).

3

After closer inspection the steps that run before the failure, there was indeed a step that was setting up a vpn and thus messing up access to the outside. Sorry for the bother but thanks for pointing up the possible issue!

1 Like
4

No problem at all, Iā€™m glad to hear you managed to solve the issue :slight_smile:

Happy Building!