Downloads:

312

Downloads of v 2.29.0:

60

Last Update:

17 Mar 2022

Package Maintainer(s):

Software Author(s):

  • https://github.com/rainforestapp/rainforest-cli/graphs/contributors

Tags:

rainforest-cli rainforest

Rainforest CLI

  • 1
  • 2
  • 3

2.29.0 | Updated: 17 Mar 2022

Downloads:

312

Downloads of v 2.29.0:

60

Maintainer(s):

Software Author(s):

  • https://github.com/rainforestapp/rainforest-cli/graphs/contributors

  • 1
  • 2
  • 3
Rainforest CLI 2.29.0

  • 1
  • 2
  • 3

Some Checks Have Failed or Are Not Yet Complete

Not All Tests Have Passed


Validation Testing Passed


Verification Testing Passed

Details

Scan Testing Resulted in Flagged as a Note:

At least one file within this package has greater than 0 detections, but less than 5

Details
Learn More

Deployment Method: Individual Install, Upgrade, & Uninstall

To install Rainforest CLI, run the following command from the command line or from PowerShell:

>

To upgrade Rainforest CLI, run the following command from the command line or from PowerShell:

>

To uninstall Rainforest CLI, run the following command from the command line or from PowerShell:

>

Deployment Method:

📝 NOTE: This applies to both open source and commercial editions of Chocolatey.

1. Enter Your Internal Repository Url

(this should look similar to https://community.chocolatey.org/api/v2/)


2. Setup Your Environment

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

2. Get the package into your environment

  • Open Source or Commercial:
    • Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to https://community.chocolatey.org/api/v2/. Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
    • You can also just download the package and push it to a repository Download

3. Copy Your Script

choco upgrade rainforest-cli -y --source="'INTERNAL REPO URL'" [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:


choco upgrade rainforest-cli -y --source="'INTERNAL REPO URL'" 
$exitCode = $LASTEXITCODE

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0
}

Exit $exitCode

- name: Install rainforest-cli
  win_chocolatey:
    name: rainforest-cli
    version: '2.29.0'
    source: INTERNAL REPO URL
    state: present

See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.


chocolatey_package 'rainforest-cli' do
  action    :install
  source   'INTERNAL REPO URL'
  version  '2.29.0'
end

See docs at https://docs.chef.io/resource_chocolatey_package.html.


cChocoPackageInstaller rainforest-cli
{
    Name     = "rainforest-cli"
    Version  = "2.29.0"
    Source   = "INTERNAL REPO URL"
}

Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.


package { 'rainforest-cli':
  ensure   => '2.29.0',
  provider => 'chocolatey',
  source   => 'INTERNAL REPO URL',
}

Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.


4. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

This package was approved as a trusted package on 17 Mar 2022.

Description

rainforest-cli

A command line interface to interact with Rainforest QA. Source and more documentation is available here

Global Options

  • --token <your-rainforest-token> - your API token if it's not set via the RAINFOREST_API_TOKEN environment variable
  • --skip-update - Do not automatically check for CLI updates

Options

  • --browsers ie8,chrome - specify browsers you wish test. This overrides the test level settings. Valid browsers can be found in your account settings.
  • --tag TAG_NAME - filter tests by tag. Can be used multiple times for filtering by multiple tags.
  • --site-id SITE_ID - filter tests by a specific site. You can see a list of your site IDs with rainforest sites.
  • --folder ID/--filter ID - filter tests in specified folder.
  • --feature ID - filter tests in a feature.
  • --run-group ID - run/filter based on a run group. When used with run, this trigger a run from the run group; it can't be used in conjunction with other test filters.
  • --environment-id - run your tests using this environment. Otherwise it will use your default environment
  • --conflict OPTION - use the abort option to abort any runs in progress in the same environment as your new run. Use the abort-all option to abort all runs in progress.
  • --bg - creates a run in the background & exits immediately after. Cannot be used together with --max-reruns.
  • --crowd [default|automation|automation_and_crowd|on_premise_crowd]
  • --wait RUN_ID - wait for an existing run to finish instead of starting a new one, and exit with a non-0 code if the run fails. rainforest-cli will exit immediately if the run is already complete.
  • --fail-fast - return an error as soon as the first failed result comes in (the run always proceeds until completion, but the CLI will return an error code early). If you don't use it, it will wait until 100% of the run is done.
  • --custom-url - specify the URL for the run to use when testing against an ephemeral environment. Temporary environments will be automatically deleted 72 hours after they were last used.
  • --description "CI automatic run" - add an arbitrary description for the run.
  • --release "1a2b3d" - add an ID to associate the run with a release. Commonly used values are commit SHAs, build IDs, branch names, etc.
  • --junit-file - Create a JUnit XML report file with the specified name. Must be run in foreground mode, or with the report command.
  • --import-variable-csv-file /path/to/csv/file.csv - Use with run and --import-variable-name to upload new tabular variable values before your run to specify the path to your CSV file.
  • --import-variable-name NAME - Use with run and --import-variable-csv-file to upload new tabular variable values before your run to specify the name of your tabular variable.
  • --single-use - Use with run or csv-upload to flag your variable upload as single-use. See --import-variable-csv-file and --import-variable-name options as well.
  • --disable-telemetry stops the cli sharing information about which CI system you may be using, and where you host your git repo (i.e. your git remote). Rainforest uses this to better integrate with CI tooling, and code hosting companies, it is not sold or shared. Disabling this may affect your Rainforest experience.
  • --max-reruns - If set to a value > 0 and a test fails, the CLI will re-run failed tests a number of times before reporting failure. If --junit-file <filename> is also used, the JUnit reports of reruns will be saved under <filename>.1, <filename>.2 etc.

Support

Email [email protected] if you're having trouble using the CLI or need help with integrating Rainforest in your CI or development workflow.


LICENSE.txt
Copyright (c) 2021 Rainforest QA, Inc

MIT License

Permission is hereby granted, free of charge, to any person obtaining
a copy of this software and associated documentation files (the
"Software"), to deal in the Software without restriction, including
without limitation the rights to use, copy, modify, merge, publish,
distribute, sublicense, and/or sell copies of the Software, and to
permit persons to whom the Software is furnished to do so, subject to
the following conditions:

The above copyright notice and this permission notice shall be
included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
rainforest.exe
md5: 89680D6180F3CFD87197B8034058DFAC | sha1: 42B9833EF531EBE56D709CB721342F79FDC5A5FC | sha256: 56C0FA0E16F69DB579BDDC1083B57D34FF7A15364D243DCE1066837482058587 | sha512: DF8385DEE1E03A3F7ACB1FCDDF272D48CFBF01D11D707DEA13F2193C9CA641571C4E24E451DD32987E66BA10F5D2F05F716E2996640CDECAEB16B6EB9E1B7258
VERIFICATION.txt

VERIFICATION
Verification is intended to assist the Chocolatey moderators and community
in verifying that this package's contents are trustworthy.

This package is published by the Rainforest QA itself. Any binaries will be identical to other package types published by the project, and can be built from source if you wish from https://github.com/rainforestapp/rainforest-cli or view the build artifacts directly from the releases page at https://github.com/rainforestapp/rainforest-cli/releases.

Manually checking the expected checksum:
Get-FileHash rainforest.exe

Expected:
89680d6180f3cfd87197b8034058dfac *D:/a/rainforest-cli-chocolatey/rainforest-cli-chocolatey/rainforest-cli/tools/rainforest.exe

Log in or click on link to see number of positives.

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Add to Builder Version Downloads Last Updated Status
Rainforest CLI 2.28.0 18 Friday, February 25, 2022 Approved
Rainforest CLI 2.27.0 29 Friday, January 21, 2022 Approved
Rainforest CLI 2.26.0 28 Thursday, January 13, 2022 Approved
Rainforest CLI 2.25.0 32 Wednesday, December 8, 2021 Approved
Rainforest CLI 2.24.0 32 Thursday, November 18, 2021 Approved
Rainforest CLI 2.23.1 27 Thursday, October 28, 2021 Approved
Rainforest CLI 2.23.0 44 Monday, October 4, 2021 Approved
Rainforest CLI 2.22.2 42 Thursday, September 30, 2021 Approved

This package has no dependencies.

Discussion for the Rainforest CLI Package

Ground Rules:

  • This discussion is only about Rainforest CLI and the Rainforest CLI package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or Rainforest CLI, or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus