vidakovic commented on PR #2270: URL: https://github.com/apache/fineract/pull/2270#issuecomment-1094387603
... as I see it that Sonar token is already defined on an org level for all Apache projects at Github... so no need to create anything else as I see it... same for Docker Hub (which is great... because that was the next thing I needed for the releases)... On Mon, Apr 11, 2022 at 12:21 AM Aleksandar Vidakovic < ***@***.***> wrote: > as for setting secrets on Github: if I'm not mistaken we need to place a > Jira ticket in Apache Infrastructure... these guys are the only ones who > have full access... > > Having said that: we should investigate these Apache Wiki pages > https://cwiki.apache.org/confluence/display/INFRA/Github+Secrets+and+Tokens > > On Sat, Apr 9, 2022 at 1:10 PM Petri Tuomola ***@***.***> > wrote: > >> If I recall @vorburger <https://github.com/vorburger>'s explanation >> correctly, I don't think it's possible to see / configure secrets through >> the Github GUI - what we need to do is to push the secret using the Github >> REST API. I think I have the rights now to create a new SonarQube token but >> I haven't tried pushing any secrets using the REST API, so not sure how >> easy that is... >> >> — >> Reply to this email directly, view it on GitHub >> <https://github.com/apache/fineract/pull/2270#issuecomment-1093917026>, >> or unsubscribe >> <https://github.com/notifications/unsubscribe-auth/AAC4ZL2ZEESJJG3YD7XGGM3VEFQRBANCNFSM5S4LLVAA> >> . >> You are receiving this because you were mentioned.Message ID: >> ***@***.***> >> > -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
