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

Michael Vorburger commented on FINERACT-1482:
---------------------------------------------

[~ptuomola] ACK. I'll look into making the Docker Hub credentials available as 
GitHub Secrets in FINERACT-1513. Also FYI note FINERACT-1164.

> Docker Hub Build broke with switch from Dockerfile to JIB
> ---------------------------------------------------------
>
>                 Key: FINERACT-1482
>                 URL: https://issues.apache.org/jira/browse/FINERACT-1482
>             Project: Apache Fineract
>          Issue Type: Bug
>          Components: Build
>    Affects Versions: 1.6.0
>            Reporter: Michael Vorburger
>            Assignee: Aleksandar Vidakovic
>            Priority: Blocker
>             Fix For: 1.7.0
>
>
> https://github.com/apache/fineract/commits/develop shows a lot of ugly red 
> crosses since recently.
> I've had a look at why that is so, and one issue (together with another one 
> re. Sonar) is _ci/dockercloud-stage — Your image failed to build_.
> I originally had set this up, see FINERACT-760 (and have access to the Docker 
> Hub Build Logs). 
> This is an impact of https://github.com/apache/fineract/pull/2009 for 
> FINERACT-1469, just like 
> https://github.com/vorburger/www.fineract.dev/issues/11.
> I'm not going to be able to further look much into this myself, but perhaps 
> [~aleks] you would be interested in researching how this could be fixed?
> If we cannot fix it (whether just time wise, or for some technical reasons), 
> then I would propose that we remove 
> https://hub.docker.com/repository/docker/apache/fineract/general. That may 
> warrant some discussion on the mailing list though - last time I looked at 
> the numbers (for ApacheCon) this container had HUGE (!) numbers of downloads.
> A possible alternative could be to open up the container I'm anyway building 
> on https://www.fineract.dev and distribute that one instead?



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Reply via email to