Monthly release of Bitrise CLI tools and summary of updates (May, 2017) - CLI v1.6.1

Changelog
, ,
1

We ship a new bitrise cli version on the second Tuesday of every month.
The new release will be available on the bitrise.io
virtual machines on the weekend after the CLI release,
unless we discover any serious bug / regression.

Read on to learn more about this month’s Bitrise CLI release and about the changes around bitrise tools and steps.

New version of Bitrise CLI (1.6.1)

1. Install local plugins:

From this bitrise-cli version you can test your local plugin directly through the CLI, by installing it:

bitrise plugin install PATH/TO/MY/LOCAL/PLUGIN

NOTE: You can specify your plugin’s source as a command argument, no need to specify it with --src flag, however using the flag is still supported.

2. Step Output Aliases

You can specify the output’s alias, by setting value to the desired alias key and the cli will export the output with the given alias.

It is as simple as :

...
workflows:
  primary:
    steps:
    - gradle-runner:
        outputs:
        - BITRISE_APK_PATH: ALIAS_APK_PATH
...

The generated apk path will be available under ALIAS_APK_PATH key, instead of the default BITRISE_APK_PATH key.

Note: if alias specified the output will be exported only with the alias, so the value will NOT be available with the original environment key.

3. bitrise-cli got a new default plugin: step

Bitrise Plugin to interact with steps, list them, retrieve information, or create your own!

Want to create your own step? Just run bitrise :step create and you can create the perfect Step in no time!

4. default plugin updates:

  • init 0.9.1
  • workflow-editor 0.9.9
  • analytics 0.9.8

5. Step development guidline updates, read more in docs.

6. bitrise.yml format specification updates, read more in docs.

7. Go toolkit’s mininum go version bumped to: 1.8.1

8. Format version bumped to: 3

New steps

  • sonarqube-scanner 1.0.0
  • authenticate-with-bitbucket-oauth 0.9.0
  • jasmine-runner 0.9.0
  • authenticate-host-with-netrc 0.9.0
  • build-number-adjust 1.0.0
  • authenticate-with-github-oauth 0.9.0
  • codified-security-bitrise 1.0.0
  • generate-gradle-wrapper 0.9.2
  • install-dotnetcore 1.0.0

Step updates

  • create-android-emulator 1.1.2:
    • updated godeps, including fix for #13
  • deploy-to-itunesconnect-deliver 2.9.2:
    • added new input: platform
  • cakebuild 1.0.3:
    • Added some environment variables to skip a long process when first building a .net core project.
    • Adding extra opensll commands
  • xamarin-archive 1.3.3:
    • godeps-update
    • revised export method
  • certificate-and-profile-installer 1.8.5:
    • added feature to show part of the devices udid
  • generate-cordova-build-configuration 0.9.2:
    • First release
    • fixed missing default value package_type input
  • cordova-archive 0.9.1:
    • First release
    • output fixes
  • set-ios-product-bundle-identifier 1.1.2:
  • post-jira-comment-with-build-details 0.1.12:
  • project-scanner 1.2.2:
    • cordova default target fix
    • step.yml & readme.md updates
  • install-missing-android-tools 1.0.2:
    • Typofixes in console messages
  • gradle-runner 1.5.6:
    • updated type_tags
  • slack 2.4.1:
  • start-android-emulator 1.3.0:
    • Godeps-update (#34)
    • Fixed emulator start on Google APIs level 25 system image (#32)
  • xcode-test 1.18.3:
    • added new retry pattern
  • git-clone 3.4.3:
    • do not fail if no changes in PR
  • karma-jasmine-runner 0.9.1:
    • First release
    • typo fix & release configs
  • resign-ipa 1.2.2:
    • deprecated
  • wait-for-android-emulator 1.0.2:
    • Fix for timeout being prolonged (#6)
  • google-play-deploy 1.2.2:
    • fixed key_path input types
2 Likes
2

This is super handy if you have the same step two times in your workflow, and you’d want to use the generated output of both steps.

Before this Alias feature you had to use a Script to alias the output before running the second step, to prevent the second one to overwrite the first one’s output.

E.g. if you have two Deploy to Bitrise.io steps, one for an iOS and one for an Android app for example, you can now simply share both “public install page” URLs in a Slack message or similar, with:

    - deploy-to-bitrise-io@1.2.9:
        inputs:
        - deploy_path: $BITRISE_IPA_PATH
        outputs:
        - BITRISE_PUBLIC_INSTALL_PAGE_URL: IPA_PUBLIC_INSTALL_PAGE
    - deploy-to-bitrise-io@1.2.9:
        inputs:
        - deploy_path: $BITRISE_APK_PATH
        outputs:
        - BITRISE_PUBLIC_INSTALL_PAGE_URL: APK_PUBLIC_INSTALL_PAGE
    - slack@2.4.1:
        inputs:
        - message: |
            IPA public install page: $IPA_PUBLIC_INSTALL_PAGE
            APK public install page: $APK_PUBLIC_INSTALL_PAGE
1 Like
3

Related discussion thread: