Re: [FINERACT] [VOTE] ️ 1.8.0 for release

[Nasser Kaze]

+1

On Wed, Aug 24, 2022 at 11:55 AM Sifiso Mtetwa 
wrote:

> +1
>
>
>
> Got it thanks. Perfect!
>
>
>
> *From:* Aleksandar Vidakovic [mailto:al...@apache.org]
> *Sent:* Tuesday, 23 August 2022 14:50
> *To:* sif...@skyburgsystems.org
> *Cc:* dev@fineract.apache.org
> *Subject:* Re: [FINERACT] [VOTE] ️ 1.8.0 for release
>
>
>
> ... thanks for the heads up... my bad, the release script didn't run
> through for this step (dist upload)... I triggered it manually again,
> please check.
>
>
>
> On Tue, Aug 23, 2022 at 2:29 PM  wrote:
>
> Hi Aleks,
>
>
>
> Hope you’re well. When we try to access the link to the source and binary
> artifact for 1.8.0 it says not found
>
>
>
> When I checked for the artifacts available it listed up to 1.7.0
>
>
>
> Please advise
>
>
>
> Regards,
>
>
>
>
>
>
>
> -Original Message-
> From: Aleksandar Vidakovic [mailto:al...@apache.org]
> Sent: Monday, 22 August 2022 18:35
> To: dev@fineract.apache.org
> Subject: [FINERACT] [VOTE] ️ 1.8.0 for release
>
>
>
> Hello everyone,
>
>
>
> ... we have created Apache Fineract 1.8.0 release, with the artifacts
> below up for a vote.
>
>
>
> It fixes the following issues:
> https://cwiki.apache.org/confluence/display/FINERACT/1.8.0+-+Apache+Fineract
>
>
>
> Source & Binary files :
> https://dist.apache.org/repos/dist/dev/fineract/1.8.0/
>
>
>
> Tag to be voted on (rc#):
> https://gitbox.apache.org/repos/asf?p=fineract.git;a=commit;h=refs/heads/1.8.0
>
>
>
> Fineract's KEYS containing the PGP key we used to sign the release:
> https://dist.apache.org/repos/dist/dev/fineract/KEYS
>
>
>
> Note that this release contains source and binary artifacts.
>
>
>
> This vote will be open for 72 hours:
>
>
>
> [ ] +1 approve
>
> [ ] +0 no opinion
>
> [ ] -1 disapprove (and reason why)
>
>
>
> Cheers,
>
>
>
> Aleksandar Vidakovic
>
>

Re: Fineract 1.6 - How do I run the Jar? War?

[Nasser Kaze]

Hi AirsayLongCon,

The error suggests a problem with connection to your database. Fineract by
default tries to connect to the database with the credentials: user: “root”
password: “mysql”.

Unless you’ve changed this setting in the project configuration, you want
to make sure your database root user has thesame password.

Regards
Nasser


AirsayLongCon  schrieb am Mo. 14. März 2022 um
07:56:

> Hello everyone,
> I am having some issues attempting to run the jar. When I run the following
>
> ```java -Dloader.path=. -jar
> fineract-provider/build/libs/fineract-provider.jar```
>
> I get the following error in the attached file.
>
> How can I fix this?
>
> Regards
> Airsay
>

Re: CI based on GitHub Actions

[Nasser Kaze]

+1

On Fri, Nov 5, 2021 at 01:41 VICTOR MANUEL ROMERO RODRIGUEZ <
victor.rom...@fintecheando.mx> wrote:

> +1
>
> El jue, 4 nov 2021 a las 17:17, Nazeer Hussain Shaik (<
> nazeerhussain.sh...@gmail.com>) escribió:
>
>> +1
>>
>> Thanks,
>> Nazeer
>>
>> On Fri, Nov 5, 2021 at 2:42 AM Bharath Gowda  wrote:
>>
>>> +1 :)
>>>
>>> On Fri, Nov 5, 2021, 2:07 AM Awasum Yannick  wrote:
>>>
 +1

 On Thu, Nov 4, 2021 at 5:36 PM Ed Cable  wrote:

> +1 from my side and I think @Michael Vorburger  has
> been a fan as well as we've implemented it as CI for Mifos/OpenMF repos.
>
> Ed
>
> On Thu, Nov 4, 2021 at 9:08 AM Aleksandar Vidakovic <
> chee...@monkeysintown.com> wrote:
>
>> +1 for Github Actions... use it for quite a while and it's really
>> reliable.
>>
>> On Thu, 4 Nov 2021, 16:20 Benura Abeywardena, 
>> wrote:
>>
>>> Hi Petri,
>>>
>>> Good idea !
>>>
>>> Thanks & Regards,
>>> Benura
>>>
>>> On Thu, Nov 4, 2021 at 8:25 PM Petri Tuomola <
>>> petri.tuom...@gmail.com> wrote:
>>>
 Hi all

 As I’m sure you’ve noticed, Travis builds have recently been
 getting more and more unreliable: either there is a queue of several 
 hours
 before the build is executed, or in many cases no build is triggered at
 all. This seems to be due to the limits on Apache’s Travis account. I 
 asked
 about this in the Apache Infra JIRA, and the answer was as follows:

 "Our Travis CI capacity is very limited and we will not be
 increasing that limit in the foreseeable future. If you are not happy 
 with
 it, we suggest you switch to GitHub Actions or our Jenkins/BuildBot CI
 instead.”

 Given this, I think it would make sense for us to explore
 alternatives.To try this out, I’ve created a CI build pipeline using 
 Github
 Actions and raised a PR for it (
 https://github.com/apache/fineract/pull/1955). This is a
 “parallel” pipeline - in that I haven’t removed the Travis one. So once
 this PR is merged, we should get both a Github build as well as a 
 Travis
 build for each PR.

 My suggestion would be to merge this and see how the two compare
 for the next week or so. If Github is more reliable / faster, then we 
 could
 switch off the Travis one altogether.

 The only caveat is: I have not been able to test this very
 comprehensively, as the actions do not run unless the PR is merged. 
 They
 seem to work OK in my own repository, but I can’t guarantee they will
 immediately work in the Apache repo. So there may be some false 
 failures
 initially until we get this build working without issues. However, 
 despite
 the possible “noise” from these failures, I think this would be a
 worthwhile exercise.

 Any concerns? If not, I can merge the actions in tomorrow and then
 address any issues to get them working asap.

 Regards
 Petri


>
> --
> *Ed Cable*
> President/CEO, Mifos Initiative
> edca...@mifos.org | Skype: edcable | Mobile: +1.484.477.8649
>
> *Collectively Creating a World of 3 Billion Maries | *http://mifos.org
>     
>
>