### Description The gradle build is caching some intermediate artifacts that influences how the reports are generated. For instance, after running the tests, if the report aggregation generates the "Features" and "Stories" tabs, these are kept generated even when the tests are modified to not generate these tabs. ### Steps to reproduce 1. Checkout the master branch of my clone of the serenity-junit-starter project: ``` $ git clone git@github.com:gallardo/serenity-junit-starter.git ``` 2. Cd into the repository and build the reports using the daemon (Notice that I'm disabling gradle's cache) ``` $ cd serenity-junit-starter $ ./gradlew --no-build-cache clean clearReports test ``` 3. The report is generated with tabs _Features_ and _Stories_: ``` $ egrep "Features|Stories" target/site/serenity/index.html Features Stories

Features

``` 4. Checkout the tag `issue-01-should-not-create-features-report` ``` $ git checkout issue-01-should-not-create-features-report $ ./gradlew --no-build-cache clean clearReports test ``` ### Expected The new report doesn't exhibit the tabs _Features_ and _Stories_ ### Actual The report is generated with tabs _Features_ and _Stories_, even when it shouldn't due to missing configuration ``` $ egrep "Features|Stories" target/site/serenity/index.html Features Stories ``` ### Workaround Build without daemon ``` $ ./gradlew --no-daemon clean clearReports test $ egrep "Features|Stories" target/site/serenity/index.html $ echo $? 1 ``` ### Environment ``` $ ./gradlew --no-daemon -version ------------------------------------------------------------ Gradle 7.2 ------------------------------------------------------------ Build time: 2021-08-17 09:59:03 UTC Revision: a773786b58bb28710e3dc96c4d1a7063628952ad Kotlin: 1.5.21 Groovy: 3.0.8 Ant: Apache Ant(TM) version 1.10.9 compiled on September 27 2020 JVM: 11.0.14.1 (Amazon.com Inc. 11.0.14.1+10-LTS) OS: Linux 5.3.18-59.34-default amd64 ``` ### Notice I came across this phenomenon trying to debug one test of mine that wasn't generating these _Features_ and _Stories_ tabs. I began with a relative complex test, and began to simplify it to the bare minimum. I compared it to the official starter project, and couldn't see why it didn't work, so I keep going simplifying the starter project until the starter project had almost anything, but generated these tabs and everything was beyond explanation...

Gradle is wrongly caching something, influencing the generation of "Features" and "Stories" tab #2796

Company

Community

Support

Connect