jeantil commented on PR #2842: URL: https://github.com/apache/james-project/pull/2842#issuecomment-3493741997
I checked the build scans of each builds for the first commits. the problem started with [ci job #8](https://ci-builds.apache.org/job/james/job/ApacheJames/job/PR-2842/8/cloudbees-pipeline-explorer/) for commit [3be7e4c](https://github.com/apache/james-project/pull/2842/commits/3be7e4c006ff07fbbc2999e2169e3db3007e6a69) The Build stage's [buildscan](https://develocity.apache.org/s/6m55njszbi3v2) is weird. It does report the scala compile goal execution as being loaded from cache. <img width="2108" height="915" alt="2025-11-05_22-19" src="https://github.com/user-attachments/assets/a9941876-01fc-4191-bbbe-b803383b3675"; /> which shouldn't be the case since the commit we are build changed a single file in the sourceDir of thes plugin which should have invalidated the cache key. But it does trigger a javac compile because of changed dependency <img width="1836" height="732" alt="2025-11-05_22-25" src="https://github.com/user-attachments/assets/5e0b8733-fb77-4a86-86ae-330463f2c969"; /> I can reproduce the problem locally : 1. enable buildscan upload in .mvn/develocity 2. run `mvn clean package -DskipTests -Djib.skip -T1C -Dorg.slf4j.simpleLogger.showDateTime=true -Dorg.slf4j.simpleLogger.dateTimeFormat=HH:mm:ss,SSS` (lasts about 1min20 on my laptop) 3. edit file `server/protocols/jmap-rfc-8621-integration-tests/jmap-rfc-8621-integration-tests-common/src/main/scala/org/apache/james/jmap/rfc8621/contract/EmailSetMethodContract.scala` with a trivial change such as <img width="1468" height="586" alt="2025-11-05_22-37" src="https://github.com/user-attachments/assets/c37f2e04-fdae-49e2-a55d-a1b85dd05c59"; /> 4. run the same build again load the buildscan. it loads the output of scala compilation from cache ignoring the file change. I asked for help on the asf slack's channel for builds :crossed_fingers: -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
