Assets 4

Release Notes

Install or upgrade

To install this version, run the following commands (in a bash shell):

curl -fL https://github.com/bitrise-io/bitrise/releases/download/1.22.0/bitrise-$(uname -s)-$(uname -m) > /usr/local/bin/bitrise

Then:

chmod +x /usr/local/bin/bitrise

That's all, you're ready to call bitrise!

@bitrise-devs-bot bitrise-devs-bot released this Aug 16, 2018

Assets 4

Release Notes

Install or upgrade

To install this version, run the following commands (in a bash shell):

curl -fL https://github.com/bitrise-io/bitrise/releases/download/1.21.0/bitrise-$(uname -s)-$(uname -m) > /usr/local/bin/bitrise

Then:

chmod +x /usr/local/bin/bitrise

That's all, you're ready to call bitrise!

@bitrise-devs-bot bitrise-devs-bot released this Jul 25, 2018

Assets 4

Release Notes

  1. Log filtering issue fix
  2. Sensitive input validation removed

Install or upgrade

To install this version, run the following commands (in a bash shell):

curl -fL https://github.com/bitrise-io/bitrise/releases/download/1.20.0/bitrise-$(uname -s)-$(uname -m) > /usr/local/bin/bitrise

Then:

chmod +x /usr/local/bin/bitrise

That's all, you're ready to go!

Optionally, you can call bitrise setup to verify that everything what's required for bitrise to run
is installed and available, but if you forget to do this it'll be performed the first
time you call bitrise run.

@godrei godrei released this Jul 12, 2018 · 15 commits to master since this release

Assets 4

Release Notes

1. Sensitive input validation update

The cli version 1.18.0 introduced a new step input option: is_sensitive.
Step inputs which store secret values, like passwords, api tokens, an SSH key, etc. can be marked as sensitive.
These step input values need to be defined as secret environment variables to make sure they are not visible in the build logs
as Bitrise CLI 1.15.0 introduced the secret filtering feature, which redacts the values defined as secret environment variables from the build log.

As the initial rollout of the sensitive step input feature, the bitrise run and bitrise trigger commands
will print a warning message at the very beginning of the build log if your configuration has a security issue. The warning message looks like this:

Security validation failed: security issue in slack step's webhook_url input: value should be defined as a secret environment variable, but does not starts with '$' mark

or

Security validation failed: security issue in slack step's webhook_url input: value should be defined as a secret environment variable, but is_expand set to: false.

While the run and trigger commands are just notifying you about the issue, the bitrise validate command fails in case of a security issue.

bitrise validate --format json command will exit with status 1 and a similar output in case of security issue:

{  
   "data":{  
      "config":{  
         "is_valid":false,
         "error":"security issue in slack step's webhook_url input: value should be defined as a secret environment variable, but is_expand set to: false"
      },
      "secrets":{  
         "is_valid":true
      }
   }
}

As the next phase of the security update, we will go through all of steps maintained by Bitrise
and release a new version with sensitive inputs marked as: is_sensitive.

2. Tools update

  • envman update to version 1.2.0
  • stepman update to version 0.10.0

3. Default plugins update

  • workflow-editor plugin updated to version 1.1.20
  • analytics plugin updated to version 0.9.14

4. Go dependencies update

Install or upgrade

To install this version, run the following commands (in a bash shell):

curl -fL https://github.com/bitrise-io/bitrise/releases/download/1.19.0/bitrise-$(uname -s)-$(uname -m) > /usr/local/bin/bitrise

Then:

chmod +x /usr/local/bin/bitrise

That's all, you're ready to go!

Optionally, you can call bitrise setup to verify that everything what's required for bitrise to run
is installed and available, but if you forget to do this it'll be performed the first
time you call bitrise run.

@trapacska trapacska released this Jun 28, 2018 · 24 commits to master since this release

Assets 4

Release Notes

  • updated analytics plugin version

Install or upgrade

To install this version, run the following commands (in a bash shell):

curl -fL https://github.com/bitrise-io/bitrise/releases/download/1.18.1/bitrise-$(uname -s)-$(uname -m) > /usr/local/bin/bitrise

Then:

chmod +x /usr/local/bin/bitrise

That's all, you're ready to go!

Optionally, you can call bitrise setup to verify that everything what's required for bitrise to run
is installed and available, but if you forget to do this it'll be performed the first
time you call bitrise run.

@trapacska trapacska released this Jun 28, 2018 · 26 commits to master since this release

Assets 4

Release Notes

1. CLI security update

  • added is_sensitive input option

2. Tools update

  • envman update to version 1.2.0
  • stepman update to version 0.10.0

Install or upgrade

To install this version, run the following commands (in a bash shell):

curl -fL https://github.com/bitrise-io/bitrise/releases/download/1.18.0/bitrise-$(uname -s)-$(uname -m) > /usr/local/bin/bitrise

Then:

chmod +x /usr/local/bin/bitrise

That's all, you're ready to go!

Optionally, you can call bitrise setup to verify that everything what's required for bitrise to run
is installed and available, but if you forget to do this it'll be performed the first
time you call bitrise run.

@godrei godrei released this Jun 11, 2018 · 32 commits to master since this release

Assets 4

Release Notes

1. Secret filtering updates

Issue fixes around secret filtering.

2. Tools update

  • envman update to version 1.1.14
  • stepman update to version 0.9.43

3. Default plugins update

  • init plugin updated to version 1.0.4
  • step plugin updated to version 0.9.8
  • workflow-editor plugin updated to version 1.1.17
  • analytics plugin updated to version 0.9.13

4. Go dependencies update

Install or upgrade

To install this version, run the following commands (in a bash shell):

curl -fL https://github.com/bitrise-io/bitrise/releases/download/1.17.0/bitrise-$(uname -s)-$(uname -m) > /usr/local/bin/bitrise

Then:

chmod +x /usr/local/bin/bitrise

That's all, you're ready to go!

Optionally, you can call bitrise setup to verify that everything what's required for bitrise to run
is installed and available, but if you forget to do this it'll be performed the first
time you call bitrise run.

@godrei godrei released this May 16, 2018 · 37 commits to master since this release

Assets 4

Release Notes

  • REGRESSION: fixed step activation from its git source

Install or upgrade

To install this version, run the following commands (in a bash shell):

curl -fL https://github.com/bitrise-io/bitrise/releases/download/1.16.1/bitrise-$(uname -s)-$(uname -m) > /usr/local/bin/bitrise

Then:

chmod +x /usr/local/bin/bitrise

That's all, you're ready to go!

Optionally, you can call bitrise setup to verify that everything what's required for bitrise to run
is installed and available, but if you forget to do this it'll be performed the first
time you call bitrise run.

@godrei godrei released this May 8, 2018 · 41 commits to master since this release

Assets 4

Release Notes

1. Secret filtering updates

Bitrise cli got a new flag to enable/disable redacting secret values in the output log: --secret-filtering.
Pass this flag to the run or trigger commands to enable filtering: bitrise run WORKFLOW_ID --secret-filtering.
The new flag can be set by an environment variable as well: BITRISE_SECRET_FILTERING=true bitrise run WORKFLOW_ID .

BITRISE_SECRET_FILTERING env var can be set as a secret env (in .bitrise.secrets.yml) as in the previous cli version.

The min length of the secret value to redact was removed.

2. Tools update

  • envman update to version 1.1.13
  • stepman update to version 0.9.41

3. Default plugins update

  • init plugin updated to version 1.0.2
  • step plugin updated to version 0.9.6
  • workflow-editor plugin updated to version 1.1.16
  • analytics plugin updated to version 0.9.12

4. Go toolkit's Go version bumped to 1.10.2

5. Go dependencies update

Install or upgrade

To install this version, run the following commands (in a bash shell):

curl -fL https://github.com/bitrise-io/bitrise/releases/download/1.16.0/bitrise-$(uname -s)-$(uname -m) > /usr/local/bin/bitrise

Then:

chmod +x /usr/local/bin/bitrise

That's all, you're ready to go!

Optionally, you can call bitrise setup to verify that everything what's required for bitrise to run
is installed and available, but if you forget to do this it'll be performed the first
time you call bitrise run.

@godrei godrei released this Apr 10, 2018 · 52 commits to master since this release

Assets 4

Release Notes

1. Bitrise secret filtering

From this version bitrise-cli can filter your secrets from the build log.

Set BITRISE_SECRET_FILTERING to true in your secrets to enable the new feature. The new functionality can hide single and multiline secrets in the log.

NOTE: Secrets with at least 6 characters will be replaced with [REDACTED] pattern in the build log.

Example:

.bitrise.secrets.yml

envs:
- BITRISE_SECRET_FILTERING: true
- MY_SSH_KEY: |
    -----BEGIN RSA PRIVATE KEY-----
    bitrise_testmfsjOSsRK7+uFr1g4jvIz/yoDrSMRcKrBi/c+iJr+aO8xIb7j2WQ
    5F4h84OLEkQEmfsjOSsRK7+uFr1g4jvIz/yoDrSMRcKrBi/c+iJr+aO8xIb7j2WQ
    sPXxhoOj4kuoxqFjrQMGyDZ+uIJMD9D+vsov4iDvIBrMkn2TuD/o1X9oISEhDw1l
    3tsWqgFxpZprcMw64rdEOJ/7+aJczWvi37kGYjQ4wvSnD+MEoFZIM3fhxDDcxb+I
    COjv7Y+Ta++KGjhyu5OJjTAzFyjal0ub0VaVdu8Vg6tAr1grdhQayPYXZqd1TqaU
    kniMwxz4hAg+QbhsdSlKzQjgbJJhzn3shiK7kMxL7DrUmhoIgQ1QMUERj4Lt8y9I
    J3zHmSq27IEXSzwBIL0JRAsKfcq914f3S2tbyQUi2doJTMxWDgcaL6jkzjCwmCx/
    bitrise_testmfsWwlaF+Y0w0xVfAcABHdYjWHx2UHP02EC1ZGUAqF9z6XaCV8l9
    oMHHu9lvWKuxpVNPcGY/kR3G897Qn+6vE3yuVwbD4reu0IHAWZzBgt7e3we5
    -----END RSA PRIVATE KEY-----

bitrise.yml

format_version: 5
default_step_lib_source: https://github.com/bitrise-io/bitrise-steplib.git

workflows:
  primary:
    steps:
    - script:
        inputs:
        - content: |
            #!/usr/bin/env bash
            echo "My ssh key: $MY_SSH_KEY"

bitrise run primary

+------------------------------------------------------------------------------+
| (0) script                                                                   |
+------------------------------------------------------------------------------+
| id: script                                                                   |
| version: 1.1.5                                                               |
| collection: https://github.com/bitrise-io/bitrise-steplib.git                |
| toolkit: bash                                                                |
| time: 2018-04-10T10:10:35+02:00                                              |
+------------------------------------------------------------------------------+
|                                                                              |
WARN[10:10:36] Secret filtering enabled
My ssh key: [REDACTED]
[REDACTED]
[REDACTED]
[REDACTED]
[REDACTED]
[REDACTED]
[REDACTED]
[REDACTED]
[REDACTED]
[REDACTED]
[REDACTED]
|                                                                              |
+---+---------------------------------------------------------------+----------+
| ✓ | script                                                        | 2.46 sec |
+---+---------------------------------------------------------------+----------+

2. Step Development Guideline updated with Step icon convention section

3. bitrise update command got improvements

  • better log messages
  • avoid updating if the current version is the latest

4. Tools update

  • envman update to version 1.1.12
  • stepman update to version 0.9.40

5. Default plugins update

  • workflow-editor plugin update to version 1.1.14

6. Go version for toolkit bumped to 1.10.1

7. Go dependencies update

Install or upgrade

To install this version, run the following commands (in a bash shell):

curl -fL https://github.com/bitrise-io/bitrise/releases/download/1.15.0/bitrise-$(uname -s)-$(uname -m) > /usr/local/bin/bitrise

Then:

chmod +x /usr/local/bin/bitrise

That's all, you're ready to go!

Optionally, you can call bitrise setup to verify that everything what's required for bitrise to run
is installed and available, but if you forget to do this it'll be performed the first
time you call bitrise run.