-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Conversation
@xurror can you locally run and fix 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). |
Was wondering where it came from. Thanks for the notice
Looking into it. It's kind of weird rat-report.txt is getting checked for license. |
eb33555
to
639412d
Compare
./gradlew rat passes locally. |
c097c8c
to
bcb7ac3
Compare
f2eea3a
to
d9103ac
Compare
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. |
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 i saw the build, in your case following test case is failing: For now may be you want to ignore the the testcase . But definitely it is not a long time solution. |
@xurror re. test failure, follow #782 to find FINERACT-899 and note #774, I think if you rebase this, that will disappear.
I don't think the
... therefore something like that would probably be acceptable / good idea; see FINERACT-911. However I do not find an option |
Oops, typo. It's failOnNoGitDirectory. |
Display fineracts git build info actuator/info endpoint
@vorburger, this passes now. Hope the you OK with the actual changes |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
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!
Commit message starts with the issue number from https://issues.apache.org/jira/projects/FINERACT/. Ex: FINERACT-646 Pockets API.
Coding conventions at https://cwiki.apache.org/confluence/display/FINERACT/Coding+Conventions have been followed.
API documentation at https://github.com/apache/fineract/blob/develop/api-docs/apiLive.htm has been updated with details of any API changes.
Integration tests have been created/updated for verifying the changes made.
All Integrations tests are passing with the new commits.
Submission is not a "code dump". (Large changes can be made "in repository" via a branch. Ask on the list.)
Our guidelines for code reviews is at https://cwiki.apache.org/confluence/display/FINERACT/Code+Review+Guide