testspace-com / setup-testspace Goto Github PK

Considering changing the Setup action to use Composite run steps vs JavaScript action. The primary purpose of the Setup action is to abstract the installing of the Testspace client on Ubuntu, Windows, and macOS.

The dependencies and steps required to update the action would be minimized.

After GitHub Actions workflow completes, sometimes "testspace-analytics" remains in "queued" state.

Usually, pushing to that branch again, or manually restarting the workflow "fixes" testspace check - i. e. it completes for the new CI run.

But now I have a pull request where "testspace-analytics" never completes, even after subsequent pushes or CI workflow restarts: ddterm/gnome-shell-extension-ddterm#250

I've authorised TestSpace for one of my repos, URL example: https://github.com/bennymeade/testing-testspace
I've then added the required steps to my GH workflow:

- name: TestSpace client
        if: always()
        // Just for the record I also tried `uses: testspace-com/setup-testspace@v1`
        uses: testspace-com/[email protected]
        with:
          domain: ${{ github.bennymeade.testspace.com }}

- name: Publish Results to Testspace
        if: always()
        run: |
          testspace results.xml

But I get the following error:

Run testspace-com/[email protected]
  with:
testspace
Testspace Client, version 2.8.5013
Copyright (C) 2021 S2 Technologies, Inc.

Unable to proceed. Unable to access "testspace-config" space in "bennymeade:testing-testspace" project at Testspace (https://.testspace.com) with specified credentials. Failed performing request: [6] Couldn't resolve host name
For more information about Testspace, visit www.testspace.com.
Error: Process completed with exit code 2.

Note that the with: is blank and causes project at Testspace (https://.testspace.com) with specified credentials

A workflow configured to run on both pushes and pull requests:

on:
  push:
  pull_request:

Will run twice for pull requests from the same repository (once for push, once for pull request).

If this action is used in a such workflow, upload will fail:

Unable to proceed. HTTP PUT failed: [403] Updating the content of a complete result is not allowed.

It will happen even if jobs of one of these workflows will be skipped.

Example: ddterm/gnome-shell-extension-ddterm#148