I’ve tried to build a step to download files from S3. It works well when run locally with bitrise run test but it doesn’t when run on bitrise.io . Or better, it does run, produces no output and doesn’t fail the build. I’m a bit puzzled: the step’s output stops after bitrise installs the dependencies…

[image] FWFabio: doesn’t fail the build. That’s because of the is_skippable: true flag - https://github.com/FutureWorkshops/bitrise-step-s3-download/blob/master/step.yml#L17 (This flag is used for steps like Slack notification, where if that step fails you don’t want to mark the build as fail…

[image] FWFabio: the step’s output stops after bitrise installs the dependencies. Could you please copy paste an example, with the log including the step’s header and footer?

- git::https://github.com/FutureWorkshops/bitrise-step-s3-download.git@master: title: Download keychain inputs: - aws_access_key: "$AWS_ACCESS_KEY_ID" - aws_secret_access_key: "$AWS_SECRET_ACCESS_KEY" - s3_bucket: my.keychain.bucket - s3_filepath: "$KEYCHAIN_NAME" And the ou…

Can you drop in a Script step before this step with this content: #!/bin/bash set -ex brew install awscli and let us know how it goes? (It seems that for some reason the installation of awscli doesn’t finish. That said, if you’re downloading, you shouldn’t even need awscli, which is declared as a …

Without the dependency it seems to be working again. It would be nice to have that as a bitrise managed dependency so I can easily deploy it for both Mac OS and linux. You need awscli if the link is not public and you need to auth with a key/secret pair don’t you?

[image] FWFabio: Without the dependency it seems to be working again. Did you try it with the Script step (brew install awscli)? [image] FWFabio: You need awscli if the link is not public and you need to auth with a key/secret pair don’t you? Ahh, you’re right, if it’s a private file …

Yes I meant: if I do brew install awscli instead of expressing the dependency it works. But I’d rather not manage that dependency manually. Do you think this is something you guys can fix on your end? Another thing that I noticed is that, when I use brew install awscli I don’t get any output neith…

[image] FWFabio: is there a way to pipe the result of the awscli command to the log output? You don’t have to pipe it, every output generated by any tool/command should be in the log by default, unless the step hides it (e.g. by redirecting it into a file, instead of writing it to stdout/stde…

That’s what I thought. Unfortunately it’s the case with awscli (works fine when testing locally). Any idea where I should look? It seems to be an issue with all the steps I’m creating. I get a lot of output if I use set -x but I don’t really want that level of debug. I can give you access to the p…

[image] FWFabio: I get a lot of output if I use set -x but I don’t really want that level of debug. What’s the last line in the log if you have set -x in it?

Unable to run custom step

Development

viktorbenei March 23, 2017, 9:32am 13

Can you please enable Bitrise Support access to the related app and then send us the app’s URL in email / through the onsite chat?

Topic		Replies	Views
AWS s3 to Bitrise workflow Question & Answer	4	1429	August 19, 2022
Failed to download step.zip Tooling Issues	3	1654	October 7, 2018
New step "wetransfer" available! Step Dev step	4	1532	May 21, 2018
Bitrise CLI fails to load steps Tooling Issues bitrise-cli	2	3423	June 15, 2019
Failed to download from bitrise-steplib-collection.s3.amazonaws.com Builds	3	1429	January 11, 2018

Unable to run custom step

Related topics