Skip to content

Conversation

kingg22
Copy link
Contributor

@kingg22 kingg22 commented Sep 3, 2025

close #2492

…with a custom test task

configuration of properties is set up before execute test and print a summary after suite. Without use of project is cacheable
… on demand, caching

run parallel don't have perfect support with test containers, have problems with ports
…guration cache, refactor use of project

ascii doctor plugin is not compatible yet asciidoctor/asciidoctor-gradle-plugin#730
…re and explicit get input of properties

Gradle need to know all input and prevent side effect with dynamic behaviors
@kingg22
Copy link
Contributor Author

kingg22 commented Sep 3, 2025

@DavideD Hey, need to check with codeql because it need pass the flag --no-configuration-cache and maybe --no-build-cache, but don't have manual workflow dispatch and is auto configure.
Where can I put the documentation about these changes in release pipeline? TLDR maven publish need pass no-configuration-cache and all task related to publish need a fresh build without cache.

If anyone have problem with the module documentation do clean and assemble, if still failing ascii, pass the flag, I mark as incompatible, but gradle can fail inclusive with this mark.

In documentation/build.gradle I recommend put dependsOn on other task (no assemble) because when a no cacheable task is in the pipeline, gradle don't store configuration cache, maybe task build or other.

@kingg22
Copy link
Contributor Author

kingg22 commented Sep 3, 2025

Current CI action fail in session example test is not related with my changes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Enable Gradle Configuration Cache for Faster Builds
1 participant