setup-gauge's Introduction

Setup Gauge

This github action allows for installation of the Gauge CLI to be used in your actions pipeline.

It has support for Linux, MacOS and Windows runners.

Inputs

`gauge-version`

Required The version needs to be installed.

Default: latest.

`gauge-plugins`

Required The plugins needs to be installed.

Default: Nothing

Example usage

Install latest

uses: getgauge/setup-gauge@master

Install a particular version

uses: getgauge/setup-gauge@master
with:
    gauge-version: '1.0.7'

Install plugins with gauge

uses: getgauge/setup-gauge@master
with:
    gauge-version: '1.0.7'
    gauge-plugins: java, html-report

Install gauge from source

uses: getgauge/setup-gauge@master
with:
    gauge-version: master
    gauge-plugins: java, html-report

setup-gauge's People

Contributors

Stargazers

Watchers

setup-gauge's Issues

Need a way to specify plugin versions to install

Read me doc states I can specify plugins to install but in practice it seems to only ever install the latest version on each plugin.

Example scenario where latest will not work:
Installing the latest dotnet plugin gets us 0.5.7 which explicitly uses dotnet 8.0.x. I need to be able to specify the 0.5.0 version of the plugin to have 6.0.x supported.
getgauge/gauge-dotnet@v0.5.0...v0.5.7#diff-5c3fa597431eda03ac3339ae6bf7f05e1a50d6fc7333679ec38e21b337cb6721L26

Failure to download results in successful completion instead of error

The getgauge/setup-gauge@master action runs and completes successfully, but later steps in my own Workflow that run Gauge tests fail because it's obviously not installed. The installation in getgauge/setup-gauge@master is what I expect to fail, not my later steps running the tests.

Run getgauge/setup-gauge@master
##[debug]Downloading gauge from Github releases
##[debug]Download version = 1.4.3
##[debug]isExplicit: 1.4.3
##[debug]explicit? true
##[debug]checking cache: /opt/hostedtoolcache/gauge/1.4.3/x64
##[debug]not found
##[debug]Tool not found in cache. Download tool from url: https://github.com/getgauge/gauge/releases/download/v1.4.3/gauge-1.4.3-linux.x86_64.zip
##[debug]Downloading https://github.com/getgauge/gauge/releases/download/v1.4.3/gauge-1.4.3-linux.x86_64.zip
##[debug]Destination /home/runner/work/_temp/24fb3d6c-01f0-4283-9d08-4c2c42fb57ea
##[debug]Failed to download from "https://github.com/getgauge/gauge/releases/download/v1.4.3/gauge-1.4.3-linux.x86_64.zip". Code(502) Message(Bad Gateway)
Unexpected HTTP response: 502
Waiting 20 seconds before trying again
##[debug]Failed to download from "https://github.com/getgauge/gauge/releases/download/v1.4.3/gauge-1.4.3-linux.x86_64.zip". Code(502) Message(Bad Gateway)
Unexpected HTTP response: 502
Waiting 19 seconds before trying again
##[debug]Failed to download from "https://github.com/getgauge/gauge/releases/download/v1.4.3/gauge-1.4.3-linux.x86_64.zip". Code(502) Message(Bad Gateway)
(node:1837) UnhandledPromiseRejectionWarning: Error: Unexpected HTTP response: 502
    at /home/runner/work/_actions/getgauge/setup-gauge/master/dist/index.js:1:49902
    at Generator.next (<anonymous>)
    at fulfilled (/home/runner/work/_actions/getgauge/setup-gauge/master/dist/index.js:1:47900)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
(node:1837) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error
originated either by throwing inside of an async function without a catch block, or by 
rejecting a promise which was not handled with .catch(). To terminate the node process on 
unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see 
https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:1837) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the 
future, promise rejections that are not handled will terminate the Node.js process with a 
non-zero exit code.
##[debug]Node Action run completed with exit code 0
##[debug]Finished: run

Recommend Projects