Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow ability to pass in --no-configuration-cache argument #43

Closed
mhernand40 opened this issue Aug 11, 2022 · 2 comments · Fixed by #44
Closed

Allow ability to pass in --no-configuration-cache argument #43

mhernand40 opened this issue Aug 11, 2022 · 2 comments · Fixed by #44

Comments

@mhernand40
Copy link

I'm working out of a project that enables configuration cache by default for the entire project. However, the dependencies currently does not work well with configuration cache.

Please see:

Whenever I try using this GitHub action in my project, I get the following failure in CI:

* What went wrong:
Execution failed for task ':app:dependencies'.
> The value of this property has been discarded during serialization.

I guess we could wait until Gradle 7.6.0 gets officially released but in the meantime, it would be great if we could pass in additional optional arguments to the dependencies task so that I can pass in --no-configuration-cache until this issue gets resolved by Gradle.

@mateuszkwiecinski
Copy link
Member

Hey 👋 Thanks for the report!
I added new argument additional-gradle-arguments which will be passed to each Gradle invocation. In your case, passing a additional-gradle-arguments: "--no-configuration-cache" should do the trick (but please make sure you're using the latest version 1.1.3)

@mhernand40
Copy link
Author

Thank you @mateuszkwiecinski. Works like a charm 👍

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

Successfully merging a pull request may close this issue.

2 participants