GitHub Actions Plugin | Gatling Blog

After integrations with Jenkins, Bamboo (Atlassian), and TeamCity (JetBrains), we're proud to inform you that Gatling Enterprise now has a native GitHub Actions plugin.

What is Github Actions?

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.

Until now, running Maven, Gradle, or sbt and updating Gatling Enterprise test packages have been possible.

You would typically trigger such an Action on commit to keep your Gatling Enterprise packages up-to-date with the latest changes in your GitHub repository containing your test sources.

With the release of our official GitHub Actions “gatling/enterprise-action@v1”, you can also trigger your tests to run on Gatling Enterprise.

How can can I run tests?

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.

Examples of succeeded and failed tests:

Any questions?

We can’t say it enough: The documentation is where you need answers and details to work smoothly with Gatling and Gatling Enterprise.

If you still have questions or want to discuss this new plugin, join the Gatling Community! Users and Gatling members will happily try to help you.