Problem with Gatling Jenkins Plugin and Gatling 2.1

Gatling (Open-Source)
1

Hi,

after a successful migration to gatling version 2.1.1 I’ll get the following exception in my jenkins job(s):

ERROR: Publisher com.excilys.ebi.gatling.jenkins.GatlingPublisher aborted due to exception
[com.fasterxml.jackson.databind.exc.UnrecognizedPropertyException](http://stacktrace.jenkins-ci.org/search?query=com.fasterxml.jackson.databind.exc.UnrecognizedPropertyException): Unrecognized field "percentiles3" (class com.excilys.ebi.gatling.jenkins.RequestReport), not marked as ignorable (13 known properties: , "minResponseTime", "numberOfRequests", "standardDeviation", "meanNumberOfRequestsPerSecond", "name", "maxResponseTime", "group1", "meanResponseTime", "group2", "group3", "group4" [truncated]])
 at [Source: /var/lib/jenkins/jobs/qaPerformance-Gatling-OX6/builds/2014-12-16_16-48-35/simulations/QAPerfOX6-7.6.1-Rev5-1418744988514/js/global_stats.json; line: 38, column: 22] (through reference chain: com.excilys.ebi.gatling.jenkins.RequestReport["percentiles3"])
	at com.fasterxml.jackson.databind.exc.UnrecognizedPropertyException.from(UnrecognizedPropertyException.java:79)
	at com.fasterxml.jackson.databind.DeserializationContext.reportUnknownProperty(DeserializationContext.java:579)
	at com.fasterxml.jackson.databind.deser.std.StdDeserializer.handleUnknownProperty(StdDeserializer.java:672)
	at com.fasterxml.jackson.databind.deser.BeanDeserializerBase.handleUnknownProperty(BeanDeserializerBase.java:906)
	at com.fasterxml.jackson.databind.deser.BeanDeserializer.deserializeFromObject(BeanDeserializer.java:328)
	at com.fasterxml.jackson.databind.deser.BeanDeserializer.deserialize(BeanDeserializer.java:121)
	at com.fasterxml.jackson.databind.ObjectMapper._readMapAndClose(ObjectMapper.java:2796)
	at com.fasterxml.jackson.databind.ObjectMapper.readValue(ObjectMapper.java:1903)
	at com.excilys.ebi.gatling.jenkins.SimulationReport.readStatsFile(SimulationReport.java:44)
	at com.excilys.ebi.gatling.jenkins.GatlingPublisher.saveFullReports(GatlingPublisher.java:131)
	at com.excilys.ebi.gatling.jenkins.GatlingPublisher.perform(GatlingPublisher.java:65)
	at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:45)
	at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:770)
	at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:734)
	at hudson.model.Build$BuildExecution.post2(Build.java:183)
	at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:683)
	at hudson.model.Run.execute(Run.java:1784)
	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
	at hudson.model.ResourceController.execute(ResourceController.java:89)
	at hudson.model.Executor.run(Executor.java:240)



Each build is marked as failed -> Finished: FAILURE



We'are using Gatling jenkins plugin 1.0.3



Greetz

Niko
2

Ah, it looks like a side-effect of adding the two additional percentiles to Gatling reports, but without updating the Jenkins plugin as well…
I can push a quick fix this evening to make it work again, adding the two additional percentiles to the reports will take a bit more time though.

3

This https://github.com/jenkinsci/gatling-plugin/pull/8 pull requests solves this new percentiles issue. Also included graphing for multiconfiguration jobs.

4

@Pierre: I also stumbled accross this problem. When do you think you’ll have a new version of the plugin in the official jenkkins repository?

It might be a good idea to set the JSON parser to ignore unknown new attributes instead of throwing an exception. This can be done using ObjectMapper.configure(DeserializationFeature.FAIL_ON_UNKNOWN_PROPERTIES, false)

5

@Christian I’ve already pushed a fix but it needs proper testing: https://github.com/jenkinsci/gatling-plugin/commit/f8e2907dfe77bcf8d15402f43f332d3916a34032

Feel free to give it a try!

Cheers,
Stéphane

6

I compiled the plugin and tested it on our Jenkins. The test was only partially successful. The reports can now be archived but the graphs are missing.
See here: http://i.imgur.com/Icxdzxc.png
and here: http://i.imgur.com/vz4SnAC.png

7

Thanks for your feedback.
I guess a proper fix will have to wait for Monday…

8

Hi,

I’m, also facing the same issue :frowning:

9

Hi,

Little question to be sure that I’m on right track here :wink:
Does this happen only for pre-existing jobs or for new jobs also ?

Cheers,

Pierre

10

Hi, I didn’t actually try that. The job I modified (added the plugin to) existed before. But that used to work in the past (I think I also added the old version of the plugin to an existing job and it started showing the statistics).
What I did do was to run the job a few times so the plugin could collect statistics (which it did according to the log).

11

Please upgrade to the new version of the Gatling maven plugin we’ve released today (1.1.0).
The synchronization process seems to be happening only very 6 hours or so, so please be patient.
https://wiki.jenkins-ci.org/display/JENKINS/Gatling+Plugin

12

Gonna do this as soon as I get back to work

13

Awesome, it works now. Thanks a lot :slight_smile: