Regarding latest gatling version 3.9.5 menu with choices

Gatling (Open-Source)
1

We are using gatling’s latest version, we tend to run our tests on ec2 instance c3 large using Jenkins. In the newer versions of gatling we get a interactive menu -

Do you want to run the simulation locally, on Gatling Enterprise, or just package it?
Type the number corresponding to your choice and press enter
[0]
[1] Run the Simulation locally
[2] Run the Simulation on Gatling Enterprise Cloud
[3] Package the Simulation for Gatling Enterprise

Now, this can be tackled when running on local, but we build our gatling repo on Jenkins as a maven project, we use clean install command to build it, we can’t get past this on Jenkins, we did try passing a command we found on gatling community while building maven goals -

${GATLING_HOME}/bin/gatling.sh --batch-mode and --run-mode local

We couldn’t get any success and our job gets stuck at the above menu, kindly help us with this.

Thank you

2

we build our gatling repo on Jenkins as a maven project,

I don’t get your issue.
This interactive mode is only on by default on the bundle, not on the maven plugin.

3

Is this what you are asking about -

    <gatling.local.home>${project.basedir}/gatling/gatling-charts-highcharts-bundle-3.9.5/bin/gatling.sh</gatling.local.home>
    <gatling.install.script>${project.basedir}/src/test/resources/install-gatling.sh</gatling.install.script>
    <gatling.root>gatling-charts-highcharts-bundle-3.9.5</gatling.root>
4

Sorry, I don’t get how it makes any sense to use the bundle distribution from a maven project instead of using the gatling-maven-plugin.

Anyway, this is your custom made deployment process we can’t help with.
On the deployment/automation side, we can only help with Gatling Enterprise.

5

Hi Stephane, one addition is that we have our test running on local -

[JENKINS] Recording test results[INFO] 
[INFO] <<< gatling-maven-plugin:4.6.0:test (default) < test-compile @ gatling <<<
[INFO] 
[INFO] 
[INFO] --- gatling-maven-plugin:4.6.0:test (default) @ gatling ---

09:48:55,824 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Could NOT find resource [logback-test.xml]
09:48:55,825 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Found resource [logback.xml] at [file:/var/lib/jenkins/workspace/Quality/DNP_EventGateway_QEService_Perf/target/test-classes/logback.xml]
09:48:55,826 |-WARN in ch.qos.logback.classic.LoggerContext[default] - Resource [logback.xml] occurs multiple times on the classpath.
09:48:55,826 |-WARN in ch.qos.logback.classic.LoggerContext[default] - Resource [logback.xml] occurs at [file:/var/lib/jenkins/workspace/Quality/DNP_EventGateway_QEService_Perf/target/test-classes/logback.xml]
09:48:55,826 |-WARN in ch.qos.logback.classic.LoggerContext[default] - Resource [logback.xml] occurs at [jar:file:/var/lib/jenkins/.m2/repository/io/gatling/gatling-maven-plugin/4.6.0/gatling-maven-plugin-4.6.0.jar!/logback.xml]
09:48:55,939 |-INFO in ch.qos.logback.classic.joran.action.ConfigurationAction - debug attribute not set
09:48:55,940 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch.qos.logback.core.ConsoleAppender]
09:48:55,946 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [CONSOLE]
09:48:55,956 |-INFO in ch.qos.logback.core.joran.action.NestedComplexPropertyIA - Assuming default type [ch.qos.logback.classic.encoder.PatternLayoutEncoder] for [encoder] property
09:48:56,060 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting level of logger [io.gatling.http.engine.response] to TRACE
09:48:56,061 |-INFO in ch.qos.logback.classic.joran.action.RootLoggerAction - Setting level of ROOT logger to WARN
09:48:56,061 |-INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [CONSOLE] to Logger[ROOT]
09:48:56,061 |-INFO in ch.qos.logback.classic.joran.action.ConfigurationAction - End of configuration.
09:48:56,062 |-INFO in ch.qos.logback.classic.joran.JoranConfigurator@123ef382 - Registering current configuration as safe fallback point

Gatling 3.10.3 is available! (you're using 3.9.5)
username:******

****************************************
SSO Configuration Values: ******
	GW Exchange EndPoint: ******
	SSO Username: ******
****************************************

username:******

****************************************
SSO Configuration Values: ******
	GW Exchange EndPoint: ******
	SSO Username: ******
****************************************

Simulation com.QeHelloWorldJava started...

We are getting stuck exactly there

6

Hi,

Then, that’s not something we can help with here.

If you’re looking for a way to automate your Gatling deployments, for example on AWS, the only way that’s supported here is Gatling Enterprise. If you decide to use it, we’ll gladly help then.

If you want to use a third party solution, you have to reach out directly its authors on their own channel, eg their GitHub repository.

Regards

7

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.