[ 
https://issues.apache.org/jira/browse/FINERACT-697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16767490#comment-16767490
 ] 

Michael Vorburger.ch commented on FINERACT-697:
-----------------------------------------------

INFRA-17814 has enabled Travis CI for fineract.git, and clarified that :

{quote}Please join and ask for help on the [email protected] mailing list. If 
you run into a specific issue that you can't solve, feel free to ask in 
#asfinfra on slack.{quote}

Next step: https://github.com/apache/fineract/pull/518 and 
https://github.com/apache/fineract/pull/519 and re-test via 
https://github.com/apache/fineract/pull/519 and a breaking change...

> github.com/apache/fineract has no CI to validate PRs
> ----------------------------------------------------
>
>                 Key: FINERACT-697
>                 URL: https://issues.apache.org/jira/browse/FINERACT-697
>             Project: Apache Fineract
>          Issue Type: Bug
>            Reporter: Michael Vorburger.ch
>            Priority: Major
>
> While code reviewing https://github.com/apache/fineract/pull/468/ I've 
> noticed that Fineract (non-CN) doesn't even have CI set-up for GH PRs... that 
> seems pretty basic?
> [~myrle] or [~vishwasbabu] is that something you would be willing to set up? 
> Or would you like me to take a moment to help set it up? I probably need to 
> be granted "admin" access to apache/fineract... so that I can see the 
> Setttings tab on that repo (which I currently do not see, probably because 
> I'm  somewhere configured to be just a committer but not an admin?) which 
> should let me add the hook required e.g. by Travis CI.
> [[email protected]] ([[email protected]] ?) or 
> [[email protected]] ([~bdelacretaz] ?), BTW FYI you confusingly got 
> two active IDs, or anyone else who can help with infra - is there an easy to 
> set up and ready to use Travis CI equivalent at apache.org which I should be 
> aware of and use for Apache Fineract instead of Travis?



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to