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

Michael Vorburger commented on FINERACT-970:
--------------------------------------------

Phew... this... actually... turned out to be a hell of a lot of work! :D

But it now seems to finally fully work nicely!!  See the 6 PRs linked above.

[https://github.com/apache/fineract/blob/develop/.github/workflows/fineract.dev.yaml]

[https://github.com/apache/fineract/actions?query=workflow%3A%22Deploy+to+https%3A%2F%2Fwww.fineract.dev%22]

[~awasum] FYI (and with apologies for my self merge "craze" just now - I needed 
to test this).

FTR the update process inside 
[https://www.fineract.dev|https://www.fineract.dev/] actually takes about 15' 
in total. About 5' are docker build, and the other 10' infrastructure switch 
over.

PS: I'm going to try fixing FINERACT-983 next - that would be really useful, to 
"see" changes rolling out.

> Automatically continuously integrate and deploy ("CI/CD") Fineract develop 
> branch to fineract.dev
> -------------------------------------------------------------------------------------------------
>
>                 Key: FINERACT-970
>                 URL: https://issues.apache.org/jira/browse/FINERACT-970
>             Project: Apache Fineract
>          Issue Type: Improvement
>            Reporter: Michael Vorburger
>            Assignee: Michael Vorburger
>            Priority: Major
>             Fix For: 1.4.0
>
>
> The goal of this issue is to have every pull request merged to the develop 
> branch on https://github.com/apache/fineract/ be as quickly as possible 
> automatically continuously built and deployed ("CI/CD") to (my) 
> https://www.fineract.dev demo server.
> I originally requested INFRA-20143 for this, but meanwhile found a better 
> way. Given that we're in in 2020 not 1990, I was surprised how non-trivial is 
> is to do this in an open yet secure way... I think I'll write up a short 
> personal blog post about it when I'm fully done with this.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to