Uploaded image for project: 'Infrastructure'
  1. Infrastructure
  2. INFRA-20143

Authorize Google Cloud Build Install Request



    • Type: Wish
    • Status: Closed
    • Priority: Major
    • Resolution: Not A Problem
    • Fix Version/s: None
    • Component/s: Github
    • Labels:
    • Project:


      Google Cloud cannot read from Docker Hub, but wants its containers to be on its own Google Cloud Container Registry.

      It's easy to set up a Google Cloud Build Trigger which rebuilds container images after every merged Pull Request to GitHub for my personal repos. For example, https://github.com/vorburger/cloudshell ==> gcr.io/vorburger/github.com/vorburger/cloudshell-fedora.

      I'd ideally like to have this work for https://github.com/apache/fineract, but that's a little less trivial than just a click, because of course I don't have the require permission on Apache's GitHub.

      So on https://github.com/apps/google-cloud-build/installations/new I've just clicked on "apache" on "Install Google Cloud Build: Where do you want to install Google Cloud Build?" and it now says "A request to install Google Cloud Build has been submitted on the @apache account."

      If you have received that request, and are comfortable approving that (even limited just to the fineract repo, not entire apache), that would be cool.

      If that is not possible, could we find another way to make this happen?

      I don't actually even have to have this in my own Google Cloud Project. Does the ASF has any Google Cloud projects where a Cloud Build for Fineract could be added to? (As as long as the container is available on [eu.]gcr.io, and set to public, any other Google Cloud projects CAN use such container images.)

      Let me know if I can help (Googler at work, but using this privately).


          Issue Links



              • Assignee:
                gmcdonald Gavin McDonald
                vorburger Michael Vorburger
              • Votes:
                0 Vote for this issue
                1 Start watching this issue


                • Created:
                  Review Date: