mikepenz/action-junit-report

JUnit report sent to wrong build

Open

#40 opened on Feb 11, 2021

View on GitHub
 (36 comments) (16 reactions) (1 assignee)TypeScript (156 forks)github user discovery
help wanted

Repository metrics

Stars
 (418 stars)
PR merge metrics
 (PR metrics pending)

Description

Dear maintainer,

Thanks so much for creating this excellent plugin and sharing it for others to use!

I have multiple workflows defined, and it seems that the check is added to the first workflow, rather than the one that actually ran the test suite. Is there some way to associate the report with the correct workflow definition? Ideally I'd like the report to be below the test suite (e.g. job that runs tests, publishes report, should have the report appended as a check below it or nearby)

Contributor guide

Research direction
Investigate how the action determines which workflow run to attach the check to. Look for usage of `github.context` or environment variables like `GITHUB WORKFLOW` to see if multiple workflows cause misidentification.
Tech stack
typescriptgithub actions
Domain
ci cd
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
GitGitHub Actions
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60