Cseda/upload to sauce labs 0.0.1

[camseda]

What to do if the build fails?

At the moment contributors do not have access to the CI workflow triggered by StepLib PRs. In case of a failed build, we ask for your patience. Maintainers of Bitrise Steplib will sort it out for you or inform you if any further action is needed.

New Pull Request Checklist

Please mark the points which you did / accept.

• I will not move an already shared step version's tag to another commit
• I read the Step Development Guideline
• I have a test for my Step, which can be run with bitrise run test (in the step's repository)
• I did run bitrise run audit-this-step (in the step's repository - note, if you don't have this workflow in your bitrise.yml, you can copy it from the step template.)
• I read and accept the Abandoned Step policy

New Step
Thank you for the new Step share! The CI check might will fail due to our extended validation engine. Nothing to worry about yet, we will get back to you shortly.

[bitrise-coresteps-bot]

Don't forget to follow semantic versioning! Breaking changes (including step inputs) should be in major versions only.

step.yml changes compared to previous version:

[godrei]

Is the git cli tool a dependency of this step? By looking at the source code git command isn't invoked directly.

[godrei]

Hi @camseda thanks for the new Step, I left one comment please have a look.

Also to clarify: we have another SauceLabs-related step: https://github.com/bitrise-io/bitrise-steplib/blob/master/steps/saucelabs-espresso-app-automate/0.1.6/step.yml, the difference between the two is that the linked one works with Android APK files and also triggers SuceLab to run Espresso test, while this Step just uploads app artifacts, right?