You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
More to the point however, is do you have any advise on how one can test/debug their implementation of .github/workflows/test-report.yml in a PR -- without having to iterate on landing updates to make it work to the master branch?
I have tried adding on: -> workflow_dispatch to my .github/workflows/test-report.yml and then running the workflow manually but that manual run doesn't find artifacts to report on, I suppose because it has no linkage back to a .github/workflows/ci.yml that uploaded artifacts?
When run from a workflow_run trigger, I am guessing that this is the triggering workflow run but when run from a workflow_dispatch trigger, it is it's self.
Any thoughts on being able to make this action simulate a workflow_run trigger by being able to provide a run id value for
when triggered from a workflow_dispatch with an input perhaps?
Or am I barking up the completely wrong tree here in trying to test my .github/workflows/test-report.yml before merging it to the default branch and there is a better way?
Alternatives considered
Not sure of any other alternatives.
The text was updated successfully, but these errors were encountered:
I just realized that my suggestion doesn't work with actions/upload-artifact@v3 or older. However, it should work with actions/upload-artifact@v4 when #363 has been resolved. (Maybe it has been resolved already.) The problem is that with actions/upload-artifact@v3 and older, artifacts are not available over the REST API (which is used by this action) as long as the workflow is still in progress.
Describe
Hello.
Per your description for Recommended setup for public repositories how does the
artifact:
option know which triggering run to go fetch the artifacts from?More to the point however, is do you have any advise on how one can test/debug their implementation of
.github/workflows/test-report.yml
in a PR -- without having to iterate on landing updates to make it work to the master branch?I have tried adding
on:
->workflow_dispatch
to my.github/workflows/test-report.yml
and then running the workflow manually but that manual run doesn't find artifacts to report on, I suppose because it has no linkage back to a.github/workflows/ci.yml
that uploaded artifacts?Proposed solution
I suppose it's this (NPI):
test-reporter/src/input-providers/artifact-provider.ts
Lines 53 to 56 in c40d89d
When run from a
workflow_run
trigger, I am guessing thatthis
is the triggering workflow run but when run from aworkflow_dispatch
trigger, it is it's self.Any thoughts on being able to make this action simulate a
workflow_run
trigger by being able to provide a run id value fortest-reporter/src/input-providers/artifact-provider.ts
Line 55 in c40d89d
workflow_dispatch
with an input perhaps?Or am I barking up the completely wrong tree here in trying to test my
.github/workflows/test-report.yml
before merging it to the default branch and there is a better way?Alternatives considered
Not sure of any other alternatives.
The text was updated successfully, but these errors were encountered: