vidakovic commented on PR #2270: URL: https://github.com/apache/fineract/pull/2270#issuecomment-1102828754
aha... now both projects show data... yesterday night one of them was definitely empty... but the one you just sent seems to be the right one (under Apache)... we should be good here. On Tue, Apr 19, 2022 at 5:23 PM Petri Tuomola ***@***.***> wrote: > Hi Aleks > > The one we've been using is this: > > https://sonarcloud.io/project/overview?id=apache_fineract > > I believe this was created by Victor (?) and he granted me access to it a > couple of months ago. I've also granted the access to the account with what > the token was created today - so hopefully the secret token should work > now. > > There's also a project called "Apache Fineract" in Sonarcloud: > > https://sonarcloud.io/project/configuration?id=fineract > > I don't know who has access to this and how it had been configured. If it > already has the token authorized we can of course also use that. > > Should be pretty easy to try accessing either/both from the GitHub action > with the existing secret token. Maybe someone can give this a go? > Alternatively I can try it when I get my machine back… > > Regards > Petri > > > > > On Tue, Apr 19, 2022, 23:05 Aleksandar Vidakovic ***@***.***> > wrote: > > > Hi Petri... I came across this issue coincidentally today... I think we > are > > using the "wrong" project handle on Sonarcloud... because Apache (the > org) > > has prepared them for all of their projects... the one we are using - as > I > > understand it - was created "manually"... but there is another one... > kind > > of the official Sonar project slug for Fineract... if you search for > > Fineract you'll see it immediately... the other thing is empty. > > > > Having said that: by default our Github repo should already contain the > > secret for our "official" Sonar project... just FYI > > > > On Tue, Apr 19, 2022 at 3:02 PM Petri Tuomola ***@***.***> > > wrote: > > > > > Sorry - my dev machine died, so have been without access for a while... > > > > > > However I've just enabled the user gmcdonald with permissions to > execute > > > analysis on our Fineract sonarcloud project. > > > > > > If I understood the wiki page correctly, this should mean we can now > use > > > the prepopulated sonarcloud token secret to trigger the analysis? > > > > > > Regards > > > Petri > > > > > > > > > On Tue, Apr 19, 2022, 20:36 Arnold Gálovics ***@***.***> > > > wrote: > > > > > > > @ptuomola <https://github.com/ptuomola> any luck so far? > > > > > > > > — > > > > Reply to this email directly, view it on GitHub > > > > < > https://github.com/apache/fineract/pull/2270#issuecomment-1102590833 > > >, > > > > or unsubscribe > > > > < > > > > > > https://github.com/notifications/unsubscribe-auth/AASJVCRQUDYG3SPXA3VYONLVF2SEHANCNFSM5S4LLVAA > > > > > > > > . > > > > You are receiving this because you were mentioned.Message ID: > > > > ***@***.***> > > > > > > > > > > — > > > Reply to this email directly, view it on GitHub > > > <https://github.com/apache/fineract/pull/2270#issuecomment-1102625172 > >, > > > or unsubscribe > > > < > > > https://github.com/notifications/unsubscribe-auth/AAC4ZL32C3Z57UPSS65JG5DVF2VF7ANCNFSM5S4LLVAA > > > > > > . > > > You are receiving this because you were mentioned.Message ID: > > > ***@***.***> > > > > > > > — > > Reply to this email directly, view it on GitHub > > <https://github.com/apache/fineract/pull/2270#issuecomment-1102766360>, > > or unsubscribe > > < > https://github.com/notifications/unsubscribe-auth/AASJVCXLTGLLBJVTFW6DYD3VF3DTDANCNFSM5S4LLVAA > > > > . > > You are receiving this because you were mentioned.Message ID: > > ***@***.***> > > > > — > Reply to this email directly, view it on GitHub > <https://github.com/apache/fineract/pull/2270#issuecomment-1102786207>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AAC4ZL6Q7QAX2KD3OI7VK7TVF3FV3ANCNFSM5S4LLVAA> > . > 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]
