feat: ci: upload junit xml reports to buildpulse

[galargh]

Related Issues

#12127

Proposed Changes

Create a workflow that uploads junit XML reports that the Test workflow produces to BuildPulse.

Additional Info

This PR depends on setting up the following repository variables:

• BUIDPULSE_ACCOUNT_ID
• BUILDPULSE_REPOSITORY_ID
• BUILDPULSE_ACCESS_KEY_ID

And the following repository secrets:

• BUILDPULSE_SECRET_ACCESS_KEY

Checklist

Before you mark the PR ready for review, please make sure that:

• Commits have a clear commit message.
• PR title is in the form of of <PR type>: <area>: <change being made>
  • example: fix: mempool: Introduce a cache for valid signatures
  • PR type: fix, feat, build, chore, ci, docs, perf, refactor, revert, style, test
  • area, e.g. api, chain, state, mempool, multisig, networking, paych, proving, sealing, wallet, deps
• Update CHANGELOG.md or signal that this change does not need it.
  • If the PR affects users (e.g., new feature, bug fix, system requirements change), update the CHANGELOG.md and add details to the UNRELEASED section.
  • If the change does not require a CHANGELOG.md entry, do one of the following:
    • Add [skip changelog] to the PR title
    • Add the label skip/changelog to the PR
• New features have usage guidelines and / or documentation updates in
  • Lotus Documentation
  • Discussion Tutorials
• Tests exist for new functionality or change in behavior
• CI is green

[BigLep]

My comments may be newbie as someone who hasn't done much with GHA.

[BigLep]

Looks good to me. I assume we'll only be able to see what BuildPulse looks like after this gets merged.

[galargh]

Looks good to me. I assume we'll only be able to see what BuildPulse looks like after this gets merged.

Yes, we'll also need the following set up in the repo.

Repository variables:

• BUIDPULSE_ACCOUNT_ID
• BUILDPULSE_REPOSITORY_ID
• BUILDPULSE_ACCESS_KEY_ID

Repository secrets:

• BUILDPULSE_SECRET_ACCESS_KEY

Would you be able to do it? If you need any help with that, let me know.

I'm going to merge this and disable the workflow. We can then reenable it once we have the secrets we need set up.

[BigLep]

@galargh: thanks - my bad for not doing that sooner.

I have added these to
https://github.com/filecoin-project/lotus/settings/secrets/actions
https://github.com/filecoin-project/lotus/settings/variables/actions