Add step that generate issues based on JUnit test results

[ArthurSens]

Description

Now that we're uploading files correctly (#38236), this PR extends the current unit test workflow to download the artifacts and calling issuegenerator to create the issues.

Link to tracking issue

Related to #36761

[ArthurSens]

Weird, I don't even see the issuegenerator logs here 🤔

https://github.com/open-telemetry/opentelemetry-collector-contrib/actions/runs/13596863176/job/38016799607?pr=38270

[ArthurSens]

@mx-psi, I just wanted to let you know that I believe I'll need to patch issuegenerator to make this work.

As seen in this workflow run, issuegenerator is failing with this error:

2025-03-11T22:06:17.144Z	FATAL	issuegenerator@v0.20.0/main.go:244	Failed to search GitHub Issues	{"error": "GET https://api.github.com/repos/open-telemetry/open-telemetry/opentelemetry-collector-contrib/issues?state=open: 404 Not Found []"}

It is writing open-telemetry twice in the URL. See the difference by clicking:

• https://api.github.com/repos/open-telemetry/open-telemetry/opentelemetry-collector-contrib/issues?state=open:
• https://api.github.com/repos/open-telemetry/opentelemetry-collector-contrib/issues?state=open:

The reason behind this is that the ENV variable GITHUB_REPOSITORY doesn't return only the repository but a string like <owner>/<repository>, as shown in the docs.

Issuegenerator is building this API call by concatenating the ENV variables, GITHUB_REPOSITORY_OWNER and GITHUB_REPOSITORY, and since the latter already contains the owners, we're duplicating that information. See code references [1], [2] and [3].

[ArthurSens]

Opened open-telemetry/opentelemetry-go-build-tools#719 to address the problem

[ArthurSens]

@mx-psi @songy23 looking at the current error:

issuegenerator@v0.21.0/main.go:305	Failed to create GitHub Issue	{"error": "POST https://api.github.com/repos/open-telemetry/opentelemetry-collector-contrib/issues: 403 Resource not accessible by integration []"}

Could this be a misconfiguration in the repo settings? I'm suggesting that based on the discussion https://github.com/orgs/community/discussions/60820#discussioncomment-6445895

[mx-psi]

@ArthurSens Can you file an issue over at https://github.com/open-telemetry/community to ask for this? Only the admins group has permission to see this I think, and we are not part of it

[ArthurSens]

open-telemetry/community#2630

[github-actions]

This PR was marked stale due to lack of activity. It will be closed in 14 days.

[ArthurSens]

PR cleaned up and ready for merge.

Latest test failed due to lack of permissions:

issuegenerator@v0.21.0/main.go:305	Failed to create GitHub Issue	{"error": "POST https://api.github.com/repos/open-telemetry/opentelemetry-collector-contrib/issues: 403 Resource not accessible by integration []"}

Our understanding is that those permissions will only be granted once running from the main branch

---

A commit with a failing test is still there, so we can quickly test the automation once it's merged. We should see an open issue right away.

I can also remove the commit if folks prefer :)

[atoulme]

@ArthurSens would you please open a separate PR removing the test? Then we can merge both PRs one after the other.

[ArthurSens]

Yes, but can we do it beginning of next week? I'm on holidays until Tuesday

[mx-psi]

Discussed offline, since it may be that the 403 error is due to this running on a fork, we are going to merge this and check if it works on main.