While testing the New Relic StatsD Integration, I needed to automate the process. So, I created a pipeline on GitHub Actions that triggered the New Relic StatsD integration every time a test code push occurred to my main branch. To run both the integration and my k6 test concurrently, I had to implement a workaround using a service container on GitHub Actions.
I already have an article published about this configuration (in Portuguese). I'd be glad to translate it to English and add it to your documentation.
While testing the New Relic StatsD Integration, I needed to automate the process. So, I created a pipeline on GitHub Actions that triggered the New Relic StatsD integration every time a test code push occurred to my main branch. To run both the integration and my k6 test concurrently, I had to implement a workaround using a service container on GitHub Actions. I already have an article published about this configuration (in Portuguese). I'd be glad to translate it to English and add it to your documentation.