Lack of lastRun.txt file

Gatling (Open-Source)
1

Gatling version:
Gatling flavor: java kotlin scala javascript typescript
Gatling build tool: maven gradle sbt bundle npm

I made sure I’ve update my Gatling version to the latest release
I read the guidelines and how to ask a question topics.
I provided a SSCCE (or at least, all information to help the community understand my topic)
I copied output I observe, and explain what I think should be.

Hello,

After upgrade gatling version from 3.13.1 to 3.14.9 I found that the lastRun.txt file is not a part of gatling results anymore.

Why such change was introduced? Is it possible somehow to re-enable such feature?

BR
Mateusz

2

Hello,

The lastRun.txt is an internal used by the gatling-maven-plugin 's gatling:verify mojo.

It was previously always generated, which was wrong.
It’s now only generated when the failOnError config option is set (which is a requirement for the verify mojo) and deleted once verify has run.

Note: I insist on the internal aspect of this file: don’t hack it for building some in-house process, we can break it anytime.

1 Like
3

Thanks. I used such file for some automation after having many simulation directories, I will update it on my side to get latest dir by modification date