Hi Gatling Community members!
After integrations with Jenkins, Bamboo (Atlassian) and TeamCity (JetBrains), we’re very proud to let you know that Gatling Enterprise now has a native GitHub Actions plugin.
GitHub Actions is GitHub’s Continuous Integration product. It lets you define jobs in a declarative way that can be either scheduled or react on your repository events such as commits or Pull Requests.
Up until now, it was already possible to run Maven, Gradle, or sbt and update Gatling Enterprise test packages.
You would typically trigger such an Action on commit to always keep your packages in Gatling Enterprise up-to-date with the latest changes in your GitHub repository containing your test sources.
Now, with the release of our official GitHub Actions “gatling/enterprise-action@v1”, you can also trigger your tests to run on Gatling Enterprise.
You can either run tests:
-
in a blocking fashion so you get the results in GitHub’s interface and possibly fail your pipeline and report performance issues;
-
or in a non-blocking fashion so you don’t consume any GitHub Actions credits for the time the load test is running.
Below is an example of succeeded and failed test:
Succesful test:
Failed test:
Still got questions?
We can’t say it enough, the documentation is that place to be if you need answers and details to work with the Gatling and Gatling Enterprise smoothly.
We hope that this new integration will make it easier for you to incorporate performance testing into your development process, so let us know about your feedback.