ok, i will delete them, even i think you should have the admin rights to do that too.

Wrt sonarcloud analysis which could re-create them again Tristan is looking into it, so need first merge that change.

BR,

Dne 10/16/23 v 08:58 Tibor Zimányi napsal(a):
+1 from me for the deletion in kiegroup.

Best regards,
Tibor

Dňa 16. októbra 2023 8:49:12 SELČ používateľ "Jan Šťastný" 
<jstastn...@apache.org> napísal:
The work is tracked as Apache INFRA ticket
https://issues.apache.org/jira/browse/INFRA-25081 .

It turns out that existing sonarcloud projects under kiegroup organization
are blocking import of the transferred repositories under apache
organization, because of matching groupId:artifactId of maven projects
before and after move.

Trying to change projectKey of the legacy kiegroup projects (in SonarCloud
only) to unblock creation of the new projects in apache DIDN'T help.

The solution is to DELETE legacy projects from the kiegroup organization in
SonarCloud (see linked references in the INFRA ticket).

Given that currently community projects are those in apache organization
and inability to analyze repositories in both organizations at the same
time, I propose we delete the already transferred repository projects from
kiegroup SonarCloud organization, which enables us to recreate in apache.

Regards
Jan



On Mon, 9 Oct 2023 at 14:54, Jan Šťastný <jstastn...@apache.org> wrote:

Hello,

based on instructions in [1] I'll be during this week registering our
transferred repositories under Apache organization [2] in Sonar Cloud.

We're looking for volunteers that would like to manage the KIE projects
there, the reports and of course maintain the integration.
There is a prerequisite in [1], so please make sure you comply with those
when you volunteer:

"Confirm that the Admins have logged into sonarcloud.io with their
ASF-linked GitHub ID."

There are no mentions of limits on the number of admins, though I think
it'd be good to have a reasonably sized group to account for time zone
differences, vacations, etc. But at the same time not to spread the admin
privilege too widely.

Important thing - the admin privilege should be bound to each particular
project, so if you're interested just in a specific ones, make the note of
them.

No need to create projects for not yet transferred repositories (e.g.
kie-tools), we'll handle when that happens.

At the moment, as I plan to work on the task to configure the integration
in the Jenkins CI and will be requesting the projects, I'll put myself as
one of the admins in all the projects.

In case of any objections or questions please reach out to me.

I'll keep the window for volunteering open till Wednesday end of day
(through this mail thread). On Thursday morning I'll be creating the INFRA
ticket(s).

Meanwhile I'll start investigating changes needed in Jenkins pipelines
that would be needed in this regard.

Regards
Jan


[1]
https://cwiki.apache.org/confluence/display/INFRA/SonarCloud+for+ASF+projects
[2] https://sonarcloud.io/organizations/apache/projects

--
Marek Novotny
--

RedHat JBoss Middleware

Red Hat Czech s.r.o.
Purkynova 111
612 45 Brno

Attachment: OpenPGP_0x5381CEF06F213715.asc
Description: OpenPGP public key

Attachment: OpenPGP_signature.asc
Description: OpenPGP digital signature

Reply via email to