step.yml

#
# A couple of useful guides & docs:
#
# - Main Bitrise CLI docs: https://github.com/bitrise-io/bitrise/tree/master/_docs
# - Step Development Guideline: https://github.com/bitrise-io/bitrise/blob/master/_docs/step-development-guideline.md
# - Bitrise.yml format spec: https://github.com/bitrise-io/bitrise/blob/master/_docs/bitrise-yml-format-spec.md
# - Bitrise docs: http://devcenter.bitrise.io/
# - Bitrise CLI guides: http://devcenter.bitrise.io/bitrise-cli/

title: |-
  rbenv
summary: |
  Install a Ruby version you specify via rbenv
description: |
  Install a Ruby version you speficy with .ruby-version or step configruation via rbenv
website: https://github.com/ainame/bitrise-step-rbenv
source_code_url: https://github.com/ainame/bitrise-step-rbenv
support_url: https://github.com/ainame/bitrise-step-rbenv/issues
host_os_tags:
  - osx-10.10
  - ubuntu-16.04

# If this step should be available only for certain project types
# just uncomment this `project_type_tags` section and include all the
# project types supported by the step. If the step can be used for all
# project types then you can just remove this section.
# If no `project_type_tags` specified (or specified as an empty array)
# that means the step can be used for any project type.
# You can find more information about project type tags in the Step Development Guideline:
# https://github.com/bitrise-io/bitrise/blob/master/_docs/step-development-guideline.md
#
# project_type_tags:
#   - ios
#   - macos
#   - android
#   - xamarin
#   - react-native
#   - cordova
#   - ionic

# Type tags are used for categorizing steps, for easier step discovery in Step Libraries.
# You can find more information about type tags in the Step Development Guideline:
# https://github.com/bitrise-io/bitrise/blob/master/_docs/step-development-guideline.md
type_tags:
  - installer

is_requires_admin_user: true
is_always_run: false
is_skippable: false
run_if: ""

deps:
  brew:
  - name: rbenv
  - name: ruby-build

toolkit:
  bash:
    entry_file: step.sh

inputs:
  - ruby_version: ""
    opts:
      title: "Ruby version to install"
      summary: "A valid Ruby version to be installed via rbenv. Leave this empty to use `.ruby-version` file."
      description: |
        A valid ruby version to be installed via rbenv. You can leave this empty to make this step read `.ruby-version` file.
        If the current stack environment has installed specifed version, this step installs nothing.
      is_expand: true
      is_required: false