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

fix(gradle-wrapper): skip artifacts update if no gradlew command found #6229

Merged
merged 3 commits into from
May 14, 2020

Conversation

rarkins
Copy link
Collaborator

@rarkins rarkins commented May 14, 2020

No description provided.

@rarkins
Copy link
Collaborator Author

rarkins commented May 14, 2020

I think our tests need updating. Currently we see some warnings in the app because we attempt to run null ...... which clearly won't work.

Copy link
Member

@viceice viceice left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes needs test updates. Do you need help for it?

@rarkins
Copy link
Collaborator Author

rarkins commented May 14, 2020

Yes needs test updates. Do you need help for it?

If you don't mind, because I skip Java tests locally still. The existing tests started failing because they were based on null gradlew

@viceice
Copy link
Member

viceice commented May 14, 2020

ok, will do after lunch 🙃

@rarkins rarkins marked this pull request as draft May 14, 2020 11:11
@viceice
Copy link
Member

viceice commented May 14, 2020

So tests are working, now i add some mock tests too, so we always have 100% coverage for the java tests too (even without real gradle tests)

@rarkins rarkins marked this pull request as ready for review May 14, 2020 12:53
@rarkins rarkins merged commit 61c4fcd into master May 14, 2020
@rarkins rarkins deleted the fix/gradle-artifacts-no-gradlew branch May 14, 2020 12:53
@renovate-release
Copy link
Collaborator

🎉 This PR is included in version 19.239.1 🎉

The release is available on:

Your semantic-release bot 📦🚀

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Dec 16, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants