Hi. As you can see, the runs feature a hash instead of a branch name, what could be the cause? Those runs showed up as a result of running
BUILDKITE_ANALYTICS_TOKEN=(token) npm test
on the branch that enables the test analytics. Thanks
Hi. As you can see, the runs feature a hash instead of a branch name, what could be the cause? Those runs showed up as a result of running
BUILDKITE_ANALYTICS_TOKEN=(token) npm test
on the branch that enables the test analytics. Thanks
Hi @artefacto ,
Welcome to the Buildkite Support Community!
Would you be able to send email us at support@buildkite.com a build URL that has the test analytics enabled? This would help us investigate your environment fully as to why the branch names are not showing as expected.
Cheers,
Lizette
Thanks for sending us the build URL, @artefacto!
If you don’t see branch names (or build numbers, commit hashes, etc.) in the Test Analytics UI, please see our documentation on CI environments to learn how to export your environment to the collector. The environment variable you’re looking for in your particular case is BUILDKITE_BRANCH
(field name: run_env[branch]
).
Best!