Hey!
Great work, Courage!
Regarding what you wrote in your first mail:
Lastly, we could publish the built Fineract CN services libraries to a
Maven Artifactory so developers will not have to manually clone and publish
these services by themselves.
You didn't put that into the Jira ticket but I got an idea how we could
smoothly solve this step using jitpack.io
I thought it would be good to share this idea in the current discussion.
Publishing a new version of a library to Maven Central is quite a work.
With jitpack.io one can just use a git commit hash as a version number (or
branchname-SNAPSHOT to get the build of the latest commit).
Basically, you one needs to configure jitpack repository as a dependency (I
use maven style as example):
<repository>
<id>jitpack.io</id>
<url>https://jitpack.io</url>
</repository>
and then there is need to specify the dependency using Github url:
For example
https://github.com/apache/fineract-cn-identity
with Latest commit 6f8498d 4 days ago
turns into the following dependency:
<dependency>
<groupId>com.github.aasaru</groupId>
<artifactId>fineract-cn-identity</artifactId>
<version>6f8498d</version>
</dependency>
Jitpack checks out and builds the jar during the first request.
And it can be also downloaded from the public Maven repo that jitpack
serves. Url would be something like:
https://jitpack.io/com/github/apache/fineract-cn-identity/6f8498d/...
For now this doesn't work yet (I suspect the gradle command that
jitpack uses doesn't result with a build
due to the current configuration of fineract-cn-identity build.gradle. This
needs yet to be investigated.
Kind regards
Juhan
Kontakt Courage Angeh (<[email protected]>) kirjutas kuupäeval P, 10.
märts 2019 kell 23:03:
> Hi Guys,
>
> I have created this task on Jira:
> https://issues.apache.org/jira/browse/FINCN-139
>
> I think the project to should be added to the GSoC 2019 idealist.
>
> Thanks,
> Courage
>
> On Sat, Mar 9, 2019 at 2:04 PM Courage Angeh <[email protected]>
> wrote:
>
> > Thanks and you're welcome.
> >
> > On Sat, Mar 9, 2019, 8:01 AM Myrle Krantz <[email protected]> wrote:
> >
> >> Wonderful!
> >>
> >> I've merged.
> >>
> >> Thank you Courage,
> >> Myrle
> >>
> >> On Sat, Mar 9, 2019 at 1:14 AM Courage Angeh <[email protected]>
> >> wrote:
> >>
> >> > Hello guys,
> >> >
> >> > Hope this email finds you well. For the past weeks, I have been
> working
> >> on
> >> > moving the different Fineract CN service Dockerfiles to their
> respective
> >> > repositories. Here are the PRs, can some please view and merge them:
> >> >
> >> > https://github.com/apache/fineract-cn-rhythm/pull/7
> >> > https://github.com/apache/fineract-cn-identity/pull/8
> >> > https://github.com/apache/fineract-cn-office/pull/8
> >> > https://github.com/apache/fineract-cn-accounting/pull/9
> >> > https://github.com/apache/fineract-cn-deposit-account-management
> >> > https://github.com/apache/fineract-cn-portfolio
> >> > https://github.com/apache/fineract-cn-teller/pull/10
> >> >
> >> > What work is left for successful deployment?
> >> >
> >> > First, we need to configure Docker scripts to deploy and manage the
> >> system
> >> > on swarm mode. Then update provision and migration script to work with
> >> > cluster environments and create the chart accounts.
> >> > We also have to add Jenkins to the different Fineract CN services,
> then
> >> > each service to its image on DockerHub.
> >> > Lastly, we could publish the built Fineract CN services libraries to a
> >> > Maven Artifactory so developers will not have to manually clone and
> >> publish
> >> > these services by themselves.
> >> >
> >> > But all this needs resources like a DockerHub and Jenkins account.
> >> > I would like to propose this project for a GSoC project.
> >> >
> >> > Thanks,
> >> > Courage.
> >> >
> >>
> >
>
