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

Display git build info (FINERACT-883) #778

Merged
merged 3 commits into from
Apr 26, 2020
Merged

Conversation

xurror
Copy link
Contributor

@xurror xurror commented Apr 21, 2020

Display fineracts git build info actuator/info endpoint

Description

Describe the changes made and why they were made. Ignore if these details are present on the associated Jira ticket

Checklist

Please make sure these boxes are checked before submitting your pull request - thanks!

Our guidelines for code reviews is at https://cwiki.apache.org/confluence/display/FINERACT/Code+Review+Guide

@vorburger
Copy link
Member

@xurror can you locally run and fix ./gradlew rat ? Some license header is missing.

BTW this has nothing to do with FINERACT-905, confusion.

PS please ignore the failed Build - Summary, and only look at Travis (see FINERACT-907).

@xurror
Copy link
Contributor Author

xurror commented Apr 22, 2020

PS please ignore the failed Build - Summary, and only look at Travis (see FINERACT-907).

Was wondering where it came from. Thanks for the notice

@xurror can you locally run and fix ./gradlew rat ? Some license header is missing.

Looking into it. It's kind of weird rat-report.txt is getting checked for license.

@xurror xurror force-pushed the FINERACT-883 branch 3 times, most recently from eb33555 to 639412d Compare April 22, 2020 07:24
@xurror
Copy link
Contributor Author

xurror commented Apr 22, 2020

./gradlew rat passes locally.

@xurror xurror closed this Apr 22, 2020
@xurror xurror reopened this Apr 22, 2020
@xurror xurror force-pushed the FINERACT-883 branch 6 times, most recently from c097c8c to bcb7ac3 Compare April 23, 2020 08:27
@xurror xurror closed this Apr 23, 2020
@xurror xurror reopened this Apr 23, 2020
@xurror xurror force-pushed the FINERACT-883 branch 2 times, most recently from f2eea3a to d9103ac Compare April 25, 2020 06:20
@xurror xurror changed the title FINERACT-883 Dispaly git build info(FINERACT-883) Apr 25, 2020
@xurror
Copy link
Contributor Author

xurror commented Apr 25, 2020

Oh now this interesting. Seems .git directory cannot be found here since it is a file which is automatically ignored

This also fails with docker build.

@xurror
Copy link
Contributor Author

xurror commented Apr 25, 2020

It's hard for me to figure out how to pull this off.

I'm thinking to set the option failOnNoDotGitFound to false. @vorburger, @awasum do you think we can go with that.

@xurror xurror closed this Apr 25, 2020
@xurror xurror reopened this Apr 25, 2020
@nikpawar89
Copy link
Member

@xurror i saw the build, in your case following test case is failing:
org.apache.fineract.integrationtests.AccountingScenarioIntegrationTest > checkPeriodicAccrualAccountingFlow FAILED
java.lang.AssertionError at AccountingScenarioIntegrationTest.java:588

For now may be you want to ignore the the testcase . But definitely it is not a long time solution.
It appears to me a concurrency issue on Loan entity object and is not limited to integration tests.

@vorburger vorburger changed the title Dispaly git build info(FINERACT-883) Display git build info (FINERACT-883) Apr 26, 2020
@vorburger
Copy link
Member

@xurror re. test failure, follow #782 to find FINERACT-899 and note #774, I think if you rebase this, that will disappear.

Oh now this interesting. Seems .git directory cannot be found here since it is a file which is automatically ignored

I don't think the .git/ is a file which is automatically ignored, but I suspect there are several situations where it's not present... this project certainly should still build even if there is no .git/ directory present. This could happen if someone builds from the Release ZIP, and a few other situations I can imagine...

I'm thinking to set the option failOnNoDotGitFound to false. @vorburger, @awasum do you think we can go with that.

... therefore something like that would probably be acceptable / good idea; see FINERACT-911.

However I do not find an option failOnNoDotGitFound so I suspect this was a typo?

@xurror
Copy link
Contributor Author

xurror commented Apr 26, 2020

@xurror re. test failure, follow #782 to find FINERACT-899 and note #774, I think if you rebase this, that will disappear.

Oh now this interesting. Seems .git directory cannot be found here since it is a file which is automatically ignored

I don't think the .git/ is a file which is automatically ignored, but I suspect there are several situations where it's not present... this project certainly should still build even if there is no .git/ directory present. This could happen if someone builds from the Release ZIP, and a few other situations I can imagine...

I'm thinking to set the option failOnNoDotGitFound to false. @vorburger, @awasum do you think we can go with that.

... therefore something like that would probably be acceptable / good idea; see FINERACT-911.

However I do not find an option failOnNoDotGitFound so I suspect this was a typo?

Oops, typo. It's failOnNoGitDirectory.

xurror added 3 commits April 26, 2020 14:31
Display fineracts git build info actuator/info endpoint
@xurror
Copy link
Contributor Author

xurror commented Apr 26, 2020

@vorburger, this passes now. Hope the you OK with the actual changes

Copy link
Member

@vorburger vorburger left a comment

Choose a reason for hiding this comment

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

LGTM!

@vorburger vorburger merged commit 394a7fb into apache:develop Apr 26, 2020
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.

3 participants