Deploy Configuration not working in any build configuration

#1

Bitrise Build Issue Report template

Description of the issue

Currently all of our deployments across different projects emit:
Issue with input: failed to parse config:

Subsequently they cannot find any of the deploy directories.

Environment:

Where did the issue happen?

Bitrise.io Xcode 10.2.x, on macOS 10.14 (Mojave)
Bitrise.io Xcode 9.4.x, on macOS 10.13 (High Sierra)

deploy-to-bitrise-io

Reproducibility

This is happening to every build and started today.

Local reproduction

Can it be reproduced on your own Mac/PC by following our local debug guide? Please follow at least the first section (“Testing with a full clean git clone”) to make sure to test the state of the code what bitrise.io will get when it does a git clone in the clean environment! If possible please note which sections you tried.

Local reproduction: Linux / Android (docker based) stack builds

Can it be reproduced by running the build locally, after doing a new git clone of the repository into the /tmp directory and running the build from there with the Bitrise CLI ( https://www.bitrise.io/cli )? If no, can it be reproduced with Docker (using the same docker images / environment we use on bitrise.io)? Related guide: http://devcenter.bitrise.io/docker/run-your-build-locally-in-docker/ .

Build log

Please copy paste the build’s bitrise.io URL here (or if the issue happens somewhere else then the full logs), or if you can’t share the url / log here then send the url or full log through a private channel (e.g. email - https://www.bitrise.io/contact ), with a link to the related Discuss issue.

0 Likes

#2

Hello there, I’m sad to hear you experience such issues, could you please send us the latest build’s url so we could check out the logs for some more details? :upside_down_face:

0 Likes

#3

Builds started working again over the weekend.

This is an example of a failed build before they started working again.

Rebuilding that, without any code changes or configuration changed now works.

We were seeing the same type of failure on our iOS builds as well.

0 Likes